Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

local install validator, heap size doesn't impact allocated RAM #1125

Closed
joey-geoloog opened this issue Oct 16, 2024 · 1 comment
Closed
Labels
deployment This issue is about the deployment of the Docker image, WAR file or operational environment

Comments

@joey-geoloog
Copy link

Confirm:

Following the deployment guide for INSPIRE validator and referencing to the docs for ETF. Can't upload files as the status shows there is too little memory assigned even when this is declared explicitly at the commandline.

Tried forcing heap size both at commandline -Xmx12G and in [etf-home]/bin/setenv.bat

set "JAVA_OPTS=%JAVA_OPTS% -Xmx12G"

No matter what I do the available RAM is always under 512 MB. I've tried calling java via powershell, in a batch script, in cmd on its own, doesn't make any difference. We've checked and there is no quota provisioning for the user and I have full admin rights.

Adding -Xms8G doesn't change this either.

{
    "name": "INSPIRE Reference Validator",
    "status": "MAJOR",
    "heartbeat": "1729091246693",
    "willExpireAt": "1729091286693",
    "version": "unknown",
    "uptime": "44",
    "allocatedMemory": "193617016",
    "presumableFreeMemory": "65905544",
    "totalSpace": "53683941376",
    "freeSpace": "37486125056",
    "cpuLoad": "0.005849",
    "messages": [
        "Less then 512 MB RAM available"
    ]
}

Would greatly appreciate any advice or insight here on what else it might be!

Thanks, Joey

@joey-geoloog joey-geoloog changed the title local install validator, local install validator, heap size doesn't impact allocated RAM Oct 16, 2024
@fabiovinci fabiovinci added the deployment This issue is about the deployment of the Docker image, WAR file or operational environment label Oct 17, 2024
@joey-geoloog
Copy link
Author

@jenriquesoriano we are going to deploy this via docker as we just can't get the local install to work and it's cost far too much time and energy trying to. thanks anyway, will close this ticket.

@joey-geoloog joey-geoloog closed this as not planned Won't fix, can't repro, duplicate, stale Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deployment This issue is about the deployment of the Docker image, WAR file or operational environment
Projects
None yet
Development

No branches or pull requests

3 participants