Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-399

Snapshot scans without an assigned timestamp should select a safe one instead of waiting for clock->Now() to be safe

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Won't Fix
    • M4
    • None
    • tserver
    • None

    Description

      When the client doesn't specify a snapshot timestamp we currently wait for clock_>Now() to be safe. We instead should use the lastest safe timestamp, thus avoiding a wait().

      Attachments

        Activity

          People

            dralves David Alves
            dralves David Alves
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: