Otherwise, the active node waits until a server-side timeout has expired; then aborts the durable write, and duly informs the client that the sturdy write has had an ambiguous outcome. The active node aborts the sturdy write, instructs all replica nodes also to abort the pending write, and informs the client that the durable write has had an ambiguous outcome. If Couchbase Server aborts a durable write, all mutations to lively and duplicate vBuckets in memory and on disk are rolled back, and all copies of the data are reverted to their worth from before the data-write.
- You also can