I'm not a Docker expert and we'll defer this question to the rest of the
community.
However, from an architecture perspective, what's the reason for deploying
multiple Ignite instances per container? If those instances are server
nodes than you are risking to lose them all and have data loss if the
container or host machine goes down.
In cases where Ignite is deployed in a virtual or cloud environment, it's
ideal (but not strictly required) to pin an Ignite server node to a single
host. This provides two benefits:
* Avoids the "noisy neighbor" problem where Ignite VM would compete for
the host resources with other applications.
This might cause performance spikes on your Ignite cluster.
* Ensures high-availability. If a host goes down and you had two or
more Ignite server node VMs pinned to it,
then it can lead to data loss.
-
Denis
On Mon, Jul 22, 2019 at 1:36 PM vitalys <[email protected]>
wrote:
> Hi,
>
> I am trying to run Ignite Cluster in Docker. I am running Docker Desktop
> 2.0.0.3 and I downloaded apacheignite image from Docker Hub. I am able to
> start multiple Ignite Nodes from Windows Power shell, on e container at a
> time.
>
> docker run --rm --name myignite -p 47500:47500 -p 47501:47501 -p
> 10800:10800
> -it apacheignite/ignite
>
> and every time I am running this command new Ignite Node joins the Cluster.
>
> Is it possible to run just one container and bring multiple Nodes of
> Ignite?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
