Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History
The recommendations here are under development and may change before implementation.

Overview

The intent of the OBSERVE operation, as implemented by Couchbase client libraries, is to give developers the ability to observe the status of a key with respect to a specific change.  For example, a developer may want to somehow mutate a document behind the key identified by the string "foo".  Given that a Couchbase cluster is distributed and concurrent and acknowledges the request before the given document, there are situations where the application developer may want to observe whether the specific mutation they made is either:

  1. safely replicated to one or more nodes within the cluster
  2. persisted to the master, or persisted to one or more nodes within the cluster
  3. has been taken into consideration in any indexes

Client API

Java

The Java client library, and it's dependencies, will require changes to return the CAS value through the OperationStatus object.

The basic idea is that given the OperationStatus object (or optionally, multiple OperationStatus objects), an Observer can report on whether or not the operation has been replicated, persisted, or processed for indexing.

OperationFuture<Boolean> setResult = cbc.set("foo", 0, "bar");

if (setResult.get()) {
  Observer watchit = new Observer(setResult.getStatus());
else {
  // do something because the set failed
}

// now that the observer knows what to observe...
ObserveBoolean observeSuccess = watchit.blockForReplication(1); // this will block
if (!observeSuccess) {
  // handle whatever we want to do for this change
  switch (observeSuccess.getStatus()) {
    case OBS_TIMEDOUT:
      // do something for the timeout case
      break;
    case OBS_MODIFIED:
      // key was either modified by someone else or failover occurred
      break;
  }
}

.NET

PHP

Ruby

Recommended Implementation

These recommendations are preliminary, and have not been reviewed.

Given that the item being mutated may be changed at any time by another actor in a deployment, the key idea here is for the client to use the CAS value returned from the mutation operation.  Since the client library knows at all times (though, asynchronously) which node is responsible for the vbucket for a given key, and knows which nodes are slaves for that key, the client library can use stats key as a method of determining what has happened with a key on this given node.

If, for example, application code wanted to check for "foo" with CAS value 12345, it would use STATS KEY against whichever nodes it needs to in order to report the status. This would be done in a loop, with some reasonable backoff (possibly guided by recommended polling times from server stats) until a reasonable or user specified timeout. In this loop, the client would first check to ensure that "foo" 12345 is still the current value on the master for this vbucket. If it is not the current value, it simply returns an error. Assuming it is still the current value, if the application code is simply checking for persistence or index processing, this can be evaluated from the STATS KEY response. If the application code is checking for replication or whether or not the modification has been persisted on multiple nodes, it can then proceed to check any slaves, as identified by the cluster configuration, for status of persistence or replication of "foo" with CAS 12345. At this stage, if it's successful, it returns that response to the application code. If it is not successful, then it waits an interval and loops again. Thus the possible set of return values would be either OBS_SUCCESS, OBS_MODIFIED, or OBS_TIMEDOUT.

Note that the status OBS_MODIFIED does not indicate monotonic forward mutation. For example, in one scenario a failover may have occurred and the item key "foo" being observed may have been reverted to a previous state. This state may even be some value prior to the initial fetch before the application code mutated the value of the document.

Implementation Constraints

OBSERVE is a binary protocol only operation. It could be implemented in ASCII, but that would currently be complicated by the fact that mutation operations do not return the new CAS value in ASCII protocol. Since Couchbase Server uses binary protocol exclusively, we do not implement that currently.

Implementation Questions

q: Is it better to return the values OBS_SUCCESS, OBS_MODIFIED, and OBS_TIMEDOUT instead of true/false and treating the timeout as an exceptional condition? Since OBS_MODIFIED and OBS_TIMEDOUT may effectively require the same error handling, it may be easier to switch on these or return some extended boolean with status.

a: ?

q: Is a C implementation of OBSERVE needed?

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.