[
https://issues.apache.org/jira/browse/ARTEMIS-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17436068#comment-17436068
]
Gary Tully commented on ARTEMIS-3545:
-------------------------------------
please attach the broker configuration files that are in play for the primary
and replica.
can you give a little more clarity on your test procedure, we will need to
reproduce with a test case.
for clarity:
primary starts, replica starts, producer starts.
30k messages produced
kill the replica? does the replica restart?
the primary in this case should stay active and do nothing, it is only the
replica that should keep old archived around. something about this
scenario/description does not compute!
please lay it out as plain as you can, even from your shell history. thanks.
> Artemis primary is filling all the disc when replica is killed
> --------------------------------------------------------------
>
> Key: ARTEMIS-3545
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3545
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.18.0, 2.19.0
> Reporter: Saulo
> Priority: Major
> Fix For: 2.17.0
>
>
> We have an app using Artemis and for some reason, it's creating oldreplica
> files until fill all the disc.
> My test was something like this:
> We have a primary and a replica with Artemis.
> I started an app producing messages on Artemis.
> When we got something around 30k messages and without stop producing we
> killed the replica and the primary started to create oldreplica files until
> fill all the disc (we tried with 20GB and 80GB discs).
> I did this test on 2.18, 2.19 and had the same behavior but on 2.17 it
> doesn't happen.
> I sent an e-mail to the mailing list if it could help.
> https://markmail.org/message/bvmeqgand7rv7tbd
> Old Jira issue:
> https://issues.apache.org/jira/browse/ARTEMIS-3527
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
