Operational Enhancements

Version 1 by Reneta Popova
on Apr 30, 2014 09:13.

compared with
Version 2 by Dimitar Manov
on Jul 17, 2014 17:37.

This line was removed.
This word was removed. This word was added.
This line was added.

Changes (8)

View Page History
h1. Background
Ontotext redesigned its cluster architecture to support the case of two or more separate data centres (each with its own master and worker nodes) and to provide asynchronous transactions and master failover. OWLIM GraphDB Enterprise already supports master-worker clusters with Automatic Replication, Load Balancing, and Transaction Logs.

h2. Client Failover Utility
- The Client Utility is provided as a separate OWLIM GraphDB artifact (JAR file);
- There is an additional configuration that lists all available OWLIM GraphDB master nodes;
- The Utility transparently provides failover to the next OWLIM GraphDB master in case of master failure;
- Both asynchronous and synchronous transactions are supported. The synchronous transactions waits until the update is executed on the server and checks if it is successful (otherwise throws an Exception);
- The ClientAPI persists the submitted transaction locally to avoid the case of a possible master failure.

[OWLIM56:Client [GraphDB56:Client Failover Utility]

h2. Smart Replication
- The worker node Status contains a field set to the current size of the storage folder and a fingerprint indicating the state of the data in the node.

[OWLIM56:Smart [GraphDB56:Smart Replication]

h3. Transaction Log Improvements
- Now OWLIM­ GraphDB­ Enterprise is always-writable and can accept update transactions (as opposed to pre-5.6 behaviour where it could transition to ReadOnly mode);
- Update transactions that are accepted for processing will be made asynchronously eventually persistent;
- All accepted transactions are recoverable after a server restart/failure or other.

[OWLIM56:Transaction [GraphDB56:Transaction Log Improvements]