-
Type:
Bug
-
Resolution: Works as Designed
-
Priority:
Major - P3
-
None
-
Affects Version/s: 3.6.3
-
Component/s: Replication
-
None
-
ALL
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
In 3.6, we do not prevent majority reads at a timestamp between the common point and reaching minValid. The data is inconsistent during this period of time, so we should not service reads that use timestamps during this period. This is only a problem for rollback via refetch.