Adds the given value to the current value.
the value to add
the updated value
Decrements by one the current value.
the updated value
Destroys this object cluster-wide. Clears all resources taken for this object.
Returns the current value of the counter.
the current value of the counter
Adds the given value to the current value.
the value to add
the previous value
Decrements by one the current value.
the previous value
Increments by one the current value.
the previous value
Subtracts the given value from the current value.
the value to add
the previous value
Returns the unique name of this object.
Returns the key of the partition that this DistributedObject is assigned to.
For a partitioned data structure, the returned value will not be null
,
but otherwise undefined
.
Returns the service name for this object.
Increments by one the current value.
the updated value
Resets the observed state by this PN counter. This method may be used
after a method invocation has thrown a ConsistencyLostError
to reset the proxy and to be able to start a new session.
Subtracts the given value from the current value.
the value to subtract
the updated value
Generated using TypeDoc
PN (Positive-Negative) CRDT counter.
The counter supports adding and subtracting values as well as retrieving the current counter value. The counter guarantees that whenever two nodes have received the same set of updates, possibly in a different order, their state is identical, and any conflicting updates are merged automatically. If no new updates are made to the shared state, all nodes that can communicate will eventually have the same data.
The invocation is remote. This may lead to indeterminate state - the update may be applied, but the response has not been received. In this case, the caller will be notified with a
TargetDisconnectedError
The read and write methods provide monotonic read and RYW (read-your-write) guarantees. These guarantees are session guarantees which means that if no replica with the previously observed state is reachable, the session guarantees are lost, and the method invocation will throw a
ConsistencyLostError
. This does not mean that an update is lost. All the updates are part of some replica and will be eventually reflected in the state of all other replicas. This error just means that you cannot observe your own writes because all replicas that contain your updates are currently unreachable. After you have received aConsistencyLostError
, you can either wait for a sufficiently up-to-date replica to become reachable in which case the session can be continued, or you can reset the session by calling thereset()
method. If you have called thereset()
method, a new session is started with the next invocation to a CRDT replica.NOTE: The CRDT state is kept entirely on non-lite (data) members. If there aren't any and the methods here are invoked, they will fail with a
NoDataMemberInClusterError
.