I recently started experimenting with axon server se, client application is spring boot.
I noticed warnings as following in axon server logs -
2023-06-10 21:20 WARN 1 Reached soft limit on queue size xxx of size 10000, priority of item failed to be added 0, soft limit 10000.
and later in the logs, there were statements as following:
2023-06-10 21:25:49.842 WARN 1 --- [MessageBroker-1] i.a.a.message.command.CommandCache : Found 1793 waiting commands to delete
Though above are listed as warning, is there any possibility of command / events losses?
Also, I tried looking around for these errors and couldn’t find much. At one place, I found the warning message
...Found 1793 waiting commands to delete could be due to time out before these commands would get handled.
Additionally, I was using postgres event store with same load, and all processing happened without any errors. My spring boot app axon config is as following -
axon: axonserver: enabled: true servers: 10.218.53.179:8080 serializer: general: jackson events: jackson messages: jackson deserializer: general: jackson events: jackson messages: jackson eventhandling: processors: sc-pgroup: # Indicates the number of segments that should be created when the processor starts for the first time. # This is static and can be only dynamically adjusted with split / merge api's. # help with concurrent processing. initialSegmentCount: 10 # The maximum number of threads the processor should process events with. Defaults to the number of initial # segments if this is not further specified. threadCount: 15 # Indicates whether this processor should be Tracking, or Subscribing its source. mode: tracking # The default policy. It will force domain events that were raised from the same aggregate to be handled sequentially. # Thus, events from different aggregates may be handled concurrently. # This policy is typically suitable for Event Handling Components that update details from aggregates in databases. sequencing-policy: sequentialPerAggregatePolicy batch-size: 20 part-pgroup: initialSegmentCount: 10 threadCount: 15 mode: tracking sequencing-policy: sequentialPerAggregatePolicy batch-size: 20 metrics: auto-configuration: enabled: true micrometer: dimensional: true
I will really appreciate if someone could share any pointers to avoid the warnings thrown by the axon server per above. Thank you.