Possible to communicate with new master without process restart?

asked 2011-11-11 05:53:07 -0600

Asomerville
2743 ●74 ●99 ●133 http://www.resquared.com/

updated 2011-11-11 05:53:54 -0600

Often when debugging, a launch which was responsible for the original Master goes down. When this happens things that were connected that stay up are unable to communicate with the new Master when it comes up.

Is there a way around this?
Is it perhaps possible to reinitialize the node so that it connects to a new Master?

edit retag flag offensive close merge delete

add a comment

0

answered 2011-11-11 06:27:38 -0600

Asomerville
2743 ●74 ●99 ●133 http://www.resquared.com/

In rospython it seems it's possible (if dangerous?) to do the following:

rospy.client._init_node_args = None
rospy.init_node( "node_name" )

I'm not sure if it's wise but it seems to work.

edit flag offensive delete link

Comments

That is not a valid workaround.

Pablo Iñigo Blasco ( 2020-02-14 12:16:59 -0600 )edit

add a comment

4

answered 2011-11-11 06:06:11 -0600

bhaskara
1479 ●15 ●24 ●32

I always launch a master manually with roscore for this reason. IMO there's too much potential for weird inconsistencies, e.g., with parameter server values, to try reconnecting.

edit flag offensive delete link

Comments

1

Probably the better option, but I'm curious none-the less to know if nodes can be made to recover from losing a Master/reattach to new Master

Asomerville ( 2011-11-11 07:53:48 -0600 )edit

add a comment

Possible to communicate with new master without process restart?

2 Answers

Comments

Comments

Question Tools

Stats

Related questions

Possible to communicate with new master without process restart? edit

2 Answers

Comments

Comments

Question Tools

Stats

Related questions

Possible to communicate with new master without process restart?