Anyone claim IGNITE-1264 (Resource SPI)?

I'm looking at taking a stab at https://issues.apache.org/jira/browse/IGNITE-1264 . It's biting us right now... we can work around it, but it's kind of annoying. Anyone already working on it? Thanks, matt

[GitHub] ignite pull request: IGNITE-3015 - Clean up some GridGain referenc...

GitHub user matthoffman opened a pull request: https://github.com/apache/ignite/pull/650 IGNITE-3015 - Clean up some GridGain references in Javadoc There's actually at least one instance here that isn't in javadoc: [VisorTopologyCommand.scala]( https://github.com/apache/ignite/com

[jira] [Created] (IGNITE-3015) Fix GridGain references in Javadoc

matt hoffman created IGNITE-3015: Summary: Fix GridGain references in Javadoc Key: IGNITE-3015 URL: https://issues.apache.org/jira/browse/IGNITE-3015 Project: Ignite Issue Type: Bug Affec

Re: About Jira https://issues.apache.org/jira/browse/IGNITE-2982

Here is the list of issues that you could get started with: https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20labels%20in%20(newbie)%20and%20status%20%3D%20OPEN On Fri, Apr 15, 2016 at 2:05 AM, Denis Magda wrote: > Hi Ken, > > Actually I’m not the one who knows where to

Re: clean up some GridGain references in javadoc

Thanks Matt! This is definitely very useful. If you don’t mind creating a Jira ticket and adding this information there, would be great. D. On Fri, Apr 15, 2016 at 12:07 PM, Matt Hoffman wrote: > I was going through the Javadoc, and found a number of references to > classes that I assume were t

Re: Small how to for Mesos + Ignite + Java

Small correction: the most recent link describing backup nodes is https://apacheignite.readme.io/v1.5/docs/primary-and-backup-copies -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Small-how-to-for-Mesos-Ignite-Java-tp8467p8490.html Sent from the Apache Ig

Re: Small how to for Mesos + Ignite + Java

Hi, I am glad I could help. Note that indeed using Mesos/Marathon, I can easily launch & scale Ignite nodes on my cluster. It is my understanding that Ignite nodes will automatically rebalance the data among nodes upon scaling, is that right ? If so, both solutions provide an easy and robust

clean up some GridGain references in javadoc

I was going through the Javadoc, and found a number of references to classes that I assume were the pre-Ignite names, like GridCompute*, GridNode (which became ClusterNode), and so on. Not a big deal, but kind of nice to clean up. I went ahead and renamed the ones I found, and pushed them to https

Re: Small how to for Mesos + Ignite + Java

Dima, Sure, when I finish updating doc I'll post the link here. On Fri, Apr 15, 2016 at 8:15 PM, Dmitriy Setrakyan wrote: > Thanks Nick! Can you please send the link to the updated documentation > here? Also, please don’t forget to update both, 1.5 and 1.6 versions. > > D. > > On Fri, Apr 15, 20

[GitHub] ignite pull request: IGNITE-2946: Implemented query results retrie...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/649 IGNITE-2946: Implemented query results retrieving in a batch. You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-2946 Altern

Re: Small how to for Mesos + Ignite + Java

Thanks Nick! Can you please send the link to the updated documentation here? Also, please don’t forget to update both, 1.5 and 1.6 versions. D. On Fri, Apr 15, 2016 at 6:36 AM, Nikolay Tikhonov wrote: > Hi, > Thank you for efforts and feedback! > > Vova, > I'll change our documentation that poi

[GitHub] ignite pull request: IGNITE-2777: Created Queries example for C++.

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/648 IGNITE-2777: Created Queries example for C++. You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-2777 Alternatively you can

Re: Semaphore blocking on tryAcquire() while holding a cache-lock

Yakov, I've finished the initialization tests for ignite-642 (and moved serialization test from GridCacheLockAbstractTest to IgniteLockAbstractSelfTest). Please check the commit and let me know if you spot anything else. Thanks! On Fri, Apr 15, 2016 at 10:11 AM, Vladisav Jelisavcic wrote: > Yak

Re: Small how to for Mesos + Ignite + Java

Hi, Thank you for efforts and feedback! Vova, I'll change our documentation that points will be more clear. On Fri, Apr 15, 2016 at 4:25 PM, Vladimir Ozerov wrote: > Hi, > Thank you for such deep and thorough analysis. I think we definitely > reflect your findings in our documentation. > > Nick

Re: Small how to for Mesos + Ignite + Java

Hi, Thank you for such deep and thorough analysis. I think we definitely reflect your findings in our documentation. Nick, Provided that you worked on Mesos integration, could you please see, how we can integrate this into our docs? Vladimir. On Fri, Apr 15, 2016 at 1:42 AM, lpalbou wrote: > H

[jira] [Created] (IGNITE-3014) Optimize GridDhtPartitionTopologyImpl#localPartition()

Ilya Lantukh created IGNITE-3014: Summary: Optimize GridDhtPartitionTopologyImpl#localPartition() Key: IGNITE-3014 URL: https://issues.apache.org/jira/browse/IGNITE-3014 Project: Ignite Issue

[GitHub] ignite pull request: unwindEvicts() usage optimization.

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/647 unwindEvicts() usage optimization. For benchmarking. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ilantukh/ignite ignite-2744 Alternatively

[jira] [Created] (IGNITE-3013) Support sorted merge index for SQL

Sergi Vladykin created IGNITE-3013: -- Summary: Support sorted merge index for SQL Key: IGNITE-3013 URL: https://issues.apache.org/jira/browse/IGNITE-3013 Project: Ignite Issue Type: Improveme

Re: API for asynchronous execution.

Yakov is right. Benchmarks show performance drop 3-8% when using asynchronous callbacks. On Fri, Apr 15, 2016 at 11:34 AM, Yakov Zhdanov wrote: > I am pretty sure that making all filter notifications asynchronous will > terribly affect performance. I would leave it only for cases when some > com

Re: kcheng.mvp thank for contributing "IGNITE-1481: It is possible to configure local cache with affinity function"

That’s perfect! You’re approaching the time when you can be granted committer permissions ;) — Denis > On Apr 15, 2016, at 1:06 PM, Ken Cheng wrote: > > Hi Denis, > > So nice to hear from you! > > Right now I have done 6 commits. and I am going to do more contribution. > > > > Thanks, > k

Re: kcheng.mvp thank for contributing "IGNITE-1481: It is possible to configure local cache with affinity function"

Hi Denis, So nice to hear from you! Right now I have done 6 commits. and I am going to do more contribution. [image: Inline image 1] Thanks, kcheng On Fri, Apr 15, 2016 at 4:37 PM, Denis Magda wrote: > kcheng.mvp, > > I want to thank you from the community side for the next contribution > yo

Re: About Jira https://issues.apache.org/jira/browse/IGNITE-2982

Hi Ken, Actually I’m not the one who knows where to dig. Also as I see it’s already taken by someone else from the community. Please peek up the other issues that may be interested for you. — Denis > On Apr 15, 2016, at 11:50 AM, Ken Cheng wrote: > > Hi Denis Magda >

About Jira https://issues.apache.org/jira/browse/IGNITE-2982

Hi Denis Magda , What's the correct behavior for this bug https://issues.apache.org/jira/browse/IGNITE-2982? Can you give me some hint? I would like to pick up this one. Thanks, kcheng

[jira] [Created] (IGNITE-3012) Filtration of defualt cache doesn't work

Pavel Konstantinov created IGNITE-3012: -- Summary: Filtration of defualt cache doesn't work Key: IGNITE-3012 URL: https://issues.apache.org/jira/browse/IGNITE-3012 Project: Ignite Issue T

kcheng.mvp thank for contributing "IGNITE-1481: It is possible to configure local cache with affinity function"

kcheng.mvp, I want to thank you from the community side for the next contribution you’ve done in Apache Ignite. Thanks for finding time for fixing bugs making Ignite better. Look forward for new contributions from your side. Regards, Denis

Re: API for asynchronous execution.

I am pretty sure that making all filter notifications asynchronous will terribly affect performance. I would leave it only for cases when some complex processing needs to be done involving, for example, cache operations. If filter is simple then I would leave it sync (by default). --Yakov 2016-04

Re: Semaphore blocking on tryAcquire() while holding a cache-lock

Yakov, I reviewed the changes in ignite-642 and it looks good to me, but I have one question. Can you please look at my comment in ignite-642 ticket? Thanks! Vladisav On Thu, Apr 14, 2016 at 7:51 PM, Vladisav Jelisavcic wrote: > Sure, I'll look into it later today, or tomorrow at the latest >