hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6833) [WINDOWS] Java Milisecond precision on Windows
Date Mon, 24 Sep 2012 21:20:07 GMT

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

Lars Hofhansl commented on HBASE-6833:
--------------------------------------

@Ram: HBASE-6784. That's a badly written test. I wrote it :)  I will fix it. No test should
make any (implicit or explicit assumptions about the progression of time).
                
> [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.94.3, 0.96.0
>            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

Mime
View raw message