[jira] [Commented] (HBASE-6833) [WINDOWS] Java Milisecond precision on Windows

["stack (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458371#comment-13458371 ] 

stack commented on HBASE-6833:
------------------------------

This one is a bit of a bummer.  As you suggest elsewhere, in tests, could user EnvironmentEdge thing that updates each time its called but what happens when you run in production?  You are going to get odd results.

This does bring to the fore how much we presume a forward moving clock (Those spanner time servers with their aerials for GPS and atomic clock cards start to make a bit more sense now) 
                
> [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
>
> 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