Re: Critical worker threads liveness checking drawbacks

[Andrey Kuznetsov]

Igniters,

Now I spot blocking / long-running code arising from
{{GridDhtPartitionsExchangeFuture#init}} calls in partition-exchanger
thread, see [1]. Ideally, all blocking operations along all possible code
paths should be guarded implicitly from critical failure detector to avoid
the thread from being considered blocked. There is a pull request [2] that
provides shallow solution. I didn't change code outside
{{GridDhtPartitionsExchangeFuture}}, otherwise it could be broken by any
upcoming change. Also, I didn't touch the code runnable by threads other
than partition-exchanger. So I have a number of guarded sections that are
wider than they could be, and this potentially hides issues from failure
detector. Does this PR make sense? Or maybe it's better to exclude
partition-exchanger from critical threads registry at all?

[1] https://issues.apache.org/jira/browse/IGNITE-9710
[2] https://github.com/apache/ignite/pull/4962


пт, 28 сент. 2018 г. в 18:56, Maxim Muzafarov :

> Andrey, Andrey
>
> > Thanks for being attentive! It's definitely a typo. Could you please
> create
> > an issue?
>
> I've created an issue [1] and prepared PR [2].
> Please, review this change.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-9723
> [2] https://github.com/apache/ignite/pull/4862
>
> On Fri, 28 Sep 2018 at 16:58 Yakov Zhdanov  wrote:
>
> > Config option + mbean access. Does that make sense?
> >
> > Yakov
> >
> > On Fri, Sep 28, 2018, 17:17 Vladimir Ozerov 
> wrote:
> >
> > > Then it should be config option.
> > >
> > > пт, 28 сент. 2018 г. в 13:15, Andrey Gura :
> > >
> > > > Guys,
> > > >
> > > > why we need both config option and system property? I believe one way
> > is
> > > > enough.
> > > > On Fri, Sep 28, 2018 at 12:38 PM Nikolay Izhikov <
> nizhi...@apache.org>
> > > > wrote:
> > > > >
> > > > > Ticket created - https://issues.apache.org/jira/browse/IGNITE-9737
> > > > >
> > > > > Fixed version is 2.7.
> > > > >
> > > > > В Пт, 28/09/2018 в 11:41 +0300, Alexey Goncharuk пишет:
> > > > > > Nikolay, I agree, a user should be able to disable both thread
> > > liveness
> > > > > > check and checkpoint read lock timeout check from config and a
> > system
> > > > > > property.
> > > > > >
> > > > > > пт, 28 сент. 2018 г. в 11:30, Nikolay Izhikov <
> nizhi...@apache.org
> > >:
> > > > > >
> > > > > > > Hello, Igniters.
> > > > > > >
> > > > > > > I found that this feature can't be disabled from config.
> > > > > > > The only way to disable it is from JMX bean.
> > > > > > >
> > > > > > > I think it very dangerous: If we have some corner case or a bug
> > in
> > > > this
> > > > > > > Watch Dog it can make Ignite unusable.
> > > > > > > I propose to implement possibility to disable this feature
> both -
> > > > from
> > > > > > > config and from JVM options.
> > > > > > >
> > > > > > > What do you think?
> > > > > > >
> > > > > > > В Чт, 27/09/2018 в 16:14 +0300, Andrey Kuznetsov пишет:
> > > > > > > > Maxim,
> > > > > > > >
> > > > > > > > Thanks for being attentive! It's definitely a typo. Could you
> > > > please
> > > > > > >
> > > > > > > create
> > > > > > > > an issue?
> > > > > > > >
> > > > > > > > чт, 27 сент. 2018 г. в 16:00, Maxim Muzafarov <
> > > maxmu...@gmail.com
> > > > >:
> > > > > > > >
> > > > > > > > > Folks,
> > > > > > > > >
> > > > > > > > > I've found in `GridCachePartitionExchangeManager:2684` [1]
> > > > (master
> > > > > > >
> > > > > > > branch)
> > > > > > > > > exchange future wrapped
> > > > > > > > > with double `blockingSectionEnd` method. Is it correct? I
> > just
> > > > want to
> > > > > > > > > understand this change and
> > > > > > > > > how should I use this in the future.
> > > > > > > > >
> > > > > > > > > Should I file a new issue to fix this? I think here
> > > > > > >
> > > > > > > `blockingSectionBegin`
> > > > > > > > > method should be used.
> > > > > > > > >
> > > > > > > > > -
> > > > > > > > > blockingSectionEnd();
> > > > > > > > >
> > > > > > > > > try {
> > > > > > > > > resVer = exchFut.get(exchTimeout,
> TimeUnit.MILLISECONDS);
> > > > > > > > > } finally {
> > > > > > > > > blockingSectionEnd();
> > > > > > > > > }
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > [1]
> > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > > > > >
> > > >
> > >
> >
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCachePartitionExchangeManager.java#L2684
> > > > > > > > >
> > > > > > > > > On Wed, 26 Sep 2018 at 22:47 Vyacheslav Daradur <
> > > > daradu...@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Andrey Gura, thank you for the answer!
> > > > > > > > > >
> > > > > > > > > > I agree that wrapping of 'init' method reduces the profit
> > of
> > > > watchdog
> > > > > > > > > > service in case of PME worker, but in other cases, we
> > should
> > > > wrap all
> > > > > > > > > > possible long sections on GridDhtPartitionExchangeFuture.
> > For
> > > > 

Re: Apache Ignite 2.7. Last Mile

[Nikolay Izhikov]

Hello, Igniters.

We made some progress yesterday.

Please, note, we have 1 new ticket mapped to 2.7 "IGNITE-9852: Create TeamCity 
suite for Python thin client"

This ticket doesn't sound like a blocker to me. Let's exclude it from release 
scope.
Thoughts?

Here is the list of remaining tickets(14) mapped to 2.7.

Peter Ivanov   - IGNITE-9852, IGNITE-9685, 
Alexey Goncharuk   - IGNITE-9784
Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
Igor Seliverstov   - IGNITE-9749, IGNITE-9292
Dmitry Melnichuk   - IGNITE-7782
Ivan Pavlukhin - IGNITE-5935
Yury Babak - IGNITE-8670
Roman Kondakov - IGNITE-7953
Igor Sapego- IGNITE-9620
Alexey Stelmak - IGNITE-9776

Unassigned:

IGNITE-9663 - MVCC: Data node failure can cause TX hanging.


В Чт, 11/10/2018 в 13:50 +0300, Nikolay Izhikov пишет:
> Alexey, we all agreed to merge in 2.7 blockers only.
> 
> Is this a blocker?
> 
> Anyway, you are more experienced Igniter that I am.
> If you think we should include this ticket to 2.7 - please, do it.
> 
> В Чт, 11/10/2018 в 13:08 +0300, Alexey Goncharuk пишет:
> > Nikolay,
> > 
> > I am waiting for final benchmark results for 9784, after that I will merge
> > the change.
> > 
> > On the subject of Ignite 2.7 scope, our fellow Igniter Alexey Platonov have
> > found another case when a failure handler is incorrectly called on node
> > stop: https://issues.apache.org/jira/browse/IGNITE-9834. The case is rare,
> > but it is quite an unpleasant UX. Should we include it to 2.7 as well?
> > 
> > чт, 11 окт. 2018 г. в 11:22, Nikolay Izhikov :
> > 
> > > Hello, Igniters.
> > > 
> > > We made a good progress yesterday.
> > > 
> > > Here is the list of remaining tickets(17) mapped to 2.7:
> > > 
> > > Alexey Goncharuk   - IGNITE-9784
> > > Taras Ledkov   - IGNITE-9171
> > > Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> > > Peter Ivanov   - IGNITE-9583, IGNITE-9823, IGNITE-9685
> > > Igor Seliverstov   - IGNITE-9749, IGNITE-9292
> > > Dmitry Melnichuk   - IGNITE-7782
> > > Ivan Pavlukhin - IGNITE-5935
> > > Yury Babak - IGNITE-8670
> > > Roman Kondakov - IGNITE-7953, IGNITE-9446
> > > Alexey Stelmak - IGNITE-9776
> > > 
> > > Unassigned:
> > > 
> > > IGNITE-9620 - MVCC: select throwing `Transaction is already completed`> >
> > > > exception after mvcc missmatch
> > > 
> > > IGNITE-9663 - MVCC: Data node failure can cause TX hanging.
> > > 
> > > 
> > > В Чт, 11/10/2018 в 10:40 +0300, Vladimir Ozerov пишет:
> > > > What kind of help is needed?
> > > > 
> > > > On Wed, Oct 10, 2018 at 11:51 PM Dmitriy Setrakyan <
> > > 
> > > dsetrak...@apache.org>
> > > > wrote:
> > > > 
> > > > > Vladimir Ozerov,
> > > > > 
> > > > > Can you help with the unassigned MVCC tickets?
> > > > > 
> > > > > D.
> > > > > 
> > > > > On Wed, Oct 10, 2018 at 3:32 AM Nikolay Izhikov 
> > > > > wrote:
> > > > > 
> > > > > > Hello, Igniters.
> > > > > > 
> > > > > > I list all contributors that assigned to the 2.7 tickets.
> > > > > > If you can help them to finish that tickets - please, do.
> > > > > > Assigners, if you need any help - please, respond to this thread.
> > > > > > 
> > > > > > NOTE: We have 6 Unassigned tickets for 2.7. Let's start work on it!
> > > > > > 
> > > > > > Peter Ivanov   - IGNITE-9559, IGNITE-9583, IGNITE-9685,
> > > 
> > > IGNITE-9823
> > > > > > Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> > > > > > Taras Ledkov   - IGNITE-9171
> > > > > > Alexey Goncharuk   - IGNITE-9784
> > > > > > Dmitriy Govorukhin - IGNITE-9550
> > > > > > Igor Seliverstov   - IGNITE-9749
> > > > > > Dmitry Melnichuk   - IGNITE-7782
> > > > > > Alexey Platonov- IGNITE-9726
> > > > > > Ivan Pavlukhin - IGNITE-5935
> > > > > > Yury Babak - IGNITE-8670
> > > > > > Roman Kondakov - IGNITE-7953, IGNITE-9446
> > > > > > Maxim Pudov- IGNITE-9126
> > > > > > Alexey Stelmak - IGNITE-9776
> > > > > > Alexey Kuznetsov   - IGNITE-7926
> > > > > > 
> > > > > > Unassigned tickets:
> > > > > > 
> > > > > > IGNITE-9781 - JDK11: SSL handshake is failed
> > > > > > IGNITE-9620 - MVCC: select throwing `Transaction is already
> > > 
> > > completed`
> > > > > > exception after mvcc missmatch
> > > > > > IGNITE-9292 - MVCC SQL: Unexpected state exception when updating
> > > 
> > > backup
> > > > > > IGNITE-9663 - MVCC: Data node failure can cause TX hanging.
> > > > > > IGNITE-9724 - MVCC SQL: Test
> > > > > > 
> > > 
> > > CacheMvccSelectForUpdateQueryAbstractTest.testSelectForUpdateDistributed
> > > > > > hangs sporadically.
> > > > > > IGNITE-9133 - MVCC: Proper empty DHT transactions handling.
> > > > > > 


signature.asc
Description: This is a digitally signed message part

[GitHub] ignite pull request #4966: IGNITE-9862 Web Console: Add support for "date", ...

[akuznetsov-gridgain]

GitHub user akuznetsov-gridgain opened a pull request:

https://github.com/apache/ignite/pull/4966

IGNITE-9862 Web Console: Add support for "date", "time" and "date-and…

…-time" to InputDialog.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-9862

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4966.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4966


commit 2fd5342ca62313638ca68b489092613139ac
Author: Alexey Kuznetsov 
Date:   2018-10-12T05:00:39Z

IGNITE-9862 Web Console: Add support for "date", "time" and "date-and-time" 
to InputDialog.




---

[jira] [Created] (IGNITE-9862) Web Console: Add support for "date", "time" and "date-and-time" on InputDialog

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-9862:


 Summary: Web Console: Add support for "date", "time" and 
"date-and-time" on InputDialog
 Key: IGNITE-9862
 URL: https://issues.apache.org/jira/browse/IGNITE-9862
 Project: Ignite
  Issue Type: Task
  Components: wizards
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 2.8


It will be useful also support following types "date", "time" and 
"date-and-time" in order to input them via this dialog.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #4957: Ignite 2.4.12 test

[antkr]

Github user antkr closed the pull request at:

https://github.com/apache/ignite/pull/4957


---

[GitHub] ignite pull request #4965: Ignite 2.4.12

[antkr]

GitHub user antkr opened a pull request:

https://github.com/apache/ignite/pull/4965

Ignite 2.4.12



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.12

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4965.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4965


commit 2c39ec5dda1a05d03e1317b740fbafee8dd874f0
Author: devozerov 
Date:   2018-03-29T10:46:47Z

Merge branch 'ignite-2.4.4' into ignite-2.4-master

commit a58bc16543e72dfc3a2b97c50506cd532d4d9dee
Author: devozerov 
Date:   2018-03-29T12:21:46Z

IGNITE-7421: Reverted invalid server-side authentication.

commit e7ec84a17c5999441f1731aad64f540fd2eda279
Author: devozerov 
Date:   2018-03-29T12:23:26Z

Merge branch 'ignite-2.4.4' into ignite-2.4-master

commit 188279848a75d6458b9441d65917fb628834355e
Author: devozerov 
Date:   2018-03-30T09:04:33Z

IGNITE-7657: Minor style fixes: imports, forgotten javadocs, annotations. 
This closes #3496.

commit b4320072ca75e5b11bbeeb033c2f60f31f4855f9
Author: devozerov 
Date:   2018-03-30T09:18:10Z

Merge remote-tracking branch 'upstream/ignite-2.4.4' into ignite-2.4.4

commit b0de9d14caaf2bfc91c4f8283b0806c354ef7b73
Author: Alexey Goncharuk 
Date:   2018-03-30T14:40:28Z

IGNITE-8053 Make sure local partitions collection does not change

commit 7214eff5b5d8102ba32a7b7bf7597ac5a4b04eee
Author: Alexey Kukushkin 
Date:   2018-04-02T08:08:05Z

IGNITE-8076: Java Thin Client: authentication. This closes #3720.

commit 2c0e269fe7793bb70d1be28d2052f1394b96f2b1
Author: devozerov 
Date:   2018-04-02T08:09:17Z

Merge branch 'ignite-2.4.4' into ignite-2.4-master

commit cb89494be26be1b0e397e06f7eaeb6419aec1828
Author: Alexey Kuznetsov 
Date:   2018-03-02T09:35:26Z

IGNITE-7803 REST: Implemented possibility to get values from cache inserted 
via API or SQL.

(cherry picked from commit a84018b)

commit 149802a3be82ba1f88770dbff75d74b892bb0a94
Author: Alexey Kuznetsov 
Date:   2018-03-07T17:17:20Z

IGNITE-7803 Fixed regression in tests.

(cherry picked from commit 90c0af8)

commit 5b5571adc7282a29cdecd8ab2e945a446ea709fc
Author: Alexey Kuznetsov 
Date:   2018-03-23T02:55:13Z

IGNITE-8002 REST: Added support of new authentication via new API.

(cherry picked from commit 921f0cf)

commit 128fdfcd874286f4a358546c0f43b6ef082a064b
Author: devozerov 
Date:   2018-04-02T10:11:16Z

IGNITE-7884: Sample data set for JDBC. This closes #3702.

commit 247a9ef5a68de198106a866b277f1bee596c3633
Author: devozerov 
Date:   2018-04-02T10:16:00Z

Merge branch 'ignite-2.4.4' into ignite-2.4-master

commit 3949df02128e3003c409e0169ad0c80948ba134c
Author: Aleksey Plekhanov 
Date:   2018-02-13T13:43:49Z

IGNITE-5265 Eviction Rate memory metric to be implemented

Signed-off-by: Anton Vinogradov 

commit 7bc6c1ad3bacaf5e354d2710931eb398c346c06c
Author: Tim Onyschak 
Date:   2018-03-31T12:58:25Z

IGNITE-7090 Semaphore Stuck when no acquirers to assign permit - Fixes 
#3443.

Signed-off-by: dspavlov 

(cherry picked from commit 3fc5d57)

commit c854ad86f4c64260171085c8c7cce97ba1ad2530
Author: Pavel Kovalenko 
Date:   2018-02-22T09:02:31Z

IGNITE-7749 Fixed testDiscoCacheReuseOnNodeJoin test. - Fixes #3540.

Signed-off-by: Alexey Goncharuk 

commit b2e94b36bddebbf7b3ff40631e099939d16926d2
Author: Alexey Goncharuk 
Date:   2018-02-13T15:53:23Z

IGNITE-7692 Corrected test to not fail when SQL is executed on backup

commit 852425d4170ed1871c79f5ac26bfb3d03cc36a6f
Author: Алексей Стельмак 
Date:   2018-04-06T15:28:22Z

IGNITE-8049 Limit the number of operation cycles in B+Tree - Fixes #3769.

Signed-off-by: dpavlov 
(cherry picked from commit e491f10)

commit 42f529f0a04ce22786bb4a23032a64f93e214233
Author: Alexey Kuznetsov 
Date:   2018-04-09T02:25:50Z

IGNITE-8159 control.sh: Fixed NPE on adding nodes on empty baseline and not 
active cluster.

(cherry picked from commit 834869c)

commit b5f180838246f895d36846ea707790c1ff7fe70a
Author: Stanislav Lukyanov 
Date:   2018-04-09T11:33:13Z

IGNITE-7904: Changed IgniteUtils::cast not to trim exception chains. This 
closes #3683.

(cherry picked from commit 3a4f23b)

commit 1ce8e1a8fd48469073592e2fb77e2881a168a219
Author: Roman Guseinov 
Date:   2018-04-09T11:45:44Z

IGNITE-7944: Disconnected client node tries to send JOB_CANCEL message. 
Applied fix:
- Skip sending message if client disconnected;
- Throw IgniteCheckedException if a client node is disconnected and 
communication client is null.
This closes #3737.

(cherry picked from commit d70477b)

commit 840e193b3e604e8b0d90be5fac16cf11d8c832e6
Author: Ilya Lantukh 
Date:   2018-04-06T10:49:10Z

   

[GitHub] ololo3000 opened a new pull request #36: IGNITE-9645 [TC Bot] Add comparison of failed tests lists in two date intervals

[GitBox]

ololo3000 opened a new pull request #36: IGNITE-9645 [TC Bot] Add comparison of 
failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/36
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] ololo3000 closed pull request #25: IGNITE-9645 [TC Bot] Add comparison of failed tests lists in two date intervals

[GitBox]

ololo3000 closed pull request #25: IGNITE-9645 [TC Bot] Add comparison of 
failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/25
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/ITeamcity.java 
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/ITeamcity.java
index 6aa3b60..b0157c8 100644
--- a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/ITeamcity.java
+++ b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/ITeamcity.java
@@ -36,15 +36,18 @@
 import org.apache.ignite.ci.tcmodel.conf.BuildType;
 import org.apache.ignite.ci.tcmodel.hist.BuildRef;
 import org.apache.ignite.ci.tcmodel.result.Build;
+import org.apache.ignite.ci.tcmodel.result.Configurations;
 import org.apache.ignite.ci.tcmodel.result.issues.IssuesUsagesList;
 import org.apache.ignite.ci.tcmodel.result.problems.ProblemOccurrences;
 import org.apache.ignite.ci.tcmodel.result.stat.Statistics;
 import org.apache.ignite.ci.tcmodel.result.tests.TestOccurrence;
 import org.apache.ignite.ci.tcmodel.result.tests.TestOccurrenceFull;
 import org.apache.ignite.ci.tcmodel.result.tests.TestOccurrences;
+import org.apache.ignite.ci.tcmodel.result.tests.TestRef;
 import org.apache.ignite.ci.tcmodel.user.User;
 import org.apache.ignite.ci.teamcity.pure.ITeamcityConn;
 import org.apache.ignite.ci.util.Base64Util;
+import org.apache.ignite.ci.web.rest.parms.FullQueryParams;
 import org.jetbrains.annotations.NotNull;
 
 import static com.google.common.base.Strings.isNullOrEmpty;
@@ -152,8 +155,12 @@ default Build getBuild(int id) {
  */
 ProblemOccurrences getProblems(Build build);
 
+ProblemOccurrences getProblems(BuildRef buildId);
+
 TestOccurrences getTests(String href, String normalizedBranch);
 
+TestOccurrences getFailedUnmutedTestsNames(String href, int count, String 
normalizedBranch);
+
 Statistics getBuildStatistics(String href);
 
 CompletableFuture getTestFull(String href);
@@ -162,6 +169,10 @@ default Build getBuild(int id) {
 
 ChangesList getChangesList(String href);
 
+CompletableFuture getTestRef(FullQueryParams key);
+
+Configurations getConfigurations(FullQueryParams key);
+
 /**
  * List of build's related issues.
  *
diff --git 
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java
 
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java
index d1e94e4..774e21b 100644
--- 
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java
+++ 
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java
@@ -66,16 +66,19 @@
 import org.apache.ignite.ci.tcmodel.conf.BuildType;
 import org.apache.ignite.ci.tcmodel.hist.BuildRef;
 import org.apache.ignite.ci.tcmodel.result.Build;
+import org.apache.ignite.ci.tcmodel.result.Configurations;
 import org.apache.ignite.ci.tcmodel.result.issues.IssuesUsagesList;
 import org.apache.ignite.ci.tcmodel.result.problems.ProblemOccurrences;
 import org.apache.ignite.ci.tcmodel.result.stat.Statistics;
 import org.apache.ignite.ci.tcmodel.result.tests.TestOccurrence;
 import org.apache.ignite.ci.tcmodel.result.tests.TestOccurrenceFull;
 import org.apache.ignite.ci.tcmodel.result.tests.TestOccurrences;
+import org.apache.ignite.ci.tcmodel.result.tests.TestRef;
 import org.apache.ignite.ci.tcmodel.user.User;
 import org.apache.ignite.ci.util.CacheUpdateUtil;
 import org.apache.ignite.ci.util.CollectionUtil;
 import org.apache.ignite.ci.util.ObjectInterner;
+import org.apache.ignite.ci.web.rest.parms.FullQueryParams;
 import org.jetbrains.annotations.NotNull;
 import org.slf4j.Logger;
 import org.slf4j.LoggerFactory;
@@ -104,6 +107,8 @@
 private static final String BUILD_HIST_FINISHED = "buildHistFinished";
 private static final String BUILD_HIST_FINISHED_OR_FAILED = 
"buildHistFinishedOrFailed";
 public static final String BOT_DETECTED_ISSUES = "botDetectedIssues";
+public static final String TEST_REFS = "testRefs";
+public static final String CONFIGURATIONS = "configurations";
 
 //todo need separate cache or separate key for 'execution time' because it 
is placed in statistics
 private static final String BUILDS_FAILURE_RUN_STAT = 
"buildsFailureRunStat";
@@ -125,6 +130,9 @@
  */
 private ConcurrentMap> 
testOccFullFutures = new ConcurrentHashMap<>();
 
+/** Cached loads of test refs.*/
+private ConcurrentMap> testRefsFutures 
= new ConcurrentHashMap<>();
+
 /** cached running builds for branch. */
 private ConcurrentMap>> queuedBuilds = 
new ConcurrentHashMap<>();
 
@@ -162,7 +170,8 @@
 buildProblemsCache(),
 

[MTCGA]: new failures in builds [2054148] needs to be handled

[dpavlov . tasks]

Hi Igniters,

 I've detected some new issue on TeamCity to be handled. You are more than 
welcomed to help.

 If your changes can lead to this failure(s): We're grateful that you were a 
volunteer to make the contribution to this project, but things change and you 
may no longer be able to finalize your contribution.
 Could you respond to this email and indicate if you wish to continue and fix 
test failures or step down and some committer may revert you commit. 

 *New stable failure of a flaky test in master 
IgniteSinkConnectorTest.testSinkPutsWithoutTransformation 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7952366899750322781=%3Cdefault%3E=testDetails
 Changes may lead to failure were done by 
 - mr.weider 
http://ci.ignite.apache.org/viewModification.html?modId=834682=false
 - pudov.max 
http://ci.ignite.apache.org/viewModification.html?modId=834650=false
 - vozerov 
http://ci.ignite.apache.org/viewModification.html?modId=834638=false
 - daradurvs 
http://ci.ignite.apache.org/viewModification.html?modId=834325=false
 - vololo100 
http://ci.ignite.apache.org/viewModification.html?modId=834310=false

 - Here's a reminder of what contributors were agreed to do 
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute 
 - Should you have any questions please contact dev@ignite.apache.org 

Best Regards,
Apache Ignite TeamCity Bot 
https://github.com/apache/ignite-teamcity-bot
Notification generated at 01:10:41 12-10-2018 

[GitHub] ignite pull request #4964: IGNITE-9284 Add standard scaler

[dehasi]

GitHub user dehasi opened a pull request:

https://github.com/apache/ignite/pull/4964

IGNITE-9284 Add standard scaler



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dehasi/ignite 
feature/ignite-9284-add-standard-scaler

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4964.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4964


commit 16a51bb2ed820e2c080a9c9d29b1be2ffc0e827b
Author: dehasi 
Date:   2018-10-07T13:25:22Z

IGNITE-9284: Create package for standard scaler

commit cb93def4914954bd9b5f9529f6153e421dea8ff1
Author: dehasi 
Date:   2018-10-07T13:42:58Z

IGNITE-9284: Implement a standard scaler

commit 34450cd6345a3540145d2c43142fd8d995803d5f
Author: dehasi 
Date:   2018-10-07T18:04:30Z

IGNITE-9284: Add a standard scaler preprocessor test template

commit a9af7030f3792628fd0cf0af70d80d89f65cb055
Author: dehasi 
Date:   2018-10-09T04:54:04Z

IGNITE-9284: Add more data to test

commit 834fea10ef6d33257499574de2c1f1b1f66e2298
Author: dehasi 
Date:   2018-10-09T15:47:12Z

IGNITE-9284: Finish preprocessor

commit 724aedf7e1afcbafe8c4feb19b3f8bcd51e54ef3
Author: dehasi 
Date:   2018-10-09T17:57:03Z

IGNITE-9284: Add standard scaler trainer

commit 9c6f5ce4a98942452cea03ad7108253d747c9e17
Author: dehasi 
Date:   2018-10-09T18:09:28Z

IGNITE-9284: Add trainer test template

commit c7bf8d815dd782c703200cdc3373ad299105617a
Author: dehasi 
Date:   2018-10-09T18:21:58Z

IGNITE-9284: Extract common part from tests

commit f49b66f80fe0b4be83984eafab2ae55956f85866
Author: dehasi 
Date:   2018-10-09T18:26:06Z

IGNITE-9284: Complete test the standard scaler trainer

commit 6019c8e00975941d2f36e3c18daeb29a52ff130b
Author: dehasi 
Date:   2018-10-10T04:39:31Z

IGNITE-9284: Add trainer example

commit 98570cf0461198873a4b9722eaa167042e59fa2e
Author: dehasi 
Date:   2018-10-10T15:46:54Z

IGNITE-9284: Count sigma with mean




---

[GitHub] ignite pull request #4963: IGNITE-9861: Authorization object names must alwa...

[BiryukovVA]

GitHub user BiryukovVA opened a pull request:

https://github.com/apache/ignite/pull/4963

IGNITE-9861: Authorization object names must always be non-null.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/BiryukovVA/ignite IGNITE-9861

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4963.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4963


commit f97dfaec3baf9d60ae1c0c8683db2e7281533b6a
Author: Vitaliy Biryukov 
Date:   2018-10-11T18:43:53Z

IGNITE-9861: Authorization object names must always be non-null.




---

[GitHub] ignite pull request #4559: Ignite 9280

[andrey-kuznetsov]

Github user andrey-kuznetsov closed the pull request at:

https://github.com/apache/ignite/pull/4559


---

[GitHub] ignite pull request #4736: Ignite 6587 debug

[andrey-kuznetsov]

Github user andrey-kuznetsov closed the pull request at:

https://github.com/apache/ignite/pull/4736


---

[GitHub] ignite pull request #4089: Ignite 6587 true

[andrey-kuznetsov]

Github user andrey-kuznetsov closed the pull request at:

https://github.com/apache/ignite/pull/4089


---

[GitHub] ignite pull request #4962: IGNITE-9710 Ignite watchdog service handles longr...

[andrey-kuznetsov]

GitHub user andrey-kuznetsov opened a pull request:

https://github.com/apache/ignite/pull/4962

IGNITE-9710 Ignite watchdog service handles longrunning cache creation



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/andrey-kuznetsov/ignite ignite-9710

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4962.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4962


commit 2eb31c9d1680ecb7a3c16284c96fc4641e330dba
Author: Andrey Kuznetsov 
Date:   2018-10-11T15:09:13Z

IGNITE-9710 Added blocking sections in GridDhtPartitionsExchangeFuture#init.

commit 269bc84894138d654fe448ca93b09369e9878e3d
Author: Andrey Kuznetsov 
Date:   2018-10-11T16:21:44Z

Merge branch 'master' into ignite-9710

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/preloader/GridDhtPartitionsExchangeFuture.java

commit d667c11853a212fb3bad41d4f7be933f4ff35dc1
Author: Andrey Kuznetsov 
Date:   2018-10-11T18:10:33Z

IGNITE-9710 Fixing blocking sections.




---

[GitHub] ignite pull request #4015: Ignite 6587

[andrey-kuznetsov]

Github user andrey-kuznetsov closed the pull request at:

https://github.com/apache/ignite/pull/4015


---

[jira] [Created] (IGNITE-9861) Authorization object names must always be non-null.

[Vitaliy Biryukov (JIRA)]

Vitaliy Biryukov created IGNITE-9861:


 Summary: Authorization object names must always be non-null.
 Key: IGNITE-9861
 URL: https://issues.apache.org/jira/browse/IGNITE-9861
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.6
Reporter: Vitaliy Biryukov
Assignee: Vitaliy Biryukov
 Fix For: 2.8


Currently, sometimes *null* name parameter passing to a method 
*GridSecurityProcessor:authorize*. This leads to the fact that it is impossible 
to determine the authorization object by authorization event.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #4961: IGNITE-9739 don't write non-baseline nodes to wal...

[macrergate]

GitHub user macrergate opened a pull request:

https://github.com/apache/ignite/pull/4961

IGNITE-9739 don't write non-baseline nodes to wal TxRecord



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-9739

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4961.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4961


commit 95ee30d9e1c0c69e7a7d251fd61b86fe9f5528d4
Author: Sergey Kosarev 
Date:   2018-10-11T17:44:51Z

IGNITE-9739 don't write non-baseline nodes to wal TxRecord




---

[GitHub] ignite pull request #4960: Ignite-2.5.1-p14-hotfix-pme

[dgovorukhin]

GitHub user dgovorukhin opened a pull request:

https://github.com/apache/ignite/pull/4960

Ignite-2.5.1-p14-hotfix-pme



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite 
ignite-2.5.1-p14-hotfix-pme

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4960.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4960


commit bad52d3843925d831e6d357a4382731751ae6bb7
Author: Ilya Lantukh 
Date:   2018-06-04T14:07:52Z

GG-13862 : Disabled fast eviction.

(cherry picked from commit 786633d)

commit 6956097ceedd2e3e9edcb627d97e49afb7f0a26d
Author: Pavel Kovalenko 
Date:   2018-06-06T12:24:39Z

IGNITE-8482 Skip 2-phase partition release wait in case of activation or 
dynamic caches start - Fixes #4078.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 7c565d2)

commit d777c76eadd0a2ccc50f1031c42626b135da5906
Author: Dmitriy Govorukhin 
Date:   2018-06-06T14:20:18Z

IGNITE-8685 Fixed switch segment record size - Fixes #4130.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 2a048bd)

commit ef4782d8a60eea870b43933480f2c9695c9fc55d
Author: Alexey Goncharuk 
Date:   2018-06-07T11:55:13Z

IGNITE-8706 Fixed testMemoryUsageMultipleNodes

commit 6902383e01ee69d7efff9613a68f3fc419152305
Author: Pavel Kovalenko 
Date:   2018-05-14T10:14:52Z

IGNITE-8422 Tests fix for Zookeeper discovery split brain detection 
shouldn't consider client nodes - Fixes #3975.

Signed-off-by: dpavlov 

(cherry-picked from commit #19cbf8058b48a1f8fec60f7ceac70229e7c5391a)

commit 6eef070f8e0627e2986d870cc09ceb9cb351ee0d
Author: Sergey Chugunov 
Date:   2018-05-14T17:09:33Z

IGNITE-8487 tmpfs is employed by ZooKeeper tests - Fixes #3994.

Signed-off-by: dpavlov 

(cherry-picked from commit #67be050a2c7b9efdef2388c579fc060c68ff8a38)

commit c9b82cc632ad1cac51661f729f8605ab6c97c1dd
Author: Anton Kalashnikov 
Date:   2018-06-08T15:24:09Z

IGNITE-8739 Implemented WA for tcp communication SPI hanging on descriptor 
reservation - Fixes #4148.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 7021651)

commit 45953256ef0f09fd5450f6f6c6967a539c5cd395
Author: Pavel Kovalenko 
Date:   2018-05-03T14:01:20Z

IGNITE-8226 Improved logging - Fixes #3796.

Signed-off-by: Alexey Goncharuk 
(cherry picked from commit 8dd9c5d61c86c831b490134c3cd21f2ed47758d2)

commit 77d089d857876f1901ade5a017a92c9835e2976a
Author: Sergey Kosarev 
Date:   2018-06-13T14:24:42Z

IGNITE-8736 Add transaction label to CU.txString() method output - Fixes 
#4152.

Signed-off-by: Alexey Goncharuk 

commit c3c80439945134867e28e8d2c6db5ef9295141b6
Author: Andrey Gura 
Date:   2018-06-09T13:37:49Z

IGNITE-8751 Failure handler accordingly to segmentation policy should be 
invoked on node segmentation instead of configured failure handler

commit d33fe100bc9fdbcb66754d43ec0199e44233190b
Author: Andrey Gura 
Date:   2018-06-13T14:30:18Z

IGNITE-8781 GridNioServer accepter threads should have different names

commit d2c304ca415919f0933461dde92fdf354539529b
Author: Aleksey Plekhanov 
Date:   2018-06-14T17:41:31Z

IGNITE-8763 java.nio.file.AccessDeniedException is not handled with default 
failure handler

Signed-off-by: Andrey Gura 

commit 2545a4d65ae9c0289c9f6faf9d2ee498375aa3c7
Author: Sergey Chugunov 
Date:   2018-06-15T08:31:33Z

IGNITE-8657 Simultaneous start of multiple clients may lead to client start 
hang when exchange history size is too short - Fixes #4102.

Signed-off-by: Alexey Goncharuk 

(cherry-picked from commit #2b928c702b2d6a7c1de8d1b3b0a1e0e65e653f21)

commit f4511d921c34fc1fc048afaf3ec10307b0f3bea2
Author: Pavel Kovalenko 
Date:   2018-06-15T09:48:24Z

IGNITE-8610 Fixed checkpoint record search for WAL delta rebalancing - 
Fixes #4090.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 10aa02a)

commit 1a8e9fcafa3a6d53ab01901be798cc8957252fe6
Author: EdShangGG 
Date:   2018-06-15T16:35:00Z

IGNITE-8610 Fix compilation

(cherry picked from commit 55af7d1)

commit 298ca37aea710e098d033fcc5750e408b4a07c24
Author: Ilya Lantukh 
Date:   2018-05-23T15:02:23Z

IGNITE-7809 fixed stable failures of IgniteWalFlushDefaultSelfTest in 
Ignite PDS 2 & PDS 2 Direct IO, new tests were added. - Fixes #3569.

Signed-off-by: dpavlov 

(cherry picked from commit fed2c02)

commit 3a1645135cf474f5760319a3c2dd7712041cc6f4
Author: dpavlov 
Date:   2018-05-25T11:48:04Z

IGNITE-7809 Corrected failure handler to avoid suite timeout

(cherry picked from commit 0c3a7a6)

commit 3c44891906171d0668fee02bc5c9e9b2d4c7b432
Author: dpavlov 
Date:   2018-06-06T18:09:25Z

   

[GitHub] ignite pull request #4959: Ignite-2.5.1-p14-hotfix

[dgovorukhin]

GitHub user dgovorukhin opened a pull request:

https://github.com/apache/ignite/pull/4959

Ignite-2.5.1-p14-hotfix



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p14-hotfix

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4959.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4959


commit dc8ba0932a944f3e966ebbe2af053488d1fe9b28
Author: Sergey Chugunov 
Date:   2018-05-04T12:26:02Z

IGNITE-8421 new implementation of getChildren method is added tolerating 
KeeperException.NoNodeException - Fixes #3939.

Signed-off-by: dpavlov 

(cherry-picked from commit #02e9ca993178d4aa648d06cb93ce1a9277eb22b1)

commit 0d37bd6749829ce07fbd4b0d2344b62588177628
Author: Ivan Rakov 
Date:   2018-06-05T11:42:43Z

IGNITE-8682 Attempt to configure IGFS in persistent mode without specific 
data region ends with AssertionError

(cherry picked from commit 2fe0a10)

commit 0c20c51025e5a550b7f3d8458acae27ec8cdcef5
Author: a-polyakov 
Date:   2018-06-05T15:49:19Z

IGNITE-8602 Add support filter "label null" for control.sh tx utility - 
Fixes #4073.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 3372590)

commit 455777d2cd2bd6b83d69dbdbbd7e95b4f375bb75
Author: a-polyakov 
Date:   2018-06-05T16:01:03Z

IGNITE-8467 Fixed filter minSize for transactions utility control.sh. Fixes 
#4069

(cherry picked from commit d61c068)

commit c40f7659f24b6037485a5ac5e1965b0c6bd573bb
Author: Sergey Kosarev 
Date:   2018-06-06T08:19:26Z

IGNITE-8587 GridToStringBuilder use ConcurrentHashMap to avoid global locks 
on classCache - Fixes #4059.

Signed-off-by: Alexey Goncharuk 
(cherry picked from commit ecd8261f1add62099fde39aa7dca49855a866eda)

commit af026c7840101e2c57c7dd882baabddb6df2fa82
Author: Ilya Lantukh 
Date:   2018-06-04T22:24:37Z

IGNITE-8693 SQL JOIN between PARTITIONED and REPLICATED cache fails - Fixes 
#4120.

Signed-off-by: Ivan Rakov 

(cherry picked from commit bc35ce0)

commit a84538a9df8ace432411736289ec8371dee215e2
Author: Sergey Kosarev 
Date:   2018-06-06T09:59:28Z

IGNITE-8696 control.sh utility does not show atomicity mode - Fixes #4127.

Signed-off-by: Ivan Rakov 
(cherry picked from commit 78e5d970be74c04b01857123b1a623038aa18440)

commit fff8a4cc48ae7d8a47f8911763a71d0d59042d87
Author: Andrey Kuznetsov 
Date:   2018-06-06T12:02:35Z

IGNITE-8642 Added thread dumping to FailureProcessor

Signed-off-by: Andrey Gura 

commit 6ea23844cfb0294a0cf3f3c21787aeff30939bcf
Author: Dmitriy Sorokin 
Date:   2018-06-06T11:34:04Z

IGNITE-8311 IgniteClientRejoinTest.testClientsReconnectDisabled causes 
exchange-worker to terminate via NPE

Signed-off-by: Andrey Gura 

commit bad52d3843925d831e6d357a4382731751ae6bb7
Author: Ilya Lantukh 
Date:   2018-06-04T14:07:52Z

GG-13862 : Disabled fast eviction.

(cherry picked from commit 786633d)

commit 6956097ceedd2e3e9edcb627d97e49afb7f0a26d
Author: Pavel Kovalenko 
Date:   2018-06-06T12:24:39Z

IGNITE-8482 Skip 2-phase partition release wait in case of activation or 
dynamic caches start - Fixes #4078.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 7c565d2)

commit d777c76eadd0a2ccc50f1031c42626b135da5906
Author: Dmitriy Govorukhin 
Date:   2018-06-06T14:20:18Z

IGNITE-8685 Fixed switch segment record size - Fixes #4130.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 2a048bd)

commit ef4782d8a60eea870b43933480f2c9695c9fc55d
Author: Alexey Goncharuk 
Date:   2018-06-07T11:55:13Z

IGNITE-8706 Fixed testMemoryUsageMultipleNodes

commit 6902383e01ee69d7efff9613a68f3fc419152305
Author: Pavel Kovalenko 
Date:   2018-05-14T10:14:52Z

IGNITE-8422 Tests fix for Zookeeper discovery split brain detection 
shouldn't consider client nodes - Fixes #3975.

Signed-off-by: dpavlov 

(cherry-picked from commit #19cbf8058b48a1f8fec60f7ceac70229e7c5391a)

commit 6eef070f8e0627e2986d870cc09ceb9cb351ee0d
Author: Sergey Chugunov 
Date:   2018-05-14T17:09:33Z

IGNITE-8487 tmpfs is employed by ZooKeeper tests - Fixes #3994.

Signed-off-by: dpavlov 

(cherry-picked from commit #67be050a2c7b9efdef2388c579fc060c68ff8a38)

commit c9b82cc632ad1cac51661f729f8605ab6c97c1dd
Author: Anton Kalashnikov 
Date:   2018-06-08T15:24:09Z

IGNITE-8739 Implemented WA for tcp communication SPI hanging on descriptor 
reservation - Fixes #4148.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 7021651)

commit 45953256ef0f09fd5450f6f6c6967a539c5cd395
Author: Pavel Kovalenko 
Date:   2018-05-03T14:01:20Z

IGNITE-8226 Improved logging - Fixes #3796.

[jira] [Created] (IGNITE-9860) Unreliable listener invocation order in GridDhtPartitionsExchangeFuture#onDone

[Andrey Kuznetsov (JIRA)]

Andrey Kuznetsov created IGNITE-9860:


 Summary: Unreliable listener invocation order in 
GridDhtPartitionsExchangeFuture#onDone
 Key: IGNITE-9860
 URL: https://issues.apache.org/jira/browse/IGNITE-9860
 Project: Ignite
  Issue Type: Bug
Reporter: Andrey Kuznetsov
 Fix For: 2.8


Listener being added right before {{super.onDone()}} call is intended to be 
invoked earlier than all other listeners. There is a small probability of 
breaking this guarantee: some other thread can call {{listen()}} before 
future-completing thread enters {{super.onDone()}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #4854: IGNITE-9561 Parallelize affinity calculation and ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4854


---

[GitHub] ignite pull request #4859: IGNITE-9726: GridCacheAbstractFailoverSelfTest ma...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4859


---

[GitHub] ignite pull request #4958: Added IgniteDataTransferObject and deprecated Vis...

[akuznetsov-gridgain]

GitHub user akuznetsov-gridgain opened a pull request:

https://github.com/apache/ignite/pull/4958

Added IgniteDataTransferObject and deprecated VisorDataTransferObject 



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-gg-14271

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4958.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4958


commit 245358d7bfde1ff6299f2c8413f265ba23fcf805
Author: Alexey Kuznetsov 
Date:   2018-10-11T12:05:03Z

GG-14271 WIP Refactoring classes.

commit f0de69f924c319371d425778ea106f9681e8be38
Author: Alexey Kuznetsov 
Date:   2018-10-11T15:23:53Z

Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ignite 
into ignite-gg-14271

commit 066f975479315cba8bbf94cc157bf7a6b4700c19
Author: Alexey Kuznetsov 
Date:   2018-10-11T15:31:46Z

GG-14271 WIP.

commit b9e2dff61b9764f55ebfd755fd451e01ba5b3630
Author: Alexey Kuznetsov 
Date:   2018-10-11T15:46:47Z

GG-14271 WIP.




---

[GitHub] ignite pull request #4957: Ignite 2.4.12 test

[antkr]

GitHub user antkr opened a pull request:

https://github.com/apache/ignite/pull/4957

Ignite 2.4.12 test

TC pre-run to check before pushing to 2.4 master

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.12-test

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4957.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4957


commit 2c39ec5dda1a05d03e1317b740fbafee8dd874f0
Author: devozerov 
Date:   2018-03-29T10:46:47Z

Merge branch 'ignite-2.4.4' into ignite-2.4-master

commit a58bc16543e72dfc3a2b97c50506cd532d4d9dee
Author: devozerov 
Date:   2018-03-29T12:21:46Z

IGNITE-7421: Reverted invalid server-side authentication.

commit e7ec84a17c5999441f1731aad64f540fd2eda279
Author: devozerov 
Date:   2018-03-29T12:23:26Z

Merge branch 'ignite-2.4.4' into ignite-2.4-master

commit 188279848a75d6458b9441d65917fb628834355e
Author: devozerov 
Date:   2018-03-30T09:04:33Z

IGNITE-7657: Minor style fixes: imports, forgotten javadocs, annotations. 
This closes #3496.

commit b4320072ca75e5b11bbeeb033c2f60f31f4855f9
Author: devozerov 
Date:   2018-03-30T09:18:10Z

Merge remote-tracking branch 'upstream/ignite-2.4.4' into ignite-2.4.4

commit b0de9d14caaf2bfc91c4f8283b0806c354ef7b73
Author: Alexey Goncharuk 
Date:   2018-03-30T14:40:28Z

IGNITE-8053 Make sure local partitions collection does not change

commit 7214eff5b5d8102ba32a7b7bf7597ac5a4b04eee
Author: Alexey Kukushkin 
Date:   2018-04-02T08:08:05Z

IGNITE-8076: Java Thin Client: authentication. This closes #3720.

commit 2c0e269fe7793bb70d1be28d2052f1394b96f2b1
Author: devozerov 
Date:   2018-04-02T08:09:17Z

Merge branch 'ignite-2.4.4' into ignite-2.4-master

commit cb89494be26be1b0e397e06f7eaeb6419aec1828
Author: Alexey Kuznetsov 
Date:   2018-03-02T09:35:26Z

IGNITE-7803 REST: Implemented possibility to get values from cache inserted 
via API or SQL.

(cherry picked from commit a84018b)

commit 149802a3be82ba1f88770dbff75d74b892bb0a94
Author: Alexey Kuznetsov 
Date:   2018-03-07T17:17:20Z

IGNITE-7803 Fixed regression in tests.

(cherry picked from commit 90c0af8)

commit 5b5571adc7282a29cdecd8ab2e945a446ea709fc
Author: Alexey Kuznetsov 
Date:   2018-03-23T02:55:13Z

IGNITE-8002 REST: Added support of new authentication via new API.

(cherry picked from commit 921f0cf)

commit 128fdfcd874286f4a358546c0f43b6ef082a064b
Author: devozerov 
Date:   2018-04-02T10:11:16Z

IGNITE-7884: Sample data set for JDBC. This closes #3702.

commit 247a9ef5a68de198106a866b277f1bee596c3633
Author: devozerov 
Date:   2018-04-02T10:16:00Z

Merge branch 'ignite-2.4.4' into ignite-2.4-master

commit 3949df02128e3003c409e0169ad0c80948ba134c
Author: Aleksey Plekhanov 
Date:   2018-02-13T13:43:49Z

IGNITE-5265 Eviction Rate memory metric to be implemented

Signed-off-by: Anton Vinogradov 

commit 7bc6c1ad3bacaf5e354d2710931eb398c346c06c
Author: Tim Onyschak 
Date:   2018-03-31T12:58:25Z

IGNITE-7090 Semaphore Stuck when no acquirers to assign permit - Fixes 
#3443.

Signed-off-by: dspavlov 

(cherry picked from commit 3fc5d57)

commit c854ad86f4c64260171085c8c7cce97ba1ad2530
Author: Pavel Kovalenko 
Date:   2018-02-22T09:02:31Z

IGNITE-7749 Fixed testDiscoCacheReuseOnNodeJoin test. - Fixes #3540.

Signed-off-by: Alexey Goncharuk 

commit b2e94b36bddebbf7b3ff40631e099939d16926d2
Author: Alexey Goncharuk 
Date:   2018-02-13T15:53:23Z

IGNITE-7692 Corrected test to not fail when SQL is executed on backup

commit 852425d4170ed1871c79f5ac26bfb3d03cc36a6f
Author: Алексей Стельмак 
Date:   2018-04-06T15:28:22Z

IGNITE-8049 Limit the number of operation cycles in B+Tree - Fixes #3769.

Signed-off-by: dpavlov 
(cherry picked from commit e491f10)

commit 42f529f0a04ce22786bb4a23032a64f93e214233
Author: Alexey Kuznetsov 
Date:   2018-04-09T02:25:50Z

IGNITE-8159 control.sh: Fixed NPE on adding nodes on empty baseline and not 
active cluster.

(cherry picked from commit 834869c)

commit b5f180838246f895d36846ea707790c1ff7fe70a
Author: Stanislav Lukyanov 
Date:   2018-04-09T11:33:13Z

IGNITE-7904: Changed IgniteUtils::cast not to trim exception chains. This 
closes #3683.

(cherry picked from commit 3a4f23b)

commit 1ce8e1a8fd48469073592e2fb77e2881a168a219
Author: Roman Guseinov 
Date:   2018-04-09T11:45:44Z

IGNITE-7944: Disconnected client node tries to send JOB_CANCEL message. 
Applied fix:
- Skip sending message if client disconnected;
- Throw IgniteCheckedException if a client node is disconnected and 
communication client is null.
This closes #3737.

(cherry picked from commit d70477b)

commit 

[jira] [Created] (IGNITE-9859) add debug logging on resendPartitions cause

[Max Shonichev (JIRA)]

Max Shonichev created IGNITE-9859:
-

 Summary: add debug logging on resendPartitions cause
 Key: IGNITE-9859
 URL: https://issues.apache.org/jira/browse/IGNITE-9859
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.5
Reporter: Max Shonichev
 Fix For: 2.5






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-9858) [Test Failed] SystemCacheNotConfiguredTest#test flaky fails on TC (timeout).

[Pavel Pereslegin (JIRA)]

Pavel Pereslegin created IGNITE-9858:


 Summary: [Test Failed] SystemCacheNotConfiguredTest#test flaky 
fails on TC (timeout).
 Key: IGNITE-9858
 URL: https://issues.apache.org/jira/browse/IGNITE-9858
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.6
Reporter: Pavel Pereslegin
Assignee: Pavel Pereslegin
 Fix For: 2.8


SystemCacheNotConfiguredTest hangs sometimes on TeamCity (timeout).

Example of such failures on master branch: 
[https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8==testDetails=-2762467041583095183=TEST_STATUS_DESC=50_IgniteTests24Java8=%3Cdefault%3E]

Typically client node cannot join server, when client discovery SPI initializes 
before server discovery, because ipfinder don't registers local node addresses 
(see TcpDiscoveryIpFinderAdapter#initializeLocalAddresses).


{noformat}
[2018-10-11 18:03:49,794][WARN 
][tcp-client-disco-msg-worker-#57%client%][TcpDiscoverySpi] IP finder returned 
empty addresses list. Please check IP finder configuration. Will retry every 
2000 ms. Change 'reconnectDelay' to configure the frequency of 
retries.{noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-9857) .NET: IgniteConfigurationTest.TestSpringXml is flaky in master

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-9857:


 Summary: .NET: IgniteConfigurationTest.TestSpringXml is flaky in 
master
 Key: IGNITE-9857
 URL: https://issues.apache.org/jira/browse/IGNITE-9857
 Project: Ignite
  Issue Type: Test
Reporter: Alexey Goncharuk


The test is constantly failing on a specific set of agents.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-9856) Add documentation for control.sh --cache config

[Sergey Antonov (JIRA)]

Sergey Antonov created IGNITE-9856:
--

 Summary: Add documentation for control.sh --cache config
 Key: IGNITE-9856
 URL: https://issues.apache.org/jira/browse/IGNITE-9856
 Project: Ignite
  Issue Type: Improvement
  Components: documentation
Reporter: Sergey Antonov


Option {{--cache config}} in {{control.sh}} must be documented.

As reference could be used help message:

{noformat}
List caches configuration:
control.sh [--host HOST_OR_IP] [--port PORT] [--user USER] [--password 
PASSWORD]  [--ping-interval PING_INTERVAL] [--ping-timeout PING_TIMEOUT] 
--cache config cacheNameRegexPattern [--human-readable]
{noformat}

And output example:

{noformat}
Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
2018 Copyright(C) Apache Software Foundation
User: santonov

ignite-sys-cache: {Name=ignite-sys-cache, Group=null, Dynamic Deployment 
ID=fb381836661-93ea1b62-7e2c-449d-82f4-ede849a03e22, System=true, 
Mode=REPLICATED, Atomicity Mode=TRANSACTIONAL, Statistic Enabled=false, 
Management Enabled=false, On-heap cache enabled=false, Partition Loss 
Policy=IGNORE, Query Parallelism=1, Copy On Read=false, Listener 
Configurations=null, Load Previous Value=false, Memory Policy Name=sysMemPlc, 
Node Filter=o.a.i.configuration.CacheConfiguration$IgniteAllNodesPredicate, 
Read From Backup=true, Topology Validator=null, Time To Live Eager Flag=true, 
Write Synchronization Mode=FULL_SYNC, Invalidate=false, Affinity 
Function=o.a.i.cache.affinity.rendezvous.RendezvousAffinityFunction, Affinity 
Backups=2147483647, Affinity Partitions=100, Affinity Exclude Neighbors=false, 
Affinity Mapper=o.a.i.i.processors.cache.GridCacheDefaultAffinityKeyMapper, 
Rebalance Mode=SYNC, Rebalance Batch Size=524288, Rebalance Timeout=1, 
Rebalance Delay=0, Time Between Rebalance Messages=0, Rebalance Batches 
Count=2, Rebalance Cache Order=-2, Eviction Policy Enabled=false, Eviction 
Policy Factory=null, Eviction Policy Max Size=null, Eviction Filter=null, Near 
Cache Enabled=false, Near Start Size=0, Near Eviction Policy Factory=null, Near 
Eviction Policy Max Size=null, Default Lock Timeout=0, Query Entities=[], Cache 
Interceptor=null, Store Enabled=false, Store Class=null, Store Factory 
Class=null, Store Keep Binary=false, Store Read Through=false, Store Write 
Through=false, Store Write Coalescing=true, Write-Behind Enabled=false, 
Write-Behind Flush Size=10240, Write-Behind Frequency=5000, Write-Behind Flush 
Threads Count=1, Write-Behind Batch Size=512, Concurrent Asynchronous 
Operations Number=500, Loader Factory Class Name=null, Writer Factory Class 
Name=null, Expiry Policy Factory Class 
Name=javax.cache.configuration.FactoryBuilder$SingletonFactory, Query Execution 
Time Threshold=3000, Query Escaped Names=false, Query SQL Schema=null, Query 
SQL functions=null, Query Indexed Types=null, Maximum payload size for offheap 
indexes=-1, Query Metrics History Size=0}
test-default: {Name=test-default, Group=null, Dynamic Deployment 
ID=fb381836661-93ea1b62-7e2c-449d-82f4-ede849a03e22, System=false, 
Mode=PARTITIONED, Atomicity Mode=ATOMIC, Statistic Enabled=false, Management 
Enabled=false, On-heap cache enabled=false, Partition Loss Policy=IGNORE, Query 
Parallelism=1, Copy On Read=true, Listener Configurations=null, Load Previous 
Value=false, Memory Policy Name=null, Node 
Filter=o.a.i.configuration.CacheConfiguration$IgniteAllNodesPredicate, Read 
From Backup=true, Topology Validator=null, Time To Live Eager Flag=true, Write 
Synchronization Mode=PRIMARY_SYNC, Invalidate=false, Affinity 
Function=o.a.i.cache.affinity.rendezvous.RendezvousAffinityFunction, Affinity 
Backups=0, Affinity Partitions=1024, Affinity Exclude Neighbors=false, Affinity 
Mapper=o.a.i.i.processors.cache.CacheDefaultBinaryAffinityKeyMapper, Rebalance 
Mode=ASYNC, Rebalance Batch Size=524288, Rebalance Timeout=1, Rebalance 
Delay=0, Time Between Rebalance Messages=0, Rebalance Batches Count=2, 
Rebalance Cache Order=0, Eviction Policy Enabled=false, Eviction Policy 
Factory=null, Eviction Policy Max Size=null, Eviction Filter=null, Near Cache 
Enabled=false, Near Start Size=0, Near Eviction Policy Factory=null, Near 
Eviction Policy Max Size=null, Default Lock Timeout=0, Query Entities=[], Cache 
Interceptor=null, Store Enabled=false, Store Class=null, Store Factory 
Class=null, Store Keep Binary=false, Store Read Through=false, Store Write 
Through=false, Store Write Coalescing=true, Write-Behind Enabled=false, 
Write-Behind Flush Size=10240, Write-Behind Frequency=5000, Write-Behind Flush 
Threads Count=1, Write-Behind Batch Size=512, Concurrent Asynchronous 
Operations Number=500, Loader Factory Class Name=null, Writer Factory Class 
Name=null, Expiry Policy Factory Class 
Name=javax.cache.configuration.FactoryBuilder$SingletonFactory, Query 

[GitHub] ignite pull request #4956: IGNITE-9853 option control.sh --cache config was ...

[antonovsergey93]

GitHub user antonovsergey93 opened a pull request:

https://github.com/apache/ignite/pull/4956

IGNITE-9853 option control.sh --cache config was added



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-9853

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4956.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4956


commit 22e35b8c25147fdb8156be4b526bec9dbbcbe532
Author: Sergey Antonov 
Date:   2018-10-11T11:18:04Z

GG-14300 First version

commit b8d1015004355fd556921300298cdcde37a475d3
Author: Sergey Antonov 
Date:   2018-10-11T11:20:47Z

GG-14300 Rename classes

commit 5413c4f435d2714b050aae4aefa87680a5c8bb87
Author: Sergey Antonov 
Date:   2018-10-11T13:09:31Z

GG-14300 Tests added.

commit f5a482eec4f450a40a6820622036b198065e7cfb
Author: Sergey Antonov 
Date:   2018-10-11T13:39:33Z

GG-14300 Added missing SerialVersionUID




---

[jira] [Created] (IGNITE-9855) Curious deadlock on shutdown when being polled over Jetty/REST

[Paul Anderson (JIRA)]

Paul Anderson created IGNITE-9855:
-

 Summary: Curious deadlock on shutdown when being polled over 
Jetty/REST
 Key: IGNITE-9855
 URL: https://issues.apache.org/jira/browse/IGNITE-9855
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.6
Reporter: Paul Anderson


have a look at this curious stack trace 

 

Attaching to process ID 2375242, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 25.71-b15
Deadlock Detection:

No deadlocks found.

Thread 2391956: (state = BLOCKED)
 - sun.misc.Unsafe.park(boolean, long) @bci=0 (Compiled frame; information may 
be imprecise)
 - java.util.concurrent.locks.LockSupport.park(java.lang.Object) @bci=14, 
line=175 (Compiled frame)
 - 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await() 
@bci=42, line=2039 (Compiled frame)
 - java.util.concurrent.LinkedBlockingQueue.take() @bci=29, line=442 (Compiled 
frame)
 - java.util.concurrent.ThreadPoolExecutor.getTask() @bci=149, line=1067 
(Interpreted frame)
 - 
java.util.concurrent.ThreadPoolExecutor.runWorker(java.util.concurrent.ThreadPoolExecutor$Worker)
 @bci=26, line=1127 (Interpreted frame)
 - java.util.concurrent.ThreadPoolExecutor$Worker.run() @bci=5, line=617 
(Interpreted frame)
 - java.lang.Thread.run() @bci=11, line=745 (Interpreted frame)


Thread 2391794: (state = BLOCKED)
 - sun.misc.Unsafe.park(boolean, long) @bci=0 (Compiled frame; information may 
be imprecise)
 - java.util.concurrent.locks.LockSupport.park(java.lang.Object) @bci=14, 
line=175 (Compiled frame)
 - 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await() 
@bci=42, line=2039 (Compiled frame)
 - java.util.concurrent.LinkedBlockingQueue.take() @bci=29, line=442 (Compiled 
frame)
 - java.util.concurrent.ThreadPoolExecutor.getTask() @bci=149, line=1067 
(Interpreted frame)
 - 
java.util.concurrent.ThreadPoolExecutor.runWorker(java.util.concurrent.ThreadPoolExecutor$Worker)
 @bci=26, line=1127 (Interpreted frame)
 - java.util.concurrent.ThreadPoolExecutor$Worker.run() @bci=5, line=617 
(Interpreted frame)
 - java.lang.Thread.run() @bci=11, line=745 (Interpreted frame)


Thread 2391563: (state = BLOCKED)
 - sun.misc.Unsafe.park(boolean, long) @bci=0 (Compiled frame; information may 
be imprecise)
 - java.util.concurrent.locks.LockSupport.park(java.lang.Object) @bci=14, 
line=175 (Compiled frame)
 - 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await() 
@bci=42, line=2039 (Compiled frame)
 - java.util.concurrent.LinkedBlockingQueue.take() @bci=29, line=442 (Compiled 
frame)
 - java.util.concurrent.ThreadPoolExecutor.getTask() @bci=149, line=1067 
(Interpreted frame)
 - 
java.util.concurrent.ThreadPoolExecutor.runWorker(java.util.concurrent.ThreadPoolExecutor$Worker)
 @bci=26, line=1127 (Interpreted frame)
 - java.util.concurrent.ThreadPoolExecutor$Worker.run() @bci=5, line=617 
(Interpreted frame)
 - java.lang.Thread.run() @bci=11, line=745 (Interpreted frame)


Thread 2391461: (state = BLOCKED)
 - sun.misc.Unsafe.park(boolean, long) @bci=0 (Compiled frame; information may 
be imprecise)
 - java.util.concurrent.locks.LockSupport.park(java.lang.Object) @bci=14, 
line=175 (Compiled frame)
 - 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await() 
@bci=42, line=2039 (Compiled frame)
 - java.util.concurrent.LinkedBlockingQueue.take() @bci=29, line=442 (Compiled 
frame)
 - java.util.concurrent.ThreadPoolExecutor.getTask() @bci=149, line=1067 
(Interpreted frame)
 - 
java.util.concurrent.ThreadPoolExecutor.runWorker(java.util.concurrent.ThreadPoolExecutor$Worker)
 @bci=26, line=1127 (Interpreted frame)
 - java.util.concurrent.ThreadPoolExecutor$Worker.run() @bci=5, line=617 
(Interpreted frame)
 - java.lang.Thread.run() @bci=11, line=745 (Interpreted frame)


Thread 2391460: (state = BLOCKED)
 - sun.misc.Unsafe.park(boolean, long) @bci=0 (Compiled frame; information may 
be imprecise)
 - java.util.concurrent.locks.LockSupport.park(java.lang.Object) @bci=14, 
line=175 (Compiled frame)
 - 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await() 
@bci=42, line=2039 (Compiled frame)
 - java.util.concurrent.LinkedBlockingQueue.take() @bci=29, line=442 (Compiled 
frame)
 - java.util.concurrent.ThreadPoolExecutor.getTask() @bci=149, line=1067 
(Interpreted frame)
 - 
java.util.concurrent.ThreadPoolExecutor.runWorker(java.util.concurrent.ThreadPoolExecutor$Worker)
 @bci=26, line=1127 (Interpreted frame)
 - java.util.concurrent.ThreadPoolExecutor$Worker.run() @bci=5, line=617 
(Interpreted frame)
 - java.lang.Thread.run() @bci=11, line=745 (Interpreted frame)


Thread 2383112: (state = BLOCKED)
 - sun.misc.Unsafe.park(boolean, long) @bci=0 (Compiled frame; information may 
be imprecise)
 - java.util.concurrent.locks.LockSupport.park(java.lang.Object) @bci=14, 

[jira] [Created] (IGNITE-9854) NullPointerException in PageMemoryImpl.refreshOutdatedPages during removing from segCheckpointPages

[Ivan Daschinskiy (JIRA)]

Ivan Daschinskiy created IGNITE-9854:


 Summary: NullPointerException in 
PageMemoryImpl.refreshOutdatedPages during removing from segCheckpointPages
 Key: IGNITE-9854
 URL: https://issues.apache.org/jira/browse/IGNITE-9854
 Project: Ignite
  Issue Type: Bug
  Components: persistence
Affects Versions: 2.6
Reporter: Ivan Daschinskiy
 Fix For: 2.8


Because of possibility of concurrently setting segCheckpointPages to null of 
segment not under segment writeLock (i.e. in PageMemoryImpl#finishCheckpoint), 
NullPointerException is possible. This causes immediate node failure. 

Example stack trace is attached (failure during iteration in rebalance 
supplier).


{code:java}
java.lang.NullPointerException: null
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.refreshOutdatedPage(PageMemoryImpl.java:840)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.access$5100(PageMemoryImpl.java:120)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.removePageForReplacement(PageMemoryImpl.java:2175)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.access$900(PageMemoryImpl.java:1841)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:686)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:627)
at 
org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:140)
at 
org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:102)
at 
org.apache.ignite.internal.processors.cache.tree.DataRow.(DataRow.java:54)
at 
org.apache.ignite.internal.processors.cache.tree.CacheDataRowStore.dataRow(CacheDataRowStore.java:73)
at 
org.apache.ignite.internal.processors.cache.tree.CacheDataTree.getRow(CacheDataTree.java:146)
at 
org.apache.ignite.internal.processors.cache.tree.CacheDataTree.getRow(CacheDataTree.java:41)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.fillFromBuffer(BPlusTree.java:4660)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.nextPage(BPlusTree.java:4760)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.next(BPlusTree.java:4689)
{code}




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-9853) control.sh show more information about cache configuration

[Sergey Antonov (JIRA)]

Sergey Antonov created IGNITE-9853:
--

 Summary: control.sh show more information about cache configuration
 Key: IGNITE-9853
 URL: https://issues.apache.org/jira/browse/IGNITE-9853
 Project: Ignite
  Issue Type: Bug
Reporter: Sergey Antonov
Assignee: Sergey Antonov






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #4955: GG-14300 option control.sh --cache config was add...

[antonovsergey93]

Github user antonovsergey93 closed the pull request at:

https://github.com/apache/ignite/pull/4955


---

[jira] [Created] (IGNITE-9852) Create TeamCity suite for Python thin client

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-9852:
---

 Summary: Create TeamCity suite for Python thin client
 Key: IGNITE-9852
 URL: https://issues.apache.org/jira/browse/IGNITE-9852
 Project: Ignite
  Issue Type: Task
  Components: thin client
Reporter: Igor Sapego
 Fix For: 2.7


Implementation of Python client is almost ready (IGNITE-7782). We need to 
figure out how to integrate it with TeamCity:
1) New suite for Python thin client is needed along with required environment
2) Suite should be able to run tests as described in the documentation [1]
3) Currently all tests rely on manually started external node. We need to 
create a set of scripts (bash?) to start/stop nodes locally just like in 
IGNITE-8463

[1] 
https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/readme.html#testing



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #4940: IGNITE-9446: Added cache status check before runn...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4940


---

[GitHub] ignite pull request #4955: GG-14300 option control.sh --cache config was add...

[antonovsergey93]

GitHub user antonovsergey93 opened a pull request:

https://github.com/apache/ignite/pull/4955

GG-14300 option control.sh --cache config was added



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite gg-14300

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4955.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4955


commit 22e35b8c25147fdb8156be4b526bec9dbbcbe532
Author: Sergey Antonov 
Date:   2018-10-11T11:18:04Z

GG-14300 First version

commit b8d1015004355fd556921300298cdcde37a475d3
Author: Sergey Antonov 
Date:   2018-10-11T11:20:47Z

GG-14300 Rename classes

commit 5413c4f435d2714b050aae4aefa87680a5c8bb87
Author: Sergey Antonov 
Date:   2018-10-11T13:09:31Z

GG-14300 Tests added.




---

[GitHub] asfgit closed pull request #34: IGNITE-9833 Update Master Trends metrics

[GitBox]

asfgit closed pull request #34: IGNITE-9833 Update Master Trends metrics
URL: https://github.com/apache/ignite-teamcity-bot/pull/34
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/current/BuildStatisticsSummary.java
 
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/current/BuildStatisticsSummary.java
index 8a428a5..d4a7bf6 100644
--- 
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/current/BuildStatisticsSummary.java
+++ 
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/current/BuildStatisticsSummary.java
@@ -64,8 +64,8 @@
 /** List of problem occurrences. */
 private List problemOccurrenceList;
 
-/** Duration printable. */
-public String durationPrintable;
+/** Duration (seconds). */
+public long duration;
 
 /** Short build run result (without snapshot-dependencies printable 
result). */
 public Map totalProblems;
@@ -95,8 +95,7 @@ public void initialize(@Nonnull final ITeamcity teamcity) {
 
 testOccurrences = build.testOccurrences;
 
-durationPrintable = TimeUtil
-.millisToDurationPrintable(build.getFinishDate().getTime() - 
build.getStartDate().getTime());
+duration = (build.getFinishDate().getTime() - 
build.getStartDate().getTime()) / 1000;
 
 List snapshotDependencies = 
getSnapshotDependencies(teamcity, build);
 
@@ -228,13 +227,13 @@ private long getOomeProblemCount(String buildTypeId) {
 Objects.equals(startDate, that.startDate) &&
 Objects.equals(testOccurrences, that.testOccurrences) &&
 Objects.equals(problemOccurrenceList, that.problemOccurrenceList) 
&&
-Objects.equals(durationPrintable, that.durationPrintable) &&
+Objects.equals(duration, that.duration) &&
 Objects.equals(totalProblems, that.totalProblems);
 }
 
 /** {@inheritDoc} */
 @Override public int hashCode() {
 return Objects.hash(buildId, startDate, testOccurrences, 
problemOccurrenceList,
-durationPrintable, totalProblems, isFakeStub);
+duration, totalProblems, isFakeStub);
 }
 }
diff --git a/ignite-tc-helper-web/src/main/webapp/comparison.html 
b/ignite-tc-helper-web/src/main/webapp/comparison.html
index bc24084..fd62a47 100644
--- a/ignite-tc-helper-web/src/main/webapp/comparison.html
+++ b/ignite-tc-helper-web/src/main/webapp/comparison.html
@@ -23,18 +23,27 @@
 
 
 
+
+DURATION
+
+
+
+
+
+
+
+
 
-
 
 FEATURES
 
 
 
-TESTS
+TESTS
 COUNT
 
-
-
+
+
 
 
 
@@ -43,8 +52,8 @@
 
 PASSED
 
-
-
+
+
 
 
 
@@ -53,8 +62,8 @@
 
 FAILED
 
-
-
+
+
 
 
 
@@ -63,8 +72,8 @@
 
 IGNORED
 
-
-
+
+
 
 
 
@@ -73,19 +82,19 @@
 
 MUTED
 
-
-
+
+
 
 
 
 
 
-PROBLEMS
+PROBLEMS
 
 TOTAL
 
-
-
+
+
 
 
 
@@ -93,8 +102,8 @@
 
 EXECUTION TIMEOUT
 
-
-
+
+
 
 
 
@@ -103,8 +112,8 @@
 
 JVM CRASH
 
-
-
+
+
 
 
 
@@ -113,8 +122,8 @@
 
 OOME
 
-
-
+
+
 
 
 
@@ -123,26 +132,62 @@
 
 EXIT CODE
 
-
-
+
+
 
 
 
 
 
 
+OTHER METRICS
+
+RUNS COUNT
+
+
+
+
 
 
 

Re: PHP thin client

[Igor Sapego]

Alexey,

Since PHP thin client is now in master, can you please add it to our
"Thin clients features" wiki page, so we can track the feature parity
of our clients?

[1] -
https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features

Best Regards,
Igor


On Wed, Oct 10, 2018 at 2:56 PM Vladimir Ozerov 
wrote:

> I am not sure there is an answer. This is just how we handled it before.
> IMO both approaches works fine. BTW, I already merged Vyacheslav's PR
> several hours ago.
>
> On Wed, Oct 10, 2018 at 1:24 PM Igor Sapego  wrote:
>
>> Vyacheslav,
>>
>> In this case, we should do the same with all existing doxygen
>> files, not only this one (see files with .dxg extension)
>>
>> Vova, Pavel,
>>
>> Were there historically any reasons to exclude doxygen files
>> from check instead of adding a license header?
>>
>> Best Regards,
>> Igor
>>
>>
>> On Tue, Oct 9, 2018 at 11:49 PM Vyacheslav Daradur 
>> wrote:
>>
>>> Great work guys, thanks!
>>>
>>> I've noticed TC fails in the build plan "Licenses Headers" which Igor
>>> have fixed already by excluding Doxyfile from checking.
>>>
>>> I've filled a ticket [1] and I'd suggest fixing the test in another
>>> way by adding the license header to Doxyfile.
>>>
>>> Igor, please, have a look at prepared PR [2] (tests passed [3]).
>>>
>>> [1] https://issues.apache.org/jira/browse/IGNITE-9832
>>> [2] https://github.com/apache/ignite/pull/4938/files
>>> [3] https://ci.ignite.apache.org/viewLog.html?buildId=2046206
>>> On Tue, Oct 9, 2018 at 6:31 PM Igor Sapego  wrote:
>>> >
>>> > As the seem to be everything OK with the code and tests and
>>> > no one had any comment for quite some time, I've merged the
>>> > PHP to Ignite's master.
>>> >
>>> > Great job, guys!
>>> >
>>> >
>>> > Best Regards,
>>> > Igor
>>> >
>>> >
>>> > On Wed, Sep 19, 2018 at 1:00 AM Prachi Garg 
>>> wrote:
>>> >
>>> > > Hi Stephan, Alexey
>>> > >
>>> > > That's exactly what readme.io contains - installation instructions,
>>> > > configuration, and examples for key-value, sql, etc. for thin
>>> clients. For
>>> > > example, see these documentation pages for Node.js (currently hidden
>>> in the
>>> > > latest version of the doc) :
>>> > >
>>> > > https://apacheignite.readme.io/v2.6/docs/nodejs-thin-client
>>> > >
>>> > >
>>> https://apacheignite.readme.io/v2.6/docs/nodejs-thin-client-initialization-and-configuration
>>> > >
>>> https://apacheignite.readme.io/v2.6/docs/nodejs-thin-client-key-value
>>> > > https://apacheignite.readme.io/v2.6/docs/nodejs-thin-client-sql
>>> > >
>>> https://apacheignite.readme.io/v2.6/docs/nodejs-thin-client-binary-types
>>> > > https://apacheignite.readme.io/v2.6/docs/nodejs-thin-client-security
>>> > >
>>> > > This how Python and PHP thin clients will also be documented on
>>> readme.io
>>> > >
>>> > > -Prachi
>>> > >
>>> > >
>>> > >
>>> > >
>>> > > On Tue, Sep 18, 2018 at 3:26 AM, Stepan Pilshchikov <
>>> > > pilshchikov@gmail.com> wrote:
>>> > >
>>> > > > > You know, I'm confused with all this documentation stuff...
>>> > > > > For nodejs client all docs were moved from the repo to readme.io
>>> but
>>> > > > the
>>> > > > > readme.md keeps the installation instructions (duplicated with
>>> > > > > readme.io). Probably, that's ok.
>>> > > > > Will add similar short readme.md to the PHP PR.
>>> > > >
>>> > > > Its good
>>> > > >
>>> > > > What i think (and how it partially now):
>>> > > > All user documentation should be on readme.io (how to install,
>>> use it,
>>> > > > configurate, description for examples)
>>> > > > All developers documentation (how to release, how to start develop)
>>> > > and(!)
>>> > > > basic description should be in repository
>>> > > >
>>> > > >
>>> > > >
>>> > > >
>>> > > > --
>>> > > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>>> > > >
>>> > >
>>>
>>>
>>>
>>> --
>>> Best Regards, Vyacheslav D.
>>>
>>

[GitHub] ignite pull request #4951: IGNITE-9583 PHP thin: php directory should be inc...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4951


---

[jira] [Created] (IGNITE-9851) Share local node statistics between all nodes

[Yury Gerzhedovich (JIRA)]

Yury Gerzhedovich created IGNITE-9851:
-

 Summary: Share local node statistics between all nodes
 Key: IGNITE-9851
 URL: https://issues.apache.org/jira/browse/IGNITE-9851
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Yury Gerzhedovich
Assignee: Yury Gerzhedovich


Each node contains it's local node statistics. User want to know cluster wide 
statistics for a caches and indexes. Need to share local node statistics 
between all nodes and expose interface to derive the statistics.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #4538: IGNITE-9171 Use lazy mode with results pre-fetch

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4538


---

[GitHub] ignite pull request #4870: Ignite 9171 for tests

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4870


---

Re: [MTCGA]: new failures in builds [2054148] needs to be handled

[Dmitriy Pavlov]

Hi Max-Pudov,

could you please take a look? This change goes also to 2.7, so this needs
to be investigated before release.

Vyacheslav, thank you for checking this failure. I will double check why
I've missed this failure during test validation.

Sincerely,
Dmitriy Pavlov

чт, 11 окт. 2018 г. в 13:53, Vyacheslav Daradur :

> The test fails with an errors related to Kafka, looks like the
> possible cause is the following task:
> https://issues.apache.org/jira/browse/IGNITE-9126 - Update Apache
> Kafka dependency
> On Thu, Oct 11, 2018 at 9:11 AM  wrote:
> >
> > Hi Igniters,
> >
> >  I've detected some new issue on TeamCity to be handled. You are more
> than welcomed to help.
> >
> >  If your changes can lead to this failure(s): We're grateful that you
> were a volunteer to make the contribution to this project, but things
> change and you may no longer be able to finalize your contribution.
> >  Could you respond to this email and indicate if you wish to continue
> and fix test failures or step down and some committer may revert you commit.
> >
> >  *New test failure in master
> IgniteSinkConnectorTest.testSinkPutsWithTransformation
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-6495637752134628320=%3Cdefault%3E=testDetails
> >  Changes may lead to failure were done by
> >  - mr.weider
> http://ci.ignite.apache.org/viewModification.html?modId=834682=false
> >  - pudov.max
> http://ci.ignite.apache.org/viewModification.html?modId=834650=false
> >  - vozerov
> http://ci.ignite.apache.org/viewModification.html?modId=834638=false
> >  - daradurvs
> http://ci.ignite.apache.org/viewModification.html?modId=834325=false
> >  - vololo100
> http://ci.ignite.apache.org/viewModification.html?modId=834310=false
> >
> >  - Here's a reminder of what contributors were agreed to do
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> >  - Should you have any questions please contact
> dev@ignite.apache.org
> >
> > Best Regards,
> > Apache Ignite TeamCity Bot
> > https://github.com/apache/ignite-teamcity-bot
> > Notification generated at 09:11:00 11-10-2018
>
>
>
> --
> Best Regards, Vyacheslav D.
>

Re: [MTCGA]: new failures in builds [2054148] needs to be handled

[Vyacheslav Daradur]

The test fails with an errors related to Kafka, looks like the
possible cause is the following task:
https://issues.apache.org/jira/browse/IGNITE-9126 - Update Apache
Kafka dependency
On Thu, Oct 11, 2018 at 9:11 AM  wrote:
>
> Hi Igniters,
>
>  I've detected some new issue on TeamCity to be handled. You are more than 
> welcomed to help.
>
>  If your changes can lead to this failure(s): We're grateful that you were a 
> volunteer to make the contribution to this project, but things change and you 
> may no longer be able to finalize your contribution.
>  Could you respond to this email and indicate if you wish to continue and fix 
> test failures or step down and some committer may revert you commit.
>
>  *New test failure in master 
> IgniteSinkConnectorTest.testSinkPutsWithTransformation 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-6495637752134628320=%3Cdefault%3E=testDetails
>  Changes may lead to failure were done by
>  - mr.weider 
> http://ci.ignite.apache.org/viewModification.html?modId=834682=false
>  - pudov.max 
> http://ci.ignite.apache.org/viewModification.html?modId=834650=false
>  - vozerov 
> http://ci.ignite.apache.org/viewModification.html?modId=834638=false
>  - daradurvs 
> http://ci.ignite.apache.org/viewModification.html?modId=834325=false
>  - vololo100 
> http://ci.ignite.apache.org/viewModification.html?modId=834310=false
>
>  - Here's a reminder of what contributors were agreed to do 
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
>  - Should you have any questions please contact dev@ignite.apache.org
>
> Best Regards,
> Apache Ignite TeamCity Bot
> https://github.com/apache/ignite-teamcity-bot
> Notification generated at 09:11:00 11-10-2018



--
Best Regards, Vyacheslav D.

Re: Apache Ignite 2.7. Last Mile

[Nikolay Izhikov]

Alexey, we all agreed to merge in 2.7 blockers only.

Is this a blocker?

Anyway, you are more experienced Igniter that I am.
If you think we should include this ticket to 2.7 - please, do it.

В Чт, 11/10/2018 в 13:08 +0300, Alexey Goncharuk пишет:
> Nikolay,
> 
> I am waiting for final benchmark results for 9784, after that I will merge
> the change.
> 
> On the subject of Ignite 2.7 scope, our fellow Igniter Alexey Platonov have
> found another case when a failure handler is incorrectly called on node
> stop: https://issues.apache.org/jira/browse/IGNITE-9834. The case is rare,
> but it is quite an unpleasant UX. Should we include it to 2.7 as well?
> 
> чт, 11 окт. 2018 г. в 11:22, Nikolay Izhikov :
> 
> > Hello, Igniters.
> > 
> > We made a good progress yesterday.
> > 
> > Here is the list of remaining tickets(17) mapped to 2.7:
> > 
> > Alexey Goncharuk   - IGNITE-9784
> > Taras Ledkov   - IGNITE-9171
> > Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> > Peter Ivanov   - IGNITE-9583, IGNITE-9823, IGNITE-9685
> > Igor Seliverstov   - IGNITE-9749, IGNITE-9292
> > Dmitry Melnichuk   - IGNITE-7782
> > Ivan Pavlukhin - IGNITE-5935
> > Yury Babak - IGNITE-8670
> > Roman Kondakov - IGNITE-7953, IGNITE-9446
> > Alexey Stelmak - IGNITE-9776
> > 
> > Unassigned:
> > 
> > IGNITE-9620 - MVCC: select throwing `Transaction is already completed`> >
> > > exception after mvcc missmatch
> > 
> > IGNITE-9663 - MVCC: Data node failure can cause TX hanging.
> > 
> > 
> > В Чт, 11/10/2018 в 10:40 +0300, Vladimir Ozerov пишет:
> > > What kind of help is needed?
> > > 
> > > On Wed, Oct 10, 2018 at 11:51 PM Dmitriy Setrakyan <
> > 
> > dsetrak...@apache.org>
> > > wrote:
> > > 
> > > > Vladimir Ozerov,
> > > > 
> > > > Can you help with the unassigned MVCC tickets?
> > > > 
> > > > D.
> > > > 
> > > > On Wed, Oct 10, 2018 at 3:32 AM Nikolay Izhikov 
> > > > wrote:
> > > > 
> > > > > Hello, Igniters.
> > > > > 
> > > > > I list all contributors that assigned to the 2.7 tickets.
> > > > > If you can help them to finish that tickets - please, do.
> > > > > Assigners, if you need any help - please, respond to this thread.
> > > > > 
> > > > > NOTE: We have 6 Unassigned tickets for 2.7. Let's start work on it!
> > > > > 
> > > > > Peter Ivanov   - IGNITE-9559, IGNITE-9583, IGNITE-9685,
> > 
> > IGNITE-9823
> > > > > Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> > > > > Taras Ledkov   - IGNITE-9171
> > > > > Alexey Goncharuk   - IGNITE-9784
> > > > > Dmitriy Govorukhin - IGNITE-9550
> > > > > Igor Seliverstov   - IGNITE-9749
> > > > > Dmitry Melnichuk   - IGNITE-7782
> > > > > Alexey Platonov- IGNITE-9726
> > > > > Ivan Pavlukhin - IGNITE-5935
> > > > > Yury Babak - IGNITE-8670
> > > > > Roman Kondakov - IGNITE-7953, IGNITE-9446
> > > > > Maxim Pudov- IGNITE-9126
> > > > > Alexey Stelmak - IGNITE-9776
> > > > > Alexey Kuznetsov   - IGNITE-7926
> > > > > 
> > > > > Unassigned tickets:
> > > > > 
> > > > > IGNITE-9781 - JDK11: SSL handshake is failed
> > > > > IGNITE-9620 - MVCC: select throwing `Transaction is already
> > 
> > completed`
> > > > > exception after mvcc missmatch
> > > > > IGNITE-9292 - MVCC SQL: Unexpected state exception when updating
> > 
> > backup
> > > > > IGNITE-9663 - MVCC: Data node failure can cause TX hanging.
> > > > > IGNITE-9724 - MVCC SQL: Test
> > > > > 
> > 
> > CacheMvccSelectForUpdateQueryAbstractTest.testSelectForUpdateDistributed
> > > > > hangs sporadically.
> > > > > IGNITE-9133 - MVCC: Proper empty DHT transactions handling.
> > > > > 


signature.asc
Description: This is a digitally signed message part

[GitHub] ignite pull request #4954: IGNITE-9749 MVCC: Assertion error in JdbcThinTran...

[gvvinblade]

GitHub user gvvinblade opened a pull request:

https://github.com/apache/ignite/pull/4954

IGNITE-9749 MVCC: Assertion error in 
JdbcThinTransactionsServerAutoCommitComplexSelfTest leading to JDBC MVCC suite 
hang



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-9749

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4954.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4954


commit 8c1ecb03ec7ac8095cb65b15b7aa51ae071a4510
Author: Igor Seliverstov 
Date:   2018-10-11T10:36:28Z

IGNITE-9749 MVCC: Assertion error in 
JdbcThinTransactionsServerAutoCommitComplexSelfTest leading to JDBC MVCC suite 
hang




---

[GitHub] ignite pull request #4950: IGNITE-9247: CPP Thin: implemented operations on ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4950


---

[GitHub] ignite pull request #4953: FsyncModeFileWriteAheadLogManager can block forev...

[SpiderRus]

GitHub user SpiderRus opened a pull request:

https://github.com/apache/ignite/pull/4953

FsyncModeFileWriteAheadLogManager can block forever in log() call



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-9776

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4953.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4953


commit 3fdd22ef28f22a0c3588b10f9b14475598642b0b
Author: Alexey Stelmak 
Date:   2018-10-11T10:17:16Z

Archiever fix




---

Re: Python thin client

[Igor Sapego]

Ok, I've filed a ticket [1] for the performance investigation and targeted
it to 2.8. Feel free to assign it to yourself.

I'm going to merge the ticket to master and ignite-2.7 branches by the
end of the week, if no one have any objections.

[1] - https://issues.apache.org/jira/browse/IGNITE-9850

Best Regards,
Igor


On Thu, Oct 11, 2018 at 12:18 PM Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com> wrote:

> Stepan,
>
> Thank you for answering my question and for the updated results.
>
> I have ran the profiler (cProfile) against the benchmark code you
> provided and have not found any particular bottleneck. One cycle took me
> 434 μs, which is the same order of magnitude as your result.
>
> I will need more time to analyze the performance of my client and find a
> way to improve it. But is it a real stopper/blocker for the client
> itself? If there are no other issues, may we merge and release the
> client? Plus submit a jira-improvement to further investigate the
> performance of the Python platform.
>
> Dmitry
>
> On 10/11/18 4:19 PM, Степан Пильщиков wrote:
> > Dmitry,
> >
> > pip install -e from latest sources
> >
> > On Thu, 11 Oct 2018, 06:37 Dmitry Melnichuk, <
> dmitry.melnic...@nobitlost.com>
> > wrote:
> >
> >> Stepan!
> >>
> >> Please tell me one thing about how you created the environment for your
> >> benchmarks, namely: how did you install the Python client. Did you just
> >> do `pip install pyignite`, or did you pull my working branch from the
> >> downstream repository and did `pip install -e
> >> ignite/modules/platforms/python`?
> >>
> >> I highly recommend the latter, because PyPI version do not yet include
> >> the latest improvements I did thanks to Dmitriy “qvad” Sherstobitov.
> >> These improvements can have a noticeable positive effect on speed.
> >>
> >> Dmitry
> >>
> >> On 10/10/18 11:06 PM, Степан Пильщиков wrote:
> >>> Dmitry,
> >>>
> >>> Thanks for review
> >>>
> >>> Agree with all suggestions.
> >>>
> >>> Made and run new benches without any redundant operations (prints, time
> >>> calculation), only with "put" in "while true" cycle (almost)
> >>> Case description, environment, results and code in ticket
> >>> https://issues.apache.org/jira/browse/IGNITE-9824 (last comment)
> >>>
> >>> Please review new metrics
> >>> Because picture is not changed so much, python still have performance
> >> issues
> >>>
> >>
> >
>
>

[GitHub] dspavlov opened a new pull request #35: Ignite 9848 load all builds

[GitBox]

dspavlov opened a new pull request #35: Ignite 9848 load all builds
URL: https://github.com/apache/ignite-teamcity-bot/pull/35
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Created] (IGNITE-9850) Python thin: Find out the cause of the python's client low performance

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-9850:
---

 Summary: Python thin: Find out the cause of the python's client 
low performance
 Key: IGNITE-9850
 URL: https://issues.apache.org/jira/browse/IGNITE-9850
 Project: Ignite
  Issue Type: Task
  Components: thin client
Affects Versions: 2.7
Reporter: Igor Sapego
 Fix For: 2.8


According to benchmarks results reported by IGNITE-9824, python thin client is 
3 to 4 times slower than Java client. We need to find out the root cause of 
this and if we can fix it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Apache Ignite 2.7. Last Mile

[Alexey Goncharuk]

Nikolay,

I am waiting for final benchmark results for 9784, after that I will merge
the change.

On the subject of Ignite 2.7 scope, our fellow Igniter Alexey Platonov have
found another case when a failure handler is incorrectly called on node
stop: https://issues.apache.org/jira/browse/IGNITE-9834. The case is rare,
but it is quite an unpleasant UX. Should we include it to 2.7 as well?

чт, 11 окт. 2018 г. в 11:22, Nikolay Izhikov :

> Hello, Igniters.
>
> We made a good progress yesterday.
>
> Here is the list of remaining tickets(17) mapped to 2.7:
>
> Alexey Goncharuk   - IGNITE-9784
> Taras Ledkov   - IGNITE-9171
> Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> Peter Ivanov   - IGNITE-9583, IGNITE-9823, IGNITE-9685
> Igor Seliverstov   - IGNITE-9749, IGNITE-9292
> Dmitry Melnichuk   - IGNITE-7782
> Ivan Pavlukhin - IGNITE-5935
> Yury Babak - IGNITE-8670
> Roman Kondakov - IGNITE-7953, IGNITE-9446
> Alexey Stelmak - IGNITE-9776
>
> Unassigned:
>
> IGNITE-9620 - MVCC: select throwing `Transaction is already completed`> >
> > exception after mvcc missmatch
> IGNITE-9663 - MVCC: Data node failure can cause TX hanging.
>
>
> В Чт, 11/10/2018 в 10:40 +0300, Vladimir Ozerov пишет:
> > What kind of help is needed?
> >
> > On Wed, Oct 10, 2018 at 11:51 PM Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> > > Vladimir Ozerov,
> > >
> > > Can you help with the unassigned MVCC tickets?
> > >
> > > D.
> > >
> > > On Wed, Oct 10, 2018 at 3:32 AM Nikolay Izhikov 
> > > wrote:
> > >
> > > > Hello, Igniters.
> > > >
> > > > I list all contributors that assigned to the 2.7 tickets.
> > > > If you can help them to finish that tickets - please, do.
> > > > Assigners, if you need any help - please, respond to this thread.
> > > >
> > > > NOTE: We have 6 Unassigned tickets for 2.7. Let's start work on it!
> > > >
> > > > Peter Ivanov   - IGNITE-9559, IGNITE-9583, IGNITE-9685,
> IGNITE-9823
> > > > Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> > > > Taras Ledkov   - IGNITE-9171
> > > > Alexey Goncharuk   - IGNITE-9784
> > > > Dmitriy Govorukhin - IGNITE-9550
> > > > Igor Seliverstov   - IGNITE-9749
> > > > Dmitry Melnichuk   - IGNITE-7782
> > > > Alexey Platonov- IGNITE-9726
> > > > Ivan Pavlukhin - IGNITE-5935
> > > > Yury Babak - IGNITE-8670
> > > > Roman Kondakov - IGNITE-7953, IGNITE-9446
> > > > Maxim Pudov- IGNITE-9126
> > > > Alexey Stelmak - IGNITE-9776
> > > > Alexey Kuznetsov   - IGNITE-7926
> > > >
> > > > Unassigned tickets:
> > > >
> > > > IGNITE-9781 - JDK11: SSL handshake is failed
> > > > IGNITE-9620 - MVCC: select throwing `Transaction is already
> completed`
> > > > exception after mvcc missmatch
> > > > IGNITE-9292 - MVCC SQL: Unexpected state exception when updating
> backup
> > > > IGNITE-9663 - MVCC: Data node failure can cause TX hanging.
> > > > IGNITE-9724 - MVCC SQL: Test
> > > >
> CacheMvccSelectForUpdateQueryAbstractTest.testSelectForUpdateDistributed
> > > > hangs sporadically.
> > > > IGNITE-9133 - MVCC: Proper empty DHT transactions handling.
> > > >
>

[GitHub] ignite pull request #4939: IGNITE-9834: Cancel tcp-client-disco-msg-worker i...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4939


---

[jira] [Created] (IGNITE-9849) Remove invalid builds from the selection

[Nikolai Kulagin (JIRA)]

Nikolai Kulagin created IGNITE-9849:
---

 Summary: Remove invalid builds from the selection
 Key: IGNITE-9849
 URL: https://issues.apache.org/jira/browse/IGNITE-9849
 Project: Ignite
  Issue Type: Sub-task
Reporter: Nikolai Kulagin
Assignee: Nikolai Kulagin


In selection sometimes there are builds with abnormal values. For example, the 
average number of failed tests is 25. But in the build [1953935] there are 2939 
failed tests. This is an anomalous value. Need to add the ability to remove it 
from the selection. Build [1953935] - not valid.

In total, 
1. While clicking on a point on the chart, show a button that allows marking a 
build invalid and excludes it from further selections.
2. Reduce the number of erroneous exceptions. Compare the value with the 
average, if the difference is small - ask for confirmation of the operation.
3. Add the ability to return an excluded build to the selection.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #4947: IGNITE-9550 Get operation returns null for a lost...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4947


---

[GitHub] ignite pull request #4952: IGNITE-9620

[devozerov]

GitHub user devozerov opened a pull request:

https://github.com/apache/ignite/pull/4952

IGNITE-9620



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-9620-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4952.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4952


commit 6fc6f146223c1b71ab14a8e139da8308d8e18592
Author: devozerov 
Date:   2018-10-11T08:06:24Z

WIP.

commit d6a93ba8a866d0572445fa901e88ec09f3cad404
Author: devozerov 
Date:   2018-10-11T08:34:40Z

WIP.

commit 7ed6b9a5e102e2d6b700b8cf69a49b143faed912
Author: devozerov 
Date:   2018-10-11T08:49:08Z

WIP.

commit 0f0f6c79e58319c0807b6183afd31f7dea7a507c
Author: devozerov 
Date:   2018-10-11T09:14:15Z

WIP.

commit 76566c13aebc6291a6c30bc7c8de8ddc05bd4e05
Author: devozerov 
Date:   2018-10-11T09:19:14Z

SQL state,

commit bb72f863f2f83c34e4592ec3afe33312fd0639c9
Author: devozerov 
Date:   2018-10-11T09:32:52Z

SQL test.

commit ad04fcd854aa484e4aa3b31bb26f13be8ffda5f8
Author: devozerov 
Date:   2018-10-11T09:35:41Z

WIP

commit 75d5df8687ee42c3c4d5183895c4df4e4b18e7ef
Author: devozerov 
Date:   2018-10-11T09:39:09Z

WIP.




---

Re: Python thin client

[Dmitry Melnichuk]

Stepan,

Thank you for answering my question and for the updated results.

I have ran the profiler (cProfile) against the benchmark code you 
provided and have not found any particular bottleneck. One cycle took me 
434 μs, which is the same order of magnitude as your result.


I will need more time to analyze the performance of my client and find a 
way to improve it. But is it a real stopper/blocker for the client 
itself? If there are no other issues, may we merge and release the 
client? Plus submit a jira-improvement to further investigate the 
performance of the Python platform.


Dmitry

On 10/11/18 4:19 PM, Степан Пильщиков wrote:

Dmitry,

pip install -e from latest sources

On Thu, 11 Oct 2018, 06:37 Dmitry Melnichuk, 
wrote:


Stepan!

Please tell me one thing about how you created the environment for your
benchmarks, namely: how did you install the Python client. Did you just
do `pip install pyignite`, or did you pull my working branch from the
downstream repository and did `pip install -e
ignite/modules/platforms/python`?

I highly recommend the latter, because PyPI version do not yet include
the latest improvements I did thanks to Dmitriy “qvad” Sherstobitov.
These improvements can have a noticeable positive effect on speed.

Dmitry

On 10/10/18 11:06 PM, Степан Пильщиков wrote:

Dmitry,

Thanks for review

Agree with all suggestions.

Made and run new benches without any redundant operations (prints, time
calculation), only with "put" in "while true" cycle (almost)
Case description, environment, results and code in ticket
https://issues.apache.org/jira/browse/IGNITE-9824 (last comment)

Please review new metrics
Because picture is not changed so much, python still have performance

issues

Re: Apache Ignite 2.7. Last Mile

[Nikolay Izhikov]

Hello, Igniters.

We made a good progress yesterday.

Here is the list of remaining tickets(17) mapped to 2.7:

Alexey Goncharuk   - IGNITE-9784
Taras Ledkov   - IGNITE-9171
Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
Peter Ivanov   - IGNITE-9583, IGNITE-9823, IGNITE-9685
Igor Seliverstov   - IGNITE-9749, IGNITE-9292
Dmitry Melnichuk   - IGNITE-7782
Ivan Pavlukhin - IGNITE-5935
Yury Babak - IGNITE-8670
Roman Kondakov - IGNITE-7953, IGNITE-9446
Alexey Stelmak - IGNITE-9776

Unassigned:

IGNITE-9620 - MVCC: select throwing `Transaction is already completed`> > > 
exception after mvcc missmatch
IGNITE-9663 - MVCC: Data node failure can cause TX hanging.


В Чт, 11/10/2018 в 10:40 +0300, Vladimir Ozerov пишет:
> What kind of help is needed?
> 
> On Wed, Oct 10, 2018 at 11:51 PM Dmitriy Setrakyan 
> wrote:
> 
> > Vladimir Ozerov,
> > 
> > Can you help with the unassigned MVCC tickets?
> > 
> > D.
> > 
> > On Wed, Oct 10, 2018 at 3:32 AM Nikolay Izhikov 
> > wrote:
> > 
> > > Hello, Igniters.
> > > 
> > > I list all contributors that assigned to the 2.7 tickets.
> > > If you can help them to finish that tickets - please, do.
> > > Assigners, if you need any help - please, respond to this thread.
> > > 
> > > NOTE: We have 6 Unassigned tickets for 2.7. Let's start work on it!
> > > 
> > > Peter Ivanov   - IGNITE-9559, IGNITE-9583, IGNITE-9685, IGNITE-9823
> > > Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> > > Taras Ledkov   - IGNITE-9171
> > > Alexey Goncharuk   - IGNITE-9784
> > > Dmitriy Govorukhin - IGNITE-9550
> > > Igor Seliverstov   - IGNITE-9749
> > > Dmitry Melnichuk   - IGNITE-7782
> > > Alexey Platonov- IGNITE-9726
> > > Ivan Pavlukhin - IGNITE-5935
> > > Yury Babak - IGNITE-8670
> > > Roman Kondakov - IGNITE-7953, IGNITE-9446
> > > Maxim Pudov- IGNITE-9126
> > > Alexey Stelmak - IGNITE-9776
> > > Alexey Kuznetsov   - IGNITE-7926
> > > 
> > > Unassigned tickets:
> > > 
> > > IGNITE-9781 - JDK11: SSL handshake is failed
> > > IGNITE-9620 - MVCC: select throwing `Transaction is already completed`
> > > exception after mvcc missmatch
> > > IGNITE-9292 - MVCC SQL: Unexpected state exception when updating backup
> > > IGNITE-9663 - MVCC: Data node failure can cause TX hanging.
> > > IGNITE-9724 - MVCC SQL: Test
> > > CacheMvccSelectForUpdateQueryAbstractTest.testSelectForUpdateDistributed
> > > hangs sporadically.
> > > IGNITE-9133 - MVCC: Proper empty DHT transactions handling.
> > > 


signature.asc
Description: This is a digitally signed message part

[GitHub] ignite pull request #4917: IGNITE-9796 NPE if you call array() method on emp...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4917


---

[jira] [Created] (IGNITE-9848) [TC Bot] Background upload of all builds from TC to the bot DB

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-9848:
--

 Summary: [TC Bot] Background upload of all builds from TC to the 
bot DB 
 Key: IGNITE-9848
 URL: https://issues.apache.org/jira/browse/IGNITE-9848
 Project: Ignite
  Issue Type: Task
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov


To fix slow loading of PR report and Master trends page.

Upload all tracked and observed branches related builds into TC Bot's Ignite DB.

Prepare compacted entities to reduce storage size.

Implement idea of having fat build, which will represent replies from a number 
of REST services.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #4943: IGNITE-9133

[devozerov]

Github user devozerov closed the pull request at:

https://github.com/apache/ignite/pull/4943


---

Re: Apache Ignite 2.7. Last Mile

[Vladimir Ozerov]

What kind of help is needed?

On Wed, Oct 10, 2018 at 11:51 PM Dmitriy Setrakyan 
wrote:

> Vladimir Ozerov,
>
> Can you help with the unassigned MVCC tickets?
>
> D.
>
> On Wed, Oct 10, 2018 at 3:32 AM Nikolay Izhikov 
> wrote:
>
> > Hello, Igniters.
> >
> > I list all contributors that assigned to the 2.7 tickets.
> > If you can help them to finish that tickets - please, do.
> > Assigners, if you need any help - please, respond to this thread.
> >
> > NOTE: We have 6 Unassigned tickets for 2.7. Let's start work on it!
> >
> > Peter Ivanov   - IGNITE-9559, IGNITE-9583, IGNITE-9685, IGNITE-9823
> > Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> > Taras Ledkov   - IGNITE-9171
> > Alexey Goncharuk   - IGNITE-9784
> > Dmitriy Govorukhin - IGNITE-9550
> > Igor Seliverstov   - IGNITE-9749
> > Dmitry Melnichuk   - IGNITE-7782
> > Alexey Platonov- IGNITE-9726
> > Ivan Pavlukhin - IGNITE-5935
> > Yury Babak - IGNITE-8670
> > Roman Kondakov - IGNITE-7953, IGNITE-9446
> > Maxim Pudov- IGNITE-9126
> > Alexey Stelmak - IGNITE-9776
> > Alexey Kuznetsov   - IGNITE-7926
> >
> > Unassigned tickets:
> >
> > IGNITE-9781 - JDK11: SSL handshake is failed
> > IGNITE-9620 - MVCC: select throwing `Transaction is already completed`
> > exception after mvcc missmatch
> > IGNITE-9292 - MVCC SQL: Unexpected state exception when updating backup
> > IGNITE-9663 - MVCC: Data node failure can cause TX hanging.
> > IGNITE-9724 - MVCC SQL: Test
> > CacheMvccSelectForUpdateQueryAbstractTest.testSelectForUpdateDistributed
> > hangs sporadically.
> > IGNITE-9133 - MVCC: Proper empty DHT transactions handling.
> >
>

[jira] [Created] (IGNITE-9847) IgniteSet#contains hang indefinitely.

[Stanilovsky Evgeny (JIRA)]

Stanilovsky Evgeny created IGNITE-9847:
--

 Summary: IgniteSet#contains hang indefinitely.
 Key: IGNITE-9847
 URL: https://issues.apache.org/jira/browse/IGNITE-9847
 Project: Ignite
  Issue Type: Bug
  Components: data structures
Affects Versions: 2.6
Reporter: Stanilovsky Evgeny
 Attachments: GridCacheSetTest0.java, t_dump.txt

In some circumstances test hangs indefinitely.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Python thin client

[Степан Пильщиков]

Dmitry,

pip install -e from latest sources

On Thu, 11 Oct 2018, 06:37 Dmitry Melnichuk, 
wrote:

> Stepan!
>
> Please tell me one thing about how you created the environment for your
> benchmarks, namely: how did you install the Python client. Did you just
> do `pip install pyignite`, or did you pull my working branch from the
> downstream repository and did `pip install -e
> ignite/modules/platforms/python`?
>
> I highly recommend the latter, because PyPI version do not yet include
> the latest improvements I did thanks to Dmitriy “qvad” Sherstobitov.
> These improvements can have a noticeable positive effect on speed.
>
> Dmitry
>
> On 10/10/18 11:06 PM, Степан Пильщиков wrote:
> > Dmitry,
> >
> > Thanks for review
> >
> > Agree with all suggestions.
> >
> > Made and run new benches without any redundant operations (prints, time
> > calculation), only with "put" in "while true" cycle (almost)
> > Case description, environment, results and code in ticket
> > https://issues.apache.org/jira/browse/IGNITE-9824 (last comment)
> >
> > Please review new metrics
> > Because picture is not changed so much, python still have performance
> issues
> >
>

[MTCGA]: new failures in builds [2054148] needs to be handled

[dpavlov . tasks]

Hi Igniters,

 I've detected some new issue on TeamCity to be handled. You are more than 
welcomed to help.

 If your changes can lead to this failure(s): We're grateful that you were a 
volunteer to make the contribution to this project, but things change and you 
may no longer be able to finalize your contribution.
 Could you respond to this email and indicate if you wish to continue and fix 
test failures or step down and some committer may revert you commit. 

 *New test failure in master 
IgniteSinkConnectorTest.testSinkPutsWithTransformation 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-6495637752134628320=%3Cdefault%3E=testDetails
 Changes may lead to failure were done by 
 - mr.weider 
http://ci.ignite.apache.org/viewModification.html?modId=834682=false
 - pudov.max 
http://ci.ignite.apache.org/viewModification.html?modId=834650=false
 - vozerov 
http://ci.ignite.apache.org/viewModification.html?modId=834638=false
 - daradurvs 
http://ci.ignite.apache.org/viewModification.html?modId=834325=false
 - vololo100 
http://ci.ignite.apache.org/viewModification.html?modId=834310=false

 - Here's a reminder of what contributors were agreed to do 
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute 
 - Should you have any questions please contact dev@ignite.apache.org 

Best Regards,
Apache Ignite TeamCity Bot 
https://github.com/apache/ignite-teamcity-bot
Notification generated at 09:11:00 11-10-2018