Re: DiscoveryMetricsProvider implementation ?

Thanks. We used a shared FS store earlier on because I believe that was the recommended configuration for large grids. On Thu, Aug 25, 2016 at 8:22 PM, vkulichenko wrote: > Hi Vinay, > > DiscoveryMetricsProvider is a different beast and it's an internal > interface > implemented by DiscoveryMana

[ANNOUNCE] Apache Ignite 1.7.0 Released

The Apache Ignite Community is pleased to announce the release of Apache Ignite 1.7.0. Apache Ignite In-Memory Data Fabric [1] is a high-performance, integrated and distributed in-memory platform for computing and transacting on large-scale data sets in real-time, orders of magnitude faster tha

[ANNOUNCE] Apache Ignite 1.7.0 Released

The Apache Ignite Community is pleased to announce the release of Apache Ignite 1.7.0. Apache Ignite In-Memory Data Fabric [1] is a high-performance, integrated and distributed in-memory platform for computing and transacting on large-scale data sets in real-time, orders of magnitude faster tha

Clearing a distributed queue hangs after taking down one node

Hi, I have come across a situation where a distributed queue hangs. My use case requires a shared queue that is populated only from the oldest node in a cluster. Then, the queue is consumed from the same node and the other nodes in the cluster (in my case only another one). Every time there is a c

Re: Deploying service programmatically hangs the app

Hi, apparently the issue we had was related to the service. It had injected some other classes that weren't serialized. In the end we relied on checking which node was the oldest to do the stuff we needed from only one node after there has been a change in the topology. Thanks. -- View this

Re: Limit on size of Apache Ignite value stored using Memcache protocol

Thanks! I will keep digging into this on my side and will follow up if any progress is made. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Limit-on-size-of-Apache-Ignite-value-stored-using-Memcache-protocol-tp7279p7351.html Sent from the Apache Ignite Users mai

javax.cache.CacheException: Failed to find mapping description

Hi, I am using Ignite 1.7 over CDH 5.8, and trying to load complete table from Hive to Ignite Cache. Error: javax.cache.CacheException: Failed to find mapping description [cache=InventoryOrdersCache, typeId=581285757]. Please configure JdbcType to associate cache 'InventoryOrdersCache' with JdbcP

Re: IgniteCompute.broadcast() stuck

It was hanging because all of our clients were stuck at the below Thread dump Name: main State: WAITING on org.apache.ignite.internal.ComputeTaskInternalFuture@3fd1be52 Total blocked: 5 Total waited: 5,975 Stack trace: sun.misc.Unsafe.park(Native Method) java.util.concurrent.locks.LockSup

Re: Local node seems to be disconnected from topology (failure detection timeout is reached)

Hello, I recoment to use failureDetectionTimeout only for test, because this timeout determines all timeout for all SPI (Communication, Dicovery). Use specific timeout of DiscoverySPI for prevention of segmentation (org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#setSocketTimeout). The config

Re: Local node seems to be disconnected from topology (failure detection timeout is reached)

The root cause of the problem just found is that the VMs are frozen sometimes. Our service team takes backup of the VMs once per day. During the backup, the VMs that our application servers are running on would be frozen for a few seconds usually, but sometimes more than 40 seconds! When I say a V

Re: LOOK THORUGH THIS ERROR

All classpaths have same jars. Any other options to cache data apart from loadCache() method?? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/LOOK-THORUGH-THIS-ERROR-tp6977p7346.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: failureDetectionTimeout NotWritablePropertyException

Hi Val, I've just upgraded Spring from version 3.1.2.RELEASE to 3.2.17, and the problem of setting failureDetectionTimeout is now gone. (I'm not upgrading to 4.1.0.RELEASE, to keep other modules in my application happy.) Thanks for your help. Yuci -- View this message in context: http://apac

Re: Spring application context resource is not injected exception while starting ignite in jdbc driver mode

Andery, It's for guarantee consistency. We should update entries in store in one transaction how in Ignite. On Fri, Aug 26, 2016 at 2:01 PM, Andrey Gura wrote: > Val, > > Why we need store on client node in case of partitioned or replicated > cache? > > On Fri, Aug 26, 2016 at 4:53 AM, vkuliche

Re: Spring application context resource is not injected exception while starting ignite in jdbc driver mode

Val, Why we need store on client node in case of partitioned or replicated cache? On Fri, Aug 26, 2016 at 4:53 AM, vkulichenko wrote: > Hi, > > This happens because JDBC driver tries to initialize the store. This is > needed for regular client nodes, but for the driver this doesn't make much >

Re: LOOK THORUGH THIS ERROR

Ravi, The exception means, what wrong jar-file hits to a classpath your application. Please, use maven or other buld to to resolve dependencies and provide example if this doesn't help. On Fri, Aug 26, 2016 at 1:17 PM, Ravi Puri wrote: > I wont be able to use maven and neither uplaod a project

Re: Spring application context resource is not injected exception while starting ignite in jdbc driver mode

Hello, At this moment Ignite support only SELECT* SQL query. You can use cache API directly for update or insert data. Ignite implements JCache API for access to data, you can look article about this[1]. [1]: http://apacheignite.gridgain.org/docs/jcache On Fri, Aug 26, 2016 at 9:32 AM, san wro

Re: LOOK THORUGH THIS ERROR

I wont be able to use maven and neither uplaod a project. But I found the class error using debugger. It was found in cache.loadCache(null,1) . During this process it throws error. Is there any other way to load cache data using IgniteCache Object. -- View this message in context: http

Re: partitions' balance among ignite nodes

Hi, blueh. Please take a look at the issue https://issues.apache.org/jira/browse/IGNITE-3018. I created partition distribution diagrams when i worked on the task. Heatmaps are attached to the issue. There are diagrams for 3, 64, 100, 128, 200, ..., 600 nodes. Pay your attention to the left

Re: why allocated containers much more than INGNITE_NODE_COUNT?

Hi, It's looks like your containers failed and ignite yarn tries to start new containers. Could you share your configurations and logs from containers? On Tue, Aug 23, 2016 at 5:18 AM, shirely wrote: > well, I tried to integrate ignite with yarn and set IGNITE_NODE_COUNT > equals > 2, but when

Re: Yarn Ignite Container Automatically exit when other yarn application running

Hi, Could you please show logs from container which was failed? On Fri, Aug 26, 2016 at 11:36 AM, percent620 wrote: > Hello, > > I faced important issues. I have deployed yarn ignite application > successfully. everything is okay. > > > But today, when others running spark job on yarn(this job

Yarn Ignite Container Automatically exit when other yarn application running

Hello, I faced important issues. I have deployed yarn ignite application successfully. everything is okay. But today, when others running spark job on yarn(this job can't contain ignite),and faced error message as below *16/08/26 16:23:52 ERROR YarnScheduler: Lost executor 1 on : Container