[jgroups-users] JGroups 4.0.13.Final
Questions/problems related to using JGroups <[email protected]> Tue, 24 Jul 2018 10:00:58 +0200
| Newsgroups | gmane.comp.java.javagroups.general |
|---|---|
| Message-ID | <mailman.34712.1532419274.978.javagroups-users@lists.sourceforge.net> |
Morning! I just released 4.0.13.Final; the most interesting issues solved were: - CENTRAL_LOCK2 [1]: new implementation of the lock protocol. On coord crash/leave, the new coord asks all members for their existing locks and pending lock requests. This eliminates the need for backup(s) of lock info. - Changed the way a coord leaves gracefully [2]: instead of creating the last view itself, the leaving coord asks the next-in-line to create and install it. This has the advantage that the new coord can retransmit the view (if lost) as it's stil alive and simplifies code, because the path for graceful leave and crash is now the same. - Reactive style of merging [3]: when using MERGE3 and TCP, a merge could be only partial and multiple merge rounds would be needed, increasing the total time for a complete merge. This was changed by providing a new event which implements a reactive style of discovery by invoking a callback every time a discovery response is received. For a list of all issues see [4]. Cheers, [1] https://issues.jboss.org/browse/JGRP-2249 [2] https://issues.jboss.org/browse/JGRP-2277 [3] https://issues.jboss.org/browse/JGRP-2281 [4] https://issues.jboss.org/projects/JGRP/versions/12337835 -- Bela Ban | http://www.jgroups.org ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot