2.21-22:Issues with Cassandra Backup/Restore
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
Fix Committed
|
High
|
Sudheendra Rao | ||
R2.20 |
Fix Committed
|
High
|
Sudheendra Rao | ||
R2.21.x |
Fix Committed
|
High
|
Sudheendra Rao | ||
R2.22.x |
Fix Committed
|
High
|
Sudheendra Rao | ||
R3.0 |
Fix Committed
|
High
|
Sudheendra Rao |
Bug Description
I have discussed this with Sudhee, Bhushana. Per Bhushan's suggestion, I am filing this bug for tracking.
Hi Sudhee,
Thanks a lot for your help yesterday. Post our discussion, I spent sometime reviewing backup_restore.py code
I find two problems with the way we backup cassandra :
Issue 1:
In case of local backup, we execute cp –R /var/lib/
SSTable* are deleted/created dynamically. If one file is merged into a new file, the old file gets deleted. When this happens during the cp command, we might try copying files that no longer exist and we finally exit with the errors I pointed out yesterday in the log files.
- Sandeep.
information type: | Proprietary → Public |
Changed in juniperopenstack: | |
importance: | Undecided → High |
assignee: | nobody → Sudheendra Rao (sudheendra-k) |
Changed in juniperopenstack: | |
status: | New → Fix Committed |
Review in progress for https:/ /review. opencontrail. org/18561
Submitter: aswani kumar (<email address hidden>)