mirror of
https://github.com/scylladb/scylladb.git
synced 2026-04-29 20:57:00 +00:00
When creating the reader, the lifecycle policy might return one that was saved on the last page and survived in the cache. This reader might have skipped some fast-forwarding ranges while sitting in the cache. To avoid using a reader reading a stale range (from the read's POV), check its read range and fast forward it if necessary. Fixes: https://github.com/scylladb/scylladb/issues/12916 Closes #12932 * github.com:scylladb/scylladb: readers/multishard: shard_reader: fast-forward created reader to current range readers/multishard: reader_lifecycle_policy: add get_read_range() test/boost/multishard_mutation_query_test: paging: handle range becoming wrapping