Bug 1195565

Summary: After coordinator change, cache topologies should be installed in parallel
Product: [JBoss] JBoss Data Grid 6 Reporter: Osamu Nagano <onagano>
Component: InfinispanAssignee: Dan Berindei <dberinde>
Status: CLOSED CURRENTRELEASE QA Contact: Martin Gencur <mgencur>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: dstahl, jdg-bugs, ksuzumur, mcimbora, pzapataf, rmarwaha
Target Milestone: ER2   
Target Release: 6.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-23 12:24:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Osamu Nagano 2015-02-24 05:16:17 UTC 
Description of problem:
When the coordinator crashes, the new coordinator has to recover the cache topologies from all the nodes in the cluster and install updated topologies for all the caches. This is done on a single thread, and it can take a long time when there are a lot of caches.

We should be accelerate this by doing the topology installation on separate threads. However, we have to be careful with the async transport pool, because executeOnClusterAsync actually needs to spawn a new thread in the same pool.
Comment 3 JBoss JIRA Server 2015-03-18 10:11:49 UTC 
Dan Berindei <dberinde> updated the status of jira ISPN-5019 to Coding In Progress
Comment 4 Dave Stahl 2015-04-17 16:52:57 UTC 
PR: https://github.com/infinispan/jdg/pull/614