Murtadha Hubail created ASTERIXDB-2444:
------------------------------------------
Summary: Potential data loss due to clock drift
Key: ASTERIXDB-2444
URL: https://issues.apache.org/jira/browse/ASTERIXDB-2444
Project: Apache AsterixDB
Issue Type: Bug
Components: STO - Storage
Affects Versions: 0.9.4
Reporter: Murtadha Hubail
Assignee: Murtadha Hubail
Fix For: 0.9.5
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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
