Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-430 Consistent Operations
  3. KUDU-398

Snapshot scans should only refuse scans with timestamps whose value is > now+error

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: M4
    • Fix Version/s: Public beta
    • Component/s: tserver
    • Labels:
      None

      Description

      We currently reject a snapshot scan timestamp if it's value if beyond clock->Now(). We should only reject it if it's value is beyond clock->Now() + error, since all values < clock->Now() + error can still be generated by perfectly valid servers.

      We should wait for the timestamp to be safe in all cases.

      Marking this as best effort as this does not make kudu return wrong values, it just makes it a little less tolerant to skew than it could be.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                tlipcon Todd Lipcon
                Reporter:
                dralves David Alves
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: