Ekta, You can get more granular memory-use data by using the "qdstat -m" command against the router when its memory footprint is larger than you think it should be.
I assume you've been using this version for some time. It might be helpful to look into what other things changed right before the memory consumption problem started. -Ted On Fri, Dec 15, 2023 at 12:08 PM Ekta Awasthi <ekta.awas...@theodpcorp.com> wrote: > Hi All & Tod, > > We are currently encountering elevated memory consumption with qpid > dispatch version 1.19.0. Although the memory is released upon restarting > qpid, it gradually accumulates again, surpassing 80% memory usage. As QPID > in our case servers as a routing mechanism, handling traffic from NLB to > QPID and then to the broker. While investigating the cause of this behavior > and examining memory usage from New Relic (NR) graph indicates that the > qdrouterd process is responsible for the memory consumption. We are seeking > insights into the root cause of this issue and whether it may be related to > the version (1.19.0). Please find additional information below. > > *Architecture*: > NLB --> QPID(2 qpids acting as consumers) --> BROKER (Total of 3 pairs. > Master/Slave configuration for HA) > > *Qpids* were restarted on 12-10-23 as you can see below the gradual > increase has been happening ever since. > > *Ekta Awasthi* > > CONFIDENTIALITY NOTICE: The information contained in this email and > attached document(s) may contain confidential information that is intended > only for the addressee(s). If you are not the intended recipient, you are > hereby advised that any disclosure, copying, distribution or the taking of > any action in reliance upon the information is prohibited. If you have > received this email in error, please immediately notify the sender and > delete it from your system. >
