Re: stdout - Message queue limit is set to 0, potential OOMEs

Hi Sam, Slow node can cause OOME, as messages for slow node can make queue grows infinitly. Also, you can receive messages with higher rate than node able to process, that also can results in OOME. On Tue, Apr 18, 2017 at 10:13 PM, javastuff@gmail.com < javastuff@gmail.com> wrote: >

Re: Input data is no significant change in multi-threading

Hi Woo, IgniteDataStreamer uses per node buffer to make bulk cache updates that shows much better throughput than single updates. Also, IgniteDataStreamer send jobs to remote nodes, to utilize multiple threads on remote nodes. In multi-node grid IgniteDataStreamer usually shows better results

Re: ignite-indexing IncompatibleClassChangeError

Hi David, Looks like your H2 version is not compatible with ignite. Please, check if correct version of H2 is in classpath. On Wed, Apr 19, 2017 at 4:37 AM, David Li wrote: > I have a working ignite cluster and clients. However, then I added the > ignite-indexing to the

ignite-indexing IncompatibleClassChangeError

I have a working ignite cluster and clients. However, then I added the ignite-indexing to the project dependency, only add the dependency, not yet change anything else yet. I got the following error: Anyone got any idea? Caused by: class

Input data is no significant change in multi-threading

When I try to input data(80 table, each 1 records) to a cluster with 3 server node(each 2 gb), it only has a small change in time if multi thread is performed (ie. max decrease from 8s to 6.5s if using IgniteCache) Is it normal? Also, I found that multi thread do not affect the data input

Re: Webinar: Apache Ignite as a backbone for microservices-based architectures

Thanks, Denis. I will surely join the conference. Take Care, Rishi > On Apr 18, 2017, at 7:38 PM, Denis Magda wrote: > > Igniters, > > Just a final reminder for those who might be interested. The slides are > ready, the demo is running..so waiting for all of you tomorrow

Re: Webinar: Apache Ignite as a backbone for microservices-based architectures

Igniters, Just a final reminder for those who might be interested. The slides are ready, the demo is running..so waiting for all of you tomorrow April 19, 11:00 AM PST on the line ;) http://bit.ly/2nEmyv1 Plus, look at our “news” section for upcoming conferences where the community is going

BinaryObjectImpl.deserializeValue with specific ClassLoader

Hi, I have a use-case where I'm deploying services to the grid where the service implementation that's deployed to all ignite data nodes is really just a skeleton that downloads implementation jar files from IGFS and initializes the "real" service using a URLClassLoader (similar to what Storm,

Re: Ignite on FreeBSD 11 and OpenJDK

Hi Denis, that is great. Thank you for the link! I hope Ignite 2.0 or some later version will eventually work on FreeBSD with OpenJDK. Kamil On 2017-04-19 00:53, Denis Magda wrote: Hi Kamil, The documentation for the new off-heap page memory is being prepared and will become public right

Re: Ignite on FreeBSD 11 and OpenJDK

Hi Kamil, The documentation for the new off-heap page memory is being prepared and will become public right after 2.0 release. You can track the progress here: https://issues.apache.org/jira/browse/IGNITE-4961 — Denis > On Apr 18, 2017, at 3:47 PM, Kamil Misuth wrote: > >

Re: Ignite on FreeBSD 11 and OpenJDK

Replying, to my own question. Indeed, it seems to be the case that for Ignite 2.0, everything will be off heap. Denis Magda just (23 hours ago) updated the relevant wiki page. https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=67638199=10=8 Sounds cool to me :).

Re: Ignite on FreeBSD 11 and OpenJDK

Sure, Andrey. In mean time, a fact-checking question: I haven't really gone through the new memory policy functionality in depth, but it does seem that for Ignite 2.0 your aim is to move data off heap implicitly for all caches (and possibly backup the off heap region by memory mapped

Re: Disable WriteBehind

Hi Nikolai, looks like that was a wrong log file. I have reran the app and here's a new log file. Appreciate your help. Jessie On Mon, Apr 17, 2017 at 3:01 AM, Nikolai Tikhonov-2 [via Apache Ignite Users] wrote: > Hi, > > I see in logs that node lives 10

Re: Ignite errors in log

Thanks, Andrew. I enabled the ipv4 stack option and see if that resolves our problem. I will keep you posted, thank you for all your help. On Tue, Apr 18, 2017 at 1:41 PM, Andrew Mashenkov [via Apache Ignite Users] wrote: > Hi Rishi, > > Would you

stdout - Message queue limit is set to 0, potential OOMEs

Recently moved to Ignite 1.9 and noticed below line on stdout - /Message queue limit is set to 0 which may lead to potential OOMEs when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to message queues growth on sender and receiver sides./ Not sure if this existed in older

Re: ScanQuery log all entries

Thanks. One question though - Below loop will automatically go over all pages or just one page with 1024 entries? for (Cache.Entry, Person> entry : cursor) System.out.println("Key: " + entry.getKey() + ", Value: " + entry.getValue()); If it

Run Ignite on a separate Yarn Queue instead of default queue

Hi, Is there any option/property to run Ignite on a separate yarn queue instead of a 'default' queue? This will allow YARN not to touch Ignite containers or else Yarn can preempt Ignite nodes if it runs short of resources. Thank you Raja -- View this message in context:

Re: Node left topology

Hi Anil 1. It shouldn't. Grid heartbeat uses separate thread. However, high CPU or network pressure with low failure detection timeout can be a reason. 2. Do you mean client doesn't reconnect to grid at all, or it reconnect to smaller part after split-brain? If first, then there is a bug [1] that

Re: Ignite errors in log

Hi Rishi, Would you please check if both nodes has same either java.net.preferIPv4Stack=true or java.net.preferIPv6Stack=true option? "remote_host/remote_host:47102" looks weird. Would you also check if all dns names are correctly resolved on both nodes? On Tue, Apr 18, 2017 at 9:29 PM, Rishi

Re: Ignite errors in log

I checked the port and all ports are open between 2 ignite instances. There is something more going on, will provide the log soon. On Tue, Apr 18, 2017 at 12:00 PM, ignite_user2016 wrote: > we use Ignite 1.7, yes application is communicating between hosts and > client

Re: Ignite errors in log

we use Ignite 1.7, yes application is communicating between hosts and client application. I will provide the logs soon. Thanks, On Tue, Apr 18, 2017 at 11:09 AM, Evgenii Zhuravlev [via Apache Ignite Users] wrote: > Which version of ignite do you use? > >

Node left topology

HI, Could you please clarify below ? 1. Can long running queries on a node cause the node to leave the topology ? 2. Can a client reconnect to larger cluster which is connected to the node that left the topology ? Thanks

Re: LocalDateTime field being ignored on Cassandra write through

Thank you Dimitry, I will take a look Cheers, Guilherme Melo www.gmelo.org On 18 April 2017 at 22:08, dkarachentsev wrote: > Guilherme, > > You may track feature development here [1] or contribute it by yourself. > > [1]

Re: Ignite errors in log

Which version of ignite do you use? It looks like nodes discovered each other via 47500+ ports, but they can't communicate through 47100+ ports. Did you opened these ports? Are you sure that all nodes was used in your application? Also, it would be helpful if you provided full logs, it's nearly

Re: Ignite errors in log

Yes, I see this logs in both the host. The log entries I have provided, here is my config file - http://www.springframework.org/schema/beans; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xmlns:util="http://www.springframework.org/schema/util; xsi:schemaLocation="

Re: what does remaps mean in DataStreamerImpl.java

Hi, DataStreamer packs all cache operations to batch request to grid server node. If this batch was not executed correct in particular node, it will by remapped to other. Maximum of remaps cunt is 32 (DFLT_MAX_REMAP_CNT). -- View this message in context:

Re: Error while building application

Hi, Please share full build log and pom.xml. Thanks! -Dmitry -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-while-building-application-tp12027p12035.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: what does remaps mean in DataStreamerImpl.java

I had subscribed to mailing list as per the mail I have received but still the query has not accepted by mailing list. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/what-does-remaps-mean-in-DataStreamerImpl-java-tp12033p12034.html Sent from the Apache Ignite

what does remaps mean in DataStreamerImpl.java

Getting below error, class org.apache.ignite.IgniteCheckedException: Failed to finish operation (too many remaps): 32 at org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$5.apply(DataStreamerImpl.java:863) Caused by: class org.apache.ignite.IgniteCheckedException: DataStreamer

Re: LocalDateTime field being ignored on Cassandra write through

Guilherme, You may track feature development here [1] or contribute it by yourself. [1] https://issues.apache.org/jira/browse/IGNITE-5013 -Dmitry. -- View this message in context:

Re: LocalDateTime field being ignored on Cassandra write through

Hi Guilherme, Now Ignite Cassandra store has hard mappings from java to Cassandra types: org.apache.ignite.cache.store.cassandra.common.PropertyMappingHelper#JAVA_TO_CASSANDRA_MAPPING If type is not in this map - it will be serialized. LocalDateTime is not there for compatibility reasons, and no

Re: IgniteCacheProxy connection failure in REPLICATAED mode

Hi, I appreciate the last response to this. I've checked out the 1.9 branch (ie. git clone -b ignite-1.9 --single-branch https://github.com/apache/ignite.git ignite-1.9)...I'm new to github so bear with me. In seeing if this patch will apply, I get the following error. I'm not exactly sure

Re: Error while running query against Ignite Server Node

Hi Nikolai, By saying: > This exception means that in during data streaming, topology was changed. Do you mean major topology or minor topology? And also what is minor topology? We have encountered same issue without no change in topology version no new nodes added or left but with different

Re: Failed to wait for initial partition map exchange

We are facing the similar issue with 1.9 version..Is there any recommended configuration parametres to overccome this issue -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Failed-to-wait-for-initial-partition-map-exchange-tp6252p12028.html Sent from the Apache

Re: Basic question on scaling of reads with ignite sql queries

Hi Tuco, ReadFromBackup works only for cache operations. On Tue, Apr 18, 2017 at 10:02 AM, tuco.ramirez wrote: > There is an option 'readFromBackup' in CacheConfiguration. > Does it work for both cache.get() calls and SQL queries or only for > cache.get() calls? >

Re: Ignite errors in log

Hi, Could you check that destination node accessible from current node via one of this addresses(remote_host/remote_host:47102, /0:0:0:0:0:0:0:1%lo:47102, /127.0.0.1:47102?) Do you have problems only with one node, or you have same messages about another nodes and on another nodes? Please

Re: Creating a distributed cache via cacheManager (JCACHE)

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. mikep-sl wrote > I have the same problem. The caches are are

Re: How do I provide AffinityFunction.BackupFilter when mainly using C++ bindings

You can use APIs only on one of them, or create a cluster of two server nodes, embed a client in the application and use APIs there. In any case, I don't see why you need custom affinity function or even backup filter. And your understanding of backup filter is not correct. Primary node for a

Re: LocalDateTime field being ignored on Cassandra write through

Hello Dimitry, Thanks, it looks like if I add all the fields on the persist.xml (even though in the documentation it says that it is not required, for Pojo)the date is stored as a blob. I've added annotations to the class to use a custom codec, however it is ignored. Is this a bug or are Cassandra

Re: Slow on 1st time query "SQL Join"

Hi, For calling the function createMissingCaches(), it will create a cache in client node. Is this cache permanent exist in client node or will drop after sometime? Thanks & Best regards, Charles 2017-04-13 21:09 GMT+08:00 afedotov : > Created a ticket for the

Re: Compute calls happening on client node

Hi, You just need to specify cluster group: ignite.compute(ignite.cluster().forServers()).run(new IgniteRunnable() { @Override public void run() { System.out.println("This will be processed on server nodes only"); } }); There a various of

Re: SqlFieldsQuery setTimeout

This is not supported because in general case the result will be completely wrong. Probably you can achieve something like this manually with IgniteCompute and local SQL queries. Sergi 2017-04-18 10:31 GMT+03:00 neerajbhatt : > Hello All > > While querying to ignite

RE: OOM when using Ignite as HDFS Cache

Yes, I'm getting "GC Overhead limit exceeded" OOME and I think this is an unexpected behavior. I'll try the off heap options days later. Thanks for your advice. I'm providing HDFS server to our customers. As you know, HDFS is not friendly to many small files. We sometimes need to merge files

Re: ScanQuery log all entries

Hi, Yes, you understand correctly. Here is example: private static void sqlQuery() { IgniteCache, Person> cache = Ignition.ignite().cache(PERSON_CACHE); // SQL clause which selects salaries based on range. String sql = "salary > ? and salary <= ?";

Re: OOM when using Ignite as HDFS Cache

Are you getting "GC Overhead limit exceeded" OOME? I think you could always move IGFS data block cache off heap if it is not the case already. I am wondering why you've set block size to 4 GB for Ignite when HDFS stock configured block size is either 64 MB or 128 MB. Have you tried to set

Re: LocalDateTime field being ignored on Cassandra write through

Hi, I tried your configuration and it works fine for me. Please check attached project. I used Cassandra v3.0.13. cassandra-test.zip -Dmitry. -- View this message in context:

SqlFieldsQuery setTimeout

Hello All While querying to ignite cluster we can set a timeout SqlFieldsQuery.setTimeout Suppose in a 5 node cluster set up if one node timed out we will get result from other 4 nodes or the query will fail altogether ? Ideally we want that maximum result from all the nodes should come, if

Re: Ignite Node Discovery IP config

Thank you! This helped a lot. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Node-Discovery-IP-config-tp11957p12013.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Basic question on scaling of reads with ignite sql queries

There is an option 'readFromBackup' in CacheConfiguration. Does it work for both cache.get() calls and SQL queries or only for cache.get() calls? Thanks -- View this message in context: