[jira] [Closed] (BOOKKEEPER-327) System.currentTimeMillis usage in BookKeeper

["Ivan Kelly (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Kelly closed BOOKKEEPER-327.
---------------------------------

    
> System.currentTimeMillis usage in BookKeeper
> --------------------------------------------
>
>                 Key: BOOKKEEPER-327
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-327
>             Project: Bookkeeper
>          Issue Type: Bug
>    Affects Versions: 4.0.0, 4.1.0
>            Reporter: Rakesh R
>            Assignee: Uma Maheswara Rao G
>            Priority: Minor
>             Fix For: 4.2.0, 4.1.1
>
>         Attachments: BOOKKEEPER-327-1.patch, BOOKKEEPER-327-2.patch, BOOKKEEPER-327-Branch4.1.patch, BOOKKEEPER-327.patch, BOOKKEEPER-327.patch
>
>
> The following exception occured in the bookie statistics logic due to the System time changes. In our bookie cluster its running a periodic syncup scripts just to unify the SystemTime in all the machines. This is causing the problem and resulting ArrayIndexOutOfBoundException.
> {code}
> Exception in thread "BookieJournal-3181" java.lang.ArrayIndexOutOfBoundsException: -423
> at org.apache.bookkeeper.proto.BKStats$OpStats.updateLatency(BKStats.java:126)
> at org.apache.bookkeeper.proto.BookieServer.writeComplete(BookieServer.java:655)
> at org.apache.bookkeeper.bookie.Journal.run(Journal.java:507)
> {code}
> This jira is raised to discuss whether to use ??System.nanoTime()?? instead of ??System.currentTimeMillis()??

--
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