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

Propagate timestamps for scans

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.0.1
    • Fix Version/s: 1.2.0
    • Component/s: tserver
    • Labels:
      None
    • Target Version/s:

      Description

      We only propagate timestamps from writes to reads, not between two reads. This leaves the door open to unrepeatable read anomalies:

      If T1, T2 are reads from the same client where T2 starts after the response from T1 is received and neither are assigned timestamps by the client. It might be the case where T2’s observed value actually precedes T1’s value in the row history if T1 and T2 are performed in different servers, as T2 can be assigned a timestamp that is lower than T1.

        Attachments

          Activity

            People

            • Assignee:
              aserbin Alexey Serbin
              Reporter:
              dralves David Alves
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: