Help Center > > User Guide> MRS Cluster Component Operation Guide> Using Kudu> Using Kudu from Scratch

Using Kudu from Scratch

Updated at: Apr 28, 2020 GMT+08:00

Kudu is a columnar storage manager developed for the Apache Hadoop platform. Kudu shares the common technical properties of Hadoop ecosystem applications. It is horizontally scalable and supports highly available operations.

Background

After an MRS cluster is successfully created, the original client is stored in the /opt/client directory on all nodes in the cluster by default. Before using the client, download and update the client configuration file, and ensure that the active management node of MRS Manager is available.

Procedure

  1. Download the client configuration file.

    1. Log in to the MRS management console. In the navigation tree on the left, choose Clusters > Active Clusters and click the cluster name.
    2. Click the Components tab.
    3. Click Download Client.

      Set Client Type to Only configuration files, Save Path to Server, and click OK to generate the client configuration file. The generated file is saved in the /tmp/MRS-client directory on the active management node by default.

      Figure 1 Downloading only configuration files

  2. Use the MRS client on any Core node in the cluster. For details, see Using the client on a Core node.
  3. Run the Kudu command line tool.

    Run the command line tool of the Kudu component to view help information.

    kudu -h

    The command output is as follows:

    Usage: ./kudu <command> [<args>]
     
    <command> can be one of the following:
             cluster   Operate on a Kudu cluster
            diagnose   Diagnostic tools for Kudu servers and clusters
                  fs   Operate on a local Kudu filesystem
                 hms   Operate on remote Hive Metastores
       local_replica   Operate on local tablet replicas via the local filesystem
              master   Operate on a Kudu Master
                 pbc   Operate on PBC (protobuf container) files
                perf   Measure the performance of a Kudu cluster
      remote_replica   Operate on remote tablet replicas on a Kudu Tablet Server
               table   Operate on Kudu tables
              tablet   Operate on remote Kudu tablets
                test   Various test actions
             tserver   Operate on a Kudu Tablet Server
                 wal   Operate on WAL (write-ahead log) files

    The Kudu command line tool does not support DDL and DML operations, but provides the refined query function for the cluster, master, tserver, fs, and table parameters.

    Common operations:

    • Check the tables in the current cluster.

      ./kudu table list KuduMaster instance IP1:7051, KuduMaster instance IP2:7051, KuduMaster instance IP3:7051

    • Query the configurations of the KuduMaster instance of the Kudu service.

      ./kudu master get_flags KuduMaster instance IP:7051

    • Query the schema of a table.

      ./kudu table describe KuduMaster instance IP1:7051, KuduMaster instance IP2:7051, KuduMaster instance IP3:7051 tablename

    • Delete a table.

      ./kudu table delete KuduMaster instance IP1:7051, KuduMaster instance IP2:7051, KuduMaster instance IP3:7051 tablename

      To obtain the IP address of the KuduMaster instance, choose Components > Kudu > Instances on the cluster details page.

  4. Delete the cluster.

    For details, see Terminating a Cluster in the User Guide.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel