XOA - Memory Usage

acebmxer

@Pilow
Yeah I was following your post. At first I thought i was having random backup issues with backups via proxies with the occasional issue with backups via xoa. Then just yesturday see the error about memory.

For now I just rebooted XOA and it down under 2gb currently. Will wait and see how long for it to build back up again or untill Dev team finds a solution to the problem.

flakpyro

Looks like the issue still persists in 6.3.1?

Here is since installing the latest update yesterday:

Pilow

@flakpyro yup still aggressive on memory consumption
I have a task that reboots XOA & XOPROXIES every two days to mitigate

since 6.3 / 6.3.1 it seems more aggressive on the ramp up (I updated just yesterday... was still on 6.1.2)

olivierlambert

Adding @Team-XO-Backend in the loop

MathieuRA

@acebmxer
Hi, we've detected a memory leak at the REST API level.
We pushed a fix on the branch: mra-fix-rest-memory-leak
Can you test the branch?

acebmxer

@MathieuRA

I have been busy at work. I will try to test this branch out when i get home tonight.

Looking back on this. This was related to XOA at work not XO from sources.

I have also changed up our back up process and this has no longer been an issues for me.

florent

@acebmxer do you know what you did change on the backups ?

acebmxer

@florent

We have allways been a veeam customer since vwmare. I have moved over to the beta version of veeam for our windows servers.

XOA is only backing up our linux servers. So half the workload was removed from backups.

acebmxer

Well i guess i should not have said anything. Backups have been running fine until tonight. Well technically last night. Got email alter that a backup job failed because job already running. This is one of my remote pools. But took a look at the memory usage in XOA..

9 total vms across 3 pools/locations. 3 vms at the remote site get backed up.

The proxy at the remote site.

If you want i can create a support ticket.