[jira] [Closed] (IGNITE-8525) Support for IgniteZeroMqStreamer non-multi-part pub-sub

[Roman Shtykh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Roman Shtykh closed IGNITE-8525.


> Support for IgniteZeroMqStreamer non-multi-part pub-sub
> ---
>
> Key: IGNITE-8525
> URL: https://issues.apache.org/jira/browse/IGNITE-8525
> Project: Ignite
>  Issue Type: Improvement
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>Priority: Major
> Fix For: 2.6
>
>
> Currently only multi-part pub-sub is supported.



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

[jira] [Commented] (IGNITE-8525) Support for IgniteZeroMqStreamer non-multi-part pub-sub

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16486702#comment-16486702
 ] 

ASF GitHub Bot commented on IGNITE-8525:


Github user asfgit closed the pull request at:

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


> Support for IgniteZeroMqStreamer non-multi-part pub-sub
> ---
>
> Key: IGNITE-8525
> URL: https://issues.apache.org/jira/browse/IGNITE-8525
> Project: Ignite
>  Issue Type: Improvement
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>Priority: Major
> Fix For: 2.6
>
>
> Currently only multi-part pub-sub is supported.



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

[jira] [Reopened] (IGNITE-8518) Web Console: Auto focus "Confirm" button in Confirmation dialog

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov reopened IGNITE-8518:
--

> Web Console: Auto focus "Confirm" button in Confirmation dialog
> ---
>
> Key: IGNITE-8518
> URL: https://issues.apache.org/jira/browse/IGNITE-8518
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.6
>
>
> This will allow to confirm from keyboard.



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

[jira] [Assigned] (IGNITE-8518) Web Console: Auto focus "Confirm" button in Confirmation dialog

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov reassigned IGNITE-8518:
--

Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Web Console: Auto focus "Confirm" button in Confirmation dialog
> ---
>
> Key: IGNITE-8518
> URL: https://issues.apache.org/jira/browse/IGNITE-8518
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.6
>
>
> This will allow to confirm from keyboard.



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

[jira] [Commented] (IGNITE-8518) Web Console: Auto focus "Confirm" button in Confirmation dialog

[Pavel Konstantinov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16486689#comment-16486689
 ] 

Pavel Konstantinov commented on IGNITE-8518:


Test failed. 
# create cluster configuration, save
# open cluster configuration list, select a cluster and choose the action 
Delete - confirmation will appear, the button Confirm is not focused

> Web Console: Auto focus "Confirm" button in Confirmation dialog
> ---
>
> Key: IGNITE-8518
> URL: https://issues.apache.org/jira/browse/IGNITE-8518
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.6
>
>
> This will allow to confirm from keyboard.



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

[jira] [Closed] (IGNITE-8370) Web console: split page-signin into three separate pages

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov closed IGNITE-8370.
--

> Web console: split page-signin into three separate pages
> 
>
> Key: IGNITE-8370
> URL: https://issues.apache.org/jira/browse/IGNITE-8370
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.6
>
>
> Currently, the page-signin component solves three separate cases: user 
> registration, sign in and password restore. Since none of those features has 
> to be on the same page, let's split those to separate pages.
> What to do:
> 1. Split signup, signin and forgot password features to separate components 
> and pages.
> 2. While at it, add an optional "Phone" input to signup page in order to 
> match inputs available on user profile page.



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

[jira] [Commented] (IGNITE-8370) Web console: split page-signin into three separate pages

[Pavel Konstantinov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16486671#comment-16486671
 ] 

Pavel Konstantinov commented on IGNITE-8370:


Tested on master

> Web console: split page-signin into three separate pages
> 
>
> Key: IGNITE-8370
> URL: https://issues.apache.org/jira/browse/IGNITE-8370
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.6
>
>
> Currently, the page-signin component solves three separate cases: user 
> registration, sign in and password restore. Since none of those features has 
> to be on the same page, let's split those to separate pages.
> What to do:
> 1. Split signup, signin and forgot password features to separate components 
> and pages.
> 2. While at it, add an optional "Phone" input to signup page in order to 
> match inputs available on user profile page.



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

[jira] [Comment Edited] (IGNITE-8566) Web console: replace extract-text-webpack-plugin with mini-css-extract-plugin

[Ilya Borisov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16486640#comment-16486640
 ] 

Ilya Borisov edited comment on IGNITE-8566 at 5/23/18 3:10 AM:
---

[~anovikov] please review.

Note that I replaced the common plugin configuration with configurations 
specific for dev/prod environments, based on what's in the advanced example of 
mini-css-extract-plugin, except that we can't use style loader in dev. When HMR 
lands in mini-css-extract-plugin, I think such a setup will be of help.


was (Author: klaster_1):
[~anovikov] please review.

> Web console: replace extract-text-webpack-plugin with mini-css-extract-plugin
> -
>
> Key: IGNITE-8566
> URL: https://issues.apache.org/jira/browse/IGNITE-8566
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Andrey Novikov
>Priority: Major
>
> The extract-text-webpack-plugin documentations says that "Since webpack v4 
> the extract-text-webpack-plugin should not be used for css. Use 
> mini-css-extract-plugin instead.", so I think that's what should be done.



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

[jira] [Assigned] (IGNITE-8566) Web console: replace extract-text-webpack-plugin with mini-css-extract-plugin

[Ilya Borisov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ilya Borisov reassigned IGNITE-8566:


Assignee: Andrey Novikov  (was: Ilya Borisov)

[~anovikov] please review.

> Web console: replace extract-text-webpack-plugin with mini-css-extract-plugin
> -
>
> Key: IGNITE-8566
> URL: https://issues.apache.org/jira/browse/IGNITE-8566
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Andrey Novikov
>Priority: Major
>
> The extract-text-webpack-plugin documentations says that "Since webpack v4 
> the extract-text-webpack-plugin should not be used for css. Use 
> mini-css-extract-plugin instead.", so I think that's what should be done.



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

[jira] [Created] (IGNITE-8566) Web console: replace extract-text-webpack-plugin with mini-css-extract-plugin

[Ilya Borisov (JIRA)]

Ilya Borisov created IGNITE-8566:


 Summary: Web console: replace extract-text-webpack-plugin with 
mini-css-extract-plugin
 Key: IGNITE-8566
 URL: https://issues.apache.org/jira/browse/IGNITE-8566
 Project: Ignite
  Issue Type: Improvement
  Components: wizards
Reporter: Ilya Borisov
Assignee: Ilya Borisov


The extract-text-webpack-plugin documentations says that "Since webpack v4 the 
extract-text-webpack-plugin should not be used for css. Use 
mini-css-extract-plugin instead.", so I think that's what should be done.



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

[jira] [Commented] (IGNITE-8547) Deserialization of Enum values as anonymous classes may cause deadlock

[Valentin Kulichenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16486490#comment-16486490
 ] 

Valentin Kulichenko commented on IGNITE-8547:
-

[~ilyak], if it's about legacy {{OptimizedMarshaller}}, I'm OK with both 
options. JDK seems to be easier to implement and more reliable.

However, I'm concerned about {{BinaryMarshaller}} - does the issue exist there 
as well?

> Deserialization of Enum values as anonymous classes may cause deadlock
> --
>
> Key: IGNITE-8547
> URL: https://issues.apache.org/jira/browse/IGNITE-8547
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.9
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
>  Labels: test
> Attachments: MarshallerDeadlockMultiJvmTest.java
>
>
> Due to the following problem:
> {code}
> package jvmtest;
> import java.util.ArrayList;
> import java.util.List;
> import java.util.concurrent.BrokenBarrierException;
> import java.util.concurrent.CyclicBarrier;
> public class LegTypeTest {
> public static void main(String[] args) throws InterruptedException, 
> BrokenBarrierException {
> List threadList = new ArrayList<>();
> CyclicBarrier b1 = new CyclicBarrier(16);
> CyclicBarrier b2 = new CyclicBarrier(17);
>   for (int i = 0; i < 16; i++) {
>   final int ii = i;
>   Thread thread = new Thread(() -> {
> try {
> b1.await();
> if (ii % 2 == 0)
> Class.forName("jvmtest.LegTypeTest$E$1");
> if (ii % 2 == 1)
> Class.forName("jvmtest.LegTypeTest$E");
> b2.await();
> } catch (Exception e) {
> e.printStackTrace();
> }
> });
> thread.start();
> threadList.add(thread);
> }
> b2.await();
> for (Thread thread : threadList) {
>   thread.join();
> }
> }
> private enum E {
> A("A"),
> B("B") {
> @Override
> public String virtual() {
> return null;
> }
> };
> private String displayString;
> E(String displayString) {
> this.displayString = displayString;
> }
> public String virtual() {
> return displayString;
> }
> }
> }
> {code}
> When doing Class.forName on different enum values deadlock can be caused. And 
> that's exactly what OptimizedMarshaller does.
> See also the attached test.



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

[jira] [Updated] (IGNITE-8564) DataStreamer fails if client reconnected to the cluster and allowOverride = true

[Denis Magda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda updated IGNITE-8564:

Fix Version/s: 2.6

> DataStreamer fails if client reconnected to the cluster and allowOverride = 
> true
> 
>
> Key: IGNITE-8564
> URL: https://issues.apache.org/jira/browse/IGNITE-8564
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
>  Labels: test
> Fix For: 2.6
>
> Attachments: DataStreamerClientReconnectAfterClusterRestartTest.java
>
>
> But wait, there's more.
> This only happens when client has reconnected to a new cluster and topology 
> version after that is exactly the same like when it left.
> Please see the attached test.



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

[jira] [Updated] (IGNITE-6241) Integrate with Kubernetes StatefulSet to support Ignite Persistence

[Denis Magda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda updated IGNITE-6241:

Description: 
Ignite Kubernetes integration has to support StatefulSet which enables Ignite 
Persistence usage in Kubernetes deployments. More details are here:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Persistence-on-Kubernetes-td16396.html

See how it's done for Cassandra and MongoDB:
* https://kubernetes.io/docs/tutorials/stateful-application/cassandra/
* https://kubernetes.io/docs/tutorials/stateless-application/guestbook/

We can reach out K8 folks and ask to add a prepared Ignite tutorial to the list.

Good reading on the stateful set: 
https://lenadroid.github.io/posts/stateful-sets-kubernetes-azure.html

  was:
Ignite Kubernetes integration has to support StatefulSet which enables Ignite 
Persistence usage in Kubernetes deployments. More details are here:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Persistence-on-Kubernetes-td16396.html

See how it's done for Cassandra and MongoDB:
* https://kubernetes.io/docs/tutorials/stateful-application/cassandra/
* https://kubernetes.io/docs/tutorials/stateless-application/guestbook/

We can reach out K8 folks and ask to add a prepared Ignite tutorial to the list.


> Integrate with Kubernetes StatefulSet to support Ignite Persistence
> ---
>
> Key: IGNITE-6241
> URL: https://issues.apache.org/jira/browse/IGNITE-6241
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Denis Magda
>Assignee: Peter Ivanov
>Priority: Critical
> Fix For: 2.6
>
>
> Ignite Kubernetes integration has to support StatefulSet which enables Ignite 
> Persistence usage in Kubernetes deployments. More details are here:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-Persistence-on-Kubernetes-td16396.html
> See how it's done for Cassandra and MongoDB:
> * https://kubernetes.io/docs/tutorials/stateful-application/cassandra/
> * https://kubernetes.io/docs/tutorials/stateless-application/guestbook/
> We can reach out K8 folks and ask to add a prepared Ignite tutorial to the 
> list.
> Good reading on the stateful set: 
> https://lenadroid.github.io/posts/stateful-sets-kubernetes-azure.html



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

[jira] [Updated] (IGNITE-8547) Deserialization of Enum values as anonymous classes may cause deadlock

[Ilya Kasnacheev (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ilya Kasnacheev updated IGNITE-8547:

Labels: test  (was: )

> Deserialization of Enum values as anonymous classes may cause deadlock
> --
>
> Key: IGNITE-8547
> URL: https://issues.apache.org/jira/browse/IGNITE-8547
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.9
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
>  Labels: test
> Attachments: MarshallerDeadlockMultiJvmTest.java
>
>
> Due to the following problem:
> {code}
> package jvmtest;
> import java.util.ArrayList;
> import java.util.List;
> import java.util.concurrent.BrokenBarrierException;
> import java.util.concurrent.CyclicBarrier;
> public class LegTypeTest {
> public static void main(String[] args) throws InterruptedException, 
> BrokenBarrierException {
> List threadList = new ArrayList<>();
> CyclicBarrier b1 = new CyclicBarrier(16);
> CyclicBarrier b2 = new CyclicBarrier(17);
>   for (int i = 0; i < 16; i++) {
>   final int ii = i;
>   Thread thread = new Thread(() -> {
> try {
> b1.await();
> if (ii % 2 == 0)
> Class.forName("jvmtest.LegTypeTest$E$1");
> if (ii % 2 == 1)
> Class.forName("jvmtest.LegTypeTest$E");
> b2.await();
> } catch (Exception e) {
> e.printStackTrace();
> }
> });
> thread.start();
> threadList.add(thread);
> }
> b2.await();
> for (Thread thread : threadList) {
>   thread.join();
> }
> }
> private enum E {
> A("A"),
> B("B") {
> @Override
> public String virtual() {
> return null;
> }
> };
> private String displayString;
> E(String displayString) {
> this.displayString = displayString;
> }
> public String virtual() {
> return displayString;
> }
> }
> }
> {code}
> When doing Class.forName on different enum values deadlock can be caused. And 
> that's exactly what OptimizedMarshaller does.
> See also the attached test.



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

[jira] [Created] (IGNITE-8564) DataStreamer fails if client reconnected to the cluster and allowOverride = true

[Ilya Kasnacheev (JIRA)]

Ilya Kasnacheev created IGNITE-8564:
---

 Summary: DataStreamer fails if client reconnected to the cluster 
and allowOverride = true
 Key: IGNITE-8564
 URL: https://issues.apache.org/jira/browse/IGNITE-8564
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.6
Reporter: Ilya Kasnacheev
Assignee: Ilya Kasnacheev
 Attachments: DataStreamerClientReconnectAfterClusterRestartTest.java

But wait, there's more.

This only happens when client has reconnected to a new cluster and topology 
version after that is exactly the same like when it left.

Please see the attached test.



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

[jira] [Updated] (IGNITE-8538) Web Console: Refactor redirecting to default state.

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-8538:
-
Fix Version/s: 2.6

> Web Console: Refactor redirecting to default state.
> ---
>
> Key: IGNITE-8538
> URL: https://issues.apache.org/jira/browse/IGNITE-8538
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.6
>
>
> We need to refactor and fix redirection to default state from Queries screen, 
> 40x screens and other similar places.



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

[jira] [Comment Edited] (IGNITE-8085) Flaky failures in Ignite Client Nodes test suite: Remote node could not start.

[Dmitriy Pavlov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484011#comment-16484011
 ] 

Dmitriy Pavlov edited comment on IGNITE-8085 at 5/22/18 3:09 PM:
-

[~ivanan.fed] it does not matter we need to fix only test or code, we are free 
to reclassify this ticket to bug or even to improvement.

If you are ready for contribute fix in code, it is up to you to create separate 
ticket (related/linked to this) or reopen current ticket.

As far as I know [~Mmuzaf] can advice about correct test stopping approach, 
[~Mmuzaf], please step in.


was (Author: dpavlov):
[~ivanan.fed] it does not matter we need to fix only test or code, we are free 
to reclassify this ticket to bug or even for improvement.

If you are ready for contribute fix in code, it is up to you to create separate 
ticket related to this or reopen current ticket.

As far as I know [~Mmuzaf] can advice about correct test stopping approach, 
[~Mmuzaf], please step in.

> Flaky failures in Ignite Client Nodes test suite:  Remote node could not 
> start. 
> 
>
> Key: IGNITE-8085
> URL: https://issues.apache.org/jira/browse/IGNITE-8085
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Ivan Fedotov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
>   Ignite Start Nodes 
>   IgniteStartStopRestartTestSuite: 
> IgniteProjectionStartStopRestartSelfTest.testStartFiveNodesInTwoCalls (master 
> fail rate 12,1%) 
>   IgniteStartStopRestartTestSuite: 
> IgniteProjectionStartStopRestartSelfTest.testStopNodes (master fail rate 
> 10,1%) 
>   IgniteStartStopRestartTestSuite: 
> IgniteProjectionStartStopRestartSelfTest.testStopNodesByIds (master fail rate 
> 10,1%) 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=6814497542781613621=%3Cdefault%3E=testDetails
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=1179745277331816127=%3Cdefault%3E=testDetails
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-842929918974855010=%3Cdefault%3E=testDetails
> Test itself is quite old. Last commits were from [~tledkov-gridgain] at 2017.
>  {noformat}
> class org.apache.ignite.IgniteException: Remote node could not start. See log 
> for details: 
> /data/teamcity/work/bd85361428dcdb1/work/log/ignite-startNodes/03-29-2018--02-47-24-2003434e.log
> at 
> org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest$7.apply(IgniteProjectionStartStopRestartSelfTest.java:388)
> at 
> org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest$7.apply(IgniteProjectionStartStopRestartSelfTest.java:383)
> at 
> org.apache.ignite.internal.util.lang.GridFunc.forEach(GridFunc.java:1897)
> at 
> org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.testStartFiveNodesInTwoCalls(IgniteProjectionStartStopRestartSelfTest.java:383)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2002)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1917)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}



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

[jira] [Commented] (IGNITE-6075) CacheLoadingConcurrentGridStartSelfTest sometimes fails

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484109#comment-16484109
 ] 

ASF GitHub Bot commented on IGNITE-6075:


Github user asfgit closed the pull request at:

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


> CacheLoadingConcurrentGridStartSelfTest sometimes fails
> ---
>
> Key: IGNITE-6075
> URL: https://issues.apache.org/jira/browse/IGNITE-6075
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Igor Seliverstov
>Assignee: Ivan Fedotov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> Seems that not all keys are in a cache after loading via DataStreamer
> {{CacheLoadingConcurrentGridStartSelfTest.testLoadCacheWithDataStreamerSequential}}
> {noformat}
> [2017-08-15 13:25:38,435][INFO 
> ][test-runner-#54053%distributed.CacheLoadingConcurrentGridStartSelfTest%][root]
>  Streaming 30'th entry.
> [2017-08-15 13:25:39,277][INFO 
> ][test-runner-#54053%distributed.CacheLoadingConcurrentGridStartSelfTest%][root]
>  Streaming 40'th entry.
> [2017-08-15 13:25:40,100][INFO 
> ][test-runner-#54053%distributed.CacheLoadingConcurrentGridStartSelfTest%][root]
>  Streaming 50'th entry.
> [2017-08-15 13:25:40,866][INFO 
> ][test-runner-#54053%distributed.CacheLoadingConcurrentGridStartSelfTest%][root]
>  Streaming 60'th entry.
> [2017-08-15 13:25:41,666][INFO 
> ][test-runner-#54053%distributed.CacheLoadingConcurrentGridStartSelfTest%][root]
>  Streaming 70'th entry.
> [2017-08-15 13:25:42,453][INFO 
> ][test-runner-#54053%distributed.CacheLoadingConcurrentGridStartSelfTest%][root]
>  Streaming 80'th entry.
> [2017-08-15 13:25:43,211][INFO 
> ][test-runner-#54053%distributed.CacheLoadingConcurrentGridStartSelfTest%][root]
>  Streaming 90'th entry.
> [2017-08-15 13:25:43,944][INFO 
> ][test-runner-#54053%distributed.CacheLoadingConcurrentGridStartSelfTest%][root]
>  Data loaded.
> [2017-08-15 13:26:06,518][INFO 
> ][test-runner-#54053%distributed.CacheLoadingConcurrentGridStartSelfTest%][root]
>  Actual cache size: 98
> [2017-08-15 13:26:06,519][INFO 
> ][test-runner-#54053%distributed.CacheLoadingConcurrentGridStartSelfTest%][root]
>  Missed key info:8fe76132-b563-4b7e-b611-386f5de4 primary=true 
> backup=false local peek=null
> [2017-08-15 13:26:06,519][INFO 
> ][test-runner-#54053%distributed.CacheLoadingConcurrentGridStartSelfTest%][root]
>  Missed key info:b774fe8f-849a-4b1f-abf6-26acd5f2 primary=false 
> backup=false local peek=null
> [2017-08-15 13:26:06,519][INFO 
> ][test-runner-#54053%distributed.CacheLoadingConcurrentGridStartSelfTest%][root]
>  Missed key info:d4f4a4ae-a1e3-4c6b-90b8-823898c3 primary=false 
> backup=false local peek=null
> [2017-08-15 13:26:06,519][INFO 
> ][test-runner-#54053%distributed.CacheLoadingConcurrentGridStartSelfTest%][root]
>  Missed key info:17a2d999-045e-4e58-8be6-55930a30 primary=false 
> backup=false local peek=null
> [2017-08-15 13:26:06,519][INFO 
> ][test-runner-#54053%distributed.CacheLoadingConcurrentGridStartSelfTest%][root]
>  Missed key info:e18c8fb1-c972-4a75-901c-818bbf91 primary=false 
> backup=true local peek=null
> {noformat}



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

[jira] [Commented] (IGNITE-7524) JDBC: Add a note about connection non-thread safety to docs

[Denis Magda (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484110#comment-16484110
 ] 

Denis Magda commented on IGNITE-7524:
-

[~tledkov-gridgain], does this go into 2.5?

> JDBC: Add a note about connection non-thread safety to docs
> ---
>
> Key: IGNITE-7524
> URL: https://issues.apache.org/jira/browse/IGNITE-7524
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.5
>
>
> Our JDBC connection is not thread safe. Let's mention it in docs.



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

[jira] [Updated] (IGNITE-7524) JDBC: Add a note about connection non-thread safety to docs

[Denis Magda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda updated IGNITE-7524:

Fix Version/s: (was: 2.6)
   2.5

> JDBC: Add a note about connection non-thread safety to docs
> ---
>
> Key: IGNITE-7524
> URL: https://issues.apache.org/jira/browse/IGNITE-7524
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.5
>
>
> Our JDBC connection is not thread safe. Let's mention it in docs.



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

[jira] [Commented] (IGNITE-8460) Document JDBC thin driver DataSource

[Denis Magda (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484104#comment-16484104
 ] 

Denis Magda commented on IGNITE-8460:
-

[~tledkov-gridgain], are these 2.5 changes, right?

> Document JDBC thin driver DataSource
> 
>
> Key: IGNITE-8460
> URL: https://issues.apache.org/jira/browse/IGNITE-8460
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, jdbc
>Reporter: Vladimir Ozerov
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.5
>
>




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

[jira] [Updated] (IGNITE-8460) Document JDBC thin driver DataSource

[Denis Magda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda updated IGNITE-8460:

Fix Version/s: (was: 2.6)
   2.5

> Document JDBC thin driver DataSource
> 
>
> Key: IGNITE-8460
> URL: https://issues.apache.org/jira/browse/IGNITE-8460
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, jdbc
>Reporter: Vladimir Ozerov
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.5
>
>




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

[jira] [Commented] (IGNITE-8526) Create web-agent docker image for k8s deployment

[Roman Guseinov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484100#comment-16484100
 ] 

Roman Guseinov commented on IGNITE-8526:


[~vveider] , I've checked those docker-images on Google Cloud (Kubernetes 
Cluster). Web Agent works well. In logs, I see that it was able to establish a 
connection to Grid and Web Console.

> Create web-agent docker image for k8s deployment
> 
>
> Key: IGNITE-8526
> URL: https://issues.apache.org/jira/browse/IGNITE-8526
> Project: Ignite
>  Issue Type: Improvement
>  Components: build, UI
>Reporter: Roman Guseinov
>Assignee: Peter Ivanov
>Priority: Major
> Attachments: Dockerfile
>
>
> Currently, apacheignite/web-console-standalone is not enough to run 
> web-console in Kubernetes environment. The only way to connect a cluster from 
> web console is to use web-agent. That's why we need a docker image which we 
> can configure (grid and console addresses, security tokens) and run on k8s 
> env.
> Dockerfile example is attached.



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

[jira] [Assigned] (IGNITE-7116) Logging minor issue as error instead of warning or info

[Dmitriy Pavlov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov reassigned IGNITE-7116:
--

Resolution: Fixed
  Assignee: Kirill Danilov

[~Donz], thank you, I've merged change to master
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=d52bfdb172ae447fd1e391e7e6dd62018fb9579f

[~EdShangGG] thank you for review.

> Logging minor issue as error instead of warning or info
> ---
>
> Key: IGNITE-7116
> URL: https://issues.apache.org/jira/browse/IGNITE-7116
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.3
>Reporter: Kirill Danilov
>Assignee: Kirill Danilov
>Priority: Major
> Fix For: 2.6
>
> Attachments: 
> 0001-IGNITE-7116-Decrease-logging-level-for-minor-problem.patch
>
>
> In case of using Ignite with Tomcat and its connection pool Tomcat tries to 
> lookup for every JDBC driver that it can found. So IgniteJdbcDriver is loaded 
> too. And this class has field
> {code:java}
> private static final IgniteLogger LOG = new JavaLogger();
> {code}
> which leads to JavaLogger loading and initialization. And in method
> {code:java}
> org.apache.ignite.logger.java.JavaLogger#defaultConfiguration
> {code}
>  there is try to get logging configuration from default file which is absent. 
> So we get 
> {code:java}
> error("Failed to resolve default logging config file: " + DFLT_CONFIG_PATH);
> {code}
> in logs and this is very annoying as any log analyzer begins to cry about 
> errors during startup.
> But really this error doesn't affect anything.
> So I offer to use warning instead of error.



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

[jira] [Commented] (IGNITE-7116) Logging minor issue as error instead of warning or info

[Eduard Shangareev (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484095#comment-16484095
 ] 

Eduard Shangareev commented on IGNITE-7116:
---

Looks fine. [~dpavlov], would you merge the patch?

> Logging minor issue as error instead of warning or info
> ---
>
> Key: IGNITE-7116
> URL: https://issues.apache.org/jira/browse/IGNITE-7116
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.3
>Reporter: Kirill Danilov
>Priority: Major
> Fix For: 2.6
>
> Attachments: 
> 0001-IGNITE-7116-Decrease-logging-level-for-minor-problem.patch
>
>
> In case of using Ignite with Tomcat and its connection pool Tomcat tries to 
> lookup for every JDBC driver that it can found. So IgniteJdbcDriver is loaded 
> too. And this class has field
> {code:java}
> private static final IgniteLogger LOG = new JavaLogger();
> {code}
> which leads to JavaLogger loading and initialization. And in method
> {code:java}
> org.apache.ignite.logger.java.JavaLogger#defaultConfiguration
> {code}
>  there is try to get logging configuration from default file which is absent. 
> So we get 
> {code:java}
> error("Failed to resolve default logging config file: " + DFLT_CONFIG_PATH);
> {code}
> in logs and this is very annoying as any log analyzer begins to cry about 
> errors during startup.
> But really this error doesn't affect anything.
> So I offer to use warning instead of error.



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

[jira] [Updated] (IGNITE-7116) Logging minor issue as error instead of warning or info

[Dmitriy Pavlov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-7116:
---
Fix Version/s: 2.6

> Logging minor issue as error instead of warning or info
> ---
>
> Key: IGNITE-7116
> URL: https://issues.apache.org/jira/browse/IGNITE-7116
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.3
>Reporter: Kirill Danilov
>Priority: Major
> Fix For: 2.6
>
> Attachments: 
> 0001-IGNITE-7116-Decrease-logging-level-for-minor-problem.patch
>
>
> In case of using Ignite with Tomcat and its connection pool Tomcat tries to 
> lookup for every JDBC driver that it can found. So IgniteJdbcDriver is loaded 
> too. And this class has field
> {code:java}
> private static final IgniteLogger LOG = new JavaLogger();
> {code}
> which leads to JavaLogger loading and initialization. And in method
> {code:java}
> org.apache.ignite.logger.java.JavaLogger#defaultConfiguration
> {code}
>  there is try to get logging configuration from default file which is absent. 
> So we get 
> {code:java}
> error("Failed to resolve default logging config file: " + DFLT_CONFIG_PATH);
> {code}
> in logs and this is very annoying as any log analyzer begins to cry about 
> errors during startup.
> But really this error doesn't affect anything.
> So I offer to use warning instead of error.



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

[jira] [Comment Edited] (IGNITE-8175) Missed CRC update in Lucene index.

[Eduard Shangareev (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484085#comment-16484085
 ] 

Eduard Shangareev edited comment on IGNITE-8175 at 5/22/18 2:50 PM:


I don't see any new test. Was there a test which failed because of the issue?

Also, we have PureJavaCrc32 which showed better performance in benchmarks.


was (Author: edshanggg):
I don't see any new test. Was there a test which failed because of the issue?

> Missed CRC update in Lucene index.
> --
>
> Key: IGNITE-8175
> URL: https://issues.apache.org/jira/browse/IGNITE-8175
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.1, 2.2, 2.3, 2.4
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>Priority: Major
> Fix For: 2.6
>
>
> We've missed CRC update in GridLuceneOutputStream.copyBytes() method.
>  See for [1] details.
> [1] 
> [http://apache-ignite-developers.2346864.n4.nabble.com/Lucene-CorruptIndexException-checksum-failed-on-GridLuceneIndex-suggested-patch-tp29016.html]



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

[jira] [Commented] (IGNITE-8175) Missed CRC update in Lucene index.

[Eduard Shangareev (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484085#comment-16484085
 ] 

Eduard Shangareev commented on IGNITE-8175:
---

I don't see any new test. Was there a test which failed because of the issue?

> Missed CRC update in Lucene index.
> --
>
> Key: IGNITE-8175
> URL: https://issues.apache.org/jira/browse/IGNITE-8175
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.1, 2.2, 2.3, 2.4
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>Priority: Major
> Fix For: 2.6
>
>
> We've missed CRC update in GridLuceneOutputStream.copyBytes() method.
>  See for [1] details.
> [1] 
> [http://apache-ignite-developers.2346864.n4.nabble.com/Lucene-CorruptIndexException-checksum-failed-on-GridLuceneIndex-suggested-patch-tp29016.html]



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

[jira] [Commented] (IGNITE-7818) Incorrect assertion in PDS page eviction method

[Dmitriy Pavlov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484080#comment-16484080
 ] 

Dmitriy Pavlov commented on IGNITE-7818:


I'm not sure I agree with fix, we still can't operate if we got invalid PTR 
after while execution.

> Incorrect assertion in PDS page eviction method
> ---
>
> Key: IGNITE-7818
> URL: https://issues.apache.org/jira/browse/IGNITE-7818
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Reporter: Aleksey Plekhanov
>Assignee: Ivan Fedotov
>Priority: Major
>
> There is an assertion in the method 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.Segment#removePageForReplacement:
>  
> {code:java}
> assert relRmvAddr != INVALID_REL_PTR;{code}
> Which seems potentially dangerous. In some rare cases, when count of 
> interations more then 40% of allocated pages and all processed pages are 
> aquired, the {{relRmvAddr}} variable will be uninitialized and 
> {{AssertionException}} will be thrown. But it's a correct case and page to 
> evict can be found later in the method {{tryToFindSequentially.}}
>  



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

[jira] [Commented] (IGNITE-8461) Scala-2.10 modules compilation failure under JDK 9

[Andrey Gura (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484067#comment-16484067
 ] 

Andrey Gura commented on IGNITE-8461:
-

[~vveider] TC run contains failed build configurations: {{Scala (Examples)}}, 
{{Scala (Visor Console)}} and {{RDD}}. All are failed with the same problem: 
{{java.lang.NoClassDefFoundError: scala/Product$class}}

I've reran this configuration in order to exclude environment problems. Will 
check later.

> Scala-2.10 modules compilation failure under JDK 9
> --
>
> Key: IGNITE-8461
> URL: https://issues.apache.org/jira/browse/IGNITE-8461
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Critical
> Fix For: 2.6
>
>
> {code}
> [ERROR] error: java.lang.NoClassDefFoundError: javax/tools/ToolProvider
> [INFO]at 
> scala.reflect.io.JavaToolsPlatformArchive.iterator(ZipArchive.scala:242)
> [INFO]at 
> scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
> [INFO]at scala.reflect.io.AbstractFile.foreach(AbstractFile.scala:92)
> [INFO]at 
> scala.tools.nsc.util.DirectoryClassPath.traverse(ClassPath.scala:308)
> [INFO]at 
> scala.tools.nsc.util.DirectoryClassPath.x$16$lzycompute(ClassPath.scala:317)
> [INFO]at 
> scala.tools.nsc.util.DirectoryClassPath.x$16(ClassPath.scala:317)
> [INFO]at 
> scala.tools.nsc.util.DirectoryClassPath.packages$lzycompute(ClassPath.scala:317)
> [INFO]at 
> scala.tools.nsc.util.DirectoryClassPath.packages(ClassPath.scala:317)
> [INFO]at 
> scala.tools.nsc.util.DirectoryClassPath.packages(ClassPath.scala:297)
> [INFO]at 
> scala.tools.nsc.util.MergedClassPath$$anonfun$packages$1.apply(ClassPath.scala:375)
> [INFO]at 
> scala.tools.nsc.util.MergedClassPath$$anonfun$packages$1.apply(ClassPath.scala:375)
> [INFO]at scala.collection.Iterator$class.foreach(Iterator.scala:727)
> [INFO]at 
> scala.collection.AbstractIterator.foreach(Iterator.scala:1157)
> [INFO]at 
> scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
> [INFO]at scala.collection.AbstractIterable.foreach(Iterable.scala:54)
> [INFO]at 
> scala.tools.nsc.util.MergedClassPath.packages$lzycompute(ClassPath.scala:375)
> [INFO]at 
> scala.tools.nsc.util.MergedClassPath.packages(ClassPath.scala:370)
> [INFO]at 
> scala.tools.nsc.symtab.SymbolLoaders$PackageLoader.doComplete(SymbolLoaders.scala:243)
> [INFO]at 
> scala.tools.nsc.symtab.SymbolLoaders$SymbolLoader.complete(SymbolLoaders.scala:194)
> [INFO]at 
> scala.reflect.internal.Symbols$Symbol.info(Symbols.scala:1231)
> [INFO]at 
> scala.reflect.internal.Mirrors$RootsBase.init(Mirrors.scala:240)
> [INFO]at scala.tools.nsc.Global.rootMirror$lzycompute(Global.scala:59)
> [INFO]at scala.tools.nsc.Global.rootMirror(Global.scala:57)
> [INFO]at scala.tools.nsc.Global.rootMirror(Global.scala:37)
> [INFO]at 
> scala.reflect.internal.Definitions$DefinitionsClass.(Definitions.scala:166)
> [INFO]at 
> scala.reflect.internal.Definitions$definitions$.(Definitions.scala:20)
> [INFO]at 
> scala.reflect.internal.SymbolTable.definitions$lzycompute(SymbolTable.scala:13)
> [INFO]at 
> scala.reflect.internal.SymbolTable.definitions(SymbolTable.scala:13)
> [INFO]at scala.tools.nsc.Global$Run.(Global.scala:1290)
> [INFO]at scala.tools.nsc.Driver.doCompile(Driver.scala:32)
> [INFO]at scala.tools.nsc.Main$.doCompile(Main.scala:79)
> [INFO]at scala.tools.nsc.Driver.process(Driver.scala:54)
> [INFO]at scala.tools.nsc.Driver.main(Driver.scala:67)
> [INFO]at scala.tools.nsc.Main.main(Main.scala)
> [INFO]at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [INFO]at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [INFO]at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [INFO]at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> [INFO]at 
> scala_maven_executions.MainHelper.runMain(MainHelper.java:164)
> [INFO]at 
> scala_maven_executions.MainWithArgsInFile.main(MainWithArgsInFile.java:26)
> [INFO]
> [INFO] java.lang.reflect.InvocationTargetException
> [INFO]at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [INFO]at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [INFO]at 
> 

[jira] [Commented] (IGNITE-6803) UriDeploymentSpi affects execution of other tasks, including Ignite internals

[Dmitriy Pavlov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484022#comment-16484022
 ] 

Dmitriy Pavlov commented on IGNITE-6803:


[~ilyak] please close not actual PR. Presence of 2 open PRs confuses a lot.

> UriDeploymentSpi affects execution of other tasks, including Ignite internals
> -
>
> Key: IGNITE-6803
> URL: https://issues.apache.org/jira/browse/IGNITE-6803
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Ilya Kasnacheev
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.6
>
> Attachments: tc.png
>
>
> From the maillist:
> http://apache-ignite-users.70518.x6.nabble.com/Code-deployment-throught-UriDeploumentSpi-tt17807.html
> In our project we need to deploy custom compute tasks into cluster without 
> cluster restart and p2p class loading.  
> I try to use org.apache.ignite.spi.deployment.uri.UriDeploumentSpi for that 
> purpose, but I have a problem.
> I have simple Ignite Service and Ignite Compute Task which use it throught 
> @ServiceResource.
> This ComputeTask located into .gar file which was deployed via 
> UriDeploumentSpi.
> If I have service implementation on each node(node singleton service) then it 
> works great. 
> But if I deploy service as a cluster singleton then task executes correctly 
> only on node with this service. 
> On other nodes @ServiceResource returns ServiceProxy that throws exception on 
> service remote method invokation (lambda with service call cannot be 
> deployed):
> {code}
> SEVERE: Failed to execute job 
> [jobId=68a96d76f51-7919c34c-9a48-4068-bcd6-70dad5595e86, 
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl [taskName=task-one, 
> dep=GridDeployment [ts=1509275650885, depMode=SHARED, 
> clsLdr=GridUriDeploymentClassLoader 
> [urls=[file:/C:/IdeaProjects/dmp_code_deployment/test/out/deployment/gg.uri.deployment.tmp/428ec712-e6d0-4eab-97f9-ce58d7b3e0f5/dirzip_task-one6814855127293591501.gar/]],
>  clsLdrId=7eb15d76f51-428ec712-e6d0-4eab-97f9-ce58d7b3e0f5, userVer=0, 
> loc=true, sampleClsName=com.gridfore.tfedyanin.deploy.Task1, 
> pendingUndeploy=false, undeployed=false, usage=1], 
> taskClsName=com.gridfore.tfedyanin.deploy.Task1, 
> sesId=38a96d76f51-7919c34c-9a48-4068-bcd6-70dad5595e86, 
> startTime=1509275650601, endTime=9223372036854775807, 
> taskNodeId=7919c34c-9a48-4068-bcd6-70dad5595e86, 
> clsLdr=GridUriDeploymentClassLoader 
> [urls=[file:/C:/IdeaProjects/dmp_code_deployment/test/out/deployment/gg.uri.deployment.tmp/428ec712-e6d0-4eab-97f9-ce58d7b3e0f5/dirzip_task-one6814855127293591501.gar/]],
>  closed=false, cpSpi=null, failSpi=null, loadSpi=null, usage=1, 
> fullSup=false, internal=false, subjId=7919c34c-9a48-4068-bcd6-70dad5595e86, 
> mapFut=IgniteFuture [orig=GridFutureAdapter [ignoreInterrupts=false, 
> state=INIT, res=null, hash=1254296516]], execName=null], 
> jobId=68a96d76f51-7919c34c-9a48-4068-bcd6-70dad5595e86]]
> class org.apache.ignite.IgniteDeploymentException: Failed to auto-deploy task 
> (was task (re|un)deployed?): class 
> org.apache.ignite.internal.processors.service.GridServiceProcessor$ServiceTopologyCallable
> {code}
> Problem works as follows:
> - Ignite has to determine which node has deployed service, by name.
> - Ignite has to send ServiceTopologyCallable task.
> - Ignite tries to deploy ServiceTopologyCallable task using UriDeploymentSpi.
> - UriDeploymentSpi doesn't have it obviously, but it also tries to fallback 
> towards "CLASS" loading from local ClassLoader
> - Which fails because it is told that ServiceTopologyCallable comes from its 
> classloader and not from the local one!
> So I'm at loss where it should be fixed properly. It is also sad that we are 
> using all that deploy pipeline to handle IgniteInternal tasks, but there 
> obviously are non-internal local tasks which might be affected by same 
> problem.



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

[jira] [Commented] (IGNITE-8085) Flaky failures in Ignite Client Nodes test suite: Remote node could not start.

[Dmitriy Pavlov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484011#comment-16484011
 ] 

Dmitriy Pavlov commented on IGNITE-8085:


[~ivanan.fed] it does not matter we need to fix only test or code, we are free 
to reclassify this ticket to bug or even for improvement.

If you are ready for contribute fix in code, it is up to you to create separate 
ticket related to this or reopen current ticket.

As far as I know [~Mmuzaf] can advice about correct test stopping approach, 
[~Mmuzaf], please step in.

> Flaky failures in Ignite Client Nodes test suite:  Remote node could not 
> start. 
> 
>
> Key: IGNITE-8085
> URL: https://issues.apache.org/jira/browse/IGNITE-8085
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Ivan Fedotov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
>   Ignite Start Nodes 
>   IgniteStartStopRestartTestSuite: 
> IgniteProjectionStartStopRestartSelfTest.testStartFiveNodesInTwoCalls (master 
> fail rate 12,1%) 
>   IgniteStartStopRestartTestSuite: 
> IgniteProjectionStartStopRestartSelfTest.testStopNodes (master fail rate 
> 10,1%) 
>   IgniteStartStopRestartTestSuite: 
> IgniteProjectionStartStopRestartSelfTest.testStopNodesByIds (master fail rate 
> 10,1%) 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=6814497542781613621=%3Cdefault%3E=testDetails
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=1179745277331816127=%3Cdefault%3E=testDetails
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-842929918974855010=%3Cdefault%3E=testDetails
> Test itself is quite old. Last commits were from [~tledkov-gridgain] at 2017.
>  {noformat}
> class org.apache.ignite.IgniteException: Remote node could not start. See log 
> for details: 
> /data/teamcity/work/bd85361428dcdb1/work/log/ignite-startNodes/03-29-2018--02-47-24-2003434e.log
> at 
> org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest$7.apply(IgniteProjectionStartStopRestartSelfTest.java:388)
> at 
> org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest$7.apply(IgniteProjectionStartStopRestartSelfTest.java:383)
> at 
> org.apache.ignite.internal.util.lang.GridFunc.forEach(GridFunc.java:1897)
> at 
> org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.testStartFiveNodesInTwoCalls(IgniteProjectionStartStopRestartSelfTest.java:383)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2002)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1917)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}



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

[jira] [Created] (IGNITE-8563) WAL file archiver does not propagate file archiving error to error handler

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-8563:


 Summary: WAL file archiver does not propagate file archiving error 
to error handler
 Key: IGNITE-8563
 URL: https://issues.apache.org/jira/browse/IGNITE-8563
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.5
Reporter: Alexey Goncharuk
 Fix For: 2.6


I observed this error when a disk with WAL archive left out of space:
{code}
...
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.finishTx(GridDhtTxLocal.java:464)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.commitDhtLocalAsync(GridDhtTxLocal.java:517)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:940)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:819)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:775)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$200(IgniteTxHandler.java:97)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:189)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:187)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1054)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
at 
org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:511)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.ignite.IgniteException: Runtime failure on row: 
Row@1ec13b23[ key: 4458000681143704309, val: 
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2119)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2066)
at 
org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:247)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.addToIndex(GridH2Table.java:548)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:480)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:659)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:1866)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:403)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:1393)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1257)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.invoke(GridCacheOffheapManager.java:1511)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:352)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.storeValue(GridCacheMapEntry.java:3602)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.storeValue(GridCacheMapEntry.java:3578)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerSet(GridCacheMapEntry.java:1040)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:652)
... 22 common frames omitted
Caused by: org.apache.ignite.IgniteException: Failed to archive WAL 

[jira] [Commented] (IGNITE-8501) Retry on GridServiceNotFoundException in GridServiceProxy needs to be fixed

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483971#comment-16483971
 ] 

ASF GitHub Bot commented on IGNITE-8501:


Github user asfgit closed the pull request at:

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


> Retry on GridServiceNotFoundException in GridServiceProxy needs to be fixed
> ---
>
> Key: IGNITE-8501
> URL: https://issues.apache.org/jira/browse/IGNITE-8501
> Project: Ignite
>  Issue Type: Bug
>Reporter: Stanislav Lukyanov
>Assignee: Stanislav Lukyanov
>Priority: Major
> Fix For: 2.6
>
>
> `GridServiceProxy::invokeMethod` attempts to invoke a method of an Ignite 
> service and performs retries in case the invocation procedure throws 
> `GridServiceNotFoundException` or `ClusterTopologyCheckedException` (these 
> exceptions may be thrown in case the service assignments were already 
> calculated, but the service instance was not yet created and initialized on 
> the affinity server).
> After the fix IGNITE-7904 the exception type thrown by the remote invocation 
> code changed to `IgniteCheckedException` (with a cause being 
> `GridServiceNotFoundException` or `ClusterTopologyCheckedException`). Because 
> of that, the retry doesn't work now.
> Need to fix the code to correctly handle new exception chain.



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

[jira] [Commented] (IGNITE-8501) Retry on GridServiceNotFoundException in GridServiceProxy needs to be fixed

[Ivan Rakov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483970#comment-16483970
 ] 

Ivan Rakov commented on IGNITE-8501:


Looks good to me as well. Merged to master.

> Retry on GridServiceNotFoundException in GridServiceProxy needs to be fixed
> ---
>
> Key: IGNITE-8501
> URL: https://issues.apache.org/jira/browse/IGNITE-8501
> Project: Ignite
>  Issue Type: Bug
>Reporter: Stanislav Lukyanov
>Assignee: Stanislav Lukyanov
>Priority: Major
> Fix For: 2.6
>
>
> `GridServiceProxy::invokeMethod` attempts to invoke a method of an Ignite 
> service and performs retries in case the invocation procedure throws 
> `GridServiceNotFoundException` or `ClusterTopologyCheckedException` (these 
> exceptions may be thrown in case the service assignments were already 
> calculated, but the service instance was not yet created and initialized on 
> the affinity server).
> After the fix IGNITE-7904 the exception type thrown by the remote invocation 
> code changed to `IgniteCheckedException` (with a cause being 
> `GridServiceNotFoundException` or `ClusterTopologyCheckedException`). Because 
> of that, the retry doesn't work now.
> Need to fix the code to correctly handle new exception chain.



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

[jira] [Commented] (IGNITE-8525) Support for IgniteZeroMqStreamer non-multi-part pub-sub

[Roman Shtykh (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483968#comment-16483968
 ] 

Roman Shtykh commented on IGNITE-8525:
--

[~dpavlov], [~gvvinblade] Thanks for having a look, guys! Will merge and close.

> Support for IgniteZeroMqStreamer non-multi-part pub-sub
> ---
>
> Key: IGNITE-8525
> URL: https://issues.apache.org/jira/browse/IGNITE-8525
> Project: Ignite
>  Issue Type: Improvement
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>Priority: Major
> Fix For: 2.6
>
>
> Currently only multi-part pub-sub is supported.



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

[jira] [Commented] (IGNITE-6587) Ignite watchdog service

[Andrey Kuznetsov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483947#comment-16483947
 ] 

Andrey Kuznetsov commented on IGNITE-6587:
--

Changing critical threads to {{GridWorkers}} has been brought to separate 
issue, since it has it's own value.

> Ignite watchdog service
> ---
>
> Key: IGNITE-6587
> URL: https://issues.apache.org/jira/browse/IGNITE-6587
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 2.2
>Reporter: Alexey Goncharuk
>Assignee: Andrey Kuznetsov
>Priority: Major
>  Labels: IEP-5
> Fix For: 2.6
>
> Attachments: watchdog.sh
>
>
> As described in [1], each Ignite node has a number of system-critical 
> threads. We should implement a periodic check that calls failure handler when 
> one of the following conditions has been detected:
> * Critical thread is not alive anymore.
> * Critical thread 'hangs' for a long time, e.g. while executing a task 
> extracted from task queue.
> In case of failure condition, call stacks of all threads should be logged 
> before invoking failure handler.
> Actual list of system-critical threads can be found at [1].
> Implementations based on separate diagnostic thread seem fragile, cause this 
> thread become a vulnerable point with respect to thread termination and CPU 
> resource starvation. So we are to use self-monitoring approach: critical 
> threads themselves should monitor each other.
> Currently we have {{o.a.i.internal.worker.WorkersRegistry}} facility that 
> fits best to store and track system critical threads. All of them should be 
> refactored to be {{GridWorker's}} and added to {{WorkersRegistry}}. Each 
> worker should periodically choose some subset of peer workers and check 
> whether
> * All of them are alive.
> * All of them are actively running.
> It's required to add a 'heartbeat' timestamp to worker in order to implement 
> latter check. Additionally, infinite queue polls, waits on monitors or thread 
> parks should be refactored to their timed equivalents in system critical 
> threads.
> Monitoring parameters (enable/disable, check interval, thread 'hang' 
> threshold, etc.) are to be set via system properties.
> [1] 
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling



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

[jira] [Created] (IGNITE-8562) Turn system-critical Ignite threads into GridWorkers

[Andrey Kuznetsov (JIRA)]

Andrey Kuznetsov created IGNITE-8562:


 Summary: Turn system-critical Ignite threads into GridWorkers
 Key: IGNITE-8562
 URL: https://issues.apache.org/jira/browse/IGNITE-8562
 Project: Ignite
  Issue Type: Improvement
Reporter: Andrey Kuznetsov
Assignee: Andrey Kuznetsov
 Fix For: 2.6


The goal of the change is to make system-critical threads (in terms of IEP-14, 
[1]) available to {{WorkersControlMXBean}}.

[1] 
https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling



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

[jira] [Commented] (IGNITE-8561) SinglSegmentLogicalRecordsIterator is broken

[Anton Kalashnikov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483932#comment-16483932
 ] 

Anton Kalashnikov commented on IGNITE-8561:
---

TC - 
[https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=projectOverview_IgniteTests24Java8=pull%2F4045%2Fhead]

 

UP - https://reviews.ignite.apache.org/ignite/review/IGNT-CR-618

> SinglSegmentLogicalRecordsIterator is broken
> 
>
> Key: IGNITE-8561
> URL: https://issues.apache.org/jira/browse/IGNITE-8561
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
>
> It causes by https://issues.apache.org/jira/browse/IGNITE-8464



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

[jira] [Assigned] (IGNITE-8548) Make Apache Ignite JCache 1.1 specification compliant

[Alexander Menshikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Menshikov reassigned IGNITE-8548:
---

Assignee: Alexander Menshikov

> Make Apache Ignite JCache 1.1 specification compliant
> -
>
> Key: IGNITE-8548
> URL: https://issues.apache.org/jira/browse/IGNITE-8548
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
>Assignee: Alexander Menshikov
>Priority: Major
>  Labels: newbie
> Fix For: 2.6
>
>
> JCache specification's license was changed to Apache 2.0, and 1.1 version was 
> released:
> https://groups.google.com/forum/#!topic/jsr107/BC1qKqknzKU
> Ignite needs to:
> * Upgrade to JCacahe 1.1 in general to use Apache 2.0 license
> *  Become JCache 1.1 compliant implementing new interfaces and passing TCK



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

[jira] [Commented] (IGNITE-8561) SinglSegmentLogicalRecordsIterator is broken

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483925#comment-16483925
 ] 

ASF GitHub Bot commented on IGNITE-8561:


GitHub user akalash opened a pull request:

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

IGNITE-8561 in SingleSegmentLogicalRecordsIterator changed archivedSe…

…gIdx to curWalSegmIdx from super class

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

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

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

https://github.com/apache/ignite/pull/4045.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 #4045


commit 64f4ce0232c2504065e6329a2da32ee2704fcc68
Author: Anton Kalashnikov 
Date:   2018-05-22T13:16:52Z

IGNITE-8561 in SingleSegmentLogicalRecordsIterator changed archivedSegIdx 
to curWalSegmIdx from super class




> SinglSegmentLogicalRecordsIterator is broken
> 
>
> Key: IGNITE-8561
> URL: https://issues.apache.org/jira/browse/IGNITE-8561
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
>
> It causes by https://issues.apache.org/jira/browse/IGNITE-8464



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

[jira] [Updated] (IGNITE-8561) SinglSegmentLogicalRecordsIterator is broken

[Anton Kalashnikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Kalashnikov updated IGNITE-8561:
--
Description: It causes by https://issues.apache.org/jira/browse/IGNITE-8464

> SinglSegmentLogicalRecordsIterator is broken
> 
>
> Key: IGNITE-8561
> URL: https://issues.apache.org/jira/browse/IGNITE-8561
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
>
> It causes by https://issues.apache.org/jira/browse/IGNITE-8464



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

[jira] [Updated] (IGNITE-7776) Check calculated values in javadoc

[Dmitriy Pavlov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-7776:
---
Fix Version/s: 2.6

> Check calculated values in javadoc
> --
>
> Key: IGNITE-7776
> URL: https://issues.apache.org/jira/browse/IGNITE-7776
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 2.0, 2.1, 2.2, 2.3
>Reporter: Alexander Belyak
>Assignee: Alexander Belyak
>Priority: Minor
> Fix For: 2.6
>
>
> We have two issue with calculated value in javadoc:
> 1) wrong numbers, for example: #\{5 * 1024 * 102 * 1024}
> 2) overflow int type, for example: #\{5 * 1024 * 1024 * 1024}
> Need to check as many places as possible.



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

[jira] [Created] (IGNITE-8561) SinglSegmentLogicalRecordsIterator is broken

[Anton Kalashnikov (JIRA)]

Anton Kalashnikov created IGNITE-8561:
-

 Summary: SinglSegmentLogicalRecordsIterator is broken
 Key: IGNITE-8561
 URL: https://issues.apache.org/jira/browse/IGNITE-8561
 Project: Ignite
  Issue Type: Bug
Reporter: Anton Kalashnikov
Assignee: Anton Kalashnikov






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

[jira] [Commented] (IGNITE-8525) Support for IgniteZeroMqStreamer non-multi-part pub-sub

[Dmitriy Pavlov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483900#comment-16483900
 ] 

Dmitriy Pavlov commented on IGNITE-8525:


[~gvvinblade] thank you for review

[~roman_s], could you please merge the change?

> Support for IgniteZeroMqStreamer non-multi-part pub-sub
> ---
>
> Key: IGNITE-8525
> URL: https://issues.apache.org/jira/browse/IGNITE-8525
> Project: Ignite
>  Issue Type: Improvement
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>Priority: Major
> Fix For: 2.6
>
>
> Currently only multi-part pub-sub is supported.



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

[jira] [Assigned] (IGNITE-8560) Update index validation utility to use statistical check approach

[Sergey Chugunov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Chugunov reassigned IGNITE-8560:
---

Assignee: Sergey Chugunov

> Update index validation utility to use statistical check approach
> -
>
> Key: IGNITE-8560
> URL: https://issues.apache.org/jira/browse/IGNITE-8560
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Sergey Chugunov
>Priority: Major
>
> Currently, the check index feature of {{control.sh}} scans the full data set 
> which has N * logN complexity. On large data sets this takes too long to 
> complete. 
> To mitigate this, I suggest to add an option 
> * to check either first K entries
> * to check each Kth entry



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

[jira] [Created] (IGNITE-8560) Update index validation utility to use statistical check approach

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-8560:


 Summary: Update index validation utility to use statistical check 
approach
 Key: IGNITE-8560
 URL: https://issues.apache.org/jira/browse/IGNITE-8560
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Goncharuk


Currently, the check index feature of {{control.sh}} scans the full data set 
which has N * logN complexity. On large data sets this takes too long to 
complete. 

To mitigate this, I suggest to add an option 
* to check either first K entries
* to check each Kth entry




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

[jira] [Commented] (IGNITE-5979) [Test Failed] GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync

[Alexey Goncharuk (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483884#comment-16483884
 ] 

Alexey Goncharuk commented on IGNITE-5979:
--

[~garus.d.g] this is a known limitation of ATOMIC cache which should be fixed 
separately from IGNITE-7833. For now I would suggest to change the test to 
either not crash originating node or check for new or previous value during 
read.

> [Test Failed]  
> GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync 
> 
>
> Key: IGNITE-5979
> URL: https://issues.apache.org/jira/browse/IGNITE-5979
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Priority: Major
>  Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.6
>
>
> Example of failing  - 
> http://ci.ignite.apache.org/viewLog.html?buildId=760709=buildResultsDiv=Ignite20Tests_IgniteDataGridFailover#testNameId6248548165747570497
> {noformat}
> junit.framework.AssertionFailedError: Failed to check value for key 
> [key=72625, node=0671e5c8-8bd5-4f2a-b1b8-9e945742, primary=false, 
> recNodeId=101770ef-a622-4f7c-b714-70ecf1f1] expected:<0> but 
> was:<-1994497644>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.TestCase.assertEquals(TestCase.java:244)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.checkRestarts(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:334)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:154)
> {noformat}



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

[jira] [Created] (IGNITE-8559) WAL rollOver can be blocked by WAL iterator reservation

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-8559:


 Summary: WAL rollOver can be blocked by WAL iterator reservation
 Key: IGNITE-8559
 URL: https://issues.apache.org/jira/browse/IGNITE-8559
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Goncharuk


I've got the following thread dump from one of the Ignite nodes (only 
meaningful threads are kept for simplicity)
WAL archiver is waiting for locked segment release
TX commit is waiting for WAL rollover
WAL rollover is blocked by the archiver
Exchange is blocked by TX commit

{code}
"sys-stripe-55-#56%GRID%GridNodeName%" #246 daemon prio=5 os_prio=0 
tid=0x7fdd1eeff000 nid=0x164252 waiting on condition [0x7fdb36eec000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x7fe0a5e96278> (a 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitUninterruptibly(AbstractQueuedSynchronizer.java:1976)
at 
org.apache.ignite.internal.util.IgniteUtils.awaitQuiet(IgniteUtils.java:7400)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.awaitNext(FileWriteAheadLogManager.java:2819)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.access$2900(FileWriteAheadLogManager.java:2390)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.rollOver(FileWriteAheadLogManager.java:1065)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.log(FileWriteAheadLogManager.java:715)
at 
org.gridgain.grid.internal.processors.cache.database.snapshot.GridCacheSnapshotManager.onChangeTrackerPage(GridCacheSnapshotManager.java:2436)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$9.applyx(GridCacheDatabaseSharedManager.java:942)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$9.applyx(GridCacheDatabaseSharedManager.java:935)
at 
org.apache.ignite.internal.util.lang.GridInClosure3X.apply(GridInClosure3X.java:34)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlockPage(PageMemoryImpl.java:1341)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:415)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:409)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeUnlock(PageHandler.java:377)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writePage(PageHandler.java:287)
at 
org.apache.ignite.internal.processors.cache.persistence.DataStructure.write(DataStructure.java:282)
at 
org.apache.ignite.internal.processors.cache.persistence.freelist.AbstractFreeList.insertDataRow(AbstractFreeList.java:509)
at 
org.apache.ignite.internal.processors.cache.persistence.RowStore.addRow(RowStore.java:102)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.createRow(IgniteCacheOffheapManagerImpl.java:1252)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.createRow(GridCacheOffheapManager.java:1370)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$UpdateClosure.call(GridCacheMapEntry.java:4429)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$UpdateClosure.call(GridCacheMapEntry.java:4374)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.invokeClosure(BPlusTree.java:3083)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.access$6200(BPlusTree.java:2977)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(BPlusTree.java:1726)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(BPlusTree.java:1703)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(BPlusTree.java:1703)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1610)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1199)
at 

[jira] [Commented] (IGNITE-6538) Ignite Activate/Deactivate Cluster suite: After tests validation improvements test became flaky on TC

[Maxim Muzafarov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483815#comment-16483815
 ] 

Maxim Muzafarov commented on IGNITE-6538:
-

This issue description is not reproducabe but test remains flaky.
I've updated description, need to investigate.

> Ignite Activate/Deactivate Cluster suite: After tests validation improvements 
> test became flaky on TC
> -
>
> Key: IGNITE-6538
> URL: https://issues.apache.org/jira/browse/IGNITE-6538
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Maxim Muzafarov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.6
>
>
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-238119157387028099=testDetails_Ignite20Tests=%3Cdefault%3E
> recent changes from [IGNITE-6124] which probably showed this problem is 
> following 
> {noformat}
>  fail("Activation should fail");
> {noformat}
> org.apache.ignite.internal.processors.cache.persistence.standbycluster.IgniteChangeGlobalStateTest#testActivateAfterFailGetLock
> Locally fail can be also reproduced, 6 from 20 failures.



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

[jira] [Updated] (IGNITE-6538) Ignite Activate/Deactivate Cluster suite: After tests validation improvements test became flaky on TC

[Maxim Muzafarov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated IGNITE-6538:

Description: 
https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-238119157387028099=testDetails_Ignite20Tests=%3Cdefault%3E

{code}
[14:36:09]W: [org.apache.ignite:ignite-core] [2018-05-22 
11:36:09,817][WARN 
][exchange-worker-#202059%node1-backUp%][GridDhtPartitionsExchangeFuture] 
Unable to await partitions release latch within timeout: ClientLatch 
[coordinator=TcpDiscoveryNode [id=ba7f90d8-3a1f-488a-a8ea-3ae2fdf016fe, 
addrs=[127.0.0.1, 172.17.0.7], sockAddrs=[/127.0.0.1:47503, 
d377975c5791/172.17.0.7:47503], discPort=47503, order=1, intOrder=1, 
lastExchangeTime=1526985998704, loc=false, ver=2.5.0#20180522-sha1:d37470c7, 
isClient=false], ackSent=true, super=CompletableLatch [id=exchange, 
topVer=AffinityTopologyVersion [topVer=6, minorTopVer=1]]]
{code}

Fail test:
{code}
org.apache.ignite.internal.processors.cache.persistence.standbycluster.IgniteChangeGlobalStateTest#testActivateAfterFailGetLock
{code}


  was:
https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-238119157387028099=testDetails_Ignite20Tests=%3Cdefault%3E

recent changes from [IGNITE-6124] which probably showed this problem is 
following 
{noformat}
 fail("Activation should fail");
{noformat}
org.apache.ignite.internal.processors.cache.persistence.standbycluster.IgniteChangeGlobalStateTest#testActivateAfterFailGetLock

Locally fail can be also reproduced, 6 from 20 failures.


> Ignite Activate/Deactivate Cluster suite: After tests validation improvements 
> test became flaky on TC
> -
>
> Key: IGNITE-6538
> URL: https://issues.apache.org/jira/browse/IGNITE-6538
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Maxim Muzafarov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.6
>
>
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-238119157387028099=testDetails_Ignite20Tests=%3Cdefault%3E
> {code}
> [14:36:09]W:   [org.apache.ignite:ignite-core] [2018-05-22 
> 11:36:09,817][WARN 
> ][exchange-worker-#202059%node1-backUp%][GridDhtPartitionsExchangeFuture] 
> Unable to await partitions release latch within timeout: ClientLatch 
> [coordinator=TcpDiscoveryNode [id=ba7f90d8-3a1f-488a-a8ea-3ae2fdf016fe, 
> addrs=[127.0.0.1, 172.17.0.7], sockAddrs=[/127.0.0.1:47503, 
> d377975c5791/172.17.0.7:47503], discPort=47503, order=1, intOrder=1, 
> lastExchangeTime=1526985998704, loc=false, ver=2.5.0#20180522-sha1:d37470c7, 
> isClient=false], ackSent=true, super=CompletableLatch [id=exchange, 
> topVer=AffinityTopologyVersion [topVer=6, minorTopVer=1]]]
> {code}
> Fail test:
> {code}
> org.apache.ignite.internal.processors.cache.persistence.standbycluster.IgniteChangeGlobalStateTest#testActivateAfterFailGetLock
> {code}



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

[jira] [Commented] (IGNITE-8526) Create web-agent docker image for k8s deployment

[Peter Ivanov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483808#comment-16483808
 ] 

Peter Ivanov commented on IGNITE-8526:
--

Prepared build configuration with Web Agent Docker image: 
https://ci.ignite.apache.org/viewLog.html?buildId=1320479=Releases_NightlyRelease_ApacheIgniteNightlyRelease3AssembleDockerImageIgnite8526=artifacts

> Create web-agent docker image for k8s deployment
> 
>
> Key: IGNITE-8526
> URL: https://issues.apache.org/jira/browse/IGNITE-8526
> Project: Ignite
>  Issue Type: Improvement
>  Components: build, UI
>Reporter: Roman Guseinov
>Assignee: Peter Ivanov
>Priority: Major
> Attachments: Dockerfile
>
>
> Currently, apacheignite/web-console-standalone is not enough to run 
> web-console in Kubernetes environment. The only way to connect a cluster from 
> web console is to use web-agent. That's why we need a docker image which we 
> can configure (grid and console addresses, security tokens) and run on k8s 
> env.
> Dockerfile example is attached.



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

[jira] [Commented] (IGNITE-4210) CacheLoadingConcurrentGridStartSelfTest.testLoadCacheFromStore() test lose data.

[Alexey Kuznetsov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483807#comment-16483807
 ] 

Alexey Kuznetsov commented on IGNITE-4210:
--

[~dpavlov] hi. 
Can you plz review the ticket?
All failed tests doesn't correspond to the patch.

> CacheLoadingConcurrentGridStartSelfTest.testLoadCacheFromStore() test lose 
> data.
> 
>
> Key: IGNITE-4210
> URL: https://issues.apache.org/jira/browse/IGNITE-4210
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Alexey Kuznetsov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> org.apache.ignite.internal.processors.cache.distributed.CacheLoadingConcurrentGridStartSelfTest#testLoadCacheFromStore
>  sometimes have failures.



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

[jira] [Updated] (IGNITE-8554) Cache metrics: expose metrics with rebalance info about keys

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-8554:
-
Fix Version/s: 2.6

> Cache metrics: expose metrics with rebalance info about keys
> 
>
> Key: IGNITE-8554
> URL: https://issues.apache.org/jira/browse/IGNITE-8554
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Alexey Kuznetsov
>Assignee: Vasiliy Sisko
>Priority: Major
> Fix For: 2.6
>
>
> In order to show info about rebalance progress we need to expose 
> estimatedRebalancingKeys and rebalancedKeys metrics.



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

[jira] [Updated] (IGNITE-8554) Cache metrics: expose metrics with rebalance info about keys

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-8554:
-
Component/s: cache

> Cache metrics: expose metrics with rebalance info about keys
> 
>
> Key: IGNITE-8554
> URL: https://issues.apache.org/jira/browse/IGNITE-8554
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Alexey Kuznetsov
>Assignee: Vasiliy Sisko
>Priority: Major
> Fix For: 2.6
>
>
> In order to show info about rebalance progress we need to expose 
> estimatedRebalancingKeys and rebalancedKeys metrics.



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

[jira] [Resolved] (IGNITE-8516) Not null constraint doesn't checked

[Anton Vinogradov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov resolved IGNITE-8516.
--
Resolution: Fixed

Looks good to me.

Merged to master branch.

Thanks for contribution!

> Not null constraint doesn't checked
> ---
>
> Key: IGNITE-8516
> URL: https://issues.apache.org/jira/browse/IGNITE-8516
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.4
>Reporter: Nikolay Izhikov
>Assignee: Denis Garus
>Priority: Major
> Fix For: 2.6
>
>
> User is able to insert null into the not null column through cache-api.
> If one uncomment line {{entries.put(new Organization("2"), new Address("Some 
> address"));}} - constraint applied and exception would be thrown.
> The same behaviour is expected for the 1 entry map.
> Reproducer:
> {code:java}
> package org.apache.ignite.internal.processors.sql;
> public class IgniteNotNullBug extends GridCommonAbstractTest {
> @Override protected void beforeTestsStarted() throws Exception {
> startGrid(0);
> Set nn = new HashSet<>();
> nn.add("address");
> jcache(grid(0), cacheConfiguration(new 
> QueryEntity(Organization.class.getName(), Address.class.getName())
> .addQueryField("address", "java.lang.String", "address")
> .setNotNullFields(nn)), "ORG_ADDRESS");
> }
> public void testPutNullField() throws Exception {
> Map entries = new HashMap<>();
> entries.put(new Organization("1"), new Address(null));
> //entries.put(new Organization("2"), new Address("Some address"));
> IgniteCache cache = jcache(0, "ORG_ADDRESS");
> cache.putAll(entries);
> System.out.println("cache.getConfiguration(CacheConfiguration) = " + 
> cache.getConfiguration(CacheConfiguration.class).getQueryEntities());
> List objects = execSql("SELECT address FROM ORG_ADDRESS.ADDRESS");
> 
> assert ((List)objects.get(0)).get(0) == null;
> }
> protected CacheConfiguration cacheConfiguration(QueryEntity qryEntity) {
> CacheConfiguration cache = defaultCacheConfiguration();
> cache.setCacheMode(CacheMode.PARTITIONED);
> cache.setAtomicityMode(CacheAtomicityMode.ATOMIC);
> cache.setBackups(1);
> cache.setWriteSynchronizationMode(FULL_SYNC);
> cache.setQueryEntities(Collections.singletonList(qryEntity));
> return cache;
> }
> private List execSql(String sql, Object... args) {
> SqlFieldsQuery qry = new SqlFieldsQuery(sql)
> .setArgs(args);
> return grid(0).context().query().querySqlFields(qry, true).getAll();
> }
> private static class Organization implements Serializable {
> private final String name;
> private Organization(String name) { this.name = name; }
> }
> private static class Address implements Serializable {
> private final String address;
> private Address(String address) { this.address = address; }
> }
> }
> {code}



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

[jira] [Updated] (IGNITE-8558) Provide an opportunity to stop grids and cancel tasks after execution all tests

[Maxim Muzafarov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated IGNITE-8558:

Description: 
IGNITE-6842 guarantee us stopping all Ignite instances after test completion by 
default and stopping it without cancelling tasks.

User should have ability to override this behavior and use stopAllGirds(true) 
after all tests execution.

  was:
IGNITE-6842 guarantee us stopping all Ignite instances after test completion by 
default and stopping it without cancelling tasks.

User should have abiliti to override this behavior and use stopAllGirds(true) 
after all tests execution.


> Provide an opportunity to stop grids and cancel tasks after execution all 
> tests
> ---
>
> Key: IGNITE-8558
> URL: https://issues.apache.org/jira/browse/IGNITE-8558
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Minor
> Fix For: 2.6
>
>
> IGNITE-6842 guarantee us stopping all Ignite instances after test completion 
> by default and stopping it without cancelling tasks.
> User should have ability to override this behavior and use stopAllGirds(true) 
> after all tests execution.



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

[jira] [Created] (IGNITE-8558) Provide an opportunity to stop grids and cancel tasks after execution all tests

[Maxim Muzafarov (JIRA)]

Maxim Muzafarov created IGNITE-8558:
---

 Summary: Provide an opportunity to stop grids and cancel tasks 
after execution all tests
 Key: IGNITE-8558
 URL: https://issues.apache.org/jira/browse/IGNITE-8558
 Project: Ignite
  Issue Type: Sub-task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
 Fix For: 2.6


IGNITE-6842 guarantee us stopping all Ignite instances after test completion by 
default and stopping it without cancelling tasks.

User should have abiliti to override this behavior and use stopAllGirds(true) 
after all tests execution.



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

[jira] [Commented] (IGNITE-5979) [Test Failed] GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync

[Dmitriy Pavlov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483782#comment-16483782
 ] 

Dmitriy Pavlov commented on IGNITE-5979:


[~garus.d.g], I've asked [~astelmak] about this ticket, and it is not fix, but 
only monitoring feature. So I've incorrectly understood issue description.

If problem is reproduced, it needs to be fixed, so I hope you could continue 
with this ticket.

> [Test Failed]  
> GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync 
> 
>
> Key: IGNITE-5979
> URL: https://issues.apache.org/jira/browse/IGNITE-5979
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Priority: Major
>  Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.6
>
>
> Example of failing  - 
> http://ci.ignite.apache.org/viewLog.html?buildId=760709=buildResultsDiv=Ignite20Tests_IgniteDataGridFailover#testNameId6248548165747570497
> {noformat}
> junit.framework.AssertionFailedError: Failed to check value for key 
> [key=72625, node=0671e5c8-8bd5-4f2a-b1b8-9e945742, primary=false, 
> recNodeId=101770ef-a622-4f7c-b714-70ecf1f1] expected:<0> but 
> was:<-1994497644>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.TestCase.assertEquals(TestCase.java:244)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.checkRestarts(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:334)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:154)
> {noformat}



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

[jira] [Assigned] (IGNITE-8506) Visor CMD: Show consistent ID in node tables.

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov reassigned IGNITE-8506:
--

Assignee: Vasiliy Sisko  (was: Pavel Konstantinov)

> Visor CMD: Show consistent ID in node tables.
> -
>
> Key: IGNITE-8506
> URL: https://issues.apache.org/jira/browse/IGNITE-8506
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
>Priority: Major
> Attachments: screenshot-1.png
>
>
> Add for topology command.
> Check other command and add on node tables if exist.



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

[jira] [Commented] (IGNITE-8506) Visor CMD: Show consistent ID in node tables.

[Pavel Konstantinov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483778#comment-16483778
 ] 

Pavel Konstantinov commented on IGNITE-8506:


Please add ConsistentID in detailed info of 'node' command.
There is no ConsistentID in result of 'config' command
 !screenshot-1.png! 

> Visor CMD: Show consistent ID in node tables.
> -
>
> Key: IGNITE-8506
> URL: https://issues.apache.org/jira/browse/IGNITE-8506
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Major
> Attachments: screenshot-1.png
>
>
> Add for topology command.
> Check other command and add on node tables if exist.



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

[jira] [Updated] (IGNITE-8506) Visor CMD: Show consistent ID in node tables.

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov updated IGNITE-8506:
---
Attachment: screenshot-1.png

> Visor CMD: Show consistent ID in node tables.
> -
>
> Key: IGNITE-8506
> URL: https://issues.apache.org/jira/browse/IGNITE-8506
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Major
> Attachments: screenshot-1.png
>
>
> Add for topology command.
> Check other command and add on node tables if exist.



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

[jira] [Commented] (IGNITE-8525) Support for IgniteZeroMqStreamer non-multi-part pub-sub

[Igor Seliverstov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483776#comment-16483776
 ] 

Igor Seliverstov commented on IGNITE-8525:
--

[~roman_s], [~dpavlov], looks OK.

> Support for IgniteZeroMqStreamer non-multi-part pub-sub
> ---
>
> Key: IGNITE-8525
> URL: https://issues.apache.org/jira/browse/IGNITE-8525
> Project: Ignite
>  Issue Type: Improvement
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>Priority: Major
> Fix For: 2.6
>
>
> Currently only multi-part pub-sub is supported.



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

[jira] [Commented] (IGNITE-6846) Add metrics for entry processor invocations

[Alexey Kuznetsov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483774#comment-16483774
 ] 

Alexey Kuznetsov commented on IGNITE-6846:
--

[~DmitriyGovorukhin] Hi. Are you going to review the task ?

> Add metrics for entry processor invocations
> ---
>
> Key: IGNITE-6846
> URL: https://issues.apache.org/jira/browse/IGNITE-6846
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Alexey Kuznetsov
>Priority: Critical
>  Labels: iep-6
> Fix For: 2.6
>
>
> {{CacheMetrics}} object has multiple metrics for various cache operations 
> like {{get}}, {{put}} and {{remove}}, but nothing for 
> {{invoke}}/{{EntryProcessor}}. It makes sense to add such metrics, for 
> example:
> * Total number of `invoke` operations executed.
> * Number of `invoke` operations that included updates.
> * Number of read-only `invoke` operations.
> * Min/max/avg execution time.
> * ...



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

[jira] [Assigned] (IGNITE-8183) ZookeeperDiscoverySpiTest#testSegmentation3 fails on TC and locally

[Denis Garus (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Garus reassigned IGNITE-8183:
---

Assignee: Denis Garus

> ZookeeperDiscoverySpiTest#testSegmentation3 fails on TC and locally
> ---
>
> Key: IGNITE-8183
> URL: https://issues.apache.org/jira/browse/IGNITE-8183
> Project: Ignite
>  Issue Type: Bug
>  Components: zookeeper
>Reporter: Sergey Chugunov
>Assignee: Denis Garus
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> Test fails with assertion on awaits on latch:
> {noformat}
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertTrue(Assert.java:31)
> at junit.framework.TestCase.assertTrue(TestCase.java:201)
> at 
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testSegmentation3(ZookeeperDiscoverySpiTest.java:1060)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2080)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1995)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> For some reason SEGMENTATION event is never fired, so assertion on latch 
> fails. Investigation is needed.



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

[jira] [Commented] (IGNITE-8525) Support for IgniteZeroMqStreamer non-multi-part pub-sub

[Dmitriy Pavlov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483770#comment-16483770
 ] 

Dmitriy Pavlov commented on IGNITE-8525:


[~roman_s] thank you, [~gvvinblade] please step in.

> Support for IgniteZeroMqStreamer non-multi-part pub-sub
> ---
>
> Key: IGNITE-8525
> URL: https://issues.apache.org/jira/browse/IGNITE-8525
> Project: Ignite
>  Issue Type: Improvement
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>Priority: Major
> Fix For: 2.6
>
>
> Currently only multi-part pub-sub is supported.



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

[jira] [Created] (IGNITE-8557) Web Console: Webpack add support for SVG images

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-8557:


 Summary: Web Console: Webpack add support for SVG images
 Key: IGNITE-8557
 URL: https://issues.apache.org/jira/browse/IGNITE-8557
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 2.6


In current implementation we forced to store images in special folder and copy 
them via copy plugin. But as we are going towards Angular with components it 
will be better to store images near components (as we do for css).

Lets add such loader to Webpack



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

[jira] [Updated] (IGNITE-4210) CacheLoadingConcurrentGridStartSelfTest.testLoadCacheFromStore() test lose data.

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-4210:
-
Fix Version/s: 2.6

> CacheLoadingConcurrentGridStartSelfTest.testLoadCacheFromStore() test lose 
> data.
> 
>
> Key: IGNITE-4210
> URL: https://issues.apache.org/jira/browse/IGNITE-4210
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Alexey Kuznetsov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> org.apache.ignite.internal.processors.cache.distributed.CacheLoadingConcurrentGridStartSelfTest#testLoadCacheFromStore
>  sometimes have failures.



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

[jira] [Commented] (IGNITE-7776) Check calculated values in javadoc

[Dmitriy Pavlov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483765#comment-16483765
 ] 

Dmitriy Pavlov commented on IGNITE-7776:


Found this one, https://github.com/apache/ignite/pull/3553/, but it contains a 
lot of merge conflicts.

> Check calculated values in javadoc
> --
>
> Key: IGNITE-7776
> URL: https://issues.apache.org/jira/browse/IGNITE-7776
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 2.0, 2.1, 2.2, 2.3
>Reporter: Alexander Belyak
>Assignee: Alexander Belyak
>Priority: Minor
>
> We have two issue with calculated value in javadoc:
> 1) wrong numbers, for example: #\{5 * 1024 * 102 * 1024}
> 2) overflow int type, for example: #\{5 * 1024 * 1024 * 1024}
> Need to check as many places as possible.



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

[jira] [Updated] (IGNITE-8556) Web Console: Improve Webpack DEV mode

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-8556:
-
Fix Version/s: 2.6

> Web Console: Improve Webpack DEV mode
> -
>
> Key: IGNITE-8556
> URL: https://issues.apache.org/jira/browse/IGNITE-8556
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.6
>
>




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

[jira] [Updated] (IGNITE-8556) Web Console: Improve Webpack DEV mode

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-8556:
-
Component/s: wizards

> Web Console: Improve Webpack DEV mode
> -
>
> Key: IGNITE-8556
> URL: https://issues.apache.org/jira/browse/IGNITE-8556
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.6
>
>




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

[jira] [Commented] (IGNITE-5979) [Test Failed] GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync

[Denis Garus (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483750#comment-16483750
 ] 

Denis Garus commented on IGNITE-5979:
-

[~dpavlov], Ok, I stop progress

> [Test Failed]  
> GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync 
> 
>
> Key: IGNITE-5979
> URL: https://issues.apache.org/jira/browse/IGNITE-5979
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Denis Garus
>Priority: Major
>  Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.6
>
>
> Example of failing  - 
> http://ci.ignite.apache.org/viewLog.html?buildId=760709=buildResultsDiv=Ignite20Tests_IgniteDataGridFailover#testNameId6248548165747570497
> {noformat}
> junit.framework.AssertionFailedError: Failed to check value for key 
> [key=72625, node=0671e5c8-8bd5-4f2a-b1b8-9e945742, primary=false, 
> recNodeId=101770ef-a622-4f7c-b714-70ecf1f1] expected:<0> but 
> was:<-1994497644>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.TestCase.assertEquals(TestCase.java:244)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.checkRestarts(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:334)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:154)
> {noformat}



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

[jira] [Assigned] (IGNITE-5979) [Test Failed] GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync

[Denis Garus (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Garus reassigned IGNITE-5979:
---

Assignee: (was: Denis Garus)

> [Test Failed]  
> GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync 
> 
>
> Key: IGNITE-5979
> URL: https://issues.apache.org/jira/browse/IGNITE-5979
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Priority: Major
>  Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.6
>
>
> Example of failing  - 
> http://ci.ignite.apache.org/viewLog.html?buildId=760709=buildResultsDiv=Ignite20Tests_IgniteDataGridFailover#testNameId6248548165747570497
> {noformat}
> junit.framework.AssertionFailedError: Failed to check value for key 
> [key=72625, node=0671e5c8-8bd5-4f2a-b1b8-9e945742, primary=false, 
> recNodeId=101770ef-a622-4f7c-b714-70ecf1f1] expected:<0> but 
> was:<-1994497644>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.TestCase.assertEquals(TestCase.java:244)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.checkRestarts(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:334)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:154)
> {noformat}



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

[jira] [Created] (IGNITE-8556) Web Console: Improve Webpack DEV mode

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-8556:


 Summary: Web Console: Improve Webpack DEV mode
 Key: IGNITE-8556
 URL: https://issues.apache.org/jira/browse/IGNITE-8556
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov






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

[jira] [Commented] (IGNITE-7776) Check calculated values in javadoc

[Dmitriy Pavlov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483744#comment-16483744
 ] 

Dmitriy Pavlov commented on IGNITE-7776:


I remember we had this PR, how can I find it?

> Check calculated values in javadoc
> --
>
> Key: IGNITE-7776
> URL: https://issues.apache.org/jira/browse/IGNITE-7776
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 2.0, 2.1, 2.2, 2.3
>Reporter: Alexander Belyak
>Assignee: Alexander Belyak
>Priority: Minor
>
> We have two issue with calculated value in javadoc:
> 1) wrong numbers, for example: #\{5 * 1024 * 102 * 1024}
> 2) overflow int type, for example: #\{5 * 1024 * 1024 * 1024}
> Need to check as many places as possible.



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

[jira] [Updated] (IGNITE-8530) Exchange hangs during start/stop stress test

[Mikhail Cherkasov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikhail Cherkasov updated IGNITE-8530:
--
Attachment: MyCounterServiceImpl.java
MyCounterService.java

> Exchange hangs during start/stop stress test
> 
>
> Key: IGNITE-8530
> URL: https://issues.apache.org/jira/browse/IGNITE-8530
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.4
>Reporter: Mikhail Cherkasov
>Assignee: Anton Kalashnikov
>Priority: Major
> Attachments: LocalRunner.java, MyCounterService.java, 
> MyCounterServiceImpl.java
>
>
> Please see attached test, it starts N_CORES*2+2 nodes first and after this 
> starts N_CORES*2 threads with while(true) cycle in which closes and starts 
> nodes with small random pause.
> After couple minutes it hangs with Failed to wait for partition map exchange.
>  



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

[jira] [Updated] (IGNITE-8530) Exchange hangs during start/stop stress test

[Mikhail Cherkasov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikhail Cherkasov updated IGNITE-8530:
--
Attachment: (was: Main2.java)

> Exchange hangs during start/stop stress test
> 
>
> Key: IGNITE-8530
> URL: https://issues.apache.org/jira/browse/IGNITE-8530
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.4
>Reporter: Mikhail Cherkasov
>Assignee: Anton Kalashnikov
>Priority: Major
> Attachments: LocalRunner.java, MyCounterService.java, 
> MyCounterServiceImpl.java
>
>
> Please see attached test, it starts N_CORES*2+2 nodes first and after this 
> starts N_CORES*2 threads with while(true) cycle in which closes and starts 
> nodes with small random pause.
> After couple minutes it hangs with Failed to wait for partition map exchange.
>  



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

[jira] [Comment Edited] (IGNITE-8524) Document consistency check utilities

[Alexander Gerus (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482680#comment-16482680
 ] 

Alexander Gerus edited comment on IGNITE-8524 at 5/22/18 9:58 AM:
--

[~ivan.glukos], Hi Ivan, do you have any forecasted date for the task to be 
completed?

Many thanks


was (Author: agerus):
[~ivan.glukos], Hi Ivan, do you have any forecasted date for the task to be 
completed? Our client is waiting for this spec.

Many thanks

> Document consistency check utilities
> 
>
> Key: IGNITE-8524
> URL: https://issues.apache.org/jira/browse/IGNITE-8524
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Ivan Rakov
>Priority: Critical
> Fix For: 2.5
>
>
> Ignite 2.5 will go with special consistency check utilities that, for 
> instance, ensure that the data stays consistent across backups, indexes are 
> correct and many other things. More details can be taken from here:
> * https://issues.apache.org/jira/browse/IGNITE-8277
> * https://issues.apache.org/jira/browse/IGNITE-7467
> Here is an empty page that is created for the documentation: 
> https://apacheignite.readme.io/docs/consistency-check-utilities



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

[jira] [Comment Edited] (IGNITE-8530) Exchange hangs during start/stop stress test

[Alexander Gerus (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482566#comment-16482566
 ] 

Alexander Gerus edited comment on IGNITE-8530 at 5/22/18 9:55 AM:
--

[~akalashnikov] Can you please help with analysis for the issue. 


was (Author: agerus):
[~akalashnikov] Can you please help with analysis for the issue. It is really 
critical for multiple clients

> Exchange hangs during start/stop stress test
> 
>
> Key: IGNITE-8530
> URL: https://issues.apache.org/jira/browse/IGNITE-8530
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.4
>Reporter: Mikhail Cherkasov
>Assignee: Anton Kalashnikov
>Priority: Major
> Attachments: LocalRunner.java, Main2.java
>
>
> Please see attached test, it starts N_CORES*2+2 nodes first and after this 
> starts N_CORES*2 threads with while(true) cycle in which closes and starts 
> nodes with small random pause.
> After couple minutes it hangs with Failed to wait for partition map exchange.
>  



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

[jira] [Commented] (IGNITE-8525) Support for IgniteZeroMqStreamer non-multi-part pub-sub

[Roman Shtykh (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483733#comment-16483733
 ] 

Roman Shtykh commented on IGNITE-8525:
--

This change doesn't affect anything but this specific streamer, I don't think 
Run-All is needed ;)

> Support for IgniteZeroMqStreamer non-multi-part pub-sub
> ---
>
> Key: IGNITE-8525
> URL: https://issues.apache.org/jira/browse/IGNITE-8525
> Project: Ignite
>  Issue Type: Improvement
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>Priority: Major
> Fix For: 2.6
>
>
> Currently only multi-part pub-sub is supported.



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

[jira] [Commented] (IGNITE-8491) Add JMX flag: Is the node in baseline or not?

[Ivan Rakov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483730#comment-16483730
 ] 

Ivan Rakov commented on IGNITE-8491:


Fixed.
*For anyone who needs to cherry-pick this ticket:* please note that there are 
*two commits*.
1. f8ae30d5dd426d995d7bae98674712055895bcb5 - original fix
2. e227f22adb99767f8f4e7b2be024cab5c9a82c30 - license header fix

> Add JMX flag: Is the node in baseline or not?
> -
>
> Key: IGNITE-8491
> URL: https://issues.apache.org/jira/browse/IGNITE-8491
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Assignee: Vladislav Pyatkov
>Priority: Major
> Fix For: 2.6
>
>
> Need to add a baseline flag on JMX.
> {code}
> public interface IgniteMXBean {
> /**
>  * Gets a flag is node in baseline.
>  *
>  * @return Return a baseline flag.
>  */
> @MXBeanDescription("Baseline node flag.")
> public boolean isNodeInBaseline();
> {code}



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

[jira] [Commented] (IGNITE-8491) Add JMX flag: Is the node in baseline or not?

[Dmitriy Pavlov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483725#comment-16483725
 ] 

Dmitriy Pavlov commented on IGNITE-8491:


[~ivan.glukos], License & Headers validation failed
https://ci.ignite.apache.org/viewLog.html?buildId=1311610=IgniteTests24Java8_LicensesHeaders=artifacts#!w3qd1wo,-5anhed3tul3b,1lt68ikb36szd

Unapproved licenses:
 core/src/test/java/org/apache/ignite/util/mbeans/GridMBeanBaselineTest.java

Please address

> Add JMX flag: Is the node in baseline or not?
> -
>
> Key: IGNITE-8491
> URL: https://issues.apache.org/jira/browse/IGNITE-8491
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Assignee: Vladislav Pyatkov
>Priority: Major
> Fix For: 2.6
>
>
> Need to add a baseline flag on JMX.
> {code}
> public interface IgniteMXBean {
> /**
>  * Gets a flag is node in baseline.
>  *
>  * @return Return a baseline flag.
>  */
> @MXBeanDescription("Baseline node flag.")
> public boolean isNodeInBaseline();
> {code}



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

[jira] [Commented] (IGNITE-5979) [Test Failed] GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync

[Dmitriy Pavlov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483718#comment-16483718
 ] 

Dmitriy Pavlov commented on IGNITE-5979:


[~garus.d.g] IMO we should wait [IGNITE-7833] fix and re-check test failure 
after fix, we can't be sure that under [IGNITE-7833] all cases would be fixed.

> [Test Failed]  
> GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync 
> 
>
> Key: IGNITE-5979
> URL: https://issues.apache.org/jira/browse/IGNITE-5979
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Denis Garus
>Priority: Major
>  Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.6
>
>
> Example of failing  - 
> http://ci.ignite.apache.org/viewLog.html?buildId=760709=buildResultsDiv=Ignite20Tests_IgniteDataGridFailover#testNameId6248548165747570497
> {noformat}
> junit.framework.AssertionFailedError: Failed to check value for key 
> [key=72625, node=0671e5c8-8bd5-4f2a-b1b8-9e945742, primary=false, 
> recNodeId=101770ef-a622-4f7c-b714-70ecf1f1] expected:<0> but 
> was:<-1994497644>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.TestCase.assertEquals(TestCase.java:244)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.checkRestarts(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:334)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:154)
> {noformat}



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

[jira] [Commented] (IGNITE-6538) Ignite Activate/Deactivate Cluster suite: After tests validation improvements test became flaky on TC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483715#comment-16483715
 ] 

ASF GitHub Bot commented on IGNITE-6538:


GitHub user Mmuzaf opened a pull request:

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

IGNITE-6538: run 200 times



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

$ git pull https://github.com/Mmuzaf/ignite ignite-6538

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

https://github.com/apache/ignite/pull/4044.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 #4044


commit d37470c7a4c76e11aca60adc06d9ff4a4584aa28
Author: Maxim Muzafarov 
Date:   2018-04-22T14:00:01Z

IGNITE-6538: run 200 times




> Ignite Activate/Deactivate Cluster suite: After tests validation improvements 
> test became flaky on TC
> -
>
> Key: IGNITE-6538
> URL: https://issues.apache.org/jira/browse/IGNITE-6538
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Maxim Muzafarov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.6
>
>
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-238119157387028099=testDetails_Ignite20Tests=%3Cdefault%3E
> recent changes from [IGNITE-6124] which probably showed this problem is 
> following 
> {noformat}
>  fail("Activation should fail");
> {noformat}
> org.apache.ignite.internal.processors.cache.persistence.standbycluster.IgniteChangeGlobalStateTest#testActivateAfterFailGetLock
> Locally fail can be also reproduced, 6 from 20 failures.



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

[jira] [Updated] (IGNITE-8555) Web console - Admin panel: the users table is partially empty on first open

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov updated IGNITE-8555:
---
Summary: Web console - Admin panel: the users table is partially empty on 
first open  (was: Web console - Admin panel: the users table is partially empty)

> Web console - Admin panel: the users table is partially empty on first open
> ---
>
> Key: IGNITE-8555
> URL: https://issues.apache.org/jira/browse/IGNITE-8555
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Attachments: image-2018-05-22-16-27-52-342.png
>
>
>  !image-2018-05-22-16-27-52-342.png! 



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

[jira] [Created] (IGNITE-8555) Web console - Admin panel: the users table is partially empty

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-8555:
--

 Summary: Web console - Admin panel: the users table is partially 
empty
 Key: IGNITE-8555
 URL: https://issues.apache.org/jira/browse/IGNITE-8555
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov
Assignee: Alexey Kuznetsov
 Attachments: image-2018-05-22-16-27-52-342.png

 !image-2018-05-22-16-27-52-342.png! 



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

[jira] [Commented] (IGNITE-6538) Ignite Activate/Deactivate Cluster suite: After tests validation improvements test became flaky on TC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483708#comment-16483708
 ] 

ASF GitHub Bot commented on IGNITE-6538:


Github user Mmuzaf closed the pull request at:

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


> Ignite Activate/Deactivate Cluster suite: After tests validation improvements 
> test became flaky on TC
> -
>
> Key: IGNITE-6538
> URL: https://issues.apache.org/jira/browse/IGNITE-6538
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Maxim Muzafarov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.6
>
>
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-238119157387028099=testDetails_Ignite20Tests=%3Cdefault%3E
> recent changes from [IGNITE-6124] which probably showed this problem is 
> following 
> {noformat}
>  fail("Activation should fail");
> {noformat}
> org.apache.ignite.internal.processors.cache.persistence.standbycluster.IgniteChangeGlobalStateTest#testActivateAfterFailGetLock
> Locally fail can be also reproduced, 6 from 20 failures.



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

[jira] [Commented] (IGNITE-2313) Need to add a mode to fail atomic operations within a transaction

[Anton Vinogradov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483699#comment-16483699
 ] 

Anton Vinogradov commented on IGNITE-2313:
--

[~SomeFire]

Looks good to me, 

but we have to pass one more final review (I'm not an expert at this code). 

 

[~dpavlov],

Could you please suggest reviewer?

> Need to add a mode to fail atomic operations within a transaction
> -
>
> Key: IGNITE-2313
> URL: https://issues.apache.org/jira/browse/IGNITE-2313
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Dmitriy Setrakyan
>Assignee: Ryabov Dmitrii
>Priority: Major
> Fix For: 2.6
>
>
> Currently atomic operations within a transaction succeed without alarming a 
> user that no transaction really occurs. We should add a mode to fail such 
> operations (such mode should be turned off by default).
> New transaction configuration flag (default is {{false}}):
> {code}TransactionConfiguration.isAllowAtomicUpdatesInTransaction(){code}
> If the flag is violated, we should throw an exception with the following 
> error message: {{Transaction spans operations on atomic cache (consider 
> setting TransactionConfiguration.isAllowAttomicUpdatesInTransaction() flag to 
> true)}}



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

[jira] [Assigned] (IGNITE-8554) Cache metrics: expose metrics with rebalance info about keys

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov reassigned IGNITE-8554:


Assignee: Vasiliy Sisko  (was: Alexey Kuznetsov)

Please implement.

> Cache metrics: expose metrics with rebalance info about keys
> 
>
> Key: IGNITE-8554
> URL: https://issues.apache.org/jira/browse/IGNITE-8554
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Kuznetsov
>Assignee: Vasiliy Sisko
>Priority: Major
>
> In order to show info about rebalance progress we need to expose 
> estimatedRebalancingKeys and rebalancedKeys metrics.



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

[jira] [Created] (IGNITE-8554) Cache metrics: expose metrics with rebalance info about keys

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-8554:


 Summary: Cache metrics: expose metrics with rebalance info about 
keys
 Key: IGNITE-8554
 URL: https://issues.apache.org/jira/browse/IGNITE-8554
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov


In order to show info about rebalance progress we need to expose 
estimatedRebalancingKeys and rebalancedKeys metrics.



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

[jira] [Created] (IGNITE-8553) Web Console: Double click on table column border make it super wide

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-8553:


 Summary: Web Console: Double click on table column border make it 
super wide
 Key: IGNITE-8553
 URL: https://issues.apache.org/jira/browse/IGNITE-8553
 Project: Ignite
  Issue Type: Improvement
  Components: wizards
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 2.6


Point mouse between two columns and do a double click.
Column become super wide.
If this a first "pined" column - no scroll will be available.



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

[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity

[ekaterina.vergizova (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483675#comment-16483675
 ] 

ekaterina.vergizova commented on IGNITE-8463:
-

Thanks, we are working on other tests.

123456 is just a keyStore/trustStore password.
ignite/ignite is default username/password for IgniteConfiguration with enabled 
authentication and they should be used for activation.

> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
>  Issue Type: Sub-task
>  Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We 
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any 
> recent version). 2) Suite should be able to run Jasmine tests [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 from Jasmine. Raw 
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/



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

[jira] [Created] (IGNITE-8552) Unable to use date as primary key

[Pavel Vinokurov (JIRA)]

Pavel Vinokurov created IGNITE-8552:
---

 Summary: Unable to use date as primary key
 Key: IGNITE-8552
 URL: https://issues.apache.org/jira/browse/IGNITE-8552
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.4
Reporter: Pavel Vinokurov


It' is unable to create cache via ddl:
create table tab(id date primary key, date_field date);

Result:
ERROR CacheAffinitySharedManager - Failed to initialize cache. Will try to 
rollback cache start routine. [cacheName=SQL_PUBLIC_T3]
class org.apache.ignite.IgniteCheckedException: Failed to find value class in 
the node classpath (use default marshaller to enable binary objects) : 
SQL_PUBLIC_T3_e90848b2_fe30_4adb_a934_6e13ca0eb409
at 
org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:426)




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

[jira] [Updated] (IGNITE-8551) Web console - User profile page: do not disable the 'Save Changes' button

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov updated IGNITE-8551:
---
Summary: Web console - User profile page: do not disable the 'Save Changes' 
button  (was: Web console - User profile: do not disable the 'Save Changes' 
button)

> Web console - User profile page: do not disable the 'Save Changes' button
> -
>
> Key: IGNITE-8551
> URL: https://issues.apache.org/jira/browse/IGNITE-8551
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Major
>
> Currently, we disable the Save Changes button in case of an invalid field.
> It will be better make the button always enabled and show an error message.



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

[jira] [Updated] (IGNITE-8551) Web console - User profile: do not disable the 'Save Changes' button

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov updated IGNITE-8551:
---
Summary: Web console - User profile: do not disable the 'Save Changes' 
button  (was: Web console - User -profile: do not disable the 'Save Changes' 
button)

> Web console - User profile: do not disable the 'Save Changes' button
> 
>
> Key: IGNITE-8551
> URL: https://issues.apache.org/jira/browse/IGNITE-8551
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Major
>
> Currently, we disable the Save Changes button in case of an invalid field.
> It will be better make the button always enabled and show an error message.



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

[jira] [Created] (IGNITE-8551) Web console - User -profile: do not disable the 'Save Changes' button

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-8551:
--

 Summary: Web console - User -profile: do not disable the 'Save 
Changes' button
 Key: IGNITE-8551
 URL: https://issues.apache.org/jira/browse/IGNITE-8551
 Project: Ignite
  Issue Type: Improvement
Reporter: Pavel Konstantinov
Assignee: Alexey Kuznetsov


Currently, we disable the Save Changes button in case of an invalid field.
It will be better make the button always enabled and show an error message.



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

[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity

[Peter Ivanov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483666#comment-16483666
 ] 

Peter Ivanov commented on IGNITE-8463:
--

Fixed TLS test, others are still failing: 
https://ci.ignite.apache.org/viewLog.html?buildId=1320110

> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
>  Issue Type: Sub-task
>  Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We 
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any 
> recent version). 2) Suite should be able to run Jasmine tests [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 from Jasmine. Raw 
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/



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

[jira] [Resolved] (IGNITE-8463) Node.js: setup TeamCity

[Peter Ivanov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Ivanov resolved IGNITE-8463.
--
Resolution: Fixed

> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
>  Issue Type: Sub-task
>  Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We 
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any 
> recent version). 2) Suite should be able to run Jasmine tests [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 from Jasmine. Raw 
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/



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

[jira] [Comment Edited] (IGNITE-7524) JDBC: Add a note about connection non-thread safety to docs

[Taras Ledkov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483651#comment-16483651
 ] 

Taras Ledkov edited comment on IGNITE-7524 at 5/22/18 8:37 AM:
---

[~dmagda], please take a look.

Adds warning block to [JDBC drived doc 
|https://dash.readme.io/project/apacheignite-sql/v2.4/docs/jdbc-driver_25_hidden].
Callout block title: *JDBC thin driver is not thread safe*


was (Author: tledkov-gridgain):
Add warning block to [JDBC drived doc 
|https://dash.readme.io/project/apacheignite-sql/v2.4/docs/jdbc-driver_25_hidden].
Callout block title: *JDBC thin driver is not thread safe*

> JDBC: Add a note about connection non-thread safety to docs
> ---
>
> Key: IGNITE-7524
> URL: https://issues.apache.org/jira/browse/IGNITE-7524
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.6
>
>
> Our JDBC connection is not thread safe. Let's mention it in docs.



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

[jira] [Commented] (IGNITE-7823) Separate cache for non collocated IgniteSet.

[Pavel Pereslegin (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483636#comment-16483636
 ] 

Pavel Pereslegin commented on IGNITE-7823:
--

Implementation details:
- DataStructuresProcessor#compatibleCache creates separate cache for each new 
non-collocated version of IgniteSet (method IgniteSet#close destroys this 
cache).
- A new version of IgniteSet called GrideCacheSetImplV2 was created, common 
internal service methods required by proxy extracted to separate interface 
called IgniteInternalSet.
- A new header GrideCacheSetHeaderV2 was created (also was added common header 
interface called CacheSetHeader).
- Duplicate code GridCacheSetImpl and GrieCacheSetHeader should be removed in 
next major release.

> Separate cache for non collocated IgniteSet.
> 
>
> Key: IGNITE-7823
> URL: https://issues.apache.org/jira/browse/IGNITE-7823
> Project: Ignite
>  Issue Type: New Feature
>  Components: data structures
>Reporter: Andrey Kuznetsov
>Assignee: Pavel Pereslegin
>Priority: Major
> Fix For: 2.6
>
>
> Currently, single data structures cache is shared between several collection 
> instances (IgniteQueue, IgniteSet).
> To support iterator() and size() IgniteSet maintains plain on-heap Java sets 
> on every node (see CacheDataStructuresManager.setDataMap). These sets 
> duplicate backing-cache entries, both primary and backup. For big 
> non-collocated sets it's too expensive to maintain redundant onheap data 
> copies. The simplest way to avoid copies is to use separate cache for 
> non-collocated IgniteSet version; hence size of set is the same as size of 
> backing cache, and also set iterator is virtually the same as backing cache 
> iterator. 
> The difference between exising set implementation and set based on separate 
> cache should be properly documented afterwards.



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