Common Kudu workflows
Some common Kudu administrative tasks include migrating to multiple Kudu masters,
recovering from a dead Kudu master, removing unwanted masters from a multi-master deployment,
adding or updating hostnames of the masters within the clusters without aliases, monitoring
the health of the cluster using ksck, changing directory configuration, recovering from disk
failures, bringing a tablet that has lost a majority of replicas back online, rebuilding a
Kudu filesystem layout, taking physical backups of an entire node, and scale the storage for
the Kudu master and the tablet severs in the cloud.
Migrating to multiple Kudu masters Recovering from a dead Kudu master in a multi-master deployment Removing Kudu masters from a multi-master deployment Changing master hostnames Best practices when adding new tablet servers Monitoring cluster health with ksck kudu CLI includes a tool called ksck that can be used for gathering information about the state of a Kudu cluster, including checking its health. ksck will identify issues such as under-replicated tablets, unreachable tablet servers, or tablets without a leader. Orchestrating a rolling restart with no downtime Changing directory configuration --fs_data_dirs Gflag configuration and restarting the server. Data is striped across data directories, and when a new data directory is added, new data will be striped across the union of the old and new directories. Recovering from disk failure Directory configuration topic.Recovering from full disks Bringing a tablet that has lost a majority of replicas back online ksck), they should be recovered instead if possible.Rebuilding a Kudu filesystem layout Physical backups of an entire node Scaling storage on Kudu master and tablet servers in the cloud 