6:31 a.m.
Paralellize discovery phase
---------------------------
Key: JGRP-375
URL: http://jira.jboss.com/jira/browse/JGRP-375
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.4
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.6
With TCPPING, if we have 10 servers defined in the list, we sequentially send a
GET_MBRS_REQ to each. However, if that server is not reachable, we will timeout out on the
socket connect call. Also, DNS lookup might take some time, so we might time out if we
cannot contact all servers. Example: servers 1 - 10. 1-9 are down or not reachable, plus
we have a slow DNS, 10 is running. So before we get to 10, the discovery will timeout and
we will become a singleton node.
SOLUTION: use threads from the common (global) thread pool in JGroups to parallelize the
sending of requests to all 10 servers.
--
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
4:13 a.m.
New subject: [JBoss JIRA] Updated: (JGRP-375) Paralellize discovery phase
[ http://jira.jboss.com/jira/browse/JGRP-375?page=all ]
Bela Ban updated JGRP-375:
--------------------------
Priority: Minor (was: Major)
Paralellize discovery phase
---------------------------
Key: JGRP-375
URL: http://jira.jboss.com/jira/browse/JGRP-375
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.4
Reporter: Bela Ban
Assigned To: Bela Ban
Priority: Minor
Fix For: 2.6
With TCPPING, if we have 10 servers defined in the list, we sequentially send a
GET_MBRS_REQ to each. However, if that server is not reachable, we will timeout out on the
socket connect call. Also, DNS lookup might take some time, so we might time out if we
cannot contact all servers. Example: servers 1 - 10. 1-9 are down or not reachable, plus
we have a slow DNS, 10 is running. So before we get to 10, the discovery will timeout and
we will become a singleton node.
SOLUTION: use threads from the common (global) thread pool in JGroups to parallelize the
sending of requests to all 10 servers.
--
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
10:46 a.m.
New subject: [JBoss JIRA] Updated: (JGRP-375) Paralellize discovery phase
[ http://jira.jboss.com/jira/browse/JGRP-375?page=all ]
Bela Ban updated JGRP-375:
--------------------------
Fix Version/s: 2.7
(was: 2.6)
Paralellize discovery phase
---------------------------
Key: JGRP-375
URL: http://jira.jboss.com/jira/browse/JGRP-375
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.4
Reporter: Bela Ban
Assigned To: Bela Ban
Priority: Minor
Fix For: 2.7
With TCPPING, if we have 10 servers defined in the list, we sequentially send a
GET_MBRS_REQ to each. However, if that server is not reachable, we will timeout out on the
socket connect call. Also, DNS lookup might take some time, so we might time out if we
cannot contact all servers. Example: servers 1 - 10. 1-9 are down or not reachable, plus
we have a slow DNS, 10 is running. So before we get to 10, the discovery will timeout and
we will become a singleton node.
SOLUTION: use threads from the common (global) thread pool in JGroups to parallelize the
sending of requests to all 10 servers.
--
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
10:28 p.m.
New subject: [JBoss JIRA] Commented: (JGRP-375) Paralellize discovery phase
[ http://jira.jboss.com/jira/browse/JGRP-375?page=comments#action_12395426 ]
Vladimir Blagojevic commented on JGRP-375:
------------------------------------------
Can we put this one in 2.6.2 as well? It is a very simple feature to implement. Instead of
sending one GET_MBRS_REQ at a time we submit each in a separate thread to the thread pool.
public void sendGetMembersRequest(String cluster_name) {
for(Iterator<Address> it = initial_hosts.iterator();it.hasNext();){
final Address addr = it.next();
final Message msg = new Message(addr, null, null);
msg.setFlag(Message.OOB);
msg.putHeader(name, new PingHeader(PingHeader.GET_MBRS_REQ, cluster_name));
if(log.isTraceEnabled())
log.trace("[FIND_INITIAL_MBRS] sending PING request to " +
msg.getDest());
timer.submit(new Runnable() {
public void run() {
try{
down_prot.down(new Event(Event.MSG, msg));
}catch(Exception ex){
if(log.isErrorEnabled())
log.error("failed sending discovery request to " +
addr, ex);
}
}
});
}
}
Paralellize discovery phase
---------------------------
Key: JGRP-375
URL: http://jira.jboss.com/jira/browse/JGRP-375
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.4
Reporter: Bela Ban
Assigned To: Bela Ban
Priority: Minor
Fix For: 2.7
With TCPPING, if we have 10 servers defined in the list, we sequentially send a
GET_MBRS_REQ to each. However, if that server is not reachable, we will timeout out on the
socket connect call. Also, DNS lookup might take some time, so we might time out if we
cannot contact all servers. Example: servers 1 - 10. 1-9 are down or not reachable, plus
we have a slow DNS, 10 is running. So before we get to 10, the discovery will timeout and
we will become a singleton node.
SOLUTION: use threads from the common (global) thread pool in JGroups to parallelize the
sending of requests to all 10 servers.
--
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
5:34 p.m.
New subject: [JBoss JIRA] Commented: (JGRP-375) Paralellize discovery phase
[ http://jira.jboss.com/jira/browse/JGRP-375?page=comments#action_12396096 ]
Vladimir Blagojevic commented on JGRP-375:
------------------------------------------
Resolved on HEAD.
Revision Changes Path
1.34 +18 -13 JGroups/src/org/jgroups/protocols/TCPPING.java
Resolved on 2.6
1.32.4.1 +19 -9 JGroups/src/org/jgroups/protocols/TCPPING.java
Paralellize discovery phase
---------------------------
Key: JGRP-375
URL: http://jira.jboss.com/jira/browse/JGRP-375
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.4
Reporter: Bela Ban
Assigned To: Bela Ban
Priority: Minor
Fix For: 2.7
With TCPPING, if we have 10 servers defined in the list, we sequentially send a
GET_MBRS_REQ to each. However, if that server is not reachable, we will timeout out on the
socket connect call. Also, DNS lookup might take some time, so we might time out if we
cannot contact all servers. Example: servers 1 - 10. 1-9 are down or not reachable, plus
we have a slow DNS, 10 is running. So before we get to 10, the discovery will timeout and
we will become a singleton node.
SOLUTION: use threads from the common (global) thread pool in JGroups to parallelize the
sending of requests to all 10 servers.
--
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
11:30 p.m.
New subject: [JBoss JIRA] Resolved: (JGRP-375) Paralellize discovery phase
[ http://jira.jboss.com/jira/browse/JGRP-375?page=all ]
Vladimir Blagojevic resolved JGRP-375.
--------------------------------------
Fix Version/s: 2.6.2
Resolution: Done
No unit tests added. No regression noticed on CC test suite runs.
Paralellize discovery phase
---------------------------
Key: JGRP-375
URL: http://jira.jboss.com/jira/browse/JGRP-375
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.4
Reporter: Bela Ban
Assigned To: Bela Ban
Priority: Minor
Fix For: 2.6.2, 2.7
With TCPPING, if we have 10 servers defined in the list, we sequentially send a
GET_MBRS_REQ to each. However, if that server is not reachable, we will timeout out on the
socket connect call. Also, DNS lookup might take some time, so we might time out if we
cannot contact all servers. Example: servers 1 - 10. 1-9 are down or not reachable, plus
we have a slow DNS, 10 is running. So before we get to 10, the discovery will timeout and
we will become a singleton node.
SOLUTION: use threads from the common (global) thread pool in JGroups to parallelize the
sending of requests to all 10 servers.
--
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
6183
days inactive
6592
days old
5 comments
3 participants
participants (3)
-
Bela Ban (JIRA) -
Bela Ban (JIRA) -
Vladimir Blagojevic (JIRA)