[
https://issues.apache.org/jira/browse/HBASE-8927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706444#comment-13706444
]
Sergey Shelukhin commented on HBASE-8927:
-----------------------------------------
[~stack] agree on first, but for general use (like e.g. measuring ttl
expiration, how long things took for normal ops, and such) having a complex ts
generation seems sillier ;) I'd do nano on case by case basis for
non-timestamps.
[~enis] hardware clocks do go back on faulty motherboards... also Windows does
adjust the clock backwards from the time server if it drifts forwards. Linux
ntpd can also do that unless explicitly disabled.
[~eclark] but does it matter across rows?
> Use nano time instead of mili time everywhere
> ---------------------------------------------
>
> Key: HBASE-8927
> URL: https://issues.apache.org/jira/browse/HBASE-8927
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Attachments: 8927.txt
>
>
> Less collisions and we are paying the price of a long anyways so might as
> well fill it.
--
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
