Skip to content

fix: Update the coalesced heartbeat logic to send all heartbeats in a…#32

Open
shaj13 wants to merge 1 commit intomainfrom
CoalescedHeartbeat
Open

fix: Update the coalesced heartbeat logic to send all heartbeats in a…#32
shaj13 wants to merge 1 commit intomainfrom
CoalescedHeartbeat

Conversation

@shaj13
Copy link
Owner

@shaj13 shaj13 commented May 8, 2025

… single message per node, instead of one heartbeat per node. This enables support for multiple leaders per node, one for each group, rather than a single leader per node.

@shaj13 shaj13 force-pushed the CoalescedHeartbeat branch 3 times, most recently from b318527 to 8ca8e4b Compare May 9, 2025 16:12
… single message per node, instead of one heartbeat per node. This enables support for multiple leaders per node, one for each group, rather than a single leader per node.
@shaj13 shaj13 force-pushed the CoalescedHeartbeat branch from 8ca8e4b to 202d2f0 Compare May 9, 2025 18:05
@Tochemey
Copy link

@shaj13 please when is this PR going to be merged?

@shaj13
Copy link
Owner Author

shaj13 commented May 10, 2025

@shaj13 please when is this PR going to be merged?

It looks like no, there’s regression with it, considering disabling coalesced heartbeats entirely until we can implement improvements to make it stable again.

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