thanks for such a quick response. Much appreciated. Is it tricky to add support for this feature? I don't mind taking a stab at it... unless it's a major change. Or would you not recommend doing that? Thanks! Anton. On Oct 5, 2011, at 12:12 PM, Steven Dake wrote: > On 10/05/2011 11:51 AM, Anton Jouline wrote: >> hello Steven, >> >> Found this post on Openais mailing list: >> http://www.mail-archive.com/openais@xxxxxxxxxxxxxxxxxxxxxxxxxx/msg05507.html >> >> This is exactly what i need: be able to tell corosync about new members, >> when using udpu transport. However, unfortunately it does not seem to >> work... or perhaps i'm not using it the right way. II can see that the >> new object/key was created via corosync-objtool, however, nothing >> happens after that: corosync does not see the new member, even though it >> is online. >> > > This feature is not implemented at this time. Also please use a more > recent version of corosync, 1.3.3 has many little totem gotchas. > > Regards > -steve > >> # corosync-objctl totem >> totem.version=2 >> totem.secauth=off >> totem.transport=udpu >> totem.interface.ringnumber=0 >> totem.interface.bindnetaddr=10.204.55.43 >> totem.interface.mcastport=5405 >> totem.interface.member.memberaddr=10.204.55.43 >> >> # corosync-objctl -n totem.interface.member.memberaddr=10.68.55.19 >> >> # corosync-objctl totem >> totem.version=2 >> totem.secauth=off >> totem.transport=udpu >> totem.interface.ringnumber=0 >> totem.interface.bindnetaddr=10.204.55.43 >> totem.interface.mcastport=5405 >> totem.interface.member.memberaddr=10.204.55.43 >> totem.interface.member.memberaddr=10.68.55.19 >> >> >> I know for sure that the other member (10.68.55.19) is live and healthy. >> If i modify the configuration file and add it there, then restart >> corosync - everything works well. >> >> Do you have any insight on why this is happening? Is there a need to >> somehow explicitly notify corosync that its objdb has changed...? >> (I am using Corosync 1.3.3 on CentOS 5 i386) >> >> Thanks! >> >> Anton. >> >> >> > _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
