[ 
https://issues.apache.org/jira/browse/KUDU-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18143959#comment-18143959
 ] 

ASF subversion and git services commented on KUDU-3811:
-------------------------------------------------------

Commit 4233503cb75e533a8fd4e77466256d5e5a6bab17 in kudu's branch 
refs/heads/master from Abhishek Chennaka
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=4233503cb ]

KUDU-3811: [tools] Operate on maintenance mode and quiescing per location

Taking a location offline means putting each of its tablet servers into
maintenance mode and quiescing them. Today the operator has to find those
servers with 'kudu tserver list' and run a command for each one, and
missing one is easy.

This adds commands to "kudu cluster location" that take a location
instead of a server:

  kudu cluster location state enter_maintenance <masters> <location>
  kudu cluster location state exit_maintenance <masters> <location>
  kudu cluster location quiesce start <masters> <location>
  kudu cluster location quiesce stop <masters> <location>
  kudu cluster location quiesce status <masters> <location>

Each one asks the master for the location's tablet servers and runs the
existing per-server operation on every one of them. The location must
start with '/', and an unknown one is an error that lists the locations
in use. --dry_run shows the affected servers without changing anything.

All servers are attempted even if some fail. The output shows the result
for each one, and the command fails if any of them did. Both operations
are idempotent, so re-running is the fix. With
--error_if_not_fully_quiesced, "quiesce start" returns Incomplete until
the location has no leaders or scanners left, like "kudu tserver quiesce
start".

Quiescing is lost on restart but maintenance mode is not, so
"exit_maintenance" still has to be run after the location comes back.

Change-Id: Ib9f76aa10428545ad15e3c76a69fe0e0d00b7c0d
Co-Authored-By: Claude Code <[email protected]>
Reviewed-on: https://gerrit.cloudera.org/25241
Reviewed-by: Marton Greber <[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)

Reply via email to