Description
Emilio Lahr-Vivaz writes on the user mailing list:
I've found that scanning lots of non-sequential single-row ranges is pretty slow in accumulo. Your best approach is probably to create an index table on whatever you are originally trying to query (assuming those 10000 ids came from some other query).
Specifically, the use case is fetching many single items, all of which are present (so, bloom filters aren't going to help).
Since this is one of the use cases Accumulo was designed to handle, look into actual performance and figure out if there are any obvious bottlenecks.
Attachments
Issue Links
- duplicates
-
ACCUMULO-3710 Scanning with many singleton ranges crashes tserver
-
- Resolved
-