Re: Data Region Concurrency

It does appear that if the global concurrentLevel is not set, that it defaults to # CPUs not 4 * # CPUs as documented here https://apacheignite.readme.io/docs/memory-configuration#section-global-configuration-parameters private long[] calculateFragmentSizes(int concLvl, long cacheSize,

Re: Need clarification on redeploy behavior

Yes I understand it now ( I found the solution to this actually ... Following work : In case if service failed to deploy for some reason for example because there is no eligible nodes . Running cancel for service and then deploy again with same config will trigger the cycle again and actually

Re: Clarification regarding nodeFilter

Thank You. The issue is that I want to extend the notion of service failures beyond simple node failure/topology change scenarios. I already have per Ignite service health check that runs custom health check on service and redeploys it if necessary obviously this is my custom implementation.

Re: Need clarification on redeploy behavior

Hi, There is no force deploying/undeploying possibility as I know. As was mentioned in another your question: http://apache-ignite-users.70518.x6.nabble.com/Clarification-regarding-nodeFilter-td21671.html Node filter predicate should be stateless and should always return the same value for the

Re: Clarification regarding nodeFilter

Hi, Please take a look at my answers below: 1)Yes. Node filter should be run only on coordinator node after reassignment process. It could be executed several times and possible that Ignite instance can be uninjected. All this behavior should be documented as well as for me. 2) Node filter

Re: NPE from the native persistence enable node

I have a similar issue. If I run local, two nodes connected via TcpDiscoveryMulticastIpFinder it works fine. But when I run o Kubernetes where the same two nodes are connected by TcpDiscoveryKubernetesIpFinder Ignite throws those errors. I have a test SQL table created: CREATE TABLE TEST (KEY

Data Region Concurrency

We have a 2.4 ignite peristence cluster on AWS with 8 i3.xlarge nodes, where the default memory region size is 160GB.When loading a large amount of data through a custom StreamReceiver, over time we see the throughput decrease, as well as network and SSD I/O, and one node with higher CPU usage

Re: Clarification regarding nodeFilter

It explains a lot I thought that I am missing something in the docs ( So this is indeed what I see as it executed on the node where the services are running I think you call it coordinator. So this behavior is correct it's just need to be fixed in documentation ? So is there a

Re: Clarification regarding nodeFilter

Hi, Indeed there is some unexpected behavior of the how it documented and how it works. I filed next issues related to service/cache deploying with node filters: https://issues.apache.org/jira/browse/IGNITE-8629 - There is no documentation about what on which node Ignite Predicate will be

Re: What is the expected ETA for the 2.5.0 release...

Hello Paul, The voting has already been started. Please take a look at this topic: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-5-0-RC1-tc30923.html So, I assume AI 2.5 will be released soon. Best regards, S. 2018-05-28 17:10 GMT+03:00 Paul Anderson

What is the expected ETA for the 2.5.0 release...

... hours, days or weeks? sorry to be a pain

Re: Support for polymorphic SQL Queries

Have you tried just use QueryEntity, as always? [1] - https://apacheignite.readme.io/docs/cache-queries#section-query-configuration-using-queryentity Best Regards, Igor On Tue, May 22, 2018 at 10:50 PM, ttlir wrote: > Yes, all models are stored in the same cache. > > > >

Re: Re: Nodes can not join the cluster after reboot

I'd recommend to set it on all nodes. Evgenii 2018-05-24 12:19 GMT+03:00 arunkjn : > Hi Evgenii, > > I am experiencing the same issue with grid affinity topology. > > We have a topology where we have 3 data nodes, 2 service nodes and several > client nodes in the cluster. The

Re: ignite c++ support service grid?

Ignite C++ does not support service API, so no, currently it is not possible. Best Regards, Igor On Mon, May 28, 2018 at 4:59 AM, wangsan wrote: > From the doc https://apacheignite-cpp.readme.io/docs > , I did not find any service