Re: [Exist-open] Running eXist-db Docker containers on AWS (Winona Salesky)

[Duncan P. <du...@ex...>]

Hi Winona, 

i m afraid the topology isn’t quite clear to me yet, from your description. Are all 7 instances supposed to run permanently, or on-demand? 
Are there cross-dependencies between the containers? Do they all live on the same network? What memory arguments are you using to run the containers? What are the max and min memory allocations per container?
Are they running out of memory due to something that happens inside exist, or due to ECS memory reallocations? 
The logs you shared on slack actually look more like there is an IO issues with disk spaces, what do the logs say that make you think its memory related?

Have you tried to switch to :latest as many bug fixes are in 5.3.0-SNAPSHOT to see if the problem persists there? Are you provisioning your own base images? 

Greetings
Duncan



We are moving our eXist-db v5.2 based applications to AWS using docker and
are experiencing some performance issues.

We have an ECS cluster running two t3a.xlarge which have 16gb, each. The
ECS service/task are running on a spread deployment where it tries to load
each task/container evenly between the nodes. We are running 7 eXist-db
based docker images.

The apps all start out running fine, but eventually run out of memory,
which can cause an unclean shutdown. This seems to happen every few days.

Any help debugging our setup would be greatly appreciated.
Thank you,
-Winona

Ceterum censeo exist-db.org esse conriganda