osd: Test peering flush batches waiting for the PG history #132
Reference in New Issue
Block a user
No description provided.
Delete Branch "koolkhel/vitastor:peering-flush-minsize-tests"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Two tests for paths of #131 that no test reached:
test_peering_flush_waiting_batch_repeer: EC 2+1, a peering flush batch waits for the history with the holders to be reported, and OSD 3 drops out before the report lands. The batch is dropped without sending any stable or rollback op, and the PG peers again. Without thecontinue_pg()in the drop branch ofon_change_pg_history_hook()the PG stays repeering and the test fails.test_peering_flush_replicated_history: replicated pool, v2 stable on OSD 1 and unstable on OSD 2. OSDs 1 and 2 are in the history before the flush is sent. It fails if replicated pools are skipped when adding the holders.Tested:
osd_test, all pass on current master.Contributor Name
Yury Luneff (MIND Software LLC, https://mindsw.io)
CLA