[jboss-jira] [JBoss JIRA] (WFCORE-4804) Topology gets loading when the write lock has been acquired on a DC

Yeray Borges (Jira) issues at jboss.org
Mon Jan 20 11:50:19 EST 2020


     [ https://issues.redhat.com/browse/WFCORE-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yeray Borges moved HAL-1643 to WFCORE-4804:
-------------------------------------------

              Project: WildFly Core  (was: HAL)
                  Key: WFCORE-4804  (was: HAL-1643)
             Workflow: GIT Pull Request workflow   (was: GIT Pull Request workflow with automatic PR triggers)
          Component/s: Management
                           (was: Domain Management)
    Affects Version/s: 11.0.0.Beta7
                           (was: 3.2.1.Final)


> Topology gets loading when the write lock has been acquired on a DC
> -------------------------------------------------------------------
>
>                 Key: WFCORE-4804
>                 URL: https://issues.redhat.com/browse/WFCORE-4804
>             Project: WildFly Core
>          Issue Type: Enhancement
>          Components: Management
>    Affects Versions: 11.0.0.Beta7
>            Reporter: Yeray Borges
>            Assignee: Yeray Borges
>            Priority: Minor
>
> Topology information is loaded by using Composite operations. A composite operation could require the write lock on the DC when there is more than one slave in the domain. In this scenario, the DC's write lock is acquired until the overall operation, which is being executed in DC and in all the slaves, finishes. 
> If there is another operation being executed in the DC that previously has acquired the write lock, e.g servers in the domain are being started or an application is being deployed, the topology won't be able to load.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)


More information about the jboss-jira mailing list