[
https://issues.apache.org/jira/browse/ARTEMIS-2622?focusedWorklogId=387530&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-387530
]
ASF GitHub Bot logged work on ARTEMIS-2622:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 14/Feb/20 18:10
Start Date: 14/Feb/20 18:10
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on pull request #2983:
ARTEMIS-2622 Making replica resilient to closed pages
URL: https://github.com/apache/activemq-artemis/pull/2983
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 387530)
Remaining Estimate: 0h
Time Spent: 10m
> Replication on paging eventually erroring on page already closed.
> -----------------------------------------------------------------
>
> Key: ARTEMIS-2622
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2622
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.11.0
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Fix For: 2.12.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I have a case where the system reports this on the replica:
> AMQ119217: Cant write to closed file: {0}:
> ActiveMQIOErrorException[errorType=IO_ERROR message=AMQ119217: Cant write to
> closed file: {0}]
> This started to happen after we introduced the exception as part of
> ARTEMIS-2088 / 90ca87c5e16df9812a65db37d05306f444dd7fb1
> Apparently the writes of the pages were happening after the delete, what
> could eventually happen on cleanup.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
