Re: Would this be crazy?

The idea are that we will have 2 nodes per call in a telephony setup.. A primary node for external service calls and a secondary node to follow the call around the system (agent/humans).. This however can amount a lot.. On Mon, Jan 18, 2016 at 2:40 PM, Alexey Kuznetsov

Execution hangs at IgniteRDD.savePairs()

Hi All, I've created a StackOverflow post (http://stackoverflow.com/questions/34815652/igniterdd-freezes-at-savepairs) but thought I might share it here also. I have a Spark cluster of three machines and am trying to use Apache Ignite for caching data. On each Spark machine I have an Ignite

Re: Would this be crazy?

Hi, Nino! I think it is quite crazy idea to setup 1000 concurrent clusters (if I understand you correctly). Starting 1000 nodes will be quite expensive. Could you please describe what business logic you are going to implement? It is not clear for me what are you expecting from Ignite and what

Would this be crazy?

Hi We are considering using Ignite as a backend for our client / server environment (for Ignites key/value store). IT's a telephony based system, and the idea are that as a telephony CALL passes through the system Ignite nodes will follow the call adding and manipulating data. Each call would

Re: Cache.put latencies high

Hi, If you're interested in the cache loading rather than in pure benchmarking then I would suggest you using IgniteDataStreamer [1] as one of the fastest way of a cache preloading. Next if you're not going to use transaction then you can switch a cache to ATOMIC mode. It will work faster.

Re: issue with 2-node ignite server cluster

Hi, There are tons of the reasons why this can happen. When the Windows client is started does it being to use the cluster somehow? If it does then your code can lead to the failure of the server. In any case please share the logs from all the nodes from us and the source of the client code that

Re: Using Ignite

Thanks all for your responses. Will look into these alternatives. On Mon, Jan 18, 2016 at 11:24 AM, Jörn Franke wrote: > You seem to look for streaming solutions , such as Spark Streaming or > Flink Streaming or Storm > > > On 18 Jan 2016, at 17:19, Dood@ODDO

Re: How to get rid of the message( Received message without registered handler ) ?

Ignite 1.6 should be released in Q1 2016. However it's up to the community to make a decision on an actual release date. Usually a release happens when some significant feature is implemented or many bugs are fixed. However, GridGain quite often assembles its community releases, that are based on

Re: Alternate way of using DBH2ServerStartup ??

thanx now its working. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Alternate-way-of-using-DBH2ServerStartup-tp2599p2614.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Would this be crazy?

Nino, Can you please elaborate why you want to start several nodes per call in your architecture? Generally, the number of nodes is a factor of number of machines you have, in rare cases you may need to start an Ignite client per external call, however, usually it is not very effective. If you

Ignite Cache best practices

I am building an ORM/Graph Database on top of Ignite.. Just wanted to know if it is best practice on machines to close a cache after using it. Is it safe to keep a map of handles to a bunch of classes? Or should we close or bound the Ignite Caches? -- View this message in context:

Re: Using Ignite

Kafka may suit your needs as a "queue" with producer/consumer and persistence capabilities also. On 1/18/2016 9:52 AM, Murthy Kakarlamudi wrote: Hi, We have a scenario where in we have a c++ application that pumps out data ticks multiple times in a second. These data ticks needs to be

Re: Using Ignite

Hi Murthy, It looks like that you can use Ignite Streaming feature [1] with pre-configured sliding window [2] basing on what you mean under "temporarily". One of the advantages of Ignite's sliding windows is that you can query particular events using advanced SQL, text or other queries. [1]

Re: Working with Ignite Cache on Scala Play

Thanks for the inputs Alexey. From: Alexey Kuznetsov Sent: Thursday, January 14, 2016 8:22 PM To: user@ignite.apache.org Subject: Re: Working with Ignite Cache on Scala Play Avi, I think there is no need to start/stop nodes on each api

Re: TcpDiscoveryVmIpFinder's isShared property

Yakov, JavaDoc is OK, but it seems to me that the confusion is caused by the fact that setShared() method is placed on the IpFinderAdapter, while it actually makes sense only for VmIpFinder. Can we deprecate it and always return false from isShared() method for JDBC, S3 and others? -Val On Mon,

Runtime error at IgniteSpiThread

I am using Ignite 1.4.0, Xmx is set to 5G and other JVM settings like -XX:+UseParNewGC -XX:+UseConcMarkSweepGC etc are also enabled. Apache Storm cluster creates 5 client connections (client mode=true) to Ignite server (single node). We also store the incoming data to Cassandra (it is running on

Re: Ignite Cache best practices

Hi Kevin, I would say that it makes sense to call IgniteCache.close() only if you do not intend to use this cache anymore on a particular client. If you're still going to use it, it's absolutely fine to store the reference somewhere. -Val -- View this message in context:

Re: Using Ignite

Hi Denis, That kind of querying will be extremely helpful if it is supported. Because in our use case, events sitting in the cache need to be queried based on time as the criteria before it can be published to the clients. Looks like the sliding window feature fits perfectly for this. Thanks