Hi Igniters:
When i using thin client binary to insert data(BinaryObjectBuilder). The
client has the following error.It seems the memory of BinaryHeapOutputStream is
not enough. How can i increase the memory when using binary to insert?
Caused by: java.lang.OutOfMemoryError: Java heap space
Hi,
Team stuck with Issue with in Ignite Cluster where in Only Single Node is able
to read data from Ignite ,other Nodes are able to write data on to Ignite ,
data is shared with other Nodes,
Below is configuration
cache.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_ASYNC);
cac
Looks like you've run out of Java heap space.
Try to increase JVM memory with Xms and Xmx options.
On Thu, Nov 25, 2021 at 11:07 AM y wrote:
> *Hi Igniters:*
> * When i using thin client binary to insert data(*BinaryObjectBuilder*). The
> client has the fol**lowing error.It seems the memory
> of
Hey,
Sorry, but I don't understand what the issue you mentioned? You are
using a transaction cache and most likely using transactions. Perhaps
you are just having design problems. Tell us more about what you are
going to achieve.
Sincerely,
Andrey
11/25/2021 11:24 AM, Gurmehar Kalra пишет:
Hey,
Let me explain Architecture
I am running 3 Ignite server nodes ,each have some services which read and
write data from Kafka and also to Ignite
all services(From all servers ) are able to read from kafka and publish it to
Ignite.(Ignite is in replication mode).
But the thread responsibl
Hi,
I think you have a singleton service that has been deployed to a random
Ignite server node. Try checking your service configuration and make
sure it contains at least the following:
svcCfg.setMaxPerNodeCount(1);
svcCfg.setTotalCount(3);
With these properties, you will have one instance
Hi,
I am not deploying any explicit service.
My Question here is if I am running 2 server nodes then both should be able to
read and write to Ignite, where as in current condition only one application
is able to read from ignite .
Ignite jar are part of Spring application which are deployed on
Hi,
Issue got resolved after adding below line of code.
ignite.cluster().baselineAutoAdjustEnabled(true);
ignite.cluster().baselineAutoAdjustTimeout(1);
Regards,
Gurmehar Singh
From: Gurmehar Kalra
Sent: 25 November 2021 23:08
To: andrei ; user@ignite.apache.org
Subject: RE: Ignite
probably this is the case: https://issues.apache.org/jira/browse/IGNITE-15990
>
>Hello Denis,
>Yes, as I said in the original message we do use the expiration on persistent
>caches.
>The corruptedPages_2021-11-08_11-03-21_999.txt and
>corruptedPages_2021-11-09_12-43-12_449.txt files were
