[
https://issues.apache.org/jira/browse/ARTEMIS-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728107#comment-17728107
]
ASF subversion and git services commented on ARTEMIS-4215:
----------------------------------------------------------
Commit c5be8b72c14860ccff0eafec0315f4383330fc42 in activemq-artemis's branch
refs/heads/main from clebert
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=c5be8b72c1 ]
ARTEMIS-4298 and ARTEMIS-4215 Fixing duplicated entries on historyFiles on
journalRetention during a replication
This is Fixing BackupSyncJournalTest::testReplicationDuringSync
ARTEMIS-4215 introduced a failure on the testsuite.
However the failure is non related to the Buffer itself. it introduced a race
that unveiled ARTEMIS-4298.
> JournalFlush might never happen when journal-sync-* is false
> ------------------------------------------------------------
>
> Key: ARTEMIS-4215
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4215
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Anton Roskvist
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When journal-sync-* is false then flushes to journal will only ever happen
> once the buffer is full or when the broker is cleanly shut down, regardless
> of how much time passes. This means that if the broker is started with these
> settings a crash/kill -9 will for sure loose messages, regardless of how much
> time passes since the messages where sent.
> This started with version 2.18.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
