Skip to content

Determine lagged controllers using time-based calculation#1543

Merged
MikeEdgar merged 3 commits intostreamshub:mainfrom
MikeEdgar:controller-lag-time
Mar 18, 2025
Merged

Determine lagged controllers using time-based calculation#1543
MikeEdgar merged 3 commits intostreamshub:mainfrom
MikeEdgar:controller-lag-time

Conversation

@MikeEdgar
Copy link
Member

Controllers will be considered as lagging behind the quorum leader based on the difference between their last caught up time and the leader's. When the difference is greater than the quorum fetch timeout, the controller will have a "lagged" status.

@MikeEdgar MikeEdgar added this to the 0.7.0 milestone Mar 17, 2025
Controllers will be considered as lagging behind the quorum leader based
on the difference between their last caught up time and the leader's.
When the difference is greater than the quorum fetch timeout, the
controller will have a "lagged" status.

Signed-off-by: Michael Edgar <medgar@redhat.com>
@MikeEdgar MikeEdgar force-pushed the controller-lag-time branch from 41e4151 to 497fe5d Compare March 18, 2025 11:22
@MikeEdgar MikeEdgar requested a review from a team March 18, 2025 11:33
Signed-off-by: Michael Edgar <medgar@redhat.com>
@MikeEdgar MikeEdgar enabled auto-merge (squash) March 18, 2025 13:51
@sonarqubecloud
Copy link

@MikeEdgar MikeEdgar merged commit aacf072 into streamshub:main Mar 18, 2025
6 of 7 checks passed
@MikeEdgar MikeEdgar deleted the controller-lag-time branch March 18, 2025 14:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants