BinaryMarshaller unmarshal error

During deploy a service, my ignite nodes failed with exception message class org.apache.ignite.IgniteCheckedException: Unknown pair [platformId=0, typeId=1421882438] at org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9867) at

Re: Tips for implementing unit tests using Ignite.Net

Hi Raymond, Try disabling assembly shadow copy in the test runner settings, this is the most common issue. If this does not help, please provide more details about the errors you get. Pavel 14 дек. 2017 г. 1:34 пользователь "Raymond Wilson" < raymond_wil...@trimble.com> написал: I have a

Re: Memory configuration change from 80%(Ignite 2.1) to 20%(Ignite 2.3)??

Hi everyone.and I also have a question about this, I am using on-heap cache,is this memory configuratin has affect only off-heap caches?. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Memory configuration change from 80%(Ignite 2.1) to 20%(Ignite 2.3)??

Hi Ignite community, In 2.1 version document, it says "By default, Ignite nodes consume up to 80% of the RAM available locally, and in most cases this is the only parameter you might need to change. " https://apacheignite.readme.io/v2.1/docs/memory-configuration In 2.3 version document, it says

Node can not join cluster

Hi, There is a cluster with 4 nodes, When I add a node to join this cluster, It failed. Here is the trace: [09:06:11,090][INFO][main][IgniteKernal] Config URL: file:/home/ignite23/config/default-config.xml [09:06:11,090][INFO][main][IgniteKernal] Daemon mode: off

Re: Ignite yarn cluster deployment

Nick, I think you’re a right person to help here. Please let me know if the documentation has to be updated. — Denis > On Dec 13, 2017, at 8:53 AM, Andrey Yatsuk wrote: > > Here: https://apacheignite-fs.readme.io/docs/installation-deployment >

Re: memory usage in 2.3

Shawn, good to hear this, Just in case here is you can find some tips and tricks on memory and garbage collection tuning for Ignite: https://apacheignite.readme.io/docs/durable-memory-tuning https://apacheignite.readme.io/docs/jvm-and-system-tuning — Denis > On Dec 12, 2017, at 10:50 PM,

Tips for implementing unit tests using Ignite.Net

I have a Visual Studio solution with some implementation that uses Ignite.Net and also a collection of unit tests. When I try to run a unit test that uses an Ignite capability I run into issues where the unit test fails with an unexpected error when executing a line like this:

Re: Failed to instantiate Spring XML application context

Hi Alex, Can you please tell me which jar is missing? If i remove the below then it's running perfectly. So i guess there is some issue with this portion. ONHEAP_TIERED"/> On Wed 13 Dec, 2017, 22:47 afedotov, wrote: > Hi, > > Looks like you don't have

Re: Failed to instantiate Spring XML application context

Hi, Looks like you don't have required Ignite libs on your classpath. Please check your classpath for its presence. Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: why the records not zero after execute "cache -clear"

Hello, I was not able to reproduce the problem on my side. Could there be a chance that you had stopped a server node with persistence before calling cache -clear? Is the problem reproducible? How do you stop nodes? Is it kill -9 or something else? Please share Ignite configuration used for

RE: Ignite yarn cluster deployment

Here: https://apacheignite-fs.readme.io/docs/installation-deployment I found “Embedded Deployment” section where is it written: Embedded deployment means that Apache Ignite nodes are started inside Apache Spark job processes and are stopped when job dies. There is no need for additional

Re: javax.cache.CacheException: Failed to run map query remotely.

Hi Alex, Sorry there was a mistake on my end that's why it was failing. I fixed it and now it's working. Thanks, Raj On Wed, Dec 13, 2017 at 5:18 PM, afedotov wrote: > Hi Raj, > > Provided is only the top of the reason, there should be more details > regarding

Re: PHP and Apache Ignite - very slow query

Ok, thank you for reply. Now I understand where is mistake. See you soon :) -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Cache Data Not Available in Other Server Nodes

Cache API doesn't have method with this signature. Also I don't see sense to insert into cache the same entry many times. :) I think that you try to get entries that are not presented in the cache. Execute Scan Query [1] over the cache and look at what really the cache contains. 1.

Re: IGNITE-4862

Hello! I will make sure this ticket gets merged after tests, since its code seems to be OK. This way it will make into the next version, in the meantime you can try the patch yourself, write your feedback if something goes wrong. Regards, -- Sent from:

Re: TcpCommunicationSpi : IgniteCheckedException: Failed to connect to node

Looks like you have some communication problems, since on the address 172.16.100.57:47100 node see not needed node. Please share logs from all nodes, it will help to understand a problem. Evgenii 2017-12-13 13:45 GMT+03:00 golgoti : > Hi there, > > We do have an app with 4

Re: queryParallelism in server XML

Hello, Yes, there is a limitation: this parameter is supported only for partitioned caches. Moreover, all PARTITIONED caches participating in the same query should have the same queryParallelismLevel. Thanks! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: PHP and Apache Ignite - very slow query

Also, please see for example this [1] article on why offset can be slow and can cause troubles (especially in a distributed system) [1] http://use-the-index-luke.com/no-offset Best Regards, Igor On Wed, Dec 13, 2017 at 9:12 AM, bagsiur wrote: > ok, I will try to

Re: Cache listener for new keys

I mentioned continuous queries and listener filters because you probably have some logic around keys that could be handled by these means. As an option, you could utilize Ignite messaging. Of course, you could have a separate cache containing only keys that you would update. Could you describe

TcpCommunicationSpi : IgniteCheckedException: Failed to connect to node

Hi there, We do have an app with 4 Ignite nodes (2.1) deployed under K8s, here are our pods with their IP : NAME READY STATUSRESTARTS AGE IP NODE ceph-2949468122-8mwmh 1/1 Running 0 56m 172.16.99.196

Memory foot print of the ignite nThe background cache eviction process was unable to free [10] percent of the cache for Context

HI am using 2.3 Doing PT for a service exposed thru REST Here is a node stats for cache called Customer, which has 10M and s nodes as part of the cluster, so each node is storing 3.3M odd records, which are on off-heap. Cache 'Customer(@c1)':