[jboss-jira] [JBoss JIRA] Commented: (JBCACHE-950) Expose information about buddy group membership

[Manik Surtani (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBCACHE-950?page=comments#action_12355961 ] 
            
Manik Surtani commented on JBCACHE-950:
---------------------------------------

Here is what I intend to do.

Every time my buddy group changes, I publish the BuddyGroup object to RuntimeConfig as "my group".  I also publish a list of other BuddyGroup objects for other groups I participate in.

I'll enhance BuddyGroup such that:

* mutators are protected.  They're only modified by the BuddyManager anyway, and should always be the case.
* a timestamp for when the group was last modified is available.

I presume this should be sufficient to then publish this via JMX, etc?




> Expose information about buddy group membership
> -----------------------------------------------
>
>                 Key: JBCACHE-950
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-950
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.0.0.GA, 2.0.0.BETA2
>
>
> Currently there is no way for external code to find out any information about how the cache participates in buddy relationships.
> Two issues (probably should be subtasks):
> 1) BuddyManager exposes getBuddyAddresses() but that only provides info about the group for which the node is data owner, not for any groups the node participates in as a buddy.  Also, it returns an internal data structure, making it unsafe to expose to random code.
> Because of this, if a "primary buddy" wanted to gravitate some or all data upon exit of the data owner, it would have no way to know if it is primary. Having all buddies gravitate data would be "a bad thing".
> 1) In 2.0.0 I believe the BuddyManager is not available except through CacheSPI. Perhaps some info about buddy group membership could be exposed via RuntimeConfig.

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