[infinispan-issues] [JBoss JIRA] (ISPN-8925) Conflict Resolution can exhaust the ASYNC_TRANSPORT_EXECUTOR

[Ryan Emerson (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-8925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543531#comment-13543531 ] 

Ryan Emerson commented on ISPN-8925:
------------------------------------

ISPN-8706 was caused by this issue as it was loading in many caches, such as counters, counter-config etc

> Conflict Resolution can exhaust the ASYNC_TRANSPORT_EXECUTOR 
> -------------------------------------------------------------
>
>                 Key: ISPN-8925
>                 URL: https://issues.jboss.org/browse/ISPN-8925
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 9.2.0.Final
>            Reporter: Ryan Emerson
>            Assignee: Ryan Emerson
>             Fix For: 9.2.1.Final
>
>
> During the execution of AvailabilityStrategyContext#updateTopologiesAfterMerge, it's necessary for a topology update to be sent to the cluster via ClusterTopologyManagerImpl#executeOnClusterAsync, which utilises the ASYNC_TRANSPORT_EXECUTOR, before a call is made to ConflictManager#resolveConflicts. This topology update is vital as it contains the topologyId which all of the conflict resolution RPCs depend on. If this topology update is not sent, then ConflictManager#resolveConflicts will eventually timeout as no progress can be made.
> The problem is that during the entire execution of AvailabilityStrategyContext#doMergePartitions, an ASYNC_TRANSPORT_EXECUTOR thread is occupied. Therefore, when AvailabilityStrategyContext#updateTopologiesAfterMerge is called prior to conflict resolution it's possible that ALL threads are executing runnables that are waiting indefinitely on ConflictManager#resolveConflicts and therefore it's not possible to send the topology update.
> As the number of caches increase the number of doMergePartition runnables on the ASYNC_TRANSPORT_EXECUTOR increases, consequently so does the likelihood of the executor's resources becoming exhausted. 



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)