Examples of RepGroupDB

• com.sleepycat.je.rep.impl.RepGroupDB
  This class is used to encapsulate all access to the rep group data that is present in every replicated JE environment. The rep group data exists primarily to support dynamic group membership. Both read and update access must be done through the APIs provided by this class. The database is simply a representation of the RepGroup. Each entry in the database represents a node in RepGroup; the key is the String node name, and the data is the serialized ReplicationNode. There is a special entry keyed by GROUP_KEY that holds the contents of the RepGroup (excluding the nodes) itself. The database may be modified concurrently by multiple transactions as a master processes requests to update it. It may also be accessed by multiple overlapping transactions as a Replica replays the rep stream. These updates need to be interleaved with operations like getGroup() that create copies of the RepGroup instance. To avoid deadlocks, entries in the database are accessed in order of ascending key. GROUP_KEY in particular is associated with the lowest key value so that it's locked first implicitly as part of any iteration and any other modifications to the database must first lock it before making changes to the group itself. An instance of this class is created as part of a replication node and is retained for the entire lifetime of that node.

Examples of com.sleepycat.je.rep.impl.RepGroupDB

Examples of com.sleepycat.je.rep.impl.RepGroupDB