(feat) Refused requests when node is overload, #138 #144
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.
Motivation:
Fix #138 , refused new requests when the raft node is overload.
Modification:
DisruptorBuilder
to build disruptor, refactor code.tryPublishEvent
to replacepublishEvent
inNodeImpl#apply
andReadOnlyServiceImpl#addRequest
to defense overload requests.TimeoutBlockingWaitStrategy
forLogManagerImpl
disruptor, whendiskQueue
is overload, it will wait at most 10 seconds(setting byRaftOptions#disruptorPublishEventWaitTimeoutSecs
) to put new event. If timed out, the node will be halt.NodeTest#testNodeTaskOverload