Re: Error while writethrough operation in Ignite

Could you please share a simple reproducer? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-while-writethrough-operation-in-Ignite-tp9696p9716.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

WARNING: Failed to load 'igniteshmem' library from classpath. Will try to load it from IGNITE_HOME. WARNING: Failed to start shared memory communication server.

Hi All, I am trying to start the Apache Ignite Server (not using the default start up script from download ) and getting few WARN statements. WARNING: Failed to load 'igniteshmem' library from classpath. Will try to load it from IGNITE_HOME. Dec 23, 2016 2:05:26 AM org.apache.ignite.logger.java

答复: 回复：Re: 答复: Cache.invoke are terribly slow and can't update cache

Thanks Val, that's good. -邮件原件- 发件人: vkulichenko [mailto:valentin.kuliche...@gmail.com] 发送时间: 2016年12月23日 9:47 收件人: user@ignite.apache.org 主题: Re: 回复：Re: 答复: Cache.invoke are terribly slow and can't update cache Shawn, You just should keep in mind that this is an object that will be ser

Re: 回复：Re: 答复: Cache.invoke are terribly slow and can't update cache

Shawn, You just should keep in mind that this is an object that will be serialized, sent across network and invoked on other side. The purpose of entry processor is to be executed on server side and atomically read and update a single entry. Having said that, the logic you described doesn't make m

回复：Re: 答复: Cache.invoke are terribly slow and can't update cache

Thanks Val!Now I understood entryprocessor better. as to "error prone", I meant if we follow the document,it will be error prone.  For EntryProcessor is just an interface, it doesn't prohibit user to use lamda or anonymous classes.  When

Re: LoadCache Performance decreases with the size of the cache

Hello Val, Yes I'll try to upload something on github tomorrow. Thanks for the help -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/LoadCache-Performance-decreases-with-the-size-of-the-cache-tp9645p9710.html Sent from the Apache Ignite Users mailing list archive

Re: LoadCache Performance decreases with the size of the cache

Hi, I tried to reproduce this behavior, but without success. Data loading time increased linearly for me when I increased number of entries. Is it possible for you to provide a reproducer that I would be able to run and investigate? -Val -- View this message in context: http://apache-ignite-u

Re: 答复: Cache.invoke are terribly slow and can't update cache

Shawn, #1 - Yes, peer class loading is needed if you don't have entry processor implementation class deployed on server nodes. #2 - Correct. Moreover, I would recommend not to use lambdas or anonymous classes for anything that can be serialized, but to use static classes instead (this is actually

Re: Ignite cluster

Anil, Nothing is stopped. Once again, in case of segmentation you will have two independently running clusters. And in of the previous messages you told that this is desirable behavior for you as you have a read-only use case. Am I missing something? Did you run any test that gave different result

Re: Improve data loading speed from persistant data storage

Absolutely, give a try to the IgniteDataStreamer approach. You can create a streamer per cache and inject the data from multiple threads in parallel. Also keep in mind that the streamer is tunable and you can improve the performance by changing some of the parameters. — Denis > On Dec 21, 2016

Re: LoadCache Performance decreases with the size of the cache

Sure here is the code QueryEntity qryEntity = new QueryEntity(); qryEntity.setKeyType("myapp.bpepoc.model.MyModelKey"); qryEntity.setValueType("myapp.bpepoc.model.MyModel"); LinkedHashMap fields = new LinkedHashMap<>(); fi

Re: Ignite questions

Hi, thank you for a quick response. 1. I've found out that the problem was in two network interfaces that I was using. All 3 nodes are visible only on one of the interfaces. Interestingly some of the communication went through (I did see 3 nodes in the topology), some obviously did not and the de

Re: Error while writethrough operation in Ignite

Ignite version 1.7 I am using Ojdbc version 7. Following is the cache config file I am using CacheConfig.java -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-while-writethrough

Re: Error while writethrough operation in Ignite

Hi! 1) What version of Ignite are you using? 2) Oracle version? Oracle JDBC driver version? 3) It is possible to share with us Table create script? We will try to reproduce. I see in logs: Caused by: java.sql.SQLSyntaxErrorException: ORA-00927: missing equal sign May be there a bug in OracleDialec

Re: Error while writethrough operation in Ignite

But I have used CacheConfig file generated by schema import, what might be problem -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-while-writethrough-operation-in-Ignite-tp9696p9701.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Error while writethrough operation in Ignite

Looks like a bug in your CacheStore implementation - wrong SQL request is built. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-while-writethrough-operation-in-Ignite-tp9696p9700.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Improve data loading speed from persistent data storage

So, most of the time are spent on getting data from DB - 3.5 min. The rest, I think, could be indexing process in cache (you may check it by removing setIndexedTypes()). For speedup you may load data from CSV file, but Ignite doesn't provide such parser, you should implement it by yourself. Of cour

答复: Cache.invoke are terribly slow and can't update cache

Hi, I fix it by myself. I make two mistakes. #1 peerClassLoadingEnabled is disabled by default. Should enable it. #2 get ignite instance using: @IgniteInstanceResource Ignite ignite; Can't pass client ignite instance to it. Anyway, IMO, for EntryProcessor API it is a little error prone

Re: Improve data loading speed from persistant data storage

Data Loading time : 214126 milliseconds DB Size : 370 MB Number of Entries : 2.4 Million Only 1 node is used for data loading part from Oracle DB to Ignite cache Indexing is applied only on primary keys(default generated using schema import) -- View this message in context: http://apache-ig

Error while writethrough operation in Ignite

I am inserting data into table and write through policy is used to write back result to Oracle DB. But I am getting following error Exception in thread "main" javax.cache.integration.CacheWriterException: class org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException: Failed

Re: Improve data loading speed from persistant data storage

loadCache() internally already uses IgniteDataStreamer. How long does it take to fetch all data from DB? Do you use SQL indexing for entities? How many data nodes in topology? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Improve-data-loading-speed-from-persist

Re: Off heap memory contents in linux

Hi, You may use JMX beans or visorcmd for that purpose. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Off-heap-memory-contents-in-linux-tp9677p9694.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.