[Users] Services updating on slave nodes

leofl [via Petals Forums] ml-node+s974793n3459033h97 at n3.nabble.com
Thu Oct 27 22:26:10 CEST 2011



Hi,

My team have tried the following experiment with Petals DSB (last version,
of 21th October): run one master Petals node and two slave nodes, with a
service (and their consumer and provider assemblies) deployed in a a slave
node.

We expected all the nodes should access* the deployed service, but only the
master node and the node where the service was deployed could access the
deployed service. The other slave node was able to access the service only
after we restart the petals of this node. 

Our conclusion is when you deploy a new service on a slave node, other slave
nodes don't become aware about this new service. Is there any way to handle
this problem?

thank you
Leonardo Leite
IME - USP

* to access the service = one service can be accessed by a node with it is
listed on petals/services/listServices page. 

_______________________________________________
If you reply to this email, your message will be added to the discussion below:
http://forum.petalslink.com/Services-updating-on-slave-nodes-tp3459033p3459033.html
To start a new topic under Users (get help, provide help), email ml-node+s974793n2681628h42 at n3.nabble.com
To unsubscribe from Users (get help, provide help), visit http://forum.petalslink.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2681628&code=dXNlcnNAZm9ydW0ucGV0YWxzbGluay5vcmd8MjY4MTYyOHwtOTE3MDU0NjU4
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://forum-list.petalslink.org/pipermail/users/attachments/20111027/ea0416aa/attachment.htm>


More information about the Users mailing list