Created: (JGRP-703) TCPGOSSIP: parallelize discovery for multiple GossipRo

TCPGOSSIP: parallelize discovery for multiple GossipRouters
-----------------------------------------------------------

                 Key: JGRP-703
                 URL: http://jir
a.jboss.com/jira/browse/JGRP-703
             Project: JGroups
          Issue Type: Bug
            Reporter: Bela Ban
         Assigned To: Bela Ban
             Fix For: 2.7


When we have multiple GossipRouters, and some GRs are
blocked on TCP (e.g. host unreachable, or unplugged, or
interface down), then we block for each GR.
SOLUTION: each discovery request sent to a GR should be run
in a separate thread, similar to TCPPING

-- 
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.atl
assian.com/software/jira

        
_______________________________________________
jboss-jira mailing list
jboss-jiralists.jboss.org
h
ttps://lists.jboss.org/mailman/listinfo/jboss-jira

     [ h
ttp://jira.jboss.com/jira/browse/JGRP-703?page=all ]

Bela Ban updated JGRP-703:
--------------------------

    Fix Version/s: 2.6.3

> TCPGOSSIP: parallelize discovery for multiple
GossipRouters
>
-----------------------------------------------------------
>
>                 Key: JGRP-703
>                 URL: http://jir
a.jboss.com/jira/browse/JGRP-703
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.7, 2.6.3
>
>
> When we have multiple GossipRouters, and some GRs are
blocked on TCP (e.g. host unreachable, or unplugged, or
interface down), then we block for each GR.
> SOLUTION: each discovery request sent to a GR should be
run in a separate thread, similar to TCPPING

-- 
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.atl
assian.com/software/jira

        
_______________________________________________
jboss-jira mailing list
jboss-jiralists.jboss.org
h
ttps://lists.jboss.org/mailman/listinfo/jboss-jira

    [ http://jira.jboss.com/jira/browse/JGRP-7
03?page=comments#action_12400909 ] 
            
Bela Ban commented on JGRP-703:
-------------------------------

This is in GossipClient._register(), _unregister() and
_getMembers()

> TCPGOSSIP: parallelize discovery for multiple
GossipRouters
>
-----------------------------------------------------------
>
>                 Key: JGRP-703
>                 URL: http://jir
a.jboss.com/jira/browse/JGRP-703
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.7, 2.6.3
>
>
> When we have multiple GossipRouters, and some GRs are
blocked on TCP (e.g. host unreachable, or unplugged, or
interface down), then we block for each GR.
> SOLUTION: each discovery request sent to a GR should be
run in a separate thread, similar to TCPPING

-- 
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.atl
assian.com/software/jira

        
_______________________________________________
jboss-jira mailing list
jboss-jiralists.jboss.org
h
ttps://lists.jboss.org/mailman/listinfo/jboss-jira

     [ h
ttp://jira.jboss.com/jira/browse/JGRP-703?page=all ]

Bela Ban updated JGRP-703:
--------------------------

    Fix Version/s:     (was: 2.6.3)

won't change this in 2.6.x, as this is new functionality

> TCPGOSSIP: parallelize discovery for multiple
GossipRouters
>
-----------------------------------------------------------
>
>                 Key: JGRP-703
>                 URL: http://jir
a.jboss.com/jira/browse/JGRP-703
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.7
>
>
> When we have multiple GossipRouters, and some GRs are
blocked on TCP (e.g. host unreachable, or unplugged, or
interface down), then we block for each GR.
> SOLUTION: each discovery request sent to a GR should be
run in a separate thread, similar to TCPPING

-- 
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.atl
assian.com/software/jira

        
_______________________________________________
jboss-jira mailing list
jboss-jiralists.jboss.org
h
ttps://lists.jboss.org/mailman/listinfo/jboss-jira

     [ h
ttp://jira.jboss.com/jira/browse/JGRP-703?page=all ]

Bela Ban resolved JGRP-703.
---------------------------

    Resolution: Done

> TCPGOSSIP: parallelize discovery for multiple
GossipRouters
>
-----------------------------------------------------------
>
>                 Key: JGRP-703
>                 URL: http://jir
a.jboss.com/jira/browse/JGRP-703
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.7
>
>
> When we have multiple GossipRouters, and some GRs are
blocked on TCP (e.g. host unreachable, or unplugged, or
interface down), then we block for each GR.
> SOLUTION: each discovery request sent to a GR should be
run in a separate thread, similar to TCPPING

-- 
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.atl
assian.com/software/jira

        
_______________________________________________
jboss-jira mailing list
jboss-jiralists.jboss.org
h
ttps://lists.jboss.org/mailman/listinfo/jboss-jira