Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Why ESR files were not processed in the morning of 26th/Jun? - Because the RabbitMQ was not accepting any incoming traffic and was not able to process transactions.

  2. Why was RabbitMQ not able to accept incoming traffic and process transactions? - Because there was not enough memory.

  3. Why there was not enough memory in RabbitMQ? - Because it was occupied by esr.queue.audit.neo queue. There were more than 4 million messages in it and it ate up the resource.

  4. Why there were more than 4 million messages in esr.queue.audit.neo queue? - Currently, we don’t knowThe message consumer could not read messages because the database was unavailable.

...

Action Items

Action Items

Owner

Comments

Investigate why there are so many message in esr.queue.audit.neo queue when ESR files are being processed and who consumes this queue.

Monitor the queue for a period of time to find out if there’re still rapid increasing on the number of messages.

Yafang Deng Jayanta Saha

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4720

Investigate why we still have incoming messages in esr.dlq.2022-08-19-jay and esr.dlq.2022.08.09

Jayanta Saha

This has led to missing another issue which appears to have increased since the start of June

Following above, test whether instance size or green/blue impacts the number of error messages produced?

Clean up queues which aren’t needed right now, even if likely to be added in the near future?

...

Lessons Learned

  • Learn more knowledge about ESR.