fix potential overflow of requestId #124
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| return System.currentTimeMillis() * 100000 + offset.incrementAndGet(); | ||
| long currentTime = System.currentTimeMillis(); | ||
| long count = offset.incrementAndGet(); | ||
| if(count == MAX_COUNT_PER_MILLIS){ |
There was a problem hiding this comment.
此处需要改为count >= MAX_COUNT_PER_MILLIS
|
LGTM |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
issue description is here.
a long value representing requestId composes of two parts:
if offset count equals to 2^20, it will be reset to 0 and the last offset reset time is recorded. If during one millis second, offset count hit max again, it will wait until this millis second passes.