BUG 2817 : Handle ServerRemoved message in Shard/ShardManager 04/29804/5
authorMoiz Raja <moraja@cisco.com>
Tue, 17 Nov 2015 03:03:40 +0000 (19:03 -0800)
committerGerrit Code Review <gerrit@opendaylight.org>
Thu, 19 Nov 2015 00:20:40 +0000 (00:20 +0000)
commit4680d02510a884b3a893345f423cedcc8c5af0f4
tree25e4beba135805002bf87f9ce72df06ff7a5aab1
parent2f523ae2a9be64bf53d1962fd9ddefe47617ff28
BUG 2817 : Handle ServerRemoved message in Shard/ShardManager

When a server is removed and the new ServerConfiguration is
replicated and consensus has been reached on it the RaftActor
sends a ServerReoved message to the Replica which has just been
removed.

This ServerRemoved messsage is received by the Shard and it
forwards the message to the ShardManager. The ShardManager
then removes the replica from it's persistent list.

Change-Id: I9252ab9d9768b549915d8cccf46f102127d97945
Signed-off-by: Moiz Raja <moraja@cisco.com>
opendaylight/md-sal/sal-distributed-datastore/src/main/java/org/opendaylight/controller/cluster/datastore/Shard.java
opendaylight/md-sal/sal-distributed-datastore/src/main/java/org/opendaylight/controller/cluster/datastore/ShardManager.java
opendaylight/md-sal/sal-distributed-datastore/src/test/java/org/opendaylight/controller/cluster/datastore/ShardManagerTest.java
opendaylight/md-sal/sal-distributed-datastore/src/test/java/org/opendaylight/controller/cluster/datastore/ShardTest.java