sandialabs/scot

activemq storage limits in Docker

ahoying opened this issue · 4 comments

Inside of docker, the default activemq configuration gives these error messages:

WARN | Store limit is 102400 mb, whilst the data directory: /opt/sandia/webapps/activemq/data/kahadb only has 5006 mb of usable space
ERROR | Temporary Store limit is 51200 mb, whilst the temporary data directory: /opt/sandia/webapps/activemq/data/localhost/tmp_storage only has 5006 mb of usable space

I updated the systemUsage in /opt/sandia/webapps/activemq/conf/scotamq.xml to the following to fix that:

      <systemUsage>
        <systemUsage>
            <memoryUsage>
                <memoryUsage limit="64 mb"/>
            </memoryUsage>
            <storeUsage>
                <storeUsage limit="4 gb"/>
            </storeUsage>
            <tempUsage>
                <tempUsage limit="1 gb"/>
            </tempUsage>
        </systemUsage>
    </systemUsage>

Thanks for finding those issues, we will will implement your fix.

Once again @ahoying great work and much thanks. 👍

I am going to leave this open until we can test that my fix works.

@ahoying if you don't mind can you check this for us as well?

=Sandy=

I've updated to the latest docker file and the changes for this and issue #3 look good. I don't think it's a problem, but the new scotmq.xml is owned by root, while the other configuration files are owned by activemq. You might include a chown as part of the install process.

The restore.sh process did take a little work, I had to copy the backup file to /opt/sandia/webapps/scot3/restore/restore.tgz for it to start, and then manually restore the scotfiles since the path in the tar didn't match up with the script, but I was able to successfully restore my database to the new docker container.

@ahoying that's great.

Yes, we are still working on persisting data outside the container. Restoring from backup falls under that as well.

I am going to pull that out into it's own issue so we can track it.