While running the IT test from
HBASE-10572, we've noticed that the number of threads jumps to 4K's when CM actions are going on.
Our Nick Dimiduk summarizes the problem quite good:
MultiThreadedReader creates this pool for each HTable:
This comes from the HTable creation
As well the javadoc says Recommended.
This is wrong.
In this issue we can change the LTT sub classes to use the shared connection object and initialize their tables using HConnection.getTable() rather than new HTable().
This is relevant to trunk as well, but there since there is only one outstanding RPC per thread, it is not such a big problem.