Introduce node ID synchronizer and time synchronizer#69
Open
GuoxinL wants to merge 1 commit intobwmarrin:masterfrom
Open
Introduce node ID synchronizer and time synchronizer#69GuoxinL wants to merge 1 commit intobwmarrin:masterfrom
GuoxinL wants to merge 1 commit intobwmarrin:masterfrom
Conversation
GuoxinL
force-pushed
the
feat_allocator_sync
branch
4 times, most recently
from
aa2b6d3 to
54c59e0
Compare
GuoxinL
force-pushed
the
feat_allocator_sync
branch
from
54c59e0 to
0fa63cc
Compare
Author
|
This is the implementation I wrote for it, without any performance loss!!! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Resolve the following issues:
Problem 1: NodeID Collision Prevention NodeID is allocated by a third-party medium, which can resolve NodeID collision issues.
Problem 2: Clock Backward Detection After Restart Since bwmarrin/snowflake is based on Go's monotonic clock, it won't encounter issues during runtime. Clock backward problems only occur during restart initialization, therefore checking for clock backward needs to be performed during initialization.