Re: Delay in obtaining connection to Ignite server

Hi, Thanks for the response. Will try out the suggestions provided. OS - CentOS 7. Should we look into any specific OS configuration ? Thanks Ganesh -- View this message in context:

Re: spark SQL thriftserver over ignite and cassandra

I am not sure that this will be performant. What do you want to achieve here? Fast lookups? Then the Cassandra Ignite store might be the right solution. If you want to do more analytic style of queries then you can put the data on HDFS/Hive and use the Ignite HDFS cache to cache certain

Re: Performance issues with Ignite L2 cache compared to ehcache

Hi, If you compare local ehcache and distributed Ignite, then it's not really fair. Ignite gives you the biggest improvement when you need to scale out and fit more data in memory than one computer allows. If memory of one node is enough for you, start with a single server node embedded into the

Re: Performance issues with Ignite L2 cache compared to ehcache

Hi! Could you share with us: 1) How many hosts you are using for starting Ignite? 2) How many Ignite nodes you are staring? 3) Ignite cache config. 4) Ignite version. 5) How often data changed in cache? May be Near Cache may help in your case? See [1] section "Near Caches on Server Nodes" [1]

Performance issues with Ignite L2 cache compared to ehcache

So I've got the L2 ignite cache working, confirmed with beans, logging, etc, and we're comparing it to our existing ehcache implementation. Unfortunately, so far it seems to be running far fewer operations per second than the ehcache version. However, it does seem like the timing on each cache

Re: spark SQL thriftserver over ignite and cassandra

Hi, Vincent! Ignite also has SQL support (also scalable), I think it will be much faster to query directly from Ignite than query from Spark. Also please mind, that before executing queries you should load all needed data to cache. To load data from Cassandra to Ignite you may use Cassandra store

Re: Configuring ignite distributed hibernate cache

Denis, Agree, I updated the doc. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Configuring-ignite-distributed-hibernate-cache-tp7975p8067.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Couchbase as persistent store

What is the exception now? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Couchbase-as-persistent-store-tp7476p8065.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Finding Key to Node Mapping

Alper, It has to go through discovery to know the topology. This is the heaviest part and there is no way to avoid this, at least within current architecture. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Finding-Key-to-Node-Mapping-tp7653p8063.html

Re: Two network interface on os

Hi, You can set IgniteConfiguration.localHost property to 172.10.2.1. This will force Ignite to bind only to this interface. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Two-network-interface-on-os-tp8058p8061.html Sent from the Apache Ignite Users

spark SQL thriftserver over ignite and cassandra

Hi, I am evaluating the possibility to use Spark SQL (and its scalability) over an Ignite cache with Cassandra persistent store to increase read workloads like OLAP style analytics. Is there any way to configure Spark thriftserver to load an external table in Ignite like we can do in Cassandra ?

Re: Two network interface on os

you may be setting the ip static, as follows ... 1.2.3.4 1.2.3.5:47500..47509 reference

Two network interface on os

Hi everyone, When initializing topology how can i force ignite to use one of my network interface cards. Lets say i have two interfaces eth0 192.168.1.103 eth1 172.10.2.1 I want to use only eth1. From other node when i call node.addresses() i want to get only one ip. Thanks. -- *Tolga

Re: CLUSTER GET HANGED SUDDENLY

Hi, Lockups may be caused that some locks may not be released. The discussion moved to chatter. Let community know about solution, if it you solved already... -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/CLUSTER-GET-HANGED-SUDDENLY-tp8027p8056.html Sent

Re: Unexpected flag value

Vladislav, The same exception is on the server side: 2016-10-03 16:01:14,301 DEBUG - Loaded class [cls=ru.depsy.TaskOutput, ldr=GridDeploymentClassLoader [id=982001b8751-37bc0767-6310-4473-964a-e329e88fed8b, singleNode=false,

Re: Unexpected flag value

Hi Vladislav, I have tried to 1) remove final modifiers, 2) then make the TaskOutput to be expliciltly Externalizable, The result is the same. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Unexpected-flag-value-tp8050p8054.html Sent from the Apache Ignite

Re: Unexpected flag value

Hi Dmitry, Could you please check what will be if you implement Externalizable explicitly? public class TaskOutput implements Externalizable {...} On Mon, Oct 3, 2016 at 4:45 PM, dmitry.parkhonin wrote: > It is not a response, it is a question. > > In addition to my

Re: Unexpected flag value

It is not a response, it is a question. In addition to my original question: Just before the error there are the following lines in the log: 2016-10-03 13:28:08,788 DEBUG - Received peer class/resource loading request [node=7c7ae245-d3f2-40a5-a5fb-47fb18f97501, req=GridDeploymentRequest

Unexpected flag value

2016-10-03 13:28:08,819 DEBUG - Received grid job response message [msg=GridJobExecuteResponse [nodeId=7c7ae245-d3f2-40a5-a5fb-47fb18f97501, sesId=0e5e38a8751-c03371e4-49be-4b34-947d-20022b45dee7, jobId=1e5e38a8751-c03371e4-49be-4b34-947d-20022b45dee7, gridEx=null, isCancelled=false],

Re: Is Apache Tomcat 8 supported for Web Session Clustering yet?

Hi Yakov, I have not vigorously tested it, but so far it has been working perfectly fine in Tomcat 8. Cheers, Yuci -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Is-Apache-Tomcat-8-supported-for-Web-Session-Clustering-yet-tp7824p8049.html Sent from the Apache