Transaction Log Improvements

Skip to end of metadata
Go to start of metadata
Search
This documentation is NOT for the latest version of GraphDB.

Latest version - GraphDB 7.1

GraphDB Documentation

Next versions

GraphDB 6.2
GraphDB 6.3
GraphDB 6.4
GraphDB 6.5
GraphDB 6.6
GraphDB 7.0
GraphDB 7.1

Previous versions

OWLIM 5.4
OWLIM 5.3
OWLIM 5.2
OWLIM 5.1
OWLIM 5.0
OWLIM 4.4
OWLIM 4.3
OWLIM 4.2
OWLIM 4.1
OWLIM 4.0

Design of the TxLog sync protocol

GraphDB HA Cluster - Transaction Log Synchronization Protocol.docx

Known Issues

  • Spurious failures (updates failing on one worker and succeeding on another) can cause the DC-s to go out of sync (workers within the same DC will still be in sync);
  • Dead workers will be undetected until an update is executed.

Notes:

  • Each synchronizing master must have the following properties set:
    • Node ID (cluster config: node-id; JMX bean: NodeID) that is unique and consistent throughout the whole cluster, across DC-s;
    • master URL (cluster config: master-url; JMX bean: masterURL) set to its Sesame protocol URL.
  • All synchronized peers must be configured in a master node's config with the following properties:
    • ID (cluster config: peer.<n>.id) equal to the peer's own unique Node ID;
    • URL (cluster config: peer.<n>.url) equal to the peer's Sesame protocol URL.

The properties can be set directly in the cluster config, or given as arguments to the JMX bean or addSyncPeer(). A master node will not synchronize with unknown (i.e. unconfigured) peers.

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