Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Dmitriy Setrakyan
Andrey, this is the link I have: https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.6.0-rc1 This list does not look short. It looks like a copy of 2.5. D. On Wed, Jul 11, 2018 at 5:48 AM, Andrey Gura wrote: > Sorry, > > You could check it

Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Ilya Suntsov
Dmitry, I see 2.6 changes above 2.5: Apache Ignite Release Notes > === > Apache Ignite In-Memory Data Fabric 2.6 > --- > Ignite: > * Fixed incorrect calculation of client affinity assignment with baseline. > * Fixed incorrect

Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Dmitriy Setrakyan
Got it. I did not see the section up top. No more questions. On Wed, Jul 11, 2018 at 11:21 AM, Ilya Suntsov wrote: > Dmitry, > > I see 2.6 changes above 2.5: > > Apache Ignite Release Notes > > === > > Apache Ignite In-Memory Data Fabric 2.6 > >

[GitHub] ignite pull request #2728: ignite-5960 Race in innerUpdate fixed

2018-07-11 Thread voipp
Github user voipp closed the pull request at: https://github.com/apache/ignite/pull/2728 ---

Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Alexey Goncharuk
+1 Checked src archive signature, verified build from source, started a node with and without persistence. ср, 11 июл. 2018 г. в 11:24, Dmitriy Setrakyan : > Got it. I did not see the section up top. No more questions. > > On Wed, Jul 11, 2018 at 11:21 AM, Ilya Suntsov > wrote: > > > Dmitry, >

Re: Potential OOM while iterating over query cursor. Review needed.

2018-07-11 Thread Alexey Goncharuk
Folks, Bumping up the discussion as it is hitting one of the Ignite users. The change seams reasonable to me, but it is a breaking change and may affect existing users. Would the community be ok if we change the QueryCursor#getAll method for scan queries? If not, we should expose the keepAll()

[jira] [Created] (IGNITE-8980) Web console: regression on Queries screen

2018-07-11 Thread Pavel Konstantinov (JIRA)
Pavel Konstantinov created IGNITE-8980: -- Summary: Web console: regression on Queries screen Key: IGNITE-8980 URL: https://issues.apache.org/jira/browse/IGNITE-8980 Project: Ignite Issue

[jira] [Created] (IGNITE-8979) Web console: Unable to choose the item by the mouse in 'Refresh rate' dropdown in the Query

2018-07-11 Thread Pavel Konstantinov (JIRA)
Pavel Konstantinov created IGNITE-8979: -- Summary: Web console: Unable to choose the item by the mouse in 'Refresh rate' dropdown in the Query Key: IGNITE-8979 URL:

Re: Subscription

2018-07-11 Thread Dmitry Pavlov
Hi Ivan, it seems you've already subscribed. To subscribe it is sufficient to send emal to dev-subscr...@ignite.apache.org https://ignite.apache.org/community/resources.html#mail-lists Sincerely, Dmitriy Pavlov ср, 11 июл. 2018 г. в 4:20, Павлухин Иван : > Hi, > > Please subscribe me. > > --

[GitHub] ignite pull request #4348: Top fut change check

2018-07-11 Thread sergey-chugunov-1985
GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/4348 Top fut change check You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite top_fut_change_check Alternatively

[GitHub] ignite pull request #4319: IGNITE-8945: Add additional checks with informati...

2018-07-11 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4319 ---

Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Dmitry Pavlov
I thought these steps are to be run automatically within chain and no manual steps are required. Petr, please step in. ср, 11 июл. 2018 г. в 14:30, Anton Vinogradov : > I do NOT see that API was checked [1] and automated check [2] performed > > [1] > >

Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Anton Vinogradov
Automation possible, but it's hard to determine previous version automatically (especially when you have 2.x and 3.x releasing concurrently) for API check [1], but RC check [1] can be chained. [1]

[GitHub] ignite pull request #4038: IGNITE-8526 Create web-agent docker image for k8s...

2018-07-11 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4038 ---

Re: Potential OOM while iterating over query cursor. Review needed.

2018-07-11 Thread Andrey Mashenkov
Alexey, I saw no issues on TC with this change, and change affect only private API. If you think it can break smth, then we can mark keepAll flag as deprecated to be deleted in 3.0 and change default value to true. I doubt this flag is useful for Ignite internals, and moreover user always can

[jira] [Created] (IGNITE-8981) [ML] Parallel optimizations for BaggingTrainer

2018-07-11 Thread Yury Babak (JIRA)
Yury Babak created IGNITE-8981: -- Summary: [ML] Parallel optimizations for BaggingTrainer Key: IGNITE-8981 URL: https://issues.apache.org/jira/browse/IGNITE-8981 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-8982) SQL TX: reuse H2 connections

2018-07-11 Thread Ivan Pavlukhin (JIRA)
Ivan Pavlukhin created IGNITE-8982: -- Summary: SQL TX: reuse H2 connections Key: IGNITE-8982 URL: https://issues.apache.org/jira/browse/IGNITE-8982 Project: Ignite Issue Type: Improvement

[GitHub] ignite pull request #4321: IGNITE-7366. Code review reaction

2018-07-11 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4321 ---

Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Dmitry Pavlov
+1, checked RC ver. 2.6.0#20180710-sha1:669feacc as new DB for Ignite TC helper (MTCGA.Bot). Data was sucessfully restored from 2.5, tool is operational. I suggest to publish link to staging in vote threads. It is very convinient as I can add to gradle only maven { url

Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Vyacheslav Daradur
+1 Checked build from sources and run several examples. On Wed, Jul 11, 2018 at 7:55 PM Dmitry Pavlov wrote: > > +1, checked RC ver. 2.6.0#20180710-sha1:669feacc as new DB for Ignite TC > helper (MTCGA.Bot). Data was sucessfully restored from 2.5, tool is > operational. > > I suggest to

Re: PR Reivew https://github.com/apache/ignite/pull/4300

2018-07-11 Thread Dmitry Pavlov
Hi, Thanks to Stanislav L. for review. In the same time TC was not re-runned after changes and there is several suspicious failures in PR, so I've retriggered run-all. Let's wait for results and I'll check it one more time. Sincerely, Dmitriy Pavlov вт, 10 июл. 2018 г. в 20:52, kcheng.mvp : >

Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Dmitry Pavlov
No, I just wondering if it could be in chain. If manual run is requires I guess we could document it somewhere, so everyone in community will be aware what should be done. ср, 11 июл. 2018 г. в 14:41, Petr Ivanov : > Currently, I have no knowledge about this build types and theirs purpose. > > I

[GitHub] ignite pull request #4350: IGNITE-8981: Parallel optimizations for BaggingTr...

2018-07-11 Thread avplatonov
GitHub user avplatonov opened a pull request: https://github.com/apache/ignite/pull/4350 IGNITE-8981: Parallel optimizations for BaggingTrainer add Learning environment with Logger and Parallelism strategy while learning You can merge this pull request into a Git repository by

[jira] [Created] (IGNITE-8983) .NET long-running suite fails in master

2018-07-11 Thread Alexey Goncharuk (JIRA)
Alexey Goncharuk created IGNITE-8983: Summary: .NET long-running suite fails in master Key: IGNITE-8983 URL: https://issues.apache.org/jira/browse/IGNITE-8983 Project: Ignite Issue Type:

Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Anton Vinogradov
I do NOT see that API was checked [1] and automated check [2] performed [1] https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency=buildTypeHistoryList_ApacheIgniteReleaseJava8=__all_branches__ [2]

Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Ilya Suntsov
Anton, Please take a look at: https://ci.ignite.apache.org/viewLog.html?buildId=1478134=buildResultsDiv=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency

Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Ilya Suntsov
Anton, Module spark-2.10 and optional lib ignite-spark_2.10 were removed during the work on IGNITE-8534 IGNITE-8768 : +

Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Dmitry Pavlov
Anton, I totally agree it is needed, but not sure I'll have free time to do it soon. I will keep community posted. ср, 11 июл. 2018 г. в 17:01, Anton Vinogradov : > Ilya, > > thanks for detailed explanation. > > +1 now (binding). > > Dmitry Pavlov, > > could you please accumulate discussed and

[GitHub] ignite pull request #4329: IGNITE-8942

2018-07-11 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4329 ---

Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Petr Ivanov
Currently, I have no knowledge about this build types and theirs purpose. I guess release engineer has to run them manually with ignite-2.6 branch or with 2.6.0-rc1 build result. Should I do it? > On 11 Jul 2018, at 14:36, Dmitry Pavlov wrote: > > I thought these steps are to be run

[GitHub] ignite pull request #4349: IGNITE-8922 Fix delivery of pending messages

2018-07-11 Thread dmekhanikov
GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/4349 IGNITE-8922 Fix delivery of pending messages You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8922

Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Anton Vinogradov
Ilya, Please confirm that all changes [1] expected [1] https://ci.ignite.apache.org/repository/download/ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/1478134:id/results/result.log ср, 11 июл. 2018 г. в 16:23, Ilya Suntsov : > Anton, > > Please take a look at: > >

Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Alexey Kuznetsov
+1 (binding) Download sources: OK Build from sources: OK Run ignite.bat: OK -- Alexey Kuznetsov

Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Anton Vinogradov
Ilya, thanks for detailed explanation. +1 now (binding). Dmitry Pavlov, could you please accumulate discussed and prepare documentation about "how to release Apache Ignite step by step"? ср, 11 июл. 2018 г. в 16:57, Ilya Suntsov : > Anton, > > Module spark-2.10 and optional lib

[jira] [Created] (IGNITE-8985) Node segmented itself after connRecoveryTimeout

2018-07-11 Thread Mikhail Cherkasov (JIRA)
Mikhail Cherkasov created IGNITE-8985: - Summary: Node segmented itself after connRecoveryTimeout Key: IGNITE-8985 URL: https://issues.apache.org/jira/browse/IGNITE-8985 Project: Ignite

[jira] [Created] (IGNITE-8986) Need to add configuration validation template on startup

2018-07-11 Thread Dmitriy Setrakyan (JIRA)
Dmitriy Setrakyan created IGNITE-8986: - Summary: Need to add configuration validation template on startup Key: IGNITE-8986 URL: https://issues.apache.org/jira/browse/IGNITE-8986 Project: Ignite

Re: Clusterwide settings validation

2018-07-11 Thread Dmitriy Setrakyan
BTW, I have added a ticket for the configuration template [1] and linked it to the ticket originally created by Yakov [2]. [1] https://issues.apache.org/jira/browse/IGNITE-8986 [2] https://issues.apache.org/jira/browse/IGNITE-8951 D. On Wed, Jul 11, 2018 at 6:58 PM, Yakov Zhdanov wrote: >

Re: Clusterwide settings validation

2018-07-11 Thread Yakov Zhdanov
Ivan, yes. We can go with reflection through configuration and SPIs and, you are rigth, suppressed list should be manually defined. --Yakov

[jira] [Created] (IGNITE-8984) Ignite 2.5 - Vulnerabilities

2018-07-11 Thread Segu Riluvan (JIRA)
Segu Riluvan created IGNITE-8984: Summary: Ignite 2.5 - Vulnerabilities Key: IGNITE-8984 URL: https://issues.apache.org/jira/browse/IGNITE-8984 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #4288: IGNITE-8905 incorrect assertion was replaced with...

2018-07-11 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4288 ---

Re: Potential OOM while iterating over query cursor. Review needed.

2018-07-11 Thread Alexey Goncharuk
Andrey, Correct me if I am wrong, but my impression was that after the change cursor#getAll() will return only the last page of the result, not the whole collection. If public API method semantics is preserved, then no objections from my side. ср, 11 июл. 2018 г. в 15:18, Andrey Mashenkov : >

[jira] [Created] (IGNITE-8987) Ignite hangs during getting of atomic structure after autoactivation

2018-07-11 Thread Andrey Aleksandrov (JIRA)
Andrey Aleksandrov created IGNITE-8987: -- Summary: Ignite hangs during getting of atomic structure after autoactivation Key: IGNITE-8987 URL: https://issues.apache.org/jira/browse/IGNITE-8987

Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Andrey Gura
+1 (binding) Checked: - build from sources; - artifacts' hashes; - examples. On Wed, Jul 11, 2018 at 5:06 PM Dmitry Pavlov wrote: > > Anton, I totally agree it is needed, but not sure I'll have free time to do > it soon. I will keep community posted. > > ср, 11 июл. 2018 г. в 17:01, Anton

[jira] [Created] (IGNITE-8988) Web console: error in Readme.txt of generated project

2018-07-11 Thread Pavel Konstantinov (JIRA)
Pavel Konstantinov created IGNITE-8988: -- Summary: Web console: error in Readme.txt of generated project Key: IGNITE-8988 URL: https://issues.apache.org/jira/browse/IGNITE-8988 Project: Ignite

[jira] [Created] (IGNITE-8990) Web console: unexpected 'Unsaved changes' warning

2018-07-11 Thread Pavel Konstantinov (JIRA)
Pavel Konstantinov created IGNITE-8990: -- Summary: Web console: unexpected 'Unsaved changes' warning Key: IGNITE-8990 URL: https://issues.apache.org/jira/browse/IGNITE-8990 Project: Ignite

[jira] [Created] (IGNITE-8989) Web console: incorrect initial state of some checkboxes on Client Configuration panel

2018-07-11 Thread Pavel Konstantinov (JIRA)
Pavel Konstantinov created IGNITE-8989: -- Summary: Web console: incorrect initial state of some checkboxes on Client Configuration panel Key: IGNITE-8989 URL: https://issues.apache.org/jira/browse/IGNITE-8989