Support Questions
Find answers, ask questions, and share your expertise
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

How to avoid InterruptedIOException in Hbase put operation

How to avoid InterruptedIOException in Hbase put operation

New Contributor

While putting data in Hbase, using the HTable.put method, I'll end up with the below exception occasionally. But the data has been actually written to Hbase when I checked the get operation for that particular rowkey.

For the same time I have searched for the logs in both HMaster and HRegionservers to identify the issue. But unable to find that.

Please help to fine tune Hbase Configurations in order to avoid InterruptedIOException


Exception: #17209, interrupted. currentNumberOfTask=1 at org.apache.hadoop.hbase.client.AsyncProcess.waitForMaximumCurrentTasks( at org.apache.hadoop.hbase.client.AsyncProcess.waitForMaximumCurrentTasks( at org.apache.hadoop.hbase.client.AsyncProcess.waitForAllPreviousOpsAndReset( at org.apache.hadoop.hbase.client.BufferedMutatorImpl.backgroundFlushCommits( at org.apache.hadoop.hbase.client.BufferedMutatorImpl.flush( at org.apache.hadoop.hbase.client.HTable.flushCommits( at org.apache.hadoop.hbase.client.HTable.put(


Please help to solve it

The same exception has been faced by someone . But in that thread, there is no explanation about which are configurations need to be checked in order to avoid it!topic/nosql-databases/UxfrmWl_ZnM