My cluster is 3-replica nodes of 1.0.3, each node has its zero, and yes the error gives out exact values for readTs and minTs.
After some hours, during the night some queries started being successful (it’s a bit intermittent right now), it seems that readTs was stuck for a very long time and I guess the cluster slowly caught up to the minTs? Is this something that makes sense? Sometimes I do another query and get the error again, with a slightly greater readTs than before. Could this be attributed to one node becoming slower perhaps?
Regardless, it may be useful to debug this either way. If you use my p folder data locally, you can see that the readTs is forever at a very low number while minTs is much greater, thus I can’t perform the query.
I’m going to DM you a zip of the p and w folders of one of the cluster nodes.