Re: Can't write to Ignite cluster when one node in baseline is down

2018-08-22 Thread ezhuravlev
Hi, It's ok for the case when you run without backups, because you lose partitions here. Do you start a new cache each time or reuse the cache from the different run? When you use persistence, Ignite persists cache's metadata on disk and if you change cache configuration after that, these

Re: Can't write to Ignite cluster when one node in baseline is down

2018-07-25 Thread Ray
Hi, I tried two cases for backup, which is backup=1 and no backup. Both cases failed with the exception I attached. I'm sure all 3 nodes are in baseline. I checked using ./control.sh --baseline command. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Can't write to Ignite cluster when one node in baseline is down

2018-07-25 Thread Evgenii Zhuravlev
Hi, Do you have configured backups for the cache? Are you sure that all 3 nodes in baseline? Could you check it using control.sh tool? Evgenii 2018-07-25 11:23 GMT+03:00 Ray : > I'm running a 3 node Ignite 2.6 cluster with persistence store enabled. > > I tested this following use case. > > 1.

Can't write to Ignite cluster when one node in baseline is down

2018-07-25 Thread Ray
I'm running a 3 node Ignite 2.6 cluster with persistence store enabled. I tested this following use case. 1. Start all three nodes. 2. Activate the cluster 3. Stop one of the node 4. Start ingesting data But I got following exception in step 4. class

Re: Can't write to Ignite cluster

2018-07-16 Thread Ray
Hello Pavel, I have found out why the topology version keeps increasing. It's because my colleague created a customized Ignite monitor system which will fetches metrics from Ignite visor. And this monitor system will launch a Visor client connects to the cluster every minute, after fetching all

Re: Can't write to Ignite cluster

2018-07-16 Thread Pavel Vinokurov
Ray, As I see from following logs: 18/07/13 01:33:18 WARN cache.GridCachePartitionExchangeManager: >>> GridDhtPartitionsExchangeFuture [topVer=AffinityTopologyVersion [topVer=25309, minorTopVer=0], evt=NODE_JOINED, evtNode=TcpDiscoveryNode [id=0caad476-3652-453f-8fc8-e8880c12eea9,

Re: Can't write to Ignite cluster

2018-07-15 Thread Pavel Vinokurov
Hi, It looks pretty strange such topology version increasing. Would you be able to show how do you launch the cluster and use the datastreamer. Thanks, Pavel 2018-07-13 9:50 GMT+03:00 Ray : > Here's the full log and thread dump for three nodes and client to ingest > data. > > node1.zip >

Re: Can't write to Ignite cluster

2018-07-13 Thread Ray
Here's the full log and thread dump for three nodes and client to ingest data. node1.zip node2.zip node3.zip

Can't write to Ignite cluster

2018-07-12 Thread Ray
I'm running a 3 nodes Ignite 2.4 cluster. After some time, I can't write to this cluster using datastreamer. Here's the log snippet. [2018-07-12T09:31:05,839][ERROR][srvc-deploy-#179][GridServiceProcessor] Error when executing service: null org.apache.ignite.IgniteException: Failed to resolve