[BOOKKEEPER-327] System.currentTimeMillis usage in BookKeeper

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 4.0.0, 4.1.0
• Fix Version/s: 4.2.0, 4.1.1
• Assignee: Uma Maheswara Rao G
• Reporter: Rakesh Radhakrishnan
• Created: 05/Jul/12 18:04
• Updated: 13/Feb/13 15:46
• Resolved: 24/Jul/12 17:03

Description

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.

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)

This jira is raised to discuss whether to use System.nanoTime() instead of System.currentTimeMillis()

Issue Links

• is related to: BOOKKEEPER-330 System.currentTimeMillis usage in Hedwig