Hi Alex,
one ignite instance per one node working good and two nodes joining the
cluster.
But when two instances started on vm, only one of the instance is joining
the cluster. Second instance logs says nothing.. no logs are rolling when
other instance is stopped/started/restarted.
We tried with
Thank you, Andrew. I appreciate the insights and will take them into
consideration when writing my persistence layer.
On Fri, Jul 14, 2017 at 5:15 PM, Andrew Mashenkov [via Apache Ignite Users]
wrote:
> Hi,
>
> 1. Ignite doesn't cate about whether persistence operations are local or
> not. It
According to the document, I copied libs\optional\ignite-rest-http to
libs\ignite-rest-http.
the libs folder is part of classpath.
and started ignite using bin/ignite.sh config/default-config.xml
And then try this:
curl http://localhost:8080/ignite?cmd=version
But it says
The requested file is n
Hi,
What is the log when you start the second node?
Why do you need heartbeatFrequency of 6 ms? Try commenting it so that
it has a default value.
Kind regards,
Alex.
On Sat, Jul 15, 2017 at 8:27 PM, Anil [via Apache Ignite Users] <
ml+s70518n14965...@n6.nabble.com> wrote:
> HI Team,
>
> I s
HI Team,
I started two ignite instances with following configuration and topology
snapshot says server = 1
Topology snapshot [ver=6, servers=1, clients=3, CPUs=32, heap=24.0GB]
*Configuration -*
Starting Ignite 2.0 data is always in off-heap meaning you can easily store
and process terabytes of data in the cluster.
Java heap is needed only for operational needs of your application (not as
data storage). Start with some value around a couple of gigabytes and
increase if the workload requir
OK .I see.
But My data is more than 80GB, and it will rise to 120G the next 3 years, and
I want to let my data always resides in off heap.
My ignite version is 2.0.
Any suggestion?
Thanks.
Lucky
At 2017-07-14 21:27:21, "Andrey Mashenkov" wrote:
Hi Lucky,
It is a bad practice to
