BUG-8392 RpcRegistry has it's buckets populated by unreachable nodes 84/56784/3
authorTomas Cere <tcere@cisco.com>
Wed, 10 May 2017 12:04:37 +0000 (14:04 +0200)
committerTomas Cere <tcere@cisco.com>
Wed, 10 May 2017 13:06:02 +0000 (13:06 +0000)
commite222d9f4a5b6957853cff9cf73987e6ce0ae3b24
tree4724e7183be006056b2f443416d4fc4bbdb454dd
parente83057f284dc3c9bf84063a47a18bb41a26aebf3
BUG-8392 RpcRegistry has it's buckets populated by unreachable nodes

In a situation when a member(f.ex member2) is isolated and the rpc registrations
are removed from the node(member1) we can still have our bucket store populated
by buckets from the remaining node(member-3) which might not have received
the memberUnreachable message yet leadig to stale routing of an rpc to
member-2.
This patch adds bucket filtering based on the currently present peers
so that we only accept Buckets that we can see.

Change-Id: I92c1e063f4754aca829bd73df4518f859e1d8497
Signed-off-by: Tomas Cere <tcere@cisco.com>
opendaylight/md-sal/sal-remoterpc-connector/src/main/java/org/opendaylight/controller/remote/rpc/registry/gossip/Gossiper.java

©2013 OpenDaylight, A Linux Foundation Collaborative Project. All Rights Reserved.
OpenDaylight is a registered trademark of The OpenDaylight Project, Inc.
Linux Foundation and OpenDaylight are registered trademarks of the Linux Foundation.
Linux is a registered trademark of Linus Torvalds.