Hello Tod,
while running the qdstat -m command, I get below error.
-sh-4.2$ qdstat -a
ConnectionException: Connection amqp://0.0.0.0:amqp disconnected:
Condition('proton.pythonio', 'Connection refused to all addresses')
Ekta Awasthi,
Engineer, EAI Operations & Support | Office Depot, Inc.
6600 North Military Trail | Boca Raton, FL 33496-2434
Office: 561-438-3552 | Mobile: 206-966-5577 |
[email protected]<mailto:[email protected]>
-- Tips for EAI Support Engagement --
-EAI Pre-Prod Support: Create requests on the following JIRA board EAI
Operations
Support<https://officedepot.atlassian.net/secure/RapidBoard.jspa?rapidView=823&projectKey=EOS>
-EAI Production Support: Create requests via IT Service
Desk<https://portal.compucom.com/SSO/Default.aspx?init=2468> self-service
portal, instructions click
here<https://officedepot.sharepoint.com/sites/portal/TechBytes/EUS/EUS%20User%20Guides/SERVICE%20DESK/RESOLVER%20PORTAL/Self-Service%20Portal%20-%20Resolver%20(IT%20to%20IT)%20Incident%20Request%20Form.pdf>:
EAI Support queue --> ODP - Enterprise Apps Integration Support
-As a reminder, the Service Availability Managers should be engaged for any
service impacting issues, with a ***Page*** to
[email protected]<mailto:[email protected]>
or by initiating a MIRT
________________________________
From: Ted Ross <[email protected]>
Sent: Friday, December 15, 2023 2:48 PM
To: Ekta Awasthi <[email protected]>
Cc: [email protected] <[email protected]>; Ajit Tathawade (Contractor)
<[email protected]>; Nilesh Khokale (Contractor)
<[email protected]>
Subject: Re: High Memory consumption with Qpid Dispatch 1.19.0
[CAUTION: EXTERNAL SENDER]
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
<[email protected]<mailto:[email protected]>> 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.
[cid:ii_18c6f0362d0cb971f161]
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.
