Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.apache.org
Date: Thu, 7 Jan 2016 05:31:07 -0800 (PST)
From: Denis Magda <dmagda@gridgain.com>
To: user@ignite.apache.org
Message-ID: <1452173467074-2433.post@n6.nabble.com>
In-Reply-To: <1452147713814-2410.post@n6.nabble.com>
References: <1452147713814-2410.post@n6.nabble.com>
Subject: Re: basic questions about apache ignite
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Ravi,

Please properly subscribe to the user list (this way we will not have to
manually approve your emails). All you need to do is send an email to =E2=
=80=9C
user-subscribe@ignite.apache.org=E2=80=9D and follow simple instructions in=
 the
reply.

Ignite has a perfect documentation hosted on readme.io that contains tons o=
f
articles on all Ignite components - [1]

In addition I would recommend to go through Ignite examples that are locate=
d
in 'examples' folder of an Ignite bundle.

Answering on your questions.

> what is node n where it stored the cache data or by which statement in
> example cache.xml(given below). or it just stores the data in jar related
> files.=20
> what is topology ?=20
> In above output what is client n servers? every time it goes to new
> command line it starts a new node how? n when the client becomes 1.?=20

When a new Ignite node is started it tries to connect to an existed cluster
using so called discovery SPI [2] that, depending on its implementation,
knows how to look for another nodes with which the cluster must be formed.

As you properly noted there are two kind of nodes in Ignite - server and
client nodes. Please refer to this article for details on the difference an=
d
specificity [3].

Ignite's topology notion is similar to a well-know network topology notion
[4]. Server and client nodes form a distributed cluster representing some
network topology. The topology may change during the cluster's lifetime: ne=
w
server and client nodes can join the cluster while the old one can leave it=
.
Every time such an event happens the physical topology and thus topology
version, you see in the logs, is changed.

Topology version's parameters, you see in the log, mean the following:
- 'ver' - current topology version. Changed automatically when a node joins
or leaves the cluster;
- 'servers' - total number of server nodes in the cluster at this time;
- 'clients' - total number of client nodes in the cluster at this time;
- 'CPUs' - total number of CPUs available.
- 'heap' - total memory available.
=20

[1] https://apacheignite.readme.io/docs
[2] https://apacheignite.readme.io/docs/cluster-config
[3] https://apacheignite.readme.io/docs/clients-vs-servers
[4] https://en.wikipedia.org/wiki/Network_topology

Regards,
Denis


--
View this message in context: http://apache-ignite-users.70518.x6.nabble.co=
m/basic-questions-about-apache-ignite-tp2410p2433.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.