[jgroups-users] Coordinator election AND SEQUENCER not working together

I have SEQUENCER protocol in the protocol stack between the STABLE and GMS
protocols. I am using JGroups version 4.0.2. I have implemented membership
change policy as described in 
http://jgroups.org/manual4/index.html#MembershipChangePolicy
<http://jgroups.org/manual4/index.html#MembershipChangePolicy>   to choose
one of the beefy servers as the coordinator. 
When the two concepts are used together I face problems. When a beefy server
joins a cluster that does not already have a beefy server, the new joiner is
added as the first member of the view (custom membership change policy) and
thus becomes the coordinator. But the SEQUENCER protocol does not seem to
realize this change. 

"non-coord dropping forward request from" messages are logged in the new
coordinator. This does not stop and continues forever.

In the protocol stack I have added an entry for CustomMembershipPolicy, 
<pbcast.GMS print_local_addr="true" join_timeout="2000"
                view_bundling="false"
membership_change_policy="c.a.b.c.membership.CustomMembershipPolicy"
max_bundling_time="50"/>

Is this an issue or am I doing it wrong?



--
View this message in context: http://jgroups.1086181.n5.nabble.com/Coordinator-election-AND-SEQUENCER-not-working-together-tp11319.html
Sent from the JGroups - General mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot