GraphDB-Enterprise Release Notes

compared with
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (38)

View Page History

* [LVM-based Backup and Replication|OWLIM56:LVM-based Backup and Replication] \- Backup can optionally be based on the LVM Shadow Volume Copy - which makes it faster and the worker is released a few seconds after the backup is started (ported from 5.4).
* [New Cluster Test (cluster deployment and test tool)|OWLIM56:New Cluster Test (cluster deployment and test tool)] \- a tool for automated deployment and testing of clusters of various sizes. It can Can deploy on AWS and local instances. Supports docker format. Allows for the running of acceptance, stress and load tests to be run on the deployed clusters. Optionally, creates Nagios configuration for the deployed cluster.
* LoadRDF tool - a tool for a faster bulk loading of data, which has been merged from 5.5 branch.
* Merged EntityPool Reverse Cache from 5.5 - will speedup larger speeds up large updates (100\+ statements).

h2. Fixes:

* All AcceptanceTests that were previously failing are now fixed:
** Improved communication between master and worker nodes with respect to the above tests acceptance tests;
** Worker thread: fixed out-of-sync handling upon initialisation;
* Improved logging and in particular logging, fixed the skip of some stacktraces by the JVM in particular;
* Initializsation of 5.6 worker from 5.4 image now skip "entityIdSize" and InferencerCRC from

h1. Version 5.6 beta 3 (build 7659)

* cluster - empty worker initialization initialisation;
* worker - initial update handling;
* log sync: 10s wait between idle rounds (network bandwidth optimization) optimisation);
* Tx log: initialization bug fixed
* Tx log: initialisation bug fixed;
* update might fail when replication is in progress;
* miscellaneous bug fixes in the cluster utils (deployment/status) and proxies restart;
* detailed logging:
** replication cluster worker events;
** HTTP client stats;
** Tx log initialization initialisation.

Known issues:
* AcceptanceTests failing: W4, M4, MW3, MW7, MW8;
* the new/experimental LVM backup/restore feature is not yet ported from 5.4 (and thus MW10 and MW11 Acceptance Tests are not implemented, because they are based on it).

h1. Version 5.6 beta 2 (build 7523)

- updated AcceptanceTests in the MastersAndWorkers section;
- replication start/wait methods improved;
- several fixes to the TxLog protocol;
- fixed replication logic to delete the Worker repo, only when the remote worker confirms the replication;
- additional sanity checks added to the Master-to-Master and Master-to-Worker synchronization synchronisation;
- improved logging, incl. "SPLITBRAIN" events logged both to logs and to JMX.

Known issues:
- some MW\* tests with the forced replication fail randomly, but rarely - related to the Proxy tool.

h1. Version 5.6 beta 1 (build 7368)

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 Enterprise already supported Master-Worker clusters with Automatic Replication, Load Balancing and Transaction Logs, but in this release these components were are improved. Owlim OWLIM 5.6 is based on 5.5 and inherits its write performance improvements.
- IMPROVEMENT: [OWLIM56:Client Failover Utility] which can be configured to fallback to the next master if the first master becomes unavailable
* [OWLIM56:Client Failover Utility], which can be configured to fallback to the next master, if the first master becomes unavailable;
- IMPROVEMENT: * Better TransactionLog support (see: [OWLIM56:Transaction Log Improvements]) - the updates are synchronizsed between all masters in all data centers;
- IMPROVEMENT: All Masters are now Read/Write
- IMPROVEMENT: [OWLIM56:Smart Replication]
* All Masters are now Read/Write;
* [OWLIM56:Smart Replication];
- IMPROVEMENT: * Protocol backwards compatibility - the ability to upgrade the OWLIM cluster without downtime, following the OWLIM Upgrade Procedure.;
- IMPROVEMENT: * [External Plug-ins|OWLIM56:External Plug-ins] \- the plugins in OWLIM are moved into a separate plugin directory, and now could can be upgraded/maintained separately.

h2. Known issues:

- CONCERN: * Transaction consistency concern. In the new cluster, the Master responds to an update from a client as soon as the test node completes it.

In a single threaded scenario the next query could can be evaluated on a node that still has either not received it or not completed it which could lead to inconsistency from the client point of view. This deviates from the update processing in 5.4, where the response is created after the last of the available nodes completes it\[OWLIM-1483\].