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

On reads at a snapshot that touch multiple tablets, without the user setting a timestamp, use the timestamp from the first server for following scans

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • Public beta
    • 1.2.0
    • client
    • None

    Description

      When performing a READ_AT_SNAPSHOT, we allow not to set a timestamp, meaning the server will pick a time. If the scan touches multiple tablets, however, we don't set the timestamp assigned to the first scan on the other scans, meaning each scan will have it's own timstamp, which is wrong.

      Attachments

        Issue Links

          is related to

          Sub-task - The sub-task of the issue KUDU-1704 Add a new read mode to perform bounded staleness snapshot reads

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              aserbin Alexey Serbin
              dralves David Alves
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: