Start line:  
End line:  

Snippet Preview

Snippet HTML Code

Stack Overflow Questions
  /*-
   * See the file LICENSE for redistribution information.
   *
   * Copyright (c) 2002, 2013 Oracle and/or its affiliates.  All rights reserved.
   *
   */
  
  package com.sleepycat.je.rep;
  
 
This exception is thrown by a Replica to indicate it could not meet the consistency requirements as defined by the ReplicaConsistencyPolicy in effect for the transaction, within the allowed timeout period.

A Replica will typically keep current with its Master. However, network problems, excessive load on the Master, or Replica, may prevent the Replica from keeping up and the Replica may fall further behind than is permitted by its consistency policy. If the Replica cannot catch up in the time defined by its ReplicaConsistencyPolicy, it will throw this exception from the Environment.beginTransaction method, thus preventing the transaction from accessing data that does not meet its consistency requirements.

If this exception is encountered frequently, it indicates that the consistency policy requirements are too strict and cannot be met routinely given the load being placed on the system and the hardware resources that are available to service the load. The exception may also indicate that there is a network related issue that is preventing the Replica from communicating with the master and keeping up with the replication stream.

The application can choose to retry the transaction, until the underlying system problem has been resolved. Or it can try relaxing the consistency constraints, or choose the NoConsistencyRequiredPolicy so that the constraints can be satisfied more easily. For example, in a href= "{@docRoot/../ReplicationGuide/lifecycle.html#twonode"> two node replication group}, if the primary goes down, the application may want the secondary node to continue to service read requests, and will lower the consistency requirement on that node in order to maintain read availability.

See also:
com.sleepycat.je.ReplicaConsistencyPolicy
Managing Consistency
 
     private static final long serialVersionUID = 1;
 

Hidden:
For internal use only.
 
                                        consistencyPolicy,
                                        boolean unknownMaster) {
         /* No need to set abortOnly, beginTransaction will fail. */
         super(null /*locker*/false /*abortOnly*/,
               "Unable to achieve consistency despite waiting for " +
               consistencyPolicy.getTimeout(.) + " ms." +
               (unknownMaster ?
                " The node is not currently in contact with a master." :
                ""),
               null /*cause*/);
         this. = consistencyPolicy;
     }
 
     public ReplicaConsistencyException(String message,
                                        ReplicaConsistencyPolicy
                                        consistencyPolicy) {
         /* No need to set abortOnly, beginTransaction will fail. */
         super(null /*locker*/false /*abortOnly*/,
               message,
               null /*cause*/);
         this. = consistencyPolicy;
     }

    
For internal use only.

Hidden:
 
     private ReplicaConsistencyException(String message,
                                         ReplicaConsistencyException cause) {
         super(messagecause);
         this. = cause.consistencyPolicy;
     }

    
For internal use only.

Hidden:
 
     @Override
     public OperationFailureException wrapSelf(String msg) {
        return new ReplicaConsistencyException(msgthis);
    }

    
Returns the Replica consistency policy that could not be satisfied.

Returns:
the Replica consistency policy
        return  ;
    }
New to GrepCode? Check out our FAQ X