[
https://issues.apache.org/jira/browse/KUDU-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18133393#comment-18133393
]
ASF subversion and git services commented on KUDU-3811:
-------------------------------------------------------
Commit d77843a98e9119ffdae1ad5f6b5a483b5a3bc8e6 in kudu's branch
refs/heads/master from Abhishek Chennaka
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=d77843a98 ]
KUDU-3811 [tools] add 'kudu cluster location check'
Before taking a location (rack, availability zone) offline, an operator
needs to know whether every tablet would keep a quorum. Neither ksck nor
the rebalancer answers that. This adds:
kudu cluster location check <master_addresses> [--location=L]
A location is safe to take offline if, for every tablet, the healthy
voters outside it form a majority of max(replication factor, voters in
config). Taking the larger covers a tablet being re-replicated, which
carries an extra voter, as well as an under-replicated one. Non-voters
and voters on unhealthy tablet servers don't count. Unlike
DetectPlacementPolicyViolations(), tablets are checked regardless of
their health.
Without --location, every location is checked. The action exits non-zero
if any location is unsafe or if --location names an unknown location. It
refuses to run unless every tablet server has a location. Having fewer
than 3 locations only produces a warning.
The result is a snapshot. Tablets with a Raft config change in progress
are listed in a notice, since their placement is about to change. To
detect replacements, ksck's consensus state now records each peer's
REPLACE attribute. Masters are not considered: Kudu does not assign them
locations, so check separately that the location doesn't hold a majority
of them.
location_maintenance-test covers the quorum arithmetic and the detection
of config changes; kudu-tool-test runs the action against multi-location
external mini clusters.
Change-Id: Ibd4cbaa8dab835d4d27270c06b4b0028aab8285b
Co-Authored-By: Claude Code <[email protected]>
Reviewed-on: http://gerrit.cloudera.org:8080/24978
Reviewed-by: Marton Greber <[email protected]>
Reviewed-by: Abhishek Chennaka <[email protected]>
Tested-by: Abhishek Chennaka <[email protected]>
> Enhance existing CLI tooling to operate at location level
> ---------------------------------------------------------
>
> Key: KUDU-3811
> URL: https://issues.apache.org/jira/browse/KUDU-3811
> Project: Kudu
> Issue Type: New Feature
> Reporter: Abhishek Chennaka
> Priority: Major
>
> The existing Kudu CLI tools operate at tablet server level and it would be
> nice to have tooling to be able to operate at location level (if there is
> location awareness configured).
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)