Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node dies if connection to caster fails #44

Open
tiesus opened this issue Sep 21, 2023 · 3 comments
Open

Node dies if connection to caster fails #44

tiesus opened this issue Sep 21, 2023 · 3 comments

Comments

@tiesus
Copy link

tiesus commented Sep 21, 2023

On my machine the node dies, raising an exception if connection to caster fails. From the parameter section, i thought the node should do retries.

@tonynajjar
Copy link

Any update there? We also have the issue. This is probably the culprit

@pondersome
Copy link

For me (on ros2) it does do retries. But it also has a retry limit: reconnect_attempt_max

If you see this line in your output:
Exception: Reconnect was attempted 10 times, but never succeeded

Then you've probably run into the intended functionality. You can change the number of attempts and/or the wait (reconnect_attempt_wait_seconds) to allow servers or the network more time to recover from outages. It doesn't make much sense to retry forever. The exception and node disappearing can signal that something needs to be attended to.

@pondersome
Copy link

To be clear, the retry behavior I described above takes place once you have successfully connected to a server at least once. Then it will retry on intermittent communications outages. It is true that if the connection fails on the first attempt, the exception raises immediately. I don't know if that's a feature or a bug.

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

No branches or pull requests

3 participants