Viewing Windows Commissioning Results

Scenario

After an HBase application is run, you can check the running result through one of the following methods:

• Viewing the IntelliJ IDEA running result.
• Viewing HBase logs.
• Logging in to the HBase WebUI, see More Information > External Interfaces > WebUI.
• Using HBase Shell command, see More Information > External Interfaces > Shell.

Procedure

• The following information is displayed in the running results:

  ...
  2020-09-09 22:11:48,496 INFO  [main] example.TestMain: Entering testCreateTable.
  2020-09-09 22:11:48,894 INFO  [main] example.TestMain: Creating table...
  2020-09-09 22:11:50,545 INFO  [main] example.TestMain: Master: 10-1-131-140,16000,1441784082485
  Number of backup masters: 1
    10-1-131-130,16000,1441784098969
  Number of live region servers: 3
    10-1-131-150,16020,1441784158435
    10-1-131-130,16020,1441784126506
    10-1-131-140,16020,1441784118303
  Number of dead region servers: 0
  Average load: 1.0
  Number of requests: 0
  Number of regions: 3
  Number of regions in transition: 0
  2020-09-09 22:11:50,562 INFO  [main] example.TestMain: Lorg.apache.hadoop.hbase.NamespaceDescriptor;@11c6af6
  2020-09-09 22:11:50,562 INFO  [main] example.TestMain: Table created successfully.
  2020-09-09 22:11:50,563 INFO  [main] example.TestMain: Exiting testCreateTable.
  2020-09-09 22:11:50,563 INFO  [main] example.TestMain: Entering testMultiSplit.
  2020-09-09 22:11:50,630 INFO  [main] example.TestMain: MultiSplit successfully.
  2020-09-09 22:11:50,630 INFO  [main] example.TestMain: Exiting testMultiSplit.
  2020-09-09 22:11:50,630 INFO  [main] example.TestMain: Entering testPut.
  2020-09-09 22:11:51,148 INFO  [main] example.TestMain: Put successfully.
  2020-09-09 22:11:51,148 INFO  [main] example.TestMain: Exiting testPut.
  2020-09-09 22:11:51,148 INFO  [main] example.TestMain: Entering createIndex.
  ...

  

  In the Windows environment, the following exception occurs but does 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 more detailed information can be viewed by changing the log level (DEBUG, INFO, WARN, ERROR, and FATL). 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
  ...