Comment 9 for bug 1417337

For the specific test case documented in this LP bug, the query will run for a very long time.
The query is not hung, it is just executing slowly.

The following hbase-site.xml settings can be used to test the new TrxRegionEndpoint coprocessor memory usage
code:

  "hbase.transaction.memory.threshold" set to a value less than 100.
  "hbase.transaction.memory.warn.only" default is true, set to false if an error message is desired to end the running query.
  "hbase.transaction.memory.perform.GC" default is false. Set to true if a garbage collection should be initiated to try to
  immediately regain memory for the region server, when the memory threshold has been exceeded.

It has been seen that when the query uses the new memory usage threshold settings, the query can finish,
but may still experience a "Unique Constraint" error. This was noted as being a possible problem in SQL
not associated with this particular LP bug.