-
Notifications
You must be signed in to change notification settings - Fork 589
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI Failure (search victim assert) in ControllerEraseTest.test_erase_controller_log
#8217
Comments
@VadimPlh : can you please help with this? |
ProblemTest delete last segment from disk and after startup node should signal that The problem is that the test isn't waiting for a node's last_applied for the controller to advance far enough before restarting it. FixChatted with @jcsp and @mmaslankaprv |
The test selected segment which contained not applied data (dirty) after the segment was deleted there was no inconsistency in the data. |
Wait for all victim node records to be applied. If a victim node contains some of the records that were not applied or about to be truncated the test should wait before selecting segments to trim as in the case if segment contains only dirty records removing it will not cause inconsistency. Fixes: redpanda-data#8217 Signed-off-by: Michal Maslanka <[email protected]>
Controller erasure test is supposed to validate if there is a mismatch between the last appended entry in kvstore and controller max offset. In order for the test to work correctly we must wait for all the messages to be committed as we only delete the last segment that contains a single message (new replicated configuration). In order to make the test reliable change the condition to wait for the applied offset on the node where controller log is going to be removed to be equal to the leader dirty offset. Fixes: redpanda-data#8217 Signed-off-by: Michal Maslanka <[email protected]> (cherry picked from commit 57fb4c0)
Controller erasure test is supposed to validate if there is a mismatch between the last appended entry in kvstore and controller max offset. In order for the test to work correctly we must wait for all the messages to be committed as we only delete the last segment that contains a single message (new replicated configuration). In order to make the test reliable change the condition to wait for the applied offset on the node where controller log is going to be removed to be equal to the leader dirty offset. Fixes: redpanda-data#8217 Signed-off-by: Michal Maslanka <[email protected]> (cherry picked from commit 57fb4c0)
Controller erasure test is supposed to validate if there is a mismatch between the last appended entry in kvstore and controller max offset. In order for the test to work correctly we must wait for all the messages to be committed as we only delete the last segment that contains a single message (new replicated configuration). In order to make the test reliable change the condition to wait for the applied offset on the node where controller log is going to be removed to be equal to the leader dirty offset. Fixes: redpanda-data#8217 Signed-off-by: Michal Maslanka <[email protected]> (cherry picked from commit 57fb4c0)
Controller erasure test is supposed to validate if there is a mismatch between the last appended entry in kvstore and controller max offset. In order for the test to work correctly we must wait for all the messages to be committed as we only delete the last segment that contains a single message (new replicated configuration). In order to make the test reliable change the condition to wait for the applied offset on the node where controller log is going to be removed to be equal to the leader dirty offset. Fixes: redpanda-data#8217 Signed-off-by: Michal Maslanka <[email protected]> (cherry picked from commit 57fb4c0)
Controller erasure test is supposed to validate if there is a mismatch between the last appended entry in kvstore and controller max offset. In order for the test to work correctly we must wait for all the messages to be committed as we only delete the last segment that contains a single message (new replicated configuration). In order to make the test reliable change the condition to wait for the applied offset on the node where controller log is going to be removed to be equal to the leader dirty offset. Fixes: redpanda-data#8217 Signed-off-by: Michal Maslanka <[email protected]> (cherry picked from commit 57fb4c0)
Wait for all victim node records to be applied. If a victim node contains some of the records that were not applied or about to be truncated the test should wait before selecting segments to trim as in the case if segment contains only dirty records removing it will not cause inconsistency. Fixes: redpanda-data#8217 Signed-off-by: Michal Maslanka <[email protected]> (cherry picked from commit 47a2c05)
When testing partial deletion the test selects a segment to remove from controller log. Before deleting the segment but after it was selected it may be accounted in the controller snapshot. Disabled controller snapshot to prevent the test racing with snapshot creation. Fixes: redpanda-data#8217 Signed-off-by: Michal Maslanka <[email protected]>
When testing partial deletion the test selects a segment to remove from controller log. Before deleting the segment but after it was selected it may be accounted in the controller snapshot. Disabled controller snapshot to prevent the test racing with snapshot creation. Fixes: redpanda-data#8217 Signed-off-by: Michal Maslanka <[email protected]> (cherry picked from commit f978777)
When testing partial deletion the test selects a segment to remove from controller log. Before deleting the segment but after it was selected it may be accounted in the controller snapshot. Disabled controller snapshot to prevent the test racing with snapshot creation. Fixes: redpanda-data#8217 Signed-off-by: Michal Maslanka <[email protected]> (cherry picked from commit f978777)
https://buildkite.com/redpanda/redpanda/builds/21131#0185aa14-d78f-4589-83fe-33c79c1b9029
The text was updated successfully, but these errors were encountered: