mirror of
https://github.com/scylladb/scylladb.git
synced 2026-05-30 03:30:49 +00:00
e6d27ac529
Range queries used to be performed sequentially and the shard performing part of the read was reading state of the merger's memory accounter directly. Now, they may be performed in parallel so it is safer to just pass relevant data by value to the intersted shards so that they are not reading something that another shard is modyfing at the same time. Since query is done in parallel there is a chance of overread. However, the parallelism is high only in sparsely populated tables and that's when the overread is less serious problem.