All, There is now a publicly available release candidate for Riak 2.9.0 for users to test in their own environment. The release candidate is available to build from source here - https://github.com/basho/riak/tree/riak-2.9.0rc1
There is only one significant change to Riak 2.2.6 for users maintaining existing configuration settings. The release adds the `vnode_soft_limits` feature that aims to reduce high percentile PUT latency, by checking the outstanding work queue for a vnode before selecting it as a coordinator of a PUT. With additional configuration, there are two major features added in riak 2.9.0: - Support for the leveled backend (as an alternative to bitcask or eleveldb), to provide for improved throughput in some use cases and lower tail latency in some use cases - https://github.com/martinsumner/riak_testing_notes/blob/master/Release%202.9%20-%20Choosing%20a%20Backend.md ; - Support for a new anti-entropy mechanism (Tictac AAE) as an alternative for the existing anti-entropy mechanism (to provide both intra-cluster and inter-cluster data repair, with greater flexibility and reliability). The release also adds support for: - The riak_core node_worker_pool - which provides a mechanism for queueing background jobs and queries to control the resource consumed on the node by different queries. No pre-existing features will use the node-worker_pool. - AAE folds which allow for both cluster-wide AAE queries (e.g. produce a merkle tree representing all or a partial range of the cluster data), and administrative queries (e.g. discovering object sizes and sibling counts within the database depending on bucket name, key range and last modified date). AAE folds depend on the Tictac AAE feature being activated. - An interface to request re-replication of an object (where variances between clusters have been discovered). Further details of the release, and the release plan in general can be found here - https://github.com/basho/riak/blob/develop-2.9/doc/Release%202.9%20Series%20-%20Overview.md . It is hoped that there will be a short period of about 1 month before the release candidate will be converted into a formal release. The period will allow for more testing by Riak users, and also there will be further enhanced testing of the new modules with the help of Quviq ( http://www.quviq.com/). There will follow additional releases under the 2.9 banner, targeted at enhancing both new and existing inter-cluster replication features. In parallel to this, work will continue on Release 3.0 which is intended to modernise the OTP/rebar platform used by Riak. Thanks to all those who contributed to the release. Apologies to those who have been kept waiting over the past few months as finalising the changes and completing the testing has dragged on. Regards Martin
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
