You can examine /jmx : http://search-hadoop.com/m/YGbb3E2a71UVLBK&subj=Re+HBase+Count+Rows+in+Regions+and+Region+Servers
Looks like your load consists of both write and read. Have you turned on bucket cache ? http://hbase.apache.org/book.html#offheap.blockcache On Fri, Sep 9, 2016 at 1:58 PM, marjana <mivko...@us.ibm.com> wrote: > all are defaults: > <name>hbase.hregion.memstore.block.multiplier</name><value>4</value> > <name>hbase.hregion.memstore.mslab.enabled</name><value>true</value> > <name>hbase.hregion.memstore.flush.size</name><value>134217728</value> > > Not sure where to see hot spotting (don't have Ambari on this cluster). > > > > -- > View this message in context: http://apache-hbase.679495.n3. > nabble.com/copyTable-mapreduce-job-failing-with-ScannerTimeoutException- > tp4082544p4082569.html > Sent from the HBase User mailing list archive at Nabble.com. >
