So, Jenkins
has this async resource disposer plugin which I have it installed.
My question: Is there a way to clean up the resources that the plugin collects because if I don't clean up manually, it seems to consume more and more CPU every time?
Sometimes it just makes Jenkins
unresponsive.
So, is there a better way to clean up these resources? As of now, I don't care with what it's capturing so is there an issue if I just remove the plugin or a way of using the API to clean up these resources every night?
I found a workaround in one of the jenkins ticket created by someone:
Ticket: https://issues.jenkins-ci.org/browse/JENKINS-24824
curl -s http://${JENKINS_URL}/administrativeMonitor/AsyncResourceDisposer/ -u${UTILITY_USER}:${UTILITY_PW} | tr '"' '\n' | grep 'stop-tracking' | cut -d '-' -f 3 | sort -n | while read ASYNC_THREAD; do curl http://${JENKINS_URL}/administrativeMonitor/AsyncResourceDisposer/stopTracking -u${UTILITY_USER}:${UTILITY_PW} -X POST --data "id=${ASYNC_THREAD}"; done
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With