Re: Google Summer Of Code 2017

Igniters, We lost the battle but still might win the war. ASF has been accepted as one of participating organizations for GSoC2017. So we can take part as an ASF project! I’ve added the following four tickets to ASF GSoC2017 list (https://issues.apache.org/jira/browse/TIKA-2262?filter=12339687)

Re: Merging all network components to a single one

Agree with Denis. It is not practical to remove any existing SPIs unless we come up with proper TCP SPI design and implementation. I think it will be enough to simply deprecate the existing SPIs we plan to remove, without physically removing them, until the design is finalized. D. On Fri, Mar 10

Re: More SEO and API doc cleanup

Hello Mauricio, Thanks a lot, I’ve reviewed and merged your changes! > - Setup rewrite rule on .htaccess so latest API doc can have always the > same URL ( for example https://ignite.apache.org/releases/latest/javadoc/ > ) In this case

Re: ignite-4804 - ready for review (Remove duplicated properties in parent-pom)

After the sync ignite-2.0 will merge my commit and the other commit, that removed extra spark version, from the master and everything should be resolved after that. — Denis > On Mar 10, 2017, at 12:32 PM, Vyacheslav Daradur wrote: > > > I'm talking about: > > - master-branch had 2 dublicate

Re: ignite-4804 - ready for review (Remove duplicated properties in parent-pom)

I'm talking about: - master-branch had 2 dublicated properties [, ] (your commit fix it ) - ignite-2.0 branch has 3 dublicated properties [, , ] After branch synchronization, ignite-2.0 branch will has one more dub

Re: ignite-4804 - ready for review (Remove duplicated properties in parent-pom)

The commit will be merged to ignite-2.0 the next time when the branches will be put in sync. — Denis > On Mar 10, 2017, at 12:06 PM, Vyacheslav Daradur wrote: > > Denis, thanks. > > I've seen your commit in the master-branch. > > Notice, the ignite-2.0 branch contains one more duplicated pro

Re: ignite-4804 - ready for review (Remove duplicated properties in parent-pom)

Denis, thanks. I've seen your commit in the master-branch. Notice, the ignite-2.0 branch contains one more duplicated property: "1.5.2". -- Best regards. 2017-03-10 22:37 GMT+03:00 Denis Magda : > Hi, > > Thanks a lot, I’ve merged your changes. > > — > Denis > > > On Mar 9, 2017, at 11:27 PM,

Re: assigning IGNITE-933

Vadim, Please prepare a pull-request and make sure that the test passes on TeamCity. — Denis > On Mar 10, 2017, at 9:25 AM, Вадим Опольский wrote: > > Hello everyone! > > Denis, I've successfully executed GridFailFastNodeFailureDetectionSelfTest in > IDE 10 times on VMware Workstation (3 GB

Re: Merging all network components to a single one

> Denis, I think we can allow this as well, but not as SPI since I want to > drop them and create 1 internal component to manage all interconnections. I > think this is enough since additions/changes will be rare and they will > result in changing internal code (including support of technologies yo

Re: ignite-4804 - ready for review (Remove duplicated properties in parent-pom)

Hi, Thanks a lot, I’ve merged your changes. — Denis > On Mar 9, 2017, at 11:27 PM, Vyacheslav Daradur wrote: > > Hello everyone. > > Please review changes. https://issues.apache.org/jira/browse/IGNITE-4804 > > I found this mistake when I worked on an another issue. > I created new issue (ign

Re: Request adding to contributors list

Hi Kartrik, I’ve added you to the contributors list. Now you can assign the ticket on yourself. — Denis > On Mar 9, 2017, at 11:23 PM, kartik somani > wrote: > > Hi Alexey, > > My ID is kay_jpr. > > Thanks & Regards, > Kartik > > On Fri, Mar 10, 2017 at 6:33 AM, Alexey Kuznetsov > wrote:

Re: IGNITE-4713 : refactoring of GridFinishedFuture and GridFutureAdapter

I'm sorry I didn't notice pair "acquireShared" and "releaseShared". Okay, well, there are no races. But we still can use "getState()" in "assert" instead "resFlag", that will allow us use boolean type. But if you think it will not make code cleaner, then I will close issue. 2017-03-01 14:55 GMT+03

Re: assigning IGNITE-933

Hello everyone! Denis, I've successfully executed GridFailFastNodeFailureDetectionSelfTest in IDE 10 times on VMware Workstation (3 GB RAM, Intel Core i5-2520M) in single core mode with 300 MILLISECONDS timeout. What's the next step ? Vadim 2017-03-07 22:25 GMT+03:00 Denis Magda : > Vadim, >

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

Yes, but I have added a few more today :) 2017-03-10 19:03 GMT+03:00 ALEKSEY KUZNETSOV : > Hmm, i have fixed all your remarks more than 20 days ago. > > пт, 10 мар. 2017 г. в 15:12, Alexey Goncharuk >: > > > Alexey, > > > > Looks good. I've left my comments in the PR, please address them and I >

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

Hmm, i have fixed all your remarks more than 20 days ago. пт, 10 мар. 2017 г. в 15:12, Alexey Goncharuk : > Alexey, > > Looks good. I've left my comments in the PR, please address them and I will > merge it. > > 2017-03-10 10:24 GMT+03:00 ALEKSEY KUZNETSOV : > > > plz review ticket again > > > >

[GitHub] ignite pull request #1613: IGNITE-4815: CollisionSPI.onCollision() confusing...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1613 IGNITE-4815: CollisionSPI.onCollision() confusing javadoc fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignit

Re: Merging all network components to a single one

Dmitry, you are right - this seems to be a very complex change. However, we can we move current implementations to internal packages, introduce configuration properties/beans so we can release and continue development in 2.0 without breaking compatibility. Denis, I think we can allow this as well,

[GitHub] ignite pull request #1612: IGNITE-4814

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/1612 IGNITE-4814 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4814 Alternatively you can review and apply these

[jira] [Created] (IGNITE-4815) CollisionSPI calls on every EVT_NODE_METRICS_UPDATED event.

Andrew Mashenkov created IGNITE-4815: Summary: CollisionSPI calls on every EVT_NODE_METRICS_UPDATED event. Key: IGNITE-4815 URL: https://issues.apache.org/jira/browse/IGNITE-4815 Project: Ignite

Re: distributed transaction of non-single coordinator

- Its a draft test, in my next one i will try to serialize transaction and send it across nodes - thats where STOPPED status comes in handy.You cannot restart transaction in another node unless it was stopped. And you cannot commit if transaction status is STOPPED. Further tests shou

Re: IgniteConfiguration.gridName is very confusing

Thanks, Alex! Sam, can you please also take a look to make sure we catch all possible issues on review? Let's merge this on Monday since this is very conflict-prone change. --Yakov 2017-03-10 12:57 GMT+03:00 Alexander Fedotov : > Hi, > PR updated. Currently no conflicts at > https://github.com/

Re: distributed transaction of non-single coordinator

What about to send special message to random/choosen node when we start transaction? And when rollback procedure begins - this second node will check state of originating node and if it is down then second node became originating? 2017-03-10 17:25 GMT+03:00 Alexey Goncharuk : > Aleksey, > > I thi

Re: general question

I've done it, but from time to time transaction doesn't roll back. Perhaps, its a known bug пт, 10 мар. 2017 г. в 9:31, Alexey Goncharuk : > Hi Aleksey, > > In order to ensure that a transaction is rolled back during a node failure, > you need to orchestrate messages in such a way that at least o

Re: REVIEW IGNITE-2552 EvictionPolicies refactored, logic changed

Aleksey, Thanks for your contribution! I've merged this PR into master branch. See JIRA issue comment for details. On Fri, Mar 10, 2017 at 2:58 PM, Andrey Gura wrote: > Aleksey, > > I don't see any new changes. So I'll check TC and merge changes today. > > On Fri, Mar 10, 2017 at 10:20 AM, ALEKS

Re: distributed transaction of non-single coordinator

Aleksey, I think I am starting to get what you want, but I have a few concerns: - What is the API for the proposed change? In your test, you pass an instance of transaction created on ignite(0) to the ignite instance ignite(1). This is obviously not possible in a truly distributed (multi-jvm) env

[GitHub] ignite pull request #1611: Rebalancing optimizations.

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/1611 Rebalancing optimizations. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12001 Alternatively you can revie

Re: distributed transaction of non-single coordinator

Alexey Goncharuk, heh, my initial understanding was that transferring of tx ownership from one node to another will be happened automatically when originating node is gone down. 2017-03-10 15:36 GMT+03:00 ALEKSEY KUZNETSOV : > Im aiming to span transaction on multiple threads, nodes, jvms(soon).

[jira] [Created] (IGNITE-4814) GridQueryProcessor: improve type registration logic

Vladimir Ozerov created IGNITE-4814: --- Summary: GridQueryProcessor: improve type registration logic Key: IGNITE-4814 URL: https://issues.apache.org/jira/browse/IGNITE-4814 Project: Ignite Is

Re: distributed transaction of non-single coordinator

Im aiming to span transaction on multiple threads, nodes, jvms(soon). So every node is able to rollback, or commit common transaction.It turned up i need to transfer tx between nodes in order to commit transaction in different node(in the same jvm). пт, 10 мар. 2017 г. в 15:20, Alexey Goncharuk :

Re: distributed transaction of non-single coordinator

Aleksey, Do you mean that you want a concept of transferring of tx ownership from one node to another? My initial understanding was that you want to be able to update keys in a transaction from multiple threads in parallel. --AG 2017-03-10 15:01 GMT+03:00 ALEKSEY KUZNETSOV : > Well. Consider tr

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

Alexey, Looks good. I've left my comments in the PR, please address them and I will merge it. 2017-03-10 10:24 GMT+03:00 ALEKSEY KUZNETSOV : > plz review ticket again > > чт, 9 мар. 2017 г. в 10:28, ALEKSEY KUZNETSOV : > > > plz review ticket again > > > > вт, 28 февр. 2017 г. в 14:14, ALEKSEY K

[GitHub] ignite pull request #1610: Ignite 4813

GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1610 Ignite 4813 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4813 Alternatively you can review and apply the

Re: distributed transaction of non-single coordinator

Well. Consider transaction started in one node, and continued in another one. The following test describes my idea: Ignite ignite1 = ignite(0); IgniteTransactions transactions = ignite1.transactions(); IgniteCache cache = ignite1.getOrCreateCache("testCache"); Transaction tx = transactions.txSt

Re: REVIEW IGNITE-2552 EvictionPolicies refactored, logic changed

Aleksey, I don't see any new changes. So I'll check TC and merge changes today. On Fri, Mar 10, 2017 at 10:20 AM, ALEKSEY KUZNETSOV wrote: > Hi! Can u plz review ticket once more > > вт, 7 мар. 2017 г. в 18:52, Andrey Gura : > >> Aleksey, thanks a lot! >> >> Answered in JIRA ticket. >> >> On Tue

Re: IGNITE-13 (ready for review)

Hi Valentin, I cant find out why it's better on long string, but worse on a short string. May be it needs to use special tools like such as oracle solaris studio performance analyzer or other. I've added links to the benchmark, unit test and results to the ticket and switched status to patch avai

[jira] [Created] (IGNITE-4813) Ignite map-reduce engine should set MRJobConfig.TASK_ATTEMPT_ID

Ivan Veselovsky created IGNITE-4813: --- Summary: Ignite map-reduce engine should set MRJobConfig.TASK_ATTEMPT_ID Key: IGNITE-4813 URL: https://issues.apache.org/jira/browse/IGNITE-4813 Project: Ignite

[GitHub] ignite pull request #1609: Ignite 2.0 merge

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/1609 Ignite 2.0 merge You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.0-merge Alternatively you can review and ap

[GitHub] ignite pull request #1608: ignite-4806 Fix infinite classloading discovery

GitHub user zstan opened a pull request: https://github.com/apache/ignite/pull/1608 ignite-4806 Fix infinite classloading discovery You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4806 Alternatively

Re: The difference between ignite instances with different startup type

Hi, Please show your configuration and the code. -Val On Fri, Mar 10, 2017 at 4:22 AM, 下奈若 <969959...@qq.com> wrote: > Hi , > I am accessing to Big Data field recently and I find Apache Ignite > is a multipurpose tool that would be useful for me. > But I meet a problem while I run a

Re: IgniteConfiguration.gridName is very confusing

Hi, PR updated. Currently no conflicts at https://github.com/apache/ignite/pull/1435. On Thu, Mar 9, 2017 at 6:50 PM, Alexander Fedotov < alexander.fedot...@gmail.com> wrote: > Sure. Will take a look. > > On Thu, Mar 9, 2017 at 6:05 PM, Yakov Zhdanov wrote: > >> Alexander, >> >> Page https://git

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Maxim, I'll take a look today. 10 марта 2017 г. 11:06 AM пользователь "Kozlov Maxim" написал: > Andrey, Alexey, please review > PR - https://github.com/apache/ignite/pull/1521 < > https://github.com/apache/ignite/pull/1521> > tests - http://ci.ignite.apache.org/viewType.html?buildTypeId= > Igni

[jira] [Created] (IGNITE-4812) Disable EventStorageSpi by default

Valentin Kulichenko created IGNITE-4812: --- Summary: Disable EventStorageSpi by default Key: IGNITE-4812 URL: https://issues.apache.org/jira/browse/IGNITE-4812 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-4811) Reduce GC pressure using page memory

Igor Seliverstov created IGNITE-4811: Summary: Reduce GC pressure using page memory Key: IGNITE-4811 URL: https://issues.apache.org/jira/browse/IGNITE-4811 Project: Ignite Issue Type: Imp

The difference between ignite instances with different startup type

Hi , I am accessing to Big Data field recently and I find Apache Ignite is a multipurpose tool that would be useful for me. But I meet a problem while I run a demo code in Eclipse, I describe it by steps as below : STEP 1) I run %IGNITE_HOME%/bin/Iginte.bat with defa

[jira] [Created] (IGNITE-4810) Remove unused "removeIndex" methods

Vladimir Ozerov created IGNITE-4810: --- Summary: Remove unused "removeIndex" methods Key: IGNITE-4810 URL: https://issues.apache.org/jira/browse/IGNITE-4810 Project: Ignite Issue Type: Task

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Andrey, Alexey, please review PR - https://github.com/apache/ignite/pull/1521 tests - http://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests_RunAll&branch_IgniteTests=pull%2F1521%2Fhead&tab=buildTypeStatusDiv