Re: Issue with querying from cache

Regarding Payroll, I had changed Payroll to tableB but missed to change it there. That is not an issue. I tried querying using cache_name.table_name but still it is not working. Please let me know if you need more inputs on this so that I can get some resolution. -- View this message in contex

Re: Deadlock during Client Continuous Query deserialization

Guys, here are my comments. As far as ticket filed by Sam. If reads are paused at some point they should get unpaused when incoming message queue gets shorter. The issues's description makes me think that Ross has very heavy logic in the listener, so notification processing takes too long. Ross,

Re: Deadlock during Client Continuous Query deserialization

Hi Yakov, You can see in the example I have provided that the only thing we try to do in the listener is to print the event to the console log. In our other code I attempted to pass the event off to another thread in order to get off the notification thread and see if that unblocked it, but this wa

Re: Deadlock during Client Continuous Query deserialization

Ross, Deserialization may be heavy. When you deserialize object Ignite implicitly goes to some internal caches to get metadata of the type. This explains why your example works when you skip deserialization. I am not sure whether 2000 is a lot or not. For me even 1 cont query bringing all the upd

Re: Deadlock during Client Continuous Query deserialization

Sure, our cluster is much smaller (2 servers, 6 clients). I guess it's not quite clear to me when/where Ignite is still storing data in the Binary Object format. Is it in this format for all Caches, or only those with withKeepBinary? Does ignite keep a Binary Object form, and a deserialized form to

Implementing a distributed crawler

Hi, I'm in the process of evaluating Ignite for use in an experimental distributed web crawler. I would like to avoid a master/worker architecture, and instead have each node pulling URLs to crawl from a distributed Queue - which is populated by the crawler instances themselves. Ignite's queue se

Re: Load data from Hadoop

Hi Vladimir, I have remote data source which produces files with data once a day. I load this data to hadoop cluster. I must provide this data to users, and also I need to process this data for a long period (90 days from current moment) and make cache with integrated data. Users want to get raw

Re: Error when trying to configure web session clustering

I get basically the same error on Wildfly server. 08:41:23,677 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC01: Failed to start service jboss.deployment.unit."tc.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."tc.war".POST_MODULE: WFL

Re: Load data from Hadoop

Hmm this would require more details. You can, for example, use ignite as a HDFS cache for hive and hive (minimum 1.2) +tez +Orc as the SQL layer. This is probably one of the most fastest way currently available. However, this depends on your use case. > On 01 Aug 2016, at 14:45, Labard wrote:

Re: Issue with querying from cache

Issue got fixed. I have set Index type in my code which was not matching my Class type. Thanks for the help. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Issue-with-querying-from-cache-tp6588p6658.html Sent from the Apache Ignite Users mailing list archive at

Re: 2PC & local storage

Hi Ionut, In this scenario 2PC will work in a different way if to compare to a shared DB case. A transaction coordinator won't commit data to a local store from its side. This will be done on primary and backup nodes at commit phase. The data will be committed to the local storage before and if th

Re: Rest-api: Returning no reply from server

Thanks. It is working now. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Rest-api-Returning-no-reply-from-server-tp6561p6660.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Server nodes unble to discover each other in Apache Ignite

Hi, Please try removing the address without the port number and leave only the one that specifies the port range: ipFinder.setAddresses(Arrays.asList("192.168.0.3","192.168.0.3:47100..47120")); -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Server-nodes

Re: Ignite Cluster node stopped

Hi, Generally, 60GB is too much. Can you try to give about 10GB of heap and switch caches to off-heap mode [1]? [1] https://apacheignite.readme.io/docs/off-heap-memory -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cluster-node-stopped-tp6608p6662

compute best practices / examples

I'm running some tests and wondering what should be provided by closure state, and what should _not_ be. For example, if I'm going to "broadcast" to the cluster - should my closure create Ignite-related objects like the caches/queues or should each of the node runnables create those explicitly? Wha

Re: compute best practices / examples

Hi, I would not recommend to serialize instances of Ignite, IgniteCache, IgniteQueue, etc. This is supported, but provides unnecessary overhead. You can always inject Ignite into your job using annotation: @IgniteInstanceResource private transient Ignite ignite; -Val -- View this message in