Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.89.20100621
-
None
Description
I'd like to brainstorm some ideas on how we can prioritize reads and writes to META above reads and writes to other tables. I've noticed that if the regionserver hosting META is under heavy load, then lots of other operations take much longer than they should. For example, I'm currently running 120 threads of YCSB across 3 client nodes hitting a 5-node cluster. Doing a full scan of META (only 600 rows) takes upwards of 30 seconds in the shell, since all of the handler threads are tied up and there's a long RPC queue.
Attachments
Attachments
Issue Links
- is related to
-
HBASE-2964 Deadlock when RS tries to RPC to itself inside SplitTransaction
- Closed
-
HADOOP-6952 Support sending priority RPC
- Open
-
HDFS-599 Improve Namenode robustness by prioritizing datanode heartbeats over client requests
- Closed
-
HBASE-2981 Improve consistency of performance during heavy load
- Closed