[
https://issues.apache.org/jira/browse/ARTEMIS-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16494187#comment-16494187
]
ASF GitHub Bot commented on ARTEMIS-1891:
-----------------------------------------
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/2114
@clebertsuconic sounds like this bug fix should hit 2.6.1, sounds nasty,
wdyt? Or is it too late.
> Sending synchronization finished packet starves when thread pool is full
> ------------------------------------------------------------------------
>
> Key: ARTEMIS-1891
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1891
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Reporter: yangwei
> Priority: Major
> Attachments: synchronization_timeout.stack
>
>
> After sending pages, the thread will hold the storage manager write lock and
> send synchronization finished packet(use the parent thread pool) to the
> backup node. At the same time, thread pool is full bcs they are waiting for
> the storage manager read lock to write the page or journal, leading to
> replication starting failure. Here we use io executor to send replicate
> packet to fix thread pool starvation problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
