Bug 1195565 - After coordinator change, cache topologies should be installed in parallel
Summary: After coordinator change, cache topologies should be installed in parallel
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER2
: 6.5.0
Assignee: Dan Berindei
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-24 05:16 UTC by Osamu Nagano
Modified: 2019-04-16 14:38 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-23 12:24:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-5019 0 Critical Resolved After coordinator change, cache topologies should be installed in parallel 2016-10-21 08:12:48 UTC
Red Hat Issue Tracker PRODMGT-1067 0 Major Resolved Coordinator promotion is keep failing successively, with massive GCs in a long loop 2016-10-21 08:12:48 UTC

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


Note You need to log in before you can comment on or make changes to this bug.