-
Notifications
You must be signed in to change notification settings - Fork 579
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
failure of rptest.tests.partition_movement_test.PartitionMovementTest.test_dynamic
test
#3400
Comments
I saw an older issue around partition movement test, The log message from that older issue looks really similar:
|
@mmaslankaprv Would you please take a look? |
Seen again today:
Note, a different test also failed in the same build, but not sure if it is related: #3277 (comment) |
The last instance of the error was caused by the fact that recovery of the offset translator state took a very long time. Added a PR that will move an offset_translator state together with the partition when it is moved cross cores. |
This test failed recently in https://buildkite.com/vectorized/redpanda/builds/6282#5d68f3e4-9caa-4586-8125-fc24a50d409f |
this failed because of bad log line |
Added configuration replication error to log entries error allow list. The configuration replication may fail when there was a truncation during partition movement operation. This is perfectly fine, configuration update operation should be retried. Fixes: redpanda-data#3400 Signed-off-by: Michal Maslanka <michal@vectorized.io>
Version & Environment
Scheduled nightly run of tests using code from
dev
branch on git commit 80f8a78.In the
debug-clang-amd64
step:https://buildkite.com/vectorized/redpanda/builds/5938#e00fdbdd-8b61-4cef-b0f8-ddb04a138711/1411-4370
What went wrong?
Buildkite job red and logs indicate failure in
rptest.tests.partition_movement_test.PartitionMovementTest.test_dynamic
test.What should have happened instead?
World peace.
How to reproduce the issue?
I haven't tried to reproduce this on my local dev env and there has not been another buildkite build on the
dev
branch yet.Additional information
From the logs:
The text was updated successfully, but these errors were encountered: