Chapter 4. Kudu Administration
The administrator’s dream is to work with a system that is resilient, fault tolerant, simple to scale, monitor, and adapt as requirements change. Even better is a system that is self-healing, shows warning signs early, and lets the administrator go to sleep knowing that the system will run in a predictable way.
Kudu is designed and built from the ground up to be fault tolerant, scalable, and resilient and provides administrators with the means to see what’s happening in the system, both through available APIs and visually through a web user interface (UI) and a handy command-line interface (CLI).
In this chapter, we get you started as an administrator so that you can hit the ground running. Installation options are covered in previous chapters, so we begin here by looking at planning for your Kudu deployment and then walk through some of the most common and useful administrator tasks.
Planning for Kudu
Let’s begin by taking time to understand how to appropriately plan for a Kudu deployment.
Note
Kudu is fully open source and made available with documentation, downloads, overviews, and more provided at http://kudu.apache.org/. However, Kudu might also be included in various Hadoop distributions. If going with a distribution, always refer to the documentation provided by the vendor as deployment strategies may vary.
Kudu can be installed as its very own cluster with no dependency on any other components; however, we expect that many installations ...