[
https://issues.apache.org/jira/browse/KUDU-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke resolved KUDU-2448.
-------------------------------
Fix Version/s: 1.11.0
Resolution: Fixed
Resolved now that we have maintenance mode.
https://kudu.apache.org/docs/administration.html#minimizing_cluster_disruption_during_temporary_single_ts_downtime
> Document how to temporarily decommission/shutdown a tablet server
> -----------------------------------------------------------------
>
> Key: KUDU-2448
> URL: https://issues.apache.org/jira/browse/KUDU-2448
> Project: Kudu
> Issue Type: Task
> Components: documentation
> Reporter: Grant Henke
> Assignee: Mitch Barnett
> Priority: Major
> Labels: beginner
> Fix For: 1.11.0
>
>
> I have been asked a few times the "best" way to shutdown a tablet server or
> master server for common maintenance like an OS upgrade, disk swap, etc. Even
> if it's straightforward, perhaps adding a section to the documentation
> [here|https://kudu.apache.org/docs/administration.html#_common_kudu_workflows]
> we make users confident about their process.
> I have heard of increasing the
> [kudu-master_follower_unavailable_considered_failed_sec|https://kudu.apache.org/docs/configuration_reference.html#kudu-master_follower_unavailable_considered_failed_sec]
> configuration to avoid re-replication during these short planned outages.
> Perhaps that tip could be added if appropriate.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
