- Newest
- Most votes
- Most comments
I don't have a solution but would like to report the exact same problem happening on a db.m7g.xlarge db at my company. There was little to no activity on the part of applications at the time that this happened, and we are suspecting that it happened many times before as we've witnessed OOM in logs before but thought our applications were at fault. We're opening up support tickets to enquire and hopefully prevent this from happening again.
Guys,
Our team member found out the root-cause for this. Enabling "Performance insights" is causing the issue... lol... Just disable it and you wont have this problem. But yeah, you lose the ability to inspect query related issues.....
Ideally - If you can ask AWS to run this query during lean times, I think it would be helpful. But I dont know if thats possible.
Hi,
thanks for the information, we do have performance insights enabled on our instance so it could explain indeed. However looking at the usefulness of this feature, I guess we'll need to live with this (occasional) issue for now .. hopefully AWS can address this at some point in time if enough users complain.
Wkr, Bert
Relevant content
- asked 2 years ago
- asked 3 years ago
- Accepted Answerasked 4 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago