[
https://issues.apache.org/jira/browse/ARTEMIS-5379?focusedWorklogId=964732&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-964732
]
ASF GitHub Bot logged work on ARTEMIS-5379:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 03/Apr/25 18:08
Start Date: 03/Apr/25 18:08
Worklog Time Spent: 10m
Work Description: clebertsuconic merged PR #5595:
URL: https://github.com/apache/activemq-artemis/pull/5595
Issue Time Tracking
-------------------
Worklog Id: (was: 964732)
Time Spent: 50m (was: 40m)
> Journal commit record recorded before Page Writer is finished leading to
> possible message loss on a crash
> ---------------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-5379
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5379
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Clebert Suconic
> Priority: Blocker
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Due to ARTEMIS-5305, the journal commit record could reach the journal before
> the page writes.
> The clients were always waiting correctly for the entire portion of the data
> being stored. However if an uncertainty happened (the failure happened before
> the page write was finished) you could have a situation where part of the TX
> is recorded and part is not.
> That could lead to DUPLICATE Cache stored and not the data.
> Or other portion of the TX stored but not the send.
> The fix is to defer the write of the journal record until the page write
> operation is finished.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
