Hi,
I had read many times about Ignite Data Grid's fault tolerance, like below
sentence...
-
Regardless of which caching mode is used, Ignite guarantees data consistency
across all cluster members, regardless of various failure conditions.
---
Hi Steve,
In general this is exception is harmless and it won't affect consistency of
caches or stability of the cluster.
However it's interesting why it happens. Do you process SIGTERM using a
shutdown hook in your? Do you call Ignite.stop() for every node or how do
you stop Ignite cluster?
Reg
I observe this exception when my application hosting an Ignite cluster is
shutdown (normal JVM termination, via SIGTERM):
2016-02-20T21:55:49.266+ [Thread-5] ERROR IgniteKernal%SOMOS_EN_FUEGO []
- Failed to pre-stop processor: GridProcessorAdapter []
javax.cache.CacheException: class org.apac
btw, do you have the same issues on starting a basic Ignite setup (without
stream processing)?
Can you share your /etc/hosts and the server log with more details
(particularly "TcpDiscoveryNode" parts)?
With this information, I think you can get some more advice.
-Roman
On Monday, Februa
Hi Saurabh,
As a quick fix, will setting "-Djava.net.preferIPv4Stack=true" help?
-Roman
On Sunday, February 21, 2016 10:50 PM, Saurabh Sharma
wrote:
Hi,
I am reading streams from Kafka topic (using ConsumerConnector with a thread
count 4). I observed that stream processing is very sl
Hi,
I am reading streams from Kafka topic (using ConsumerConnector with a thread
count 4). I observed that stream processing is very slow and sometimes I am
getting following exception. Could you please let me know what could be the
reason of this slow processing.
I am trying to read a log fil
Hi Vladimir,
Sure. I am up for any assistance to make Ignite better.
I shared server configs and stacktraces in previous communications. I will
try my best to replicate this issue again. If i could find exact steps
then i will try to write a test case for simplification.
It may take some time f
