[
https://issues.jboss.org/browse/WFLY-315?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on WFLY-315:
----------------------------------
Ideally, dependency-oriented tasks would be asynchronous/callback-based. I have a simple
DependencyTask class in jboss-threads that might be interesting for certain trivial cases
(probably not for this case though). The idea is to avoid submitting tasks that you know
will block, instead favoring tasks that will proceed and that will resolve future
tasks' blocks before they are executed.
Avoid running out of threads when connecting to the DC from a slave
to pull down missing data
---------------------------------------------------------------------------------------------
Key: WFLY-315
URL:
https://issues.jboss.org/browse/WFLY-315
Project: WildFly
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Domain Management
Reporter: Kabir Khan
Assignee: Emanuel Muckenhuber
Priority: Blocker
Fix For: 9.0.0.CR1
For WFLY-259 when a slave connects to the DC to pull down missing data, it does this by
either getting a lock for the DC, or by joining the permit of the existing DC lock if the
request to update a slave's server-config was executed as part of a composite
obtaining a lock on the DC.
The way it works at present there is a thread per slave which is blocked until the
transaction completes. The DC threads are a finite resource, so a large number of slaves
trying to pull down dats will cause deadlock
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira