Viewing the HBase Application Commissioning Result

Scenario

After HBase application running is complete, you can obtain the running status by viewing the running result or HBase logs.

Procedure

• If the application running is successful, the following information is displayed.

  ...
  2020-01-09 10:43:49,338 INFO  [main] examples.HBaseExample: Entering dropTable.
  2020-01-09 10:43:49,341 INFO  [main] client.HBaseAdmin: Started disable of hbase_sample_table
  2020-01-09 10:43:50,080 INFO  [main] client.HBaseAdmin: Operation: DISABLE, Table Name: default:hbase_sample_table, procId: 41 completed
  2020-01-09 10:43:50,550 INFO  [main] client.HBaseAdmin: Operation: DELETE, Table Name: default:hbase_sample_table, procId: 43 completed
  2020-01-09 10:43:50,550 INFO  [main] examples.HBaseExample: Drop table successfully.
  2020-01-09 10:43:50,550 INFO  [main] examples.HBaseExample: Exiting dropTable.
  2020-01-09 10:43:50,550 INFO  [main] client.ConnectionImplementation: Closing master protocol: MasterService
  2020-01-09 10:43:50,556 INFO  [main] examples.TestMain: -----------finish to test HBase API------------------- 

  

  The following exception may occur when the sample code is running in the Windows OS, but it will not affect services.

  java.io.IOException: Could not locate executable null\bin\winutils.exe in the Hadoop binaries.

• Log description

  The log level is INFO by default and you can view more detailed information by changing the log level, such as DEBUG, INFO, WARN, ERROR, and FATAL. You can modify the log4j.properties file to change log levels, for example:

  hbase.root.logger=INFO,console
  log4j.logger.org.apache.zookeeper=INFO
  #log4j.logger.org.apache.hadoop.fs.FSNamesystem=DEBUG
  log4j.logger.org.apache.hadoop.hbase=INFO
  # Make these two classes DEBUG-level. Make them DEBUG to see more zk debug.
  log4j.logger.org.apache.hadoop.hbase.zookeeper.ZKUtil=INFO
  log4j.logger.org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher=INFO