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.

Sign up for GitHub

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

Jump to bottom

[Conductor] transition error #299

Open

dwlee opened this issue Jun 8, 2015 · 1 comment

Collaborator

dwlee commented Jun 8, 2015

If client is marked as BAD due to the slow network( >200ms latency), it cannot come back to be available unless the client goes out and rejoin.

There should be a way to transit from BAD to AVAILABLE.

Pending -> Uninvited
This lines marks clients as bad if it cannot find services within 100ms.

Joining -> Available
This lines also marks clients as bad if it cannot find services within 100ms.

dwlee mentioned this issue

Concert usage Issues in slow network environment robotics-in-concert/rocon#36

Open

5 tasks

Collaborator

jihoonl commented Jun 9, 2015

It needs two patches to resolve the issue.

increase wait_for_service timeout to use robot's to be robust in slow network environment([conductor] rosparam for service timeout #300)
Create transition from BAD to Pending. So the client can recover back from BAD without leaving and rejoining.

jihoonl mentioned this issue

[conductor] rosparam for service timeout #300

Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment