Comment 10 for bug 1417337

This is what's seen on the v0519 build when executing x2. This bug report was originally created hoping that work can be done from the SQL side to ease such resource pressure, or to deal with it internally by disabling the index during the data loading and re-enabling it back after the loading is done. But there is no plan to do so currently. Instead, it was recommended that the user create the index only after the data has been loaded.

We will close this report as 'Won't Fix' for now.

>>sh date;
Wed May 20 18:55:44 UTC 2015
>>execute x2;

*** ERROR[8448] Unable to access Hbase interface. Call to ExpHbaseInterface::rowExists returned error HBASE_ACCESS_ERROR(-705). Cause:
java.io.IOException: java.io.IOException: TrxRegionEndpoint coprocessor: checkAndPut - java.lang.RuntimeException: org.apache.hadoop.hbase.regionserver.Leases$LeaseStillHeldException
org.apache.hadoop.hbase.client.transactional.TransactionalTable.checkAndPut(TransactionalTable.java:450)
org.apache.hadoop.hbase.client.transactional.RMInterface.checkAndPut(RMInterface.java:347)
org.trafodion.sql.HBaseAccess.HTableClient.putRow(HTableClient.java:929)
org.trafodion.sql.HBaseAccess.HTableClient.checkAndInsertRow(HTableClient.java:1005)
.

--- 0 row(s) inserted.
>>sh date;
Wed May 20 20:56:44 UTC 2015