Re: Ignite 2.0.0 GridUnsafe unmonitor

+1 for warning about potential deadlock and improving javadocs --Yakov

Re: when client node connect to server node, server node throws NotSerializableException

Hi Andrew, Thanks a lot for all the replies. yes BoConverter implements Serializable, or Ignite will throw NotSerializableException. The "Class" here is actually for hibernate to get data from DB: org.hibernate.Session.get(Class clazz, Serializable id). After getting the data, BoConverter

Re: Ignite 2.0.0 GridUnsafe unmonitor

I like the idea to print out a warning if unsorted map is provided. The fact that there are tons of other ways to get a deadlock doesn't mean that we should ignore this case which is actually very common. -Val On Tue, Oct 31, 2017 at 12:34 PM, Dmitry Pavlov wrote: >

What's the maximum number of nodes for an Apache Ignite cluster?

Is there a limit for an ignite cluster? I was told it is 2000 nodes. Thanks

Re: Ignite 2.0.0 GridUnsafe unmonitor

Vladimir, thank you. Good point for optimistic tx, but still putAll usage require using sorted collections. User, of course, may broke this scenario also by using sorted maps with incorrect custom comparators (one asc, one desc). Producing warning in code for Igntie for potential deadlock is good

Re: Ignite 2.0.0 GridUnsafe unmonitor

Vladimir, That’s an oversight and lack of explanation on our side. The goal is to avoid unexpected deadlocks when a user passed a HashMap in cache.putAll. Before printing out a warning we can filter out OPTIMISTIC/SERIALIZABLE and other suitable scenarios. So you’re free to offer another

Re: Ignite 2.0.0 GridUnsafe unmonitor

Guys, Printing a warning in this case is really strange idea. First, how would explain it in case of OPTIMISTIC/SERIALIZABLE transactions where deadlocks are impossible? Second, what would you do in case tow sorted maps are passed one by one in a transaction? User still may have a deadlock.

Re: Modify the underlying IgniteRDD Cache

Okay so it looks like my problem was I was trying to dynamically create a cache config and you are correct it was not working due to some sort of indexing issue. I think using this template fixes my the issue thanks. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite 2.0.0 GridUnsafe unmonitor

Here is a ticket for the improvement: https://issues.apache.org/jira/browse/IGNITE-6804 — Denis > On Oct 31, 2017, at 3:55 AM, Dmitry Pavlov wrote: > > I agree with Denis, if we don't have such warning we should continiously warn > users in wiki

Re: Code deployment throught UriDeploumentSpi

Hello Dmitriy! I was able to reproduce your case. Unfortunately there's no apparent workaround yet. I have filed an issue https://issues.apache.org/jira/browse/IGNITE-6803 There's a patch that fixes the reproducer but its impact on the rest of codebase is unpredictable. -- Ilya Kasnacheev

Re: Node failed to startup due to deadlock

Thanks Alexey. Please find the attached logs and configuration on Node 2. Regards, Naresh Node2.log Node2_configuration.txt -- Sent

Re: NullPointerException in FileWriteAheadLogManager.java:1313

Opened a ticket to address this: https://issues.apache.org/jira/browse/IGNITE-6802

Re: NullPointerException in FileWriteAheadLogManager.java:1313

Hi, Please set WAL archive path to be different from WAL store path. Indicating this misconfiguration with NullPointerException is a usability issue. I will open a ticket. On Tue, Oct 31, 2017 at 7:13 PM, Sébastien Bouchex Bellomié < sbouc...@infovista.com> wrote: > Hello, > > > > I’m getting

Re: Renentrant Lock & deadlock

That one was with ignite.getOrCreate This one is with ignite.reentractLock. Are the both due to the same defect? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Node failed to startup due to deadlock

Hi Alexey, Is there an associated defect in Jira? Is there an isolated & verified patch that can be backported to 2.0? thanks, Rajeev -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

NullPointerException in FileWriteAheadLogManager.java:1313

Hello, I'm getting the following NullPointerException in FileWriteAheadLogManager.java at line 1313 while doing the following with 2.2.0 version of Ignite. 2017-10-31 16:54:13,330 ERROR [exchange-worker-#34%IVTelemetryStorageIgnite%] o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture Failed to

Re: Deadlock on Node Remove and Add

Yes - its the same. thanks -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Out of memory streaming to Ignite Apache 2.0

I'm running compute tasks to load csv files into an a cache. Program runs fine on one node but I get out of memory errors (Java heap) when running on 3 vms. It's 2.2 and I've tried various config options. If I comment out the stream use then Ignite still seems to stop after several 1000 tasks

Re: Failed to create string representation of binary object.

Hi Ankit, I see two lines in the exception below: "Failed to read field: registrationInfoResponse " "com.partygaming.services.mds.userprofile.api.UserRegistrationInfoResponse" It seems that UserRegistrationInfoResponse.registrationInfoResponse becomes null / incorrect during your test and it

Re: How can I get Ignite security plugin to work with JDBC thin client?

Caleb, I've found authorization should work only when you use url like "jdbc:ignite://" with thick driver, and won't if "jdbc:ignite:cfg://" is used. On Tue, Oct 31, 2017 at 4:33 PM, calebs wrote: > The javadoc for the jdbc thick client states that property: >

Re: when client node connect to server node, server node throws NotSerializableException

Hi Jeff, Is BoConverter object serializable and is class present on all nodes? You store configured with storeKeepBinary true, so store will receive binary objects. Why you need value class here? Binary object concept is to overcome a requirement to have all value classes on server side. On

Re: How can I get Ignite security plugin to work with JDBC thin client?

The javadoc for the jdbc thick client states that property: "ignite.client.credentials" is available to pass "Client credentials used in authentication process." Is this not being used for authentication/authorization? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Modify the underlying IgniteRDD Cache

Well, all changes in Ignite cache (regardless whether they were caused by another RDD or external changes in cache) will be visible to RDD users immediately. Most possible this happened because you set different types for keys and values in ignite native api and ignite rdd. I've checked this

Re: Deadlock on Node Remove and Add

Hi, Is it the same issue http://apache-ignite-users.70518.x6.nabble.com/Node-failed-to-startup-due-to-deadlock-tc17839.html? Can you try the build from a master branch? Thanks, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Node failed to startup due to deadlock

Hi Naresh, Can you share your log from Node 2 and configuration file? The issue is related to Cache PartitionExchange procedure during node startup. Very probably this issue is already fixed on master branch. Thank you in advance, Alexey -- Sent from:

Re: Quick questions on replication and write synchronization mode

Hi, Read requests by default goes to PRIMARY node until readFromBackup is true that allow to read local backup data. Write requests always applies on PRIMARY node first then primary node send request to backup nodes. The main difference between FULL and PRIMARY sync modes is that with second

Re: Ignite Transaction with Locks but not SERIALIZABLE user case.

Hello, increment/decrement is a read-modify-write operation, so to achieve the desired behavior you need to lock the key and perform the operation under that lock. So you need to use a transaction mode and isolation level that meet the requirements. For this case, you could use the approach

Re: Ignite 2.0.0 GridUnsafe unmonitor

I agree with Denis, if we don't have such warning we should continiously warn users in wiki pages/blogs/presentations. It is simpler to warn from code. What do you think if we will issue warning only if size > 1. HashMap with 1 item will not cause deadlock. Moreover where can be some custom

Re: Quick questions on replication and write synchronization mode

Hello, > 1. Assume I write data item X with a FULL_ASYNC write synchronization > mode, what happens if I immediately attempt to read X? > Will I read an old value or do I wait till the previous writes are > completed? It depends on the fact whether the write operation is executed on the primary

Re: deadlock

Hello! Can you please attach full thread dump from the node once it stops responding? You can collect thread dump by using jstack JVM utility. Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: deadlock

Hi, Most possible you update entries in different order. Before using bulk operations such as updateAll removeAll invokeAll, make sure that entries you applying to it sorted in the same order Evgenii 2017-10-31 9:51 GMT+03:00 shawn.du : > Hi, > > My ignite server stop

deadlock

Hi, My ignite server stop to response.  Any client can't connect it, and I found dead lock in logs,what's the possible reason for this?  I use ignite 1.9.0.Thanks in advance.log===deadlock: truecompleted: 29519967Thread

Re: when client node connect to server node, server node throws NotSerializableException

my factory is very easy, just override the create method and set attributes, please see the code below. In the cache store i use hibernate to get data from Oracle and convert it to binaryObject and then put into Ignite, so I make people can config their own converter and class. Thanks. import