[
https://issues.apache.org/jira/browse/HBASE-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HBASE-6833:
---------------------------------
Attachment: NanoSecondPrecisionEnvironmentEdge.java
Attaching a class, which does adjust the milis time by using the more precise
nanoTime() counters. EnvironmentEgde.currentTimeMilis() is how HBase obtains
the time from the system. The default implementation just returns
System.currentTimeMilis().
This is not intended for inclusion, but just for experimentation. This seems to
do a decent job of providing more "incremental" updates to the system milis
clock, but there are a couple of problems, like synchronization, and different
CPUs returning inconsistent nanoTime()'s. Note that even if we inject this to
the test, it still fails.
> [WINDOWS] Java Milisecond precision on Windows
> ----------------------------------------------
>
> Key: HBASE-6833
> URL: https://issues.apache.org/jira/browse/HBASE-6833
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 0.96.0, 0.94.3
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Labels: windows
> Attachments: NanoSecondPrecisionEnvironmentEdge.java
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
