[HBASE-6833] [WINDOWS] Java Milisecond precision on Windows

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Abandoned
• Affects Version/s: 0.94.3, 0.95.2
• Labels: windows
• Assignee: Unassigned
• Reporter: Enis Soztutar
• Created: 19/Sep/12 01:14
• Updated: 14/Jun/22 18:01
• Resolved: 14/Jun/22 18:01

Description

HBase relies on the system clock obtained by System.currentTimeMilis() to supply the version, if it is not provided by the client in Put's and Delete's. At HBASE-6832 and HBASE-6826, we discovered that on some platforms, the milis clock might not be updated every milisecond, which might cause unexpected behavior. We also did some preliminary analysis there.
In this issue, we can further discuss and inspect whether it is a problem for main target platforms and if so what can be done.

Issue Links

• is related to: HBASE-6832 [WINDOWS] Tests should use explicit timestamp for Puts, and not rely on implicit RS timing
• is related to: HBASE-8927 Use nano time instead of mili time everywhere
• is related to: HBASE-14070 Hybrid Logical Clocks for HBase