[ https://issues.apache.org/jira/browse/HBASE-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458930#comment-13458930 ]
ramkrishna.s.vasudevan commented on HBASE-6833: ----------------------------------------------- I recently raised an issue HBASE-6784 again a testcase failure just because the Puts got the same timestamp and the test was failing randomly. Based on the discussion over here i can provide a patch for that HBASe-6784. > [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