Timeweb Cloud adds OpenSearch 3.7 and observable database operations

Timeweb Cloud has updated its managed database service with OpenSearch 3.7.0. The provider has also changed database and user operations to expose an explicit asynchronous state.

Why the operation state matters

The API previously confirmed that a task had been accepted, but a delay made it difficult to tell whether the change had actually completed. A user or database now carries a status that separates processing from a successfully applied result.

This is more than a control-panel detail. Automation must not interpret acceptance of a command as the resource’s final state. After creating, deleting, or changing an object, a client should poll for a terminal status, enforce a timeout, and process failure separately.

Checks before moving to OpenSearch 3.7

• Index, analyser, template, and plugin compatibility.
• Backup and restore behaviour.
• Memory consumption and garbage-collection timing.
• Search and aggregation results on a representative data copy.
• Compatibility of existing clients and libraries.
• A rollback path if query output or latency changes.

For asynchronous operations, store both task and resource identifiers, use bounded polling, define a final timeout, and avoid repeating a mutating command until the earlier result is known. Otherwise, a temporary panel delay can produce duplicate actions.

What the changelog does not specify

The official entry confirms version availability and the new status model. It does not provide an operation-specific SLA, maximum completion time, complete plugin matrix, or the upgrade path for existing clusters. These details need documentation review and a test instance.

Source: the official Timeweb Cloud changelog dated 18 August 2026.