Re: Does Ignite message support C++?

2019-01-13 Thread summasumma
hi all, Can you please clarify if Ignite C++ CLIENT(both thin and thick/normal) supports following: 1. Async read/insert/update/delete operations (from our application we will send a read request asynchronously, and once the Ignite server responds back we should get notification on the

Re: Web Console set up

2019-01-13 Thread newigniter
Worked. Tnx :) -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Abnormal termination of nodes with native persistence enabled

2019-01-13 Thread 李玉珏
Hi, The console log is as follows: But if all nodes are killed, all nodes can start successfully, and the data is normal. Only after a single node fails, it can not join the cluster when it starts again. thanks! -log start--

Ignite Data Streamer Kafka version 2.0

2019-01-13 Thread Mahesh Nair
Hi, I am trying to stream some data from a few kafka topics to an Ignite cache using the ignite data streamer. I was using ignite version 2.6.0 and kafka version 0.10 and that was working fine. Now we have upgraded the kafka version to 2.0 and the streamer has stopped working. I understand with

unsubscribe

2019-01-13 Thread Mimmo Celano

Re: Baseline Nodes not able to join the cluster

2019-01-13 Thread Manu
Hi! You need one work directory (not only wal) for each server node. If you have persistence enabled, once server nodes start, you need to activate cluster: ignite.cluster().active(true) this creates a cluster baseline topology. Please note that once cluster is activated, if you add a new

Concurrent merge into operations cause critical system error on ignite 2.7 node.

2019-01-13 Thread yangjiajun
Hello. I have a ignite 2.7 node with persistence enabled.I test concurrent merge into operations on it and find below concurrent operations can cause critical system error: 1.Thread 1 executes "merge INTO city2(id,name,name1) VALUES(1,'1','1'),(2,'1','1'),(3,'1','1')". 2.Thread 2 executes "merge

Re: Ingite deploy in AWS

2019-01-13 Thread newigniter
Its a while from this thread but I am having the same issue. I host configuration file on S3 bucket. First I added this bucket to be publically accessible and everything works correctly. I simply pass https://s3.amazonaws.com/... link to my docker run command when I start ignite(I am using docker)