You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Mitch Barnett (JIRA)" <ji...@apache.org> on 2019/04/09 17:20:00 UTC
[jira] [Assigned] (KUDU-2448) Document how to temporarily
decommission/shutdown a tablet server
[ https://issues.apache.org/jira/browse/KUDU-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mitch Barnett reassigned KUDU-2448:
-----------------------------------
Assignee: Mitch Barnett
> 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
>
> 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
(v7.6.3#76005)