Re: Why may "tablet read ahead" take long time? (was: Profile a (batch) scan)

2019-01-17 Thread Keith Turner
Maxim, Below are some pointers into the code you asked about. Let me know if you have any questions about the code. The following tablet server code puts a task on a thread pool for a batch scan.

Re: Why may "tablet read ahead" take long time? (was: Profile a (batch) scan)

2019-01-16 Thread Maxim Kolchin
Hi Adam, Thank you for the list! In my case, there is only one client which runs a single query which I'm tracing, so I hope the thread pools have free threads. I'd like to look at the code which runs in the scope of the "table read ahead". Do you know where I should look at? I tried to search

Re: Why may "tablet read ahead" take long time? (was: Profile a (batch) scan)

2019-01-15 Thread Adam Fuchs
Hi Maxim, What you're seeing is an artifact of the threading model that Accumulo uses. When you launch a query, Accumulo tablet servers will coordinate RPCs via Thrift in one thread pool (which grows unbounded) and queue up scans (rfile lookups, decryption/decompression, iterators, etc.) in