Cloudera Enterprise 5.15.x | Other versions

Configuring the HBase Scanner Heartbeat

A scanner heartbeat check enforces a time limit on the execution of scan RPC requests. This helps prevent scans from taking too long and causing a timeout at the client.

When the server receives a scan RPC request, a time limit is calculated to be half of the smaller of two values: hbase.client.scanner.timeout.period and hbase.rpc.timeout (which both default to 60000 milliseconds, or one minute). When the time limit is reached, the server returns the results it has accumulated up to that point. This result set may be empty. If your usage pattern includes that scans will take longer than a minute, you can increase these values.

To make sure the timeout period is not too short, you can configure hbase.cells.scanned.per.heartbeat.check to a minimum number of cells that must be scanned before a timeout check occurs. The default value is 10000. A smaller value causes timeout checks to occur more often.

Configure the Scanner Heartbeat Using Cloudera Manager

Minimum Required Role: Configurator (also provided by Cluster Administrator, Full Administrator)

  1. Go to the HBase service.
  2. Click the Configuration tab.
  3. Select HBase or HBase Service-Wide.
  4. Locate the RPC Timeout property by typing its name in the Search box, and edit the property.
  5. Locate the HBase RegionServer Lease Period property by typing its name in the Search box, and edit the property.
  6. Click Save Changes to commit the changes.
  7. Restart the role.
  8. Restart the service.

Configure the Scanner Heartbeat Using the Command Line

  1. Edit hbase-site.xml and add the following properties, modifying the values as needed. 
    <property>
  <name>hbase.rpc.timeout</name>
  <value>60000</value>
</property>
<property>
  <name>hbase.client.scanner.timeout.period</name>
  <value>60000</value>
</property>
<property>
  <name>hbase.cells.scanned.per.heartbeat.check</name>
  <value>10000</value>
</property>
  2. Distribute the modified hbase-site.xml to all your cluster hosts and restart the HBase master and RegionServer processes for the change to take effect.
Page generated May 18, 2018.