Additional Administration Considerations for Apache Kudu

This page describes supplementary administration practices, including master hostname changes, tablet server best practices, directory configurations, disk recovery, rebalancing, and decommissioning. It also highlights integration requirements and availability guidelines.

Key Administration References

For detailed procedures, refer to the Apache Kudu Administration documentation:

• Changing the Master Hostnames

• Best Practices When Adding New Tablet Servers

• Changing Directory Configurations

• Recovering from Disk Failure

• Running the Tablet Rebalancing Tool

• Decommissioning or Permanently Removing a Tablet Server from a Cluster

Additional Information

Impala Integration

• A new Impala Mpack is required to integrate with Kudu.

• The Mpack includes the necessary flags to enable Impala-Kudu integration.

Master Node Availability

• It is recommended to have at least three master nodes to ensure fault tolerance.

• If the cluster drops below two master nodes, schedule a maintenance window to add another master.

Configuration Management

• You do not need to manually enter the master and tablet server addresses into kudu-master-env or kudu-tablet-env.

• Ambari automatically populates this configuration.

• Manual entry is only required if you want to override Ambari’s automatic configuration for master servers.