Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Process cassandra db configuration upon SIGUSR1 in control-node
During ISSU, V2 control-node needs to be notified to read the cassandra db again as rabbitmq v2 which sends update notifications would not have been up for a small time window. Currently, DB is re-read only if the contrail-control.conf is modified (wrt cassandra db server list, user name, password, etc.). We can do the same re-read process upon SIGUSR1 signal as well. This can come in handy in case control-node is stuck ever with stale config data as well. (as a work around to restarting the control-node process itself) This fix was verified by systest. TODO: Unit tests for this entire config-db re-read is still a pending action item. Change-Id: Ib8b9e39a572cfb688d95e81756372a1f33964d8f Closes-Bug: 1779186
- Loading branch information
1 parent
d211c8d
commit a1b3a99
Showing
3 changed files
with
14 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters