Node exists in entity-owner data even after killing the instance

In ovsdb southbound 3 nodes clustering csit,

ovsdb-csit-3node-clustering-only-beryllium

when a node goes down and if i check the entity owner among the other two nodes
the member 1/2/3 which is killed should not exist but its there in the candidates list.

Added more delay of 20s to get the entity owner after killing one node. But still the down node exist in operational ds for entity candidates list.

Here goes the log for the observed behaviour:

KEYWORD ${data} = Utils . Get Data From URI controller@

{controller_index_list}[0], /restconf/operational/entity-owners:entity-owners
Documentation:
Issue a GET request and return the data obtained or on error log the error and fail.
Start / End / Elapsed: 20160118 20:06:49.764 / 20160118 20:06:49.792 / 00:00:00.028
00:00:00.020KEYWORD ${response} = RequestsLibrary . Get Request ${session}, ${uri}, ${headers}
00:00:00.005KEYWORD BuiltIn . Return From Keyword If ${response.status_code} == 200, ${response.text}
Documentation:
Returns from the enclosing user keyword if condition is true.
Start / End / Elapsed: 20160118 20:06:49.787 / 20160118 20:06:49.792 / 00:00:00.005
20:06:49.791 INFO Returning from the enclosing user keyword.
20:06:49.792 INFO ${data} = {"entity-owners":{"entity-type":[{"type":"ovsdb","entity":[{"id":"/network-topology:network-topology/network-topology:topology[network-topology:topology-id='ovsdb:1']/network-topology:node[network-top...
00:00:00.001KEYWORD BuiltIn . Log ${data}
Documentation:
Logs the given message with the given level.
Start / End / Elapsed: 20160118 20:06:49.793 / 20160118 20:06:49.794 / 00:00:00.001
20:06:49.793 INFO {"entity-owners":{"entity-type":[{"type":"ovsdb","entity":[{"id":"/network-topology:network-topology/network-topology:topology[network-topology:topology-id='ovsdb:1']/network-topology:node[network-topology:node-id='ovsdb://uuid/a96ec4e2-c457-4a2c-963c-1e6300210032']","candidate":[{"name":"member-1"},{"name":"member-2"},{"name":"member-3"}],"owner":"member-2"}]},{"type":"ovsdb-southbound-provider","entity":[{"id":"/general-entity:entity[general-entity:name='ovsdb-southbound-provider']","candidate":[{"name":"member-1"},{"name":"member-3"},{"name":"member-2"}],"owner":"member-3"}]}]}}KEYWORD ${data} = Utils . Get Data From URI controller@{controller_index_list}

[0], /restconf/operational/entity-owners:entity-owners
00:00:00.001KEYWORD BuiltIn . Log ${data}
Documentation:
Logs the given message with the given level.
Start / End / Elapsed: 20160118 17:51:08.456 / 20160118 17:51:08.457 / 00:00:00.001
17:51:08.457 INFO {"entity-owners":{"entity-type":[{"type":"ovsdb","entity":[{"id":"/network-topology:network-topology/network-topology:topology[network-topology:topology-id='ovsdb:1']/network-topology:node[network-topology:node-id='ovsdb://uuid/a96ec4e2-c457-4a2c-963c-1e6300210032']","candidate":[

{"name":"member-3"}

,

{"name":"member-1"}

,

{"name":"member-2"}

],"owner":"member-1"}]},{"type":"ovsdb-southbound-provider","entity":[{"id":"/general-entity:entity[general-entity:name='ovsdb-southbound-provider']","candidate":[

{"name":"member-3"}

,

{"name":"member-1"}

,

{"name":"member-2"}

],"owner":"member-1"}]}]}}

Full log is available in below link:

https://jenkins.opendaylight.org/sandbox/job/ovsdb-csit-3node-clustering-only-beryllium/11/robot/report/log.html