If you have "dense" tablets where you're scanning for multiple Ranges which are all co-located on the same tablet, I believe that those multiple Ranges that lie on a single tablet (within one ScanSession) will be binned together and then run sequentially, so you wouldn't see server-side concurrency there.
tserver.readahead.concurrent.max controls the size of a thread pool on the tserver used to service scans and batch scans On Tue, Feb 11, 2014 at 2:59 PM, Roshan Punnoose <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext