Short read protection is a feature added in 3.0 to work around a possible
situation in 2.1 where we could fail to return all rows in a result
The basic premise is that when you read, we ask for the same number of rows
from all of the replicas involved in the query. It’s possible, with the righ
I upgraded a test cluster from 3.11.11 to 4.0.1 today and the following
message started appearing the logs fairly regularly:
INFO [Native-Transport-Requests-1] ShortReadPartitionsProtection.java:153
- Requesting 4951 extra rows from
Full(/10.132.39.33:25469,(8972614703113750908,-91638223484521669
