The code trying to wait(block) for repair result to come back in 3.X is below:
in DataResolver class, but this close method is never called and it's also not auto close(RepairMergeListener is not extending from AutoCloseable/CloseableIterator) which means we never wait for repair to finish before returning final result.
The steps to reproduce:
1. create some keyspace/table with RF = 2
2. start 2 nodes using ccm
3. stop node2
4. disable node1 hinted hand off
5. write some data to node1 with consistency level one
6. start node2
7. query some data from node1
This should trigger read repair. I put some log in above close method, and can not see log print put.
So this bug will basically violate "monotonic quorum reads " guarantee.