EdColeman commented on issue #3075: URL: https://github.com/apache/accumulo/issues/3075#issuecomment-1332884790
Depending on the timer precision 1 millisecond may not be enough to guarantee the timestamp changes - it will depend on the underlying clock and currentTimeMillis() likely does not use nano seconds (that's why its faster) The sleep "may" work because of the additional overhead - but using a larger value (say > 65 millis) may force it to always be a new timestamp. The 65 millis sticks in my head as being the worst case precision of a windows timer, but that may not be accurate anymore, or it was a different value. But there is a precision difference between the reported milliseconds and the underlying clock so 1 millisecond may not guarantee a different value. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
