-
Notifications
You must be signed in to change notification settings - Fork 577
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
kafka/server: Improve kafka::map_topic_error_code #2422
kafka/server: Improve kafka::map_topic_error_code #2422
Conversation
Signed-off-by: Ben Pope <ben@vectorized.io>
This change looks good to me, modulo the discussion about NotController above. @BenPope when you update this, please can you close this one and re-open against |
Instead of returning `unknown_server_error`, return `not_controller` This is a retriable error code, with metadata refresh. Fixes redpanda-data#2406 Signed-off-by: Ben Pope <ben@vectorized.io>
When a new `cluster::errc` is added, a compilation error will force consideration of the mapping here. Signed-off-by: Ben Pope <ben@vectorized.io>
Signed-off-by: Ben Pope <ben@vectorized.io>
24fed00
to
7c7c503
Compare
I moved the base to |
Closed in favour of #2428 since buildkite didn't spot that I changed the base to dev. |
Note: Let's wait for this to bake on
test-staging
for a bit before merge.Cover letter
Map
cluster::errc::no_leader_controller
tokafka::error_code::not_controller
so that the error is retriable, with metadata refresh.Fixes #2406
Also:
vlog
cluster::errc
is introduced.See #2425 for followup work.
Changes in force-push
cluster::errc::not_controller
Release notes
Release note: redpanda/kafka: leader_not_available is now a retriable error.