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

Apache Ignite Issue Under ECS Fargate #11871

Open
vigneshkumarpr opened this issue Feb 13, 2025 · 0 comments
Open

Apache Ignite Issue Under ECS Fargate #11871

vigneshkumarpr opened this issue Feb 13, 2025 · 0 comments

Comments

@vigneshkumarpr
Copy link

I am running the Apache Ignite Server in a Docker Container and have mounted a location to stored cached data.

Step 1:

I started the service using below command

docker run -d --name ignitedocker -p 10800:10800
-v /home/user/Documents/ignite_second/data:/opt/ignite/data
-v /home/user/Documents/ignite_second/wal:/opt/ignite/apache-ignite/work/db/wal
-v /home/user/Documents/ignite_second/wal/archive:/opt/ignite/apache-ignite/work/db/wal/archive
-e IGNITE_FORCE_RECOVERY_MODE=true apache/ignite:apache-ignite-2.16.0-0.4

Apache Ignite service is up and running

Step 2 :

If I execute the below commands.

docker stop containerId and
docker start containerId

still I am able to retrieve the cached data using Apache Ignite. Reason being same container and container Id is being used.

Step 3:

However, when the Docker container ID changes (When we are removing/deleting the container and creating the new container pointing to same cached location ), we are unable to retrieve the cached data, even though Apache Ignite is running.

Are there any limitations or issues when using different Docker container IDs? Does Apache Ignite have tight coupling with docker containers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant