GraphDB-Enterprise Release Notes

compared with
Version 9 by Reneta Popova
on Sep 09, 2014 14:28.

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

Changes (29)

View Page History
{panel}major.minor.build_number{panel}

e.g. 5.3.5928 where the major number is 5, the minor number is 3 and the build number is 5928. Releases with the same major and minor version numbers do not contain any new features, the features. The only difference is that releases with later build numbers contain fixes for bugs discovered since the previous release. New or significantly changed features are released with a higher major or minor version number.

h1. GraphDB version 6.0-RC3 (build 7914)


h2. Fixes:
* The plugins were moved to <webapps>/openrdf-sesame/WEB-INF/classes/plugins
* Running GraphDB under embedded Tomcat failed with NPE (because of non existing webapps/ folder)

* The plugins were moved to <webapps>/openrdf-sesame/WEB-INF/classes/plugins;
* Running GraphDB under embedded Tomcat failed with NPE (because of non existing webapps/ folder).

h1. GraphDB version 6.0-RC2 (build 7892)

h2. Improvements:
* Added mini LDBC Semantic Publishing Benchmark (http://ldbc.eu) into benchmark/ldbc-spb folder in the distribution
* The plugins are now in <webapps>/openrdf-sesame/plugins folder. Lucene plugin is enabled by default. This could be overwritten by the
-Dregister-external-plugins option
* Minor rearrangement of the files in the main distribution folder (all .pie files are put into rules/ subfolder, the scripts into scripts/ subfolder)

* Added mini LDBC Semantic Publishing Benchmark ([http://ldbc.eu]) into benchmark/ldbc-spb folder in the distribution;
* The plugins are now in <webapps>/openrdf-sesame/plugins folder. Lucene plugin is enabled by default. This could be overwritten by the \-Dregister-external-plugins option;
* Minor rearrangement of the files in the main distribution folder (all .pie files are put into rules/ subfolder, the scripts into scripts/ subfolder).

h2. Fixes:
* Fixed issue with the default/evaluation license
* Fixed issue with the LoadRDF tool

* Fixed issue with the default/evaluation license;
* Fixed issue with the LoadRDF tool.


h1. GraphDB version 6.0 (build 7784)
GraphDB 6.0 is a re-branded Owlim 5.6 version. The differences are given to the last stable Owlim 5.4 release.

GraphDB 6.0 is a re-branded Owlim 5.6 version. The differences are given in the last stable Owlim 5.4 release.

h2. Improvements:
* High Availability Cluster
* Faster writes in SAFE Mode (OWLIM 5.5 improvement which lead to incompatible binary formats between 5.4 and 5.5+)
* LoadRDF tool for faster bulk loading of data; speeds ~100KSt/s and above, without inference
* Explain Plan like functionality
* LVM-based Backup and Replication

* High Availability Cluster;
* Fast writes in SAFE Mode (OWLIM 5.5 improvement, which lead to incompatible binary formats between 5.4 and 5.5+);
* LoadRDF tool for faster bulk loading of data; speeds \~100KSt/s and above, without inference;
* Explain Plan like functionality;
* LVM-based Backup and Replication.

h2. Fixes:

* Databases created with one setting of the "entity-id-size" parameter (32 vs 40-bit) and opened with another setting, would crash in versions prior to 6.0. Now an exception is thrown and the repository is not initialized.


h2. Improvements:

* [OWLIM56:LVM-based [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).
* [OWLIM56: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. Can It can deploy on AWS and local instances. Supports docker format. Allows for the running of acceptance, stress and load tests on the deployed clusters. Optionally creates Nagios configuration for the deployed cluster
* LoadRDF tool - a tool for faster bulk loading of data has been merged from 5.5 branch
* Merged EntityPool Reverse Cache from 5.5 - will speedup larger updates (100\+ statements)

h2. Fixes:

* All AcceptanceTests that were previosly failing are now fixed
** Improved communication between master and worker nodes with respect to the above tests

h1. Version 5.6 beta 3 (build 7659)

Fixes:
* cluster - empty worker initialization
** Tx log initialization

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)

Fixes:
- 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

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 improved. 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
- IMPROVEMENT: Better TransactionLog support (see: [OWLIM56:Transaction Log Improvements]) - the updates are synchronized between all masters in all data centers
- IMPROVEMENT: [OWLIM56:Smart Replication]
- IMPROVEMENT: Protocol backward 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 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 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 update processing in 5.4 where the response is created after last of the available nodes complete it\[OWLIM-1483\]