Skip to content

Address reconnects and protocol stability in backend communication #74

Merged
0mbi merged 2 commits intomasterfrom
fixes
Jul 10, 2025
Merged

Address reconnects and protocol stability in backend communication #74
0mbi merged 2 commits intomasterfrom
fixes

Conversation

@satta
Copy link
Member

@satta satta commented Jul 10, 2025

This PR introduces the following changes:

  • Enable reconnects when the TCP connection to a backend host goes away. Even if the backend service immediately restarts, the client code had no way of reestablishing a new connection.
  • Make sure that fields (e.g. tags, selectors) recently added to the InputObservation struct do not end up in the msgpack messages. The backend is not prepared to see them in the input.

Note: For the reconnects, the intention here is explicitly not to buffer all observations to ensure we don't lose any single one if the backend goes away. That is a much bigger task maybe not to be tackled here. In this case, we simply want to trigger some kind of reconnect to have a working Conn to a backend expected to be back up again, e.g. for short and temporary backend outages like restarts.
This is still much better than never getting a chance to ever reconnect, as it was the case before.

satta added 2 commits July 10, 2025 16:01
The new tag and selector fields must not be included in the msgpack
messages sent towards the backend, as they will not be expected by the
receiving side.
@0mbi
Copy link
Contributor

0mbi commented Jul 10, 2025

as this integration tested already and the changes were explained reasonably, this is accepted.

@0mbi 0mbi merged commit 613277c into master Jul 10, 2025
7 checks passed
@satta satta deleted the fixes branch July 10, 2025 15:24
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

Comments