Uploaded image for project: 'Apache AsterixDB'
  1. Apache AsterixDB
  2. ASTERIXDB-2444

Potential data loss due to clock drift

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.9.4
    • Fix Version/s: 0.9.5
    • Component/s: STO - Storage
    • Labels:
      None

      Description

      Currently we use a timestamp based on the current system time to sort the index files to identify the order in which the index components should be searched. If the system clock is changed to a time earlier than the latest index component time and a new component written, it will result in sorting the components in a wrong order. This issue can also be encountered if a current master replica has a system time that is ahead of another replica. If the current master fails and that replica is promoted, it might generate new components with an earlier timestamp. The same issue is applicable in component ids.

      Proposed Fix:
      Avoid using the system clock timestamp and use a simple monotonically increasing sequencer.

        Attachments

          Activity

            People

            • Assignee:
              mhubail Murtadha Makki Al Hubail
              Reporter:
              mhubail Murtadha Makki Al Hubail
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: