Re: State of initially started cache with CacheRebalanceMode.SYNC ?

Great stuff ! I looked at your branch and the fix and the testcases look really neat :) This community rocks ! Kristian 2016-06-14 2:57 GMT+02:00 Alexey Goncharuk : > Kristian, > > Got it, thank you for reporting this. Your expectations are correct, there > is an issue with handling of SYNC reb

Re: State of initially started cache with CacheRebalanceMode.SYNC ?

Kristian, Got it, thank you for reporting this. Your expectations are correct, there is an issue with handling of SYNC rebalance mode for dynamically started cache. If your cache was set in IgniteConfiguration, you would get correct size without calling rebalance().get(); I created an issue [1] w

Re: State of initially started cache with CacheRebalanceMode.SYNC ?

Alexey, we were discussing what was happening in the 10-20 seconds while the cache was being replicated, to find out if any inconsistencies could occur in this window. So I started a first node with a known number of elements, say 1 million. The testcase I showed in the first code was then started

Re: transaction not timing out

I will get this out to you shortly. In the meantime could you please explain how transaction timeout works? Why does commit block forever? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p5617.html Sent from the Apache Ignite User

Re: State of initially started cache with CacheRebalanceMode.SYNC ?

Kristian, I am a little bit confused by the example you provided in your first e-mail. From the code I see that you create a cache dynamically by calling getOrCreateCache, and the next line asserts that cache size is equal to a knownRemoteCacheSize. This does not make sense to me because cache cre

Re: Performance Degredation when adding more nodes

Thank you. A DS made a huge difference. Now I have 8 nodes with a cache configured for one backup and it takes abut 15 seconds to load the 100k records. Not perfect but much better than minutes. Regarding transactions, I presume that wrapping the whole put operation in a tx.begin() and tx.commit()

Re: Slow Transaction Performance

Thanks for the replies > do you execute transactions in parallel? Usually if keys that are used in > transactions are not intersected you can start several Thread an execute > transactions from them simultaneously. The timings I posed are to update 11k entries in a cache that was pre-loaded with

Re: Ignite - Spark integration

Hi, Not sure that is the problem, because I'm using deploy a local Ignite cluster and it works by using the multicast discover. However I've tried using TcpDiscoveryVmIpFinder and providing the local addresses. It changes the warning message but it continues to hangs. 12516 [tcp-client-disco-msg

Re: Performance Degredation when adding more nodes

Hi, Please properly subscribe to the user list (this way we will not have to manually approve your emails). All you need to do is send an email to ì user-subscr...@ignite.apache.orgî and follow simple instructions in the reply. Do I understand you properly that every transaction performs 1000 put

Ignite with Cassandra and SSL

Good morning Could you please help me understand how to establish persistence to Cassandrea via SSL? What else do I need to ensure apart from setting the below flag to true *useSSL* false Enables the use of SSL -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/I

Re: Performance Degredation when adding more nodes

Hello thammoud, Every operation cache.put() takes network roundtrip, by this reason performance of single operation depends on client network adapter. Try to use IgniteDataStreamer for bulk loading. Example: try (IgniteDataStreamer stmr = Ignition.ignite().dataStreamer(cache.getName()))

Re: Cache.put delays

Binti, Please share your cache configuration and test with us. You can use Gist [1] or other tool for that. [1] http://gist.github.com — Denis > On Jun 8, 2016, at 10:57 PM, bintisepaha wrote: > > We still saw issues with 1.6.0, but sing FULL_SYNC mode resolves it.

Re: Meaning of multiple index types

Hi Colin, Please properly subscribe to the user list (this way we will not have to manually approve your emails). All you need to do is send an email to ì user-subscr...@ignite.apache.orgî and follow simple instructions in the reply. It's possible to store object of different types in the same ca

Re: Exception on Ignite shutdown

Hi Colin, Please properly subscribe to the user list (this way we will not have to manually approve your emails). All you need to do is send an email to ì user-subscr...@ignite.apache.orgî and follow simple instructions in the reply. In fact there is no reason to worry about this kind of exceptio

Re: Warning TcpCommunicationSpi: Failed to allocate shared memory segment

Hi Luis, Please properly subscribe to the user list (this way we will not have to manually approve your emails). All you need to do is send an email to ì user-subscr...@ignite.apache.orgî and follow simple instructions in the reply. In regards to your question, yes, Ignite automatically use the s

Re: State of initially started cache with CacheRebalanceMode.SYNC ?

> Yes, the newly started node won’t be considered for cache related operations > until the rebalancing has finished. The rest of the nodes will be processing > all the cache related operations like there is no new node at all. Sweet ! I'm not really sure if I missed this in the documentation or

Re: Ignite - Spark integration

Hi Paolo, The application hangs because Ignite client node, that is used by Spark worker, can’t connect to the cluster 3797 [tcp-client-disco-msg-worker-#4%null%] WARN org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi - IP finder returned empty addresses list. Please check IP finder configu

Re: State of initially started cache with CacheRebalanceMode.SYNC ?

Yes, the newly started node won’t be considered for cache related operations until the rebalancing has finished. The rest of the nodes will be processing all the cache related operations like there is no new node at all. — Denis > On Jun 13, 2016, at 10:59 AM, Kristian Rosenvold > wrote: > >

Re: Where to watch the cache informations in IGFS.

Vasiliy, as on of maintainer of Visor CMD please comment on this. — Denis > On Jun 12, 2016, at 7:56 AM, Jason <410353...@qq.com> wrote: > > when i used SecondryFileSystem as my hadoop storage, when i used > "ignitevisorcmd.sh" with cmd "cache" or "cache -system", i can only see some > Entrie

Re: State of initially started cache with CacheRebalanceMode.SYNC ?

This is a replicated cache and I see the unexpected behaviour with 2 nodes. All I'm trying to do is to make sure the newly started server is not processing requests before its cache is fully populated. It seems to me you're saying the "get" request will actually be served by the other node before r

Re: whether IgniteHadoopIgfsSecondaryFileSystem will cache HDFS filein IGFS?

Do you measure cache reads or cache puts? Cache reads should be faster after IGFS is warmed up. > On Jun 12, 2016, at 5:40 AM, Xun Zhai <410353...@qq.com> wrote: > > my job work correctly， the ignite version is 1.6.0, i run the job twice, but > when i watch my cache hits by cmd "cache -system",

Re: State of initially started cache with CacheRebalanceMode.SYNC ?

Kristian, How many nodes do you have in the cluster? If there are more than two server nodes then there shouldn’t be any blocking because while rebalancing is happening on one node the other node can accept and fulfill cache related operations. The main point is that the cluster won’t stuck unt

Re: State of initially started cache with CacheRebalanceMode.SYNC ?

2016-06-13 9:14 GMT+02:00 Denis Magda : > This property means that a node that is being started and where a part of > cache data is being rebalanced won’t be considered for any cache related > operations until the rebalancing has finished. > > In my understanding such a node won’t be considered f

Re: Ignite: QuerySqlField - index question

Hi, Yes, your initial understanding is absolutely correct: if a field is not exposed as QuerySqlField then you won’t be able to use it in both “SELECT” and “WHERE” clauses of a query. When a field is used in the “WHERE” clause (“select … where myField = 10”) then it makes sense to make it an in

Re: transaction not timing out

Hi Binti, Could you share the source code of the test that reproduces that issue? This will help us to get to the bottom of the issue. You can use Gist [1] or other code sharing tool for that. [1] https://gist.github.com — Denis > On Jun 10, 2016, at 9:39 PM, bintis

Re: Slow Transaction Performance

Hi, In case with the primary sync mode that data will be always synced up on a primary node only. The backups will be synced up asynchronously. To answer on your initial question on how to improve the performance of transactions more details are needed: - do you execute transactions in paralle

Re: Simulating Graph Dependencies With Ignite

Hi, java.lang.OutOfMemoryError: GC overhead limit exceeded This kind of OOM exception says that your application spends almost all its time garbage collecting the heap. The first obvious reason is a small heap size and high allocation rate of objects in the heap. Please refer to the page Alexe

Re: Persistence using Cassandra

Hi, To bypass this kind of exceptions you need either to add a class of CodingScheme to the class path of all remote nodes or avoid deserialization on a remote side following these principles. 1. Set CacheConfiguraiton.setStoreKeepBinary flag to true. The the deserialization of your custom cla

Re: State of initially started cache with CacheRebalanceMode.SYNC ?

Hi Kristian, This property means that a node that is being started and where a part of cache data is being rebalanced won’t be considered for any cache related operations until the rebalancing has finished. In my understanding such a node won’t be considered for cache operations like put, get,

Re: Maven conflicts within ignite-core from duplicated classes

Hi Pete, CC-ing Ignite dev list to the thread as well. Igniters, up to today is there any reason why we need to include sources of Nullable JetBrain’s annotation in Ignite sources? As I see we can rather import that latest version from the maven repository https://maven-repository.com/artifact/