dev@shoal.java.net

Re: [Shoal-Dev] Re: JoinedAndReady Notification

From: Sheetal Vartak <Sheetal.Vartak_at_Sun.COM>
Date: Fri, 22 Feb 2008 11:07:17 -0800

Hi Kazem,
Please see inline comments :

Kazem Ardekanian wrote:
> Sheetal,
>
> 1) What does it mean if only one of the messages you mentioned is seen?
I will add another log message set to FINE level as follows :
GMS : JoinedAndReady event reported to group XX

This will be the message that you can completely rely on for this event.

> 2) What does happen between these two messages?
> 3) Shouldn't the assertion be put on the spectator and any other early
> started instance, in receiving the following message from cluster
> members?
> ... addReadyMembers;_RequestID=<request id>;|Adding Joined And Ready
> member : <instance name>

The above message will be seen by instances (CORE/SPECTATOR) that have
been started well in advance. It is possible during cluster startup for
some instances to not see this event if they started up a little late.
It will be good if we can also check if the cluster instances receive
this event. And it they don't, can we check if the instance started
late? Not sure how we can do this. Your suggestions are welcome.

Hope this answers your questions.
Thanks
Sheetal

>
> Thank you,
> Kazem
>
>
> Sheetal Vartak wrote, On 2/19/08 3:27 PM:
>> Hi Kazem,
>> The following messages indicates that this particular instance has
>> sent out the JoinedAndReady notification to the cluster :
>>
>> [#|2008-02-19T12:13:51.446-0800|FINE|sun-appserver9.1|ShoalLogger|_ThreadID=10;_ThreadName=main;ClassName=com.sun.enterprise.ee.cms.impl.common.GroupManagementServiceImpl;MethodName=reportJoinedAndReadyState;_RequestID=7810caa6-2eac-4f33-a5de-e0685f60417b;|GMS:Reporting
>> Joined and Ready state to group clusterz1|#]
>> [#|2008-02-19T12:13:51.450-0800|FINEST|sun-appserver9.1|ShoalLogger|_ThreadID=10;_ThreadName=main;ClassName=com.sun.enterprise.jxtamgmt.HealthMonitor;MethodName=reportJoinedAndReadyState;_RequestID=7810caa6-2eac-4f33-a5de-e0685f60417b;|Calling
>> reportMyState() with READY...|#]
>>
>> The above 2 messages should be a good check to see if the instances
>> are sending out the READY state.
>>
>> hths,
>> Sheetal
>>
>>
>> Kazem Ardekanian wrote:
>>> Hello Sheetal,
>>>
>>> The log lines containing JoinedAndReadyNotification do not convey
>>> any information about 'who' has joined and ready.
>>>
>>> As an example, the JoinedAndReady log lines below belong to an
>>> instance of a 8-node cluster (using the latest build).
>>>
>>> Please let me know how to find out about the name of the
>>> joinedAndReady cluster member.
>>>
>>> Thanks,
>>> Kazem
>>>
>>> [#|2008-02-19T12:13:48.299-0800|FINE|sun-appserver9.1|ShoalLogger|_ThreadID=16;_ThreadName=ViewWindowThread;ClassName=com.sun.enterprise.ee.cms.impl.jxta.ViewWindow;MethodName=addJoinedAndReadyNotificationSignal;_RequestID=ed6f54f7-51c2-4184-91a8-85cb7c87bb54;|adding
>>> join and ready signal|#]
>>>
>>> [#|2008-02-19T12:13:48.309-0800|FINEST|sun-appserver9.1|ShoalLogger|_ThreadID=20;_ThreadName=com.sun.enterprise.ee.cms.impl.common.Router
>>> Thread;ClassName=com.sun.enterprise.ee.cms.impl.common.SignalHandler;MethodName=analyzeSignal;_RequestID=97f4568b-66ea-4152-a197-c50866b23364;|SignalHandler
>>> : processing a received signal
>>> com.sun.enterprise.ee.cms.impl.common.JoinedAndReadyNotificationSignalImpl|#]
>>>
>>>
>>> [#|2008-02-19T12:13:48.720-0800|FINE|sun-appserver9.1|ShoalLogger|_ThreadID=16;_ThreadName=ViewWindowThread;ClassName=com.sun.enterprise.ee.cms.impl.jxta.ViewWindow;MethodName=addJoinedAndReadyNotificationSignal;_RequestID=ed6f54f7-51c2-4184-91a8-85cb7c87bb54;|adding
>>> join and ready signal|#]
>>>
>>> [#|2008-02-19T12:13:48.721-0800|FINEST|sun-appserver9.1|ShoalLogger|_ThreadID=20;_ThreadName=com.sun.enterprise.ee.cms.impl.common.Router
>>> Thread;ClassName=com.sun.enterprise.ee.cms.impl.common.SignalHandler;MethodName=analyzeSignal;_RequestID=97f4568b-66ea-4152-a197-c50866b23364;|SignalHandler
>>> : processing a received signal
>>> com.sun.enterprise.ee.cms.impl.common.JoinedAndReadyNotificationSignalImpl|#]
>>>
>>>
>>> [#|2008-02-19T12:13:51.113-0800|FINE|sun-appserver9.1|ShoalLogger|_ThreadID=16;_ThreadName=ViewWindowThread;ClassName=com.sun.enterprise.ee.cms.impl.jxta.ViewWindow;MethodName=addJoinedAndReadyNotificationSignal;_RequestID=ed6f54f7-51c2-4184-91a8-85cb7c87bb54;|adding
>>> join and ready signal|#]
>>>
>>> [#|2008-02-19T12:13:51.114-0800|FINEST|sun-appserver9.1|ShoalLogger|_ThreadID=20;_ThreadName=com.sun.enterprise.ee.cms.impl.common.Router
>>> Thread;ClassName=com.sun.enterprise.ee.cms.impl.common.SignalHandler;MethodName=analyzeSignal;_RequestID=97f4568b-66ea-4152-a197-c50866b23364;|SignalHandler
>>> : processing a received signal
>>> com.sun.enterprise.ee.cms.impl.common.JoinedAndReadyNotificationSignalImpl|#]
>>>
>>>
>>> [#|2008-02-19T12:13:51.446-0800|FINE|sun-appserver9.1|ShoalLogger|_ThreadID=10;_ThreadName=main;ClassName=com.sun.enterprise.ee.cms.impl.common.GroupManagementServiceImpl;MethodName=reportJoinedAndReadyState;_RequestID=7810caa6-2eac-4f33-a5de-e0685f60417b;|GMS:Reporting
>>> Joined and Ready state to group clusterz1|#]
>>>
>>> [#|2008-02-19T12:13:51.450-0800|FINEST|sun-appserver9.1|ShoalLogger|_ThreadID=10;_ThreadName=main;ClassName=com.sun.enterprise.jxtamgmt.HealthMonitor;MethodName=reportJoinedAndReadyState;_RequestID=7810caa6-2eac-4f33-a5de-e0685f60417b;|Calling
>>> reportMyState() with READY...|#]
>>>
>>> [#|2008-02-19T12:13:51.615-0800|FINE|sun-appserver9.1|ShoalLogger|_ThreadID=16;_ThreadName=ViewWindowThread;ClassName=com.sun.enterprise.ee.cms.impl.jxta.ViewWindow;MethodName=addJoinedAndReadyNotificationSignal;_RequestID=ed6f54f7-51c2-4184-91a8-85cb7c87bb54;|adding
>>> join and ready signal|#]
>>>
>>> [#|2008-02-19T12:13:51.616-0800|FINEST|sun-appserver9.1|ShoalLogger|_ThreadID=20;_ThreadName=com.sun.enterprise.ee.cms.impl.common.Router
>>> Thread;ClassName=com.sun.enterprise.ee.cms.impl.common.SignalHandler;MethodName=analyzeSignal;_RequestID=97f4568b-66ea-4152-a197-c50866b23364;|SignalHandler
>>> : processing a received signal
>>> com.sun.enterprise.ee.cms.impl.common.JoinedAndReadyNotificationSignalImpl|#]
>>>
>>>
>>> [#|2008-02-19T12:13:56.678-0800|FINE|sun-appserver9.1|ShoalLogger|_ThreadID=16;_ThreadName=ViewWindowThread;ClassName=com.sun.enterprise.ee.cms.impl.jxta.ViewWindow;MethodName=addJoinedAndReadyNotificationSignal;_RequestID=ed6f54f7-51c2-4184-91a8-85cb7c87bb54;|adding
>>> join and ready signal|#]
>>>
>>> [#|2008-02-19T12:13:56.680-0800|FINEST|sun-appserver9.1|ShoalLogger|_ThreadID=20;_ThreadName=com.sun.enterprise.ee.cms.impl.common.Router
>>> Thread;ClassName=com.sun.enterprise.ee.cms.impl.common.SignalHandler;MethodName=analyzeSignal;_RequestID=97f4568b-66ea-4152-a197-c50866b23364;|SignalHandler
>>> : processing a received signal
>>> com.sun.enterprise.ee.cms.impl.common.JoinedAndReadyNotificationSignalImpl|#]
>>>
>>>
>>> [#|2008-02-19T12:13:56.892-0800|FINE|sun-appserver9.1|ShoalLogger|_ThreadID=16;_ThreadName=ViewWindowThread;ClassName=com.sun.enterprise.ee.cms.impl.jxta.ViewWindow;MethodName=addJoinedAndReadyNotificationSignal;_RequestID=ed6f54f7-51c2-4184-91a8-85cb7c87bb54;|adding
>>> join and ready signal|#]
>>>
>>> [#|2008-02-19T12:13:56.894-0800|FINEST|sun-appserver9.1|ShoalLogger|_ThreadID=20;_ThreadName=com.sun.enterprise.ee.cms.impl.common.Router
>>> Thread;ClassName=com.sun.enterprise.ee.cms.impl.common.SignalHandler;MethodName=analyzeSignal;_RequestID=97f4568b-66ea-4152-a197-c50866b23364;|SignalHandler
>>> : processing a received signal
>>> com.sun.enterprise.ee.cms.impl.common.JoinedAndReadyNotificationSignalImpl|#]
>>>
>>>
>>>
>>> Sheetal Vartak wrote, On 02/11/08 14:44:
>>>> Hi Kazem,
>>>> Just wanted to let you know that a new feature was added around
>>>> November of last year. The feature was about adding a new
>>>> notification for instances which have joined the group and are
>>>> ready for processing client requests. This notification is
>>>> different from the Join notification. The Join notification only
>>>> tells the other instances that a particular instance has joined the
>>>> group. It does not mean that the instance is completely up and
>>>> ready to serve.
>>>> You can read more about this on Shreedhar's blog :
>>>> http://blogs.sun.com/shreedhar/date/20080117
>>>>
>>>> This new feature needs to be tested. Testing will be very simple
>>>> and all we need to know is if each of the instances in a group send
>>>> out the JoinedAndReadyEvent. Since instances start at different
>>>> times, its possible that an instance A will not see this event from
>>>> instance B. This is perfectly acceptable. All we need to know is
>>>> that instances A and B have sent out this event.
>>>>
>>>> Please let me know if you have any other questions.
>>>>
>>>> Thanks
>>>> Sheetal
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_shoal.dev.java.net
>>> For additional commands, e-mail: dev-help_at_shoal.dev.java.net
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_shoal.dev.java.net
> For additional commands, e-mail: dev-help_at_shoal.dev.java.net
>

--