[jira] [Comment Edited] (ARTEMIS-3545) Artemis primary is filling all the disc when replica is killed

["Saulo (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17436119#comment-17436119 ] 

Saulo edited comment on ARTEMIS-3545 at 10/29/21, 5:45 PM:
-----------------------------------------------------------

[~gtully], i added the broker.xml files.

"primary starts, replica starts, producer starts."

You need the logs?

kill the replica? does the replica restart?

Yes, on production environment it restart but i found this behavior killing the replica (we use it on a docker container).

Yeah, but the primary disc is filled.

Both Artemis nodes starts on this script: 
{code:java}
/artemis/current/bin/artemis create --user ${ARTEMIS_USER} --password ${ARTEMIS_PASSWORD} --http-host 0.0.0.0 --require-login --relax-jolokia ${ARTEMIS_BROKER}
/artemis/${ARTEMIS_BROKER}/bin/artemis run --broker ${ARTEMIS_BROKER_FILE}
{code}
The producer is a simple Java EE JMS producer.

 
{code:java}

@Inject
private JMSContext context;
...

context.createProducer().send(checkSynchronizedQueue, jsonb.toJson(event));
 
{code}
{color:#172b4d}Our event object is a simple JSON VO with these attributes:
{color}

 
{code:java}
private Long id;
private Long rootObjectId;
private LocalDateTime createdAt = LocalDateTime.now();
private LocalDateTime processedAt;
private LocalDate referenceDate;
private boolean processed = false;
private String previous;
private String actual;{code}
 


was (Author: carvalho neto):
[~gtully], i added the broker.xml files.

"primary starts, replica starts, producer starts."

You need the logs?

kill the replica? does the replica restart?

Yes, on production environment it restart but i found this behavior killing the replica (we use it on a docker container).

Yeah, but the primary disc is filled.

Both Artemis nodes starts on this script:

 
{code:java}
/artemis/current/bin/artemis create --user ${ARTEMIS_USER} --password ${ARTEMIS_PASSWORD} --http-host 0.0.0.0 --require-login --relax-jolokia ${ARTEMIS_BROKER}
/artemis/${ARTEMIS_BROKER}/bin/artemis run --broker ${ARTEMIS_BROKER_FILE}
{code}
 

> 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
>
>         Attachments: broker-primary.xml, broker-replica.xml
>
>
> 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)