[JBoss JIRA] Created: (JGRP-375) Paralellize discovery phase
by Bela Ban (JIRA)
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
18 years, 6 months
[JBoss JIRA] Updated: (JBCACHE-131) Cache Loaders (when unshared, and not used with passivation) Should Persist Transient State Upon Startup
by Manik Surtani (JIRA)
[ http://jira.jboss.com/jira/browse/JBCACHE-131?page=all ]
Manik Surtani updated JBCACHE-131:
----------------------------------
Fix Version/s: 2.2.0.GA
(was: 2.1.0.GA)
(was: 1.4.X)
> Cache Loaders (when unshared, and not used with passivation) Should Persist Transient State Upon Startup
> --------------------------------------------------------------------------------------------------------
>
> Key: JBCACHE-131
> URL: http://jira.jboss.com/jira/browse/JBCACHE-131
> Project: JBoss Cache
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 1.2.2
> Reporter: Jimmy Wilson
> Assigned To: Manik Surtani
> Priority: Minor
> Fix For: 2.2.0.GA
>
> Attachments: TreeCache.zip
>
>
> Given the following single, unshared cache loader use case in the TreeCache documentation:
> "This is a similar case as the previous one, but here only one node in the cluster interacts with a backend store via its CacheLoader. All other nodes perform in-memory replication. A use case for this is HTTP session replication, where all nodes replicate sessions in-memory, and - in addition - one node saves the sessions to a persistent backend store"
> A cache with attached cache loader should persist the transient state of the cache to disk upon startup in order to maintain cache recoverability.
> I have modified TreeCache to handle this situation, and I will attach the modified code to this issue.
--
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
18 years, 6 months