DAOS-19591 container: avoid false sluggish EC boundary warning - #19015
Merged
Conversation
A new container service leader loads the EC aggregation boundary from rdb, which can be far behind the current time. The first comparison of the tracked epoch against the newly reported minimum then shows a large gap and triggers a bogus "Sluggish EC boundary reporting" warning. Record the time when the leader starts tracking a container and only warn when the leader has been tracking it at least as long as the observed epoch gap, so a gap that predates this leader is not reported as a stall. Signed-off-by: Xuezhao Liu <xuezhao.liu@hpe.com>
|
Ticket title is 'Aurora daos_user: engine printing continuously in log "cont_agg_eph_sync() 66e9ae82/2416cc43: Sluggish EC boundary report from rank 117, 165933 Seconds." ' |
wangshilong
reviewed
Sep 4, 2026
wangshilong
approved these changes
Sep 4, 2026
liw
approved these changes
Sep 8, 2026
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
4 participants
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.
A new container service leader loads the EC aggregation boundary from rdb, which can be far behind the current time. The first comparison of the tracked epoch against the newly reported minimum then shows a large gap and triggers a bogus "Sluggish EC boundary reporting" warning.
Record the time when the leader starts tracking a container and only warn when the leader has been tracking it at least as long as the observed epoch gap, so a gap that predates this leader is not reported as a stall.
Steps for the author:
After all prior steps are complete: