[infinispan-issues] [JBoss JIRA] Commented: (ISPN-360) create NodeJoined event

Manik Surtani (JIRA) jira-events at lists.jboss.org
Mon Mar 8 07:36:58 EST 2010


    [ https://jira.jboss.org/jira/browse/ISPN-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12518680#action_12518680 ] 

Manik Surtani commented on ISPN-360:
------------------------------------

NodeJoined is still just an indication that a single node has joined, and not that the entire cluster is ready.  You could loop until expected cluster size matches the cluster size, but that would still be very similar to the "workaround" proposed, without using NodeJoined.

So NodeJoined really won't help tell you that a cluster of a certain size has formed.

I'm not suggesting that NodeJoined is *not* useful - I think it is, which is why I am keeping this JIRA open - I just don't think it will solve your specific issue.  Or won't help *much* in any case.

> create NodeJoined event
> -----------------------
>
>                 Key: ISPN-360
>                 URL: https://jira.jboss.org/jira/browse/ISPN-360
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Listeners, State transfer
>            Reporter: Mircea Markus
>            Assignee: Manik Surtani
>
> In relation to http://community.jboss.org/message/529547#529547 
> It's an well known scenario to start a cluster, and only after the ENTIRE cluster is started to start and do work. Right now, we have CacheStarted and ViewChanged notifications. First only tells us that the local node is started but other nodes might still be in the process of starting. Second one tells us that the view has changed, but not that the cluster has started, i.e. the cache might be in the process of rebalancing state etc. 
> A possible solution would be to have an NodeJoined event, that would be called  whenever a new node finished joining the cluster. Finished joining means state transfer happened and that node is started.
> For a possible workaround to this feature see the forum post. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the infinispan-issues mailing list