Summary: imm: improve cascade delete [#2667]
Review request for Ticket(s): 2667
Peer Reviewer(s): *** Ravi, Hans, Anders, Lennart, Zoran
Pull request to: *** LIST THE PERSON WITH PUSH ACCESS HERE ***
Affected branch(es): develop
Development branch: ticket-2667
Base revision: 30b70f4a56ab0225d3ade3c
When an object is deleted, and the object has children, the delete meesage is
sent for each deleted object to PBE. Since there are a lot of messages in the
cascade delete from IMMND to PBE at once, there is a limitation that the cascade
delete should not be done on object that contains more than 1
Hi Hans,
Thanks for reviewing the patch. I've made the necessary changes based on
your comments before having the patch pushed.
Regards,
Nguyen
On 3/9/2018 4:58 PM, Hans Nordebäck wrote:
ack, review only. Some comments below marked with [HansN].
/Thanks HansN
On 03/06/2018 07:39 AM, Nguye
Hi Gary,
Ack, with some comments
1) The current example that you have given is for static etcd cluster
configuration
In the Cloud environment, the Cluster will be growing and shrinking
dynamically, accordingly we might need to add or remove new nodes to the etcd
cluster
It will be better