Actions
Incident #10717
closed
Tagme stops responding because is going out of heap space
Start date:
Dec 15, 2017
Due date:
% Done:
100%
Estimated time:
Infrastructure:
Production
Description
It seems that a lot of accesses started today from 141.115.102.180 (many requests per second, often) and the service is not able to cope with them.
We can increase the VM resources somewhat, but I fear that it would only slow down the interval between failures.
Updated by Tommaso Piccioli over 7 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 90
We placed a rule to reject network 141.115.102.160/27.
Tomcat restarted, let see what happens.
Updated by Tommaso Piccioli over 7 years ago
- Status changed from In Progress to Feedback
- % Done changed from 90 to 100
Updated by Andrea Dell'Amico over 7 years ago
Closing the ticket. If those accesses were legit, they should rate limit it before removing the firewall rules.
Updated by Andrea Dell'Amico over 7 years ago
- Status changed from Feedback to Closed
Actions
