Re: How many nodes within your ignite cluster

Hi Duke, I think, Ignite should be cope with any issue. For example: looped thread which does not handle flag of interrupted. But you always can to try do that, by way implement your segmentation behavior. Something like this: ignite.events().localListen(new IgnitePredicate() { @Override

Connection Cleanup when IgniteCallable Killed

All, I currently broadcast an IgniteCallable in my cluster which opens connections to various resources, specifically Zookeeper via Apache Curator. If the originating node (the client that launched the IgniteCallable) is stopped prematurely I see that Ignite will rightfully cancel the broadcast

Re: Hive job submsiion failed with exception ”java.io.UTFDataFormatException“

Hi，Andery： Thanks for your attention, but I tried use “OptimizedMarshaller” and "JdkMarshaller", but it did not work. I use the ignite version 1.6, and do I need to upgrade to 1.7? Or how can I modify the limitation of the ObjectOutputStream. Thanks. -- View this message in context:

Re: How many nodes within your ignite cluster

Hi vdpyatkov, Finally, I figured out not only one but all nodes become segmentation due to unknown VMWare infrastructure. I changed failuredetectiontimeout/sockettimeout/networktimeout, and the cluster survived last day, need more time to observe their behavior. I'm thinking

Visor console

Hi, Is it possible to deploy the visor console in a embedded manner? I mean just including the visor dependencies into an application classpath and launch it? Is there any example of that? Cheers, Paolo

Re: Multiple servers in a Ignite Cluster

Hi Vlad, The ideal work flow for my use case is: I host two clusters, one is computation cluster that run Spark jobs, the other is data cluster that host Ignite node and cache hot data. Then at the run time, multiple Spark jobs share this data cluster and query it. The problem I have is, I am

Re: Hive job submsiion failed with exception ”java.io.UTFDataFormatException“

Hi lapalette, There is a limitation in ObjectOutputStream, it fails to write UTF strings longer than 65k bytes. Have you try to use another marshaller? https://ignite.apache.org/releases/1.7.0/javadoc/index.html?org/apache/ignite/marshaller/Marshaller.html On Thu, Nov 10, 2016 at 6:20 AM,

Re: One server node seems to hang onto heap memory after clear

Hi, If your caches are off_heap, these do not consume heap basically. Could you please, get heap dump and try to provide briefly analyze, which object consume heap? -- View this message in context:

Re: rest-http can't get data if key is Integer or others

Hi Victor, Please have a look at our contribution guidelines: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute * You are writing to user list, but this discussion should be on the dev list (d...@ignite.apache.org) * Pull request name should include JIRA ticket (IGNITE-4195) *

Re: ignite-spring conflict

It looks like, now you run out of memory. You can try to increase heap memory size. Please, attach full stacktrace, so one can see if there is another possible issue. On Thu, Nov 10, 2016 at 11:54 AM, ewg wrote: > Yeah, that was the problem. We use spring.version

Re: Ignite with cassandra

Hi, i think it problem related to cassandra configuration or network, check you firewall. You can try change cassandra configuration and enable port 9160 for using. Also check which version cassandra-jdbc driver using, different version use different ports. -- View this message in context:

Re: Very high memory consumption in apache ignite

Cache configuration I have used is, CacheConfiguration ccfg_order_line = new CacheConfiguration<>(); ccfg_order_line.setIndexedTypes(order_lineKey.class, order_line.class); ccfg_order_line.setName("order_line_cache"); ccfg_order_line.setCopyOnRead(false);

Re: Very high memory consumption in apache ignite

Hi, could you please provide your final jvm options and cache configuration? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Very-high-memory-consumption-in-apache-ignite-tp8822p8879.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Jdbc connection

Any help in understanding below ? On 10 November 2016 at 16:31, Anil wrote: > I have couple of questions on ignite jdbc connection. Could you please > clarify ? > > 1. Should connection be closed like other jdbc db connection ? - I see > connection close is shutdown of

Re: What's the difference between EntryProcessor and distributed closure?

Hi Tracyl, You can use "invoke", the method will be most effective for retrieve part of value from cache. For the withKeepBinary off_heap cache "invoke" takes lock on entry and can to manipulate with off_heap pointer wrapped on BinaryObject. -- View this message in context:

Re: rest-http can't get data if key is Integer or others

Hi, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. Could you please provide test for reproduce issue? And i

Re: How many nodes within your ignite cluster

Hi Duke, I don't know, why one node fail leads to fail all other. It is not a normal behavior. What is reason fail first node, and others? Can you increase failureDetectionTimeout, if you think this is network issue? (or network timeouts in discovery SPI) Could I look at logs from each nodes?

Re: server node is java , and client is c++, client can't join cluster

Hi, Can it be that you use JDKs from different vendors for different nodes? Best Regards, Igor On Wed, Nov 9, 2016 at 2:27 PM, smile wrote: > Hi, all > when I start one c++ server node, and then start java server node, > which successfully joins in the cluster, and

Re: Ignite Jdbc connection

I have couple of questions on ignite jdbc connection. Could you please clarify ? 1. Should connection be closed like other jdbc db connection ? - I see connection close is shutdown of ignite client node. 2. Connection objects are not getting released and all connections are busy ? 3. Connection

Re: ON HEAP vs OFF HEAP memory mode performance Apache Ignite

Hi, Work with OFF_HEAP requires more CPU time than ON_HEAP, because each "get" should get bytes from memory (by pointer to off_heap) and deserialize these bytes to business object. However you can use Binary interface in order to avoid deserialization: IgniteCache =

Re: ignite-spring conflict

Yeah, that was the problem. We use spring.version 4.1.4.RELEASE, after downgrading to 4.1.0 the exception is gone. One step forward, and I am getting some other exeption: [08:47:37,702][SEVERE][tcp-disco-sock-reader-#102%null%][TcpDiscoverySpi] Runtime error caught during grid runnable execution:

ON HEAP vs OFF HEAP memory mode performance Apache Ignite

Following are average execution time for running 14 queries against 16 million entries (DB size: 370 MB) OFF HEAP memory mode - 47 millisec ON HEAP memory mode - 16 millisec why there is difference in execution times between off heap and on heap memory modes as both are In-memory? What