Skip to content

Conversation

in3xes
Copy link
Contributor

@in3xes in3xes commented Aug 29, 2025

summary:
When the master leader fails over, there’s a short window before the new leader receives heartbeats from tablet servers. During this gap, the master reports uptime=0 for alive tservers, which is misleading (the tserver has been up; the leader just hasn’t learned its uptime yet).

If a tablet server is marked ALIVE but the reported uptime is 0, display the uptime as "unknown" instead of 0. This prevents falsely implying a restart during leader transitions.

…r failover gap

summary:
When the master leader fails over, there’s a short window before the new leader
receives heartbeats from tablet servers. During this gap, the master reports uptime=0
for alive tservers, which is misleading (the tserver has been up; the leader
just hasn’t learned its uptime yet).

If a tablet server is marked ALIVE but the reported uptime is 0, display the
uptime as "unknown" instead of 0. This prevents falsely implying a restart
during leader transitions.
@hari90 hari90 self-requested a review August 30, 2025 16:52
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.

1 participant