-
Notifications
You must be signed in to change notification settings - Fork 599
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
Feature cleanup #24055
Feature cleanup #24055
Conversation
/dt |
001d8d6
to
4ae8c7b
Compare
00d1de9
to
b763ec7
Compare
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/57783#0193076e-5362-4916-ad29-22271c770799:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/57783#0193076e-5364-47b5-b206-449540932c26:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/57783#0193076e-535c-4938-99dc-325d973c05d8:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/57783#01930788-4f8d-4ffb-99c1-7694a65bc261:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/57783#01930788-4f90-4180-b3f7-5a7b6204b707:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/57783#01930788-4f8c-4667-98a0-2c2994c04648:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/57955#01932106-407e-4144-bb6f-399068f79303:
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/58373#01934b13-e2b4-4de3-9ea2-922f6599cb72:
|
Retry command for Build#57783please wait until all jobs are finished before running the slash command
|
b763ec7
to
d1d15c5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My understanding:
features::earliest_version
is alreadyv23_3_1
application::post_start_tasks
checks against earliest- So we don't need to assert anywhere on any of these features
I basically approve this PR, but think we should wait until the branch of v24.3 to merge it.
d1d15c5
to
b7abd1b
Compare
@BenPope thanks for your review
I'm not sure I understand why. |
ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/57955#01932103-0b84-4b8b-b377-816084c35acd |
"serde_raft_0", | ||
"license", | ||
"raft_improved_configuration", | ||
"raftless_node_status", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you're now missing "transaction_ga",
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no, it is already there
I agree, it should be safe. You may want to fix some subtasks of CORE-2754 |
Retry command for Build#57955please wait until all jobs are finished before running the slash command
|
the failure is https://redpandadata.atlassian.net/issues/CORE-7833 |
/ci-repeat 1 |
2 similar comments
/ci-repeat 1 |
/ci-repeat 1 |
/dt |
@@ -299,20 +299,18 @@ ss::future<> feature_manager::maybe_log_license_check_info() { | |||
// Shutting down - next iteration will drop out |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
redpanda/admin/server, cluster/feature_manager: do not check feature:…
…:license
as it is on everywhere now
Commit message subject should not wrap. Body should stand on its own.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oops, sorry, I thought the limit was 80, but it's 50 for header and 72 for body, will fix
lgtm, afte Noah's suggestion is applied |
b7abd1b
to
009a3d2
Compare
do we need to backport it v24.3.x ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
c/rm_stm: remove feature::transaction_ga check
this commit removes an assertion but doesn't explain anything. seems like you may be missing a statement in the commit message.
That's feature::rpc_transport_unknown_errc. On boostrap, when a node doesn't have all RPC services available yet, it may return non-retriable errors on RPC requests. There is already a mechanism thatmakes RPC return a retriable error on unknown method if some services are still yet to start. Unfortunately, this mechanism requires all nodes to support it, so we check for a feature flag before we use it. As a result, non-retriable errors still can sneak through, as checking the feature flag across all nodes takes some time. This is to remove the feature flag check, as current and previous versions definitely support it.
as it is always on in all suppoted versions now
feature::raft_improved_configuration is always on in all suppoted versions now
as it is always on in all suppoted versions now
feature::raftless_node_status is always on in all suppoted versions now
feature::node_id_assignment is always on in all suppoted versions now
feature::replication_factor_change is always on in all suppoted versions
feature::ephemeral_secrets is always on in all suppoted versions now
feature::seeds_driven_bootstrap_capable is always on in all suppoted versions now
it is always on in all suppoted versions now
feature::partition_move_revert_cancel is always on in all suppoted versions now
it is always on in all suppoted versions now
009a3d2
to
40e7af3
Compare
Retry command for Build#58373please wait until all jobs are finished before running the slash command
|
/dt |
/backport v24.3.x |
I mostly started it because of the first commit to always get retriable RPC response when not all services started.
The rest is just cleanup for the sake of removing unneeded code.
Backports Required
Release Notes