Hi Julius
Not sure if you saw my email response to the users list yesterday.
Shoal 1.1 has significant number of bug fixes, improvements and
features, so you did the right thing by picking that up.
Your approach to use JoinedAndReady reporting is a better one that only
relying on JoinNotificationSignal, to ensure that the group state
reaches some level of stability. It is always better to let the
concurrent startup of all members settle down before operations begin
and that is the reason we added Joined and Ready constructs.
--Shreedhar
JuliusOliverFernandes wrote:
> Dear All,
> I tested the same in version 1.0 of Shoal. Now I switched to Shoal
> 1.1. This version notifies when the node first joins.
> (groupManagementService.addActionFactory(new
> JoinNotificationActionFactoryImpl(this)))
>
> I could manage my tasks with the following algo.
> 1) Whenever the node join, we get JoinNotificationSignal
> 2) Here I fire the JoinedAndReadyNotificationSignal
> 3) When I get this signal I start my application if its not already
> started.
>
> The reason I went with this algo was, if I start my application on
> JoinNotificationSignal (earlier approach). The node might not have
> received the other nodes information when it first joins. So I will
> not know if there is another application thats already started on
> another node. With this algo, there is sometime for it to recieve
> other nodes information. I dont know if this approach is right. What I
> am afraid of is, if the node receives its own signal first then it
> will start the application on it while there is already another
> instance running on another node.I want only one application running
> at a time.
>
> If you can help please write to me on this email id.If you want me to
> send the code, give your email id and I shall send the same across.
>
> Regards
> Julius
>
>
>
>
> <http://sigads.rediff.com/RealMedia/ads/click_nx.ads/www.rediffmail.com/signatureline.htm@Middle?>
>
>