hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8927) Use nano time instead of mili time everywhere
Date Wed, 17 Jul 2013 18:09:49 GMT

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

stack commented on HBASE-8927:
------------------------------

So, left-shifting the timestamping opens up the two least significant bytes.  We could make
these two bytes be a counter inside the millisecond.  We could give each edit that comes in
during this millisecond its own unique counter.  We should never ever after have clashes (hard
to do 64k ops inside a millisecond).

No-clashing edits would help the distributed log replay case.

Here is max long: http://en.wikipedia.org/wiki/9223372036854775807 which in hex is 0x7FFFFFFFFFFFFFFF.
 If we left shift currentTimeMillis, we can run it up to "Tue Oct 16 19:45:55 PDT 6429" before
it'd rollover.



                
> 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

Mime
View raw message