Re: Problem of datastorage after compute finished

2018-04-13 Thread Michael Jay
Really appreciate for your reply, Andrei. Now I understand why the result didn't store on the same node where it was calculated. I will try your suggestions. But there still remain a problem that job b,d,f were calculated on Node_B, the results were lost. No partitions store these jobs' results.

Re: Problem of datastorage after compute finished

2018-04-13 Thread aealexsandrov
Hi Michael, As I see from your configuration you are going to have cluster with two ignite servers and PARTITIONED cache. You can't choose directly on what node will be stored your cache entities because ignite will use its own affinity function that will maps keys to partitions (not nodes). In

Problem of datastorage after compute finished

2018-04-13 Thread Michael Jay
Hi, all! I am trying to use the computegird of ignite to do some compute job, but I met a problem. I started two server nodes(different host) to form a clustergroup. Node_A was started by eclipse, Node_B was started by ignite.cmd, two nodes had the same configurations except heap size(Node_A