[jboss-jira] [JBoss JIRA] Commented: (JGRP-910) Shared transport: 'members' variable incorrect (remove from TP ?)
Bela Ban (JIRA)
jira-events at lists.jboss.org
Mon Feb 23 08:18:44 EST 2009
[ https://jira.jboss.org/jira/browse/JGRP-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12453759#action_12453759 ]
Bela Ban commented on JGRP-910:
-------------------------------
Possible solution:
--> The 'members' variable remains in TP, but is only used when the transport is non-shared
--> When we need to send a message to all members *without* multicasting, the following happens:
- Regular transport:
- We iterate over 'members' and send the same message to every member (same as now)
- Shared transport
- TP.ProtocolAdapter adds the cluster name to the message as a header
- We grab the header and retrieve the cluster name
- We look up the corresponding TP.ProtocolAdapter in up_prots
- TP.ProtocolAdapter also maintains a 'members' membership variable. We use it to iterate over the members
> Shared transport: 'members' variable incorrect (remove from TP ?)
> -----------------------------------------------------------------
>
> Key: JGRP-910
> URL: https://jira.jboss.org/jira/browse/JGRP-910
> Project: JGroups
> Issue Type: Bug
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 2.8
>
>
> TP.members is the union of all views received on *all* channels. This is incorrect, and sendToAllMembers() iterating over 'members' would unnecessarily send messages to members in a different cluster ! (these would get dropped, but it is still spurious traffic)
> Logically, 'members' belongs to a cluster, so maybe we ahould should have a table of cluster names and views in TP ?
--
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 jboss-jira
mailing list