Initially, it began with around 130,000kb in RSS (as per ps), but now it has increased to around 400,000kb. It appears that there may be a memory leak in that part of the system.
Here's what I've found during my testing:
I removed all services in eventloop.py and tested only service_monitor. It was ok.
I called maas cli to check machines, Bash encountered out-of-memory (OOM) errors three times in several attempts. Strangely, it was fine when running Bash 'for' 10,000 times, but after completing or restarting it, it suddenly faced OOM errors, exhausting all memory in the VM.
With the maas api, I noticed a gradual increase in memory usage over time.
Please give me any advice how to solve this issue. I'll also check maas code if there is something I can do.
Hello,
I've set up a test environment and have been making API calls using the command below:
curl --header "Authorization: OAuth oauth_version=1.0, oauth_signature _method= PLAINTEXT, oauth_consumer_ key=$API_ KEY1, oauth_token= $API_KEY2, oauth_signature =&$API_ KEY3, oauth_nonce= $(uuidgen) , oauth_timestamp =$(date +%s)" $MAAS_URL/ MAAS/api/ 2.0/machines/
This has been running for about a day.
Initially, it began with around 130,000kb in RSS (as per ps), but now it has increased to around 400,000kb. It appears that there may be a memory leak in that part of the system.
Here's what I've found during my testing:
I removed all services in eventloop.py and tested only service_monitor. It was ok.
I called maas cli to check machines, Bash encountered out-of-memory (OOM) errors three times in several attempts. Strangely, it was fine when running Bash 'for' 10,000 times, but after completing or restarting it, it suddenly faced OOM errors, exhausting all memory in the VM.
With the maas api, I noticed a gradual increase in memory usage over time.
Please give me any advice how to solve this issue. I'll also check maas code if there is something I can do.
Thanks.