Re: [jgroups-users] jgroups - callRemoteMethodsWithFuture blocks on coordinator crash
Questions/problems related to using JGroups <[email protected]> Thu, 31 Aug 2017 09:25:10 +0200
| Newsgroups | gmane.comp.java.javagroups.general |
|---|---|
| Message-ID | <mailman.14739.1504164317.7456.javagroups-users@lists.sourceforge.net> |
This is the expected behavior. Consider a similar case where you're making a blocking RPC on all cluster members. If one of the members crash during the RPC and is thus not able to send a response, the caller will block until either a timeout occurs (if the call is time-bounded) or failure detection kicks in and marks the response of the crashed member as faulty, so that the call can return. You could try bounding your blocking RPCs or make them async if the app allows that... On 31/08/17 09:08, Questions/problems related to using JGroups wrote: > The problem is with SEQUENCER in the stack, > callRemoteMethodsWithFuture() is blocking until the message is forwarded > to the coordinator. Coordinator loss during such situations make the > call blocking until a view change occurs. This is something I want to > avoid in my application. When I tested without SEQUENCER in the stack > the call does not block until a view change but removing SEQUENCER is > not an option in my application. If this is the expected behavior then > how does one overcome this delay in processing? > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > _______________________________________________ > javagroups-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/javagroups-users > -- 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