Re: Ignite in docker (Native Persistence)

This is the ECS task we use to create the container. Caveat: we have a custom docker image with some enhancements to run.sh. Especially around consistent ID and what we call Autobaseline, and support for AWS instance storage (Ignite persistence is useless for us with EBS/GP2). I'll generate a pu

Re: Ignite in docker (Native Persistence)

See attached, which we use in our AWS ECS containers. Note that beside WAL and data, the work directory needs persistence, because it has all the typeID mappings. On Tue, Dec 18, 2018 at 7:32 AM Павлухин Иван wrote: > Hi Rahul, > > Could you please share an ignite configuration and how do you l

Re: Ignite in docker (Native Persistence)

Hi Rahul, Could you please share an ignite configuration and how do you launch a docker container with Ignite? Do you see something in your ignitedata/persistence ignitedata/wal ignitedata/wal/archive after container stop? I guess you can configure a consistentId by configuring IgniteConfiguration

Re: Ignite in docker (Native Persistence)

Hi All, I followed following steps for persistence in docker but i am observing that cache is not retained after restart. From documentation i see that consisitentID need to be set to retain cache after restart but i am not sure how it can set in configuration xml file. Any help is greatly appreci

Re: Ignite in docker (Native Persistence)

Nick, Excellent, here is a ticket! Please reassign it on me once you complete with the doc: https://issues.apache.org/jira/browse/IGNITE-7132 — Denis > On Dec 7, 2017, at 3:57 AM, Nikolai Tikhonov wrote: > > Hello! > > Yes, sure! I'll investigate this question and update our doc. > > On Thu

Re: Ignite in docker (Native Persistence)

Hello! Yes, sure! I'll investigate this question and update our doc. On Thu, Dec 7, 2017 at 9:57 AM, Denis Magda wrote: > Nick, > > As one of Ignite docker maintainers, could you please investigate one how > to map Ignite persistence to docker volumes: > https://docs.docker.com/engine/admin/vol

Re: Ignite in docker (Native Persistence)

Nick, As one of Ignite docker maintainers, could you please investigate one how to map Ignite persistence to docker volumes: https://docs.docker.com/engine/admin/volumes/volumes/#use-a-read-only-volume and update the

Re: Ignite in docker (Native Persistence)

Hi, You need to create volumes and map them to the ${IGNITE_HOME}/work/db or any other path that you might have specified via setPersistentStorePath. These volumes should outlive the Ignite containers and thus it will be possible to reuse them on restart. It's worth trying docker-compose, docker-

Ignite in docker (Native Persistence)

Has anyone use Ignite Native Persistence with Docker? Is there a solution on how to map the Volume dynamically? And how about when you restart the whole cluster, how does it maps all volumes? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/