Re: Transaction operations using the Ignite Thin Client Protocol

Igor, Could you please elaborate whether C++ thin client is going to have transactions support in 2.8? AFAIR, it was implemented only for Java thin client. пт, 29 нояб. 2019 г. в 18:29, Stephen Darlington : > > The ticket says “Fix version: 2.8” so I would assume it would be available > then.

Primary Entry Count are not correct in cache

Hi I have created a cache with following configuration. I started four nodes,each node on different machines. I have loaded this cache with loader. Issue: I am not performing any operation on this cache but I am able to see the primary key count not constant. Its keep on changing after some time.

Re: Transaction operations using the Ignite Thin Client Protocol

The ticket says “Fix version: 2.8” so I would assume it would be available then. Currently planned for late January. > On 29 Nov 2019, at 13:58, dkurzaj wrote: > > Hello, > > Since this improvement : https://issues.apache.org/jira/browse/IGNITE-9410 > is resolved, I'd assume that it is now

Re: Transaction operations using the Ignite Thin Client Protocol

Hello, Since this improvement : https://issues.apache.org/jira/browse/IGNITE-9410 is resolved, I'd assume that it is now possible to do SQL transactions using the C++ thin client, though I'm not sure it is yet since I did not find documentation about that. Would someone happen to know more about

Re: Improving Get operation performance

Hello! Not if there's enough parallelism, since nodes are not busy while requests do round trips. I recommend gathering jstack stack traces from all nodes, seeing what threads are up to. Regards, -- Ilya Kasnacheev чт, 28 нояб. 2019 г. в 21:58, Victor : > Not sure i follow. The data is on

Re: can't use "cache -a "command , warn info is " the cluster is inactive"

Hello! You have to activate your cluster, by doing something like bin/control.sh --host 172.17.122.126 --activate This is a requirement on the first start of persistent cluster, after all nodes has joined. Regards, -- Ilya Kasnacheev пт, 29 нояб. 2019 г. в 11:34, ?青春狂-^ : > because of the

can't use "cache -a "command , warn info is " the cluster is inactive"

because of the program'Exception, I wanted to see the cache infos. so I use the ./ignitevisorcmd.sh command. then I use "open -d" and "cache -a" but it print warn info : [WARN ] Can not perform the operation because the cluster is inactive. I have 3 nodes of ignite ,and process is alive.