You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/14 18:02:00 UTC
[jira] [Resolved] (HBASE-6833) [WINDOWS] Java Milisecond precision on Windows
[ https://issues.apache.org/jira/browse/HBASE-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Kyle Purtell resolved HBASE-6833.
----------------------------------------
Assignee: (was: Enis Soztutar)
Resolution: Abandoned
> [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.95.2
> Reporter: Enis Soztutar
> Priority: Major
> 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 was sent by Atlassian Jira
(v8.20.7#820007)