Move tick check to after heartbeat for avoiding the impact of other node heartbeat. fix #1719 #1738
+3
−3
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.
In the past, fluentd supports only UDP heartbeat and it uses async check between fluentd nodes.
So if previous node takes longer time for heartbeat, it doesn't affect elapsed time.
On the other hand, recent fluentd supports TCP heartbeat and it uses sync check via tcp connection.
So if previous node takes longer time, it affects elapsed time for current node and it causes misjudgment.
To avoid the problem, elapsed time calculation should be done after heartbeat.