Is there any chance you could add a print data of your journal to the JIRA?
The Artemis data print has a —safe argument that would obfuscate any data only leaving journal structure recorded. ./artemjs data print —safe The system has to be stopped or you could copy your journal on another server for this operation. On Tue, Sep 20, 2022 at 6:24 AM <s...@cecurity.com.invalid> wrote: > Hello, > > This is related to my ticket > https://issues.apache.org/jira/browse/ARTEMIS-3992 > > We still have occasional spurts of messages like > > 2022-09-20 10:32:43,913 WARN [org.apache.activemq.artemis.journal] > AMQ142007: Can not find record 268 566 334 during compact replay > 2022-09-20 10:32:43,913 WARN [org.apache.activemq.artemis.journal] > AMQ142007: Can not find record 268 568 921 during compact replay > 2022-09-20 10:32:43,913 WARN [org.apache.activemq.artemis.journal] > AMQ142007: Can not find record 268 567 786 during compact replay > 2022-09-20 10:32:43,913 WARN [org.apache.activemq.artemis.journal] > AMQ142007: Can not find record 268 569 685 during compact replay > 2022-09-20 10:32:43,913 WARN [org.apache.activemq.artemis.journal] > AMQ142007: Can not find record 268 569 347 during compact replay > 2022-09-20 10:32:43,913 WARN [org.apache.activemq.artemis.journal] > AMQ142007: Can not find record 268 566 991 during compact replay > > and some consumers are dead slow (~4msg/s) . It may be their fault but > they struggle to find a client side cause. The queue they are querying > now holds 14M msg > > I'm trying to determine > > a/ the severity of the problem exposed by those warning. Can the store > be corrupt ? (we don't really have doubts on the physical layer, this is > local storage on the server, no errors reported by the os) > > b/ it there a possibility that theses issues play a role in the > performance problem ? > > Still on 2.24.0 like exposed in the jira issue. > > Any ideas ? > > Regards, > > SL > -- Clebert Suconic
