[jira] [Updated] (IGNITE-7767) Update WALMode configuration in .NET

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-7767:
---
Component/s: platforms

> Update WALMode configuration in .NET
> 
>
> Key: IGNITE-7767
> URL: https://issues.apache.org/jira/browse/IGNITE-7767
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>Priority: Major
>  Labels: .NET, MakeTeamcityGreenAgain
> Fix For: 2.4
>
>
> In https://issues.apache.org/jira/browse/IGNITE-7594 we changed values for 
> WALMode enum, but .NET code wasn't modified accordingly.



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

[jira] [Updated] (IGNITE-7767) Update WALMode configuration in .NET

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-7767:
---
Affects Version/s: 2.4

> Update WALMode configuration in .NET
> 
>
> Key: IGNITE-7767
> URL: https://issues.apache.org/jira/browse/IGNITE-7767
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>Priority: Major
>  Labels: .NET, MakeTeamcityGreenAgain
> Fix For: 2.4
>
>
> In https://issues.apache.org/jira/browse/IGNITE-7594 we changed values for 
> WALMode enum, but .NET code wasn't modified accordingly.



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

[jira] [Updated] (IGNITE-7767) .NET: Update WALMode configuration

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-7767:
---
Summary: .NET: Update WALMode configuration  (was: Update WALMode 
configuration in .NET)

> .NET: Update WALMode configuration
> --
>
> Key: IGNITE-7767
> URL: https://issues.apache.org/jira/browse/IGNITE-7767
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>Priority: Major
>  Labels: .NET, MakeTeamcityGreenAgain
> Fix For: 2.4
>
>
> In https://issues.apache.org/jira/browse/IGNITE-7594 we changed values for 
> WALMode enum, but .NET code wasn't modified accordingly.



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

[jira] [Updated] (IGNITE-7767) Update WALMode configuration in .NET

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-7767:
---
Labels: .NET MakeTeamcityGreenAgain  (was: MakeTeamcityGreenAgain)

> Update WALMode configuration in .NET
> 
>
> Key: IGNITE-7767
> URL: https://issues.apache.org/jira/browse/IGNITE-7767
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>Priority: Major
>  Labels: .NET, MakeTeamcityGreenAgain
> Fix For: 2.4
>
>
> In https://issues.apache.org/jira/browse/IGNITE-7594 we changed values for 
> WALMode enum, but .NET code wasn't modified accordingly.



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

[jira] [Updated] (IGNITE-7767) Update WALMode configuration in .NET

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-7767:
---
Fix Version/s: 2.4

> Update WALMode configuration in .NET
> 
>
> Key: IGNITE-7767
> URL: https://issues.apache.org/jira/browse/IGNITE-7767
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.4
>
>
> In https://issues.apache.org/jira/browse/IGNITE-7594 we changed values for 
> WALMode enum, but .NET code wasn't modified accordingly.



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

[jira] [Comment Edited] (IGNITE-7767) Update WALMode configuration in .NET

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-7767 at 2/21/18 7:18 AM:
-

Thanks [~ilantukh].

Merged to master: {{0fd5631cad2e3c4269aefae341f77a835d215182}}.
Cherry-picked to ignite-2.4: {{c82b4bfe9e77852b69784077e8ac47d8425a2b82}}


was (Author: ptupitsyn):
Thanks [~ilantukh], merged to master: 
{{0fd5631cad2e3c4269aefae341f77a835d215182}}.

> Update WALMode configuration in .NET
> 
>
> Key: IGNITE-7767
> URL: https://issues.apache.org/jira/browse/IGNITE-7767
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.4
>
>
> In https://issues.apache.org/jira/browse/IGNITE-7594 we changed values for 
> WALMode enum, but .NET code wasn't modified accordingly.



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

[jira] [Updated] (IGNITE-7688) DDL does not work properly on sql queries.

[Muratcan TUKSAL (JIRA)]

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

Muratcan TUKSAL updated IGNITE-7688:

Summary: DDL does not work properly on sql queries.  (was: DDL does not 
working properly on sql queries.)

> DDL does not work properly on sql queries.
> --
>
> Key: IGNITE-7688
> URL: https://issues.apache.org/jira/browse/IGNITE-7688
> Project: Ignite
>  Issue Type: Bug
>  Components: 2.3
>Affects Versions: 2.3
> Environment: we have 5 node running on Ubuntu 16.04(VM). we 
> donwloaded binary dist. from download page. 
>Reporter: Muratcan TUKSAL
>Priority: Critical
>  Labels: persistant, persistence, persistence.xml
> Fix For: 2.5
>
> Attachments: buggy-config.xml
>
>
> * start ignite cluster persistent enabled mode (tried on 5 node)
>  * activate cluster via ignitevisor
>  * Create a table through jdbc 
>  * kill all nodes
>  * start all nodes again
>  * activate cluster via ignitevisor
>  * drop that specific table
>  * deactivate cluster(doesnt matter via top -deactivate or kill all nodes)
>  * activate cluster
>  * dropped table still there with no data



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

[jira] [Commented] (IGNITE-7767) Update WALMode configuration in .NET

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-7767:


Thanks [~ilantukh], merged to master: 
{{0fd5631cad2e3c4269aefae341f77a835d215182}}.

> Update WALMode configuration in .NET
> 
>
> Key: IGNITE-7767
> URL: https://issues.apache.org/jira/browse/IGNITE-7767
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> In https://issues.apache.org/jira/browse/IGNITE-7594 we changed values for 
> WALMode enum, but .NET code wasn't modified accordingly.



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

[jira] [Closed] (IGNITE-7320) Multilevel header in admin panel looks wierd in Safari and Edge

[Andrey Novikov (JIRA)]

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

Andrey Novikov closed IGNITE-7320.
--

> Multilevel header in admin panel looks wierd in Safari and Edge
> ---
>
> Key: IGNITE-7320
> URL: https://issues.apache.org/jira/browse/IGNITE-7320
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Andrey Novikov
>Priority: Minor
> Attachments: Lk1YqS (1).jpg
>
>




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

[jira] [Commented] (IGNITE-7320) Multilevel header in admin panel looks wierd in Safari and Edge

[Andrey Novikov (JIRA)]

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

Andrey Novikov commented on IGNITE-7320:


Tested. Merged to master.

> Multilevel header in admin panel looks wierd in Safari and Edge
> ---
>
> Key: IGNITE-7320
> URL: https://issues.apache.org/jira/browse/IGNITE-7320
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Andrey Novikov
>Priority: Minor
> Attachments: Lk1YqS (1).jpg
>
>




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

[jira] [Assigned] (IGNITE-7320) Multilevel header in admin panel looks wierd in Safari and Edge

[Andrey Novikov (JIRA)]

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

Andrey Novikov reassigned IGNITE-7320:
--

Assignee: Andrey Novikov  (was: Pavel Konstantinov)

> Multilevel header in admin panel looks wierd in Safari and Edge
> ---
>
> Key: IGNITE-7320
> URL: https://issues.apache.org/jira/browse/IGNITE-7320
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Andrey Novikov
>Priority: Minor
> Attachments: Lk1YqS (1).jpg
>
>




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

[jira] [Updated] (IGNITE-7773) Add getRebalanceClearingPartitionsLeft JMX metric to .NET

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-7773:
---
Labels: .NET  (was: )

> Add getRebalanceClearingPartitionsLeft JMX metric to .NET
> -
>
> Key: IGNITE-7773
> URL: https://issues.apache.org/jira/browse/IGNITE-7773
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Pavel Kovalenko
>Priority: Major
>  Labels: .NET
> Fix For: 2.5
>
>
> New metric is introduced in IGNITE-6113 .



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

[jira] [Updated] (IGNITE-7773) .NET: Add getRebalanceClearingPartitionsLeft JMX metric

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-7773:
---
Summary: .NET: Add getRebalanceClearingPartitionsLeft JMX metric  (was: Add 
getRebalanceClearingPartitionsLeft JMX metric to .NET)

> .NET: Add getRebalanceClearingPartitionsLeft JMX metric
> ---
>
> Key: IGNITE-7773
> URL: https://issues.apache.org/jira/browse/IGNITE-7773
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Pavel Kovalenko
>Priority: Major
>  Labels: .NET
> Fix For: 2.5
>
>
> New metric is introduced in IGNITE-6113 .



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

[jira] [Updated] (IGNITE-6094) Web console: Implement persistent store in demo mode.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-6094:
-
Fix Version/s: 2.5

> Web console: Implement persistent store in demo mode.
> -
>
> Key: IGNITE-6094
> URL: https://issues.apache.org/jira/browse/IGNITE-6094
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 2.5
>
>




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

[jira] [Assigned] (IGNITE-6094) Web console: Implement persistent store in demo mode.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-6094:


Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

Merged to master.

> Web console: Implement persistent store in demo mode.
> -
>
> Key: IGNITE-6094
> URL: https://issues.apache.org/jira/browse/IGNITE-6094
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.5
>
>




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

[jira] [Commented] (IGNITE-7729) Add usage of Roles for Web Console E2E tests

[Alexander Kalinin (JIRA)]

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

Alexander Kalinin commented on IGNITE-7729:
---

[~anovikov] Please review

> Add usage of Roles for Web Console E2E tests
> 
>
> Key: IGNITE-7729
> URL: https://issues.apache.org/jira/browse/IGNITE-7729
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Andrey Novikov
>Priority: Major
>




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

[jira] [Assigned] (IGNITE-7729) Add usage of Roles for Web Console E2E tests

[Alexander Kalinin (JIRA)]

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

Alexander Kalinin reassigned IGNITE-7729:
-

Assignee: Andrey Novikov  (was: Ilya Borisov)

> Add usage of Roles for Web Console E2E tests
> 
>
> Key: IGNITE-7729
> URL: https://issues.apache.org/jira/browse/IGNITE-7729
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Andrey Novikov
>Priority: Major
>




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

[jira] [Commented] (IGNITE-7660) Refactor LSQR algorithm

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7660:


GitHub user Andy92 opened a pull request:

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

IGNITE-7660: Refactor LSQR algorithm

Refactor for the issue ignite-7660.

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

$ git pull https://github.com/Andy92/ignite master

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

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


commit 8fee202a0594416e8975919f49de19e8fc68b5bd
Author: Andy 
Date:   2018-02-20T23:49:50Z

IGNITE-7660: Refactor LSQR algorithm




> Refactor LSQR algorithm
> ---
>
> Key: IGNITE-7660
> URL: https://issues.apache.org/jira/browse/IGNITE-7660
> Project: Ignite
>  Issue Type: Improvement
>  Components: ml
>Reporter: Anton Dmitriev
>Priority: Minor
>
> This issues is the nest step of the IGNITE-7438 task.
> In the IGNITE-7438 the AbstractLSQR implementation has been copied from the 
> SciPy implementation which has been copies from another old implementation. 
> As result the code in the 
> [AbstractLSQR|https://github.com/apache/ignite/blob/master/modules/ml/src/main/java/org/apache/ignite/ml/math/isolve/lsqr/AbstractLSQR.java]
>  looks a bit weird. All variables have meaningless names and the whole 
> algorithm written as the one method.
> The goal of this task is to refactor the LSQR code and:
>  * Make variable names more meaningful.
>  * Add comments to the variables and result (see 
> [LSQRResult|https://github.com/apache/ignite/blob/master/modules/ml/src/main/java/org/apache/ignite/ml/math/isolve/lsqr/LSQRResult.java]).
>  * Move parts of the algorithm into separate methods where it's appropriate.



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

[jira] [Commented] (IGNITE-7193) IgniteReflectionFactory does not handle primitive data types.

[Vyacheslav Koptilin (JIRA)]

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

Vyacheslav Koptilin commented on IGNITE-7193:
-

Hi [~dpavlov],
Thanks for the review. I really appreciate it.
I fixed all your comments/findings. TC looks good to me.

> IgniteReflectionFactory does not handle primitive data types.
> -
>
> Key: IGNITE-7193
> URL: https://issues.apache.org/jira/browse/IGNITE-7193
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.1
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Minor
> Fix For: 2.5
>
>
> {code:java}
> public class TestClass {
> public static final int INITIAL_VALUE = 12;
> public static final int UPDATED_VALUE = 42;
> private int field = INITIAL_VALUE;
> public void setField(int value) {
> this.field = value;
> }
> public int getField() {
> return this.field;
> }
> public static void main(String[] args) {
> Map props = new HashMap<>();
> props.put("field", UPDATED_VALUE);
> IgniteReflectionFactory factory = new 
> IgniteReflectionFactory<>(ExampleNodeStartup.TestClass.class);
> factory.setProperties(props);
> assertEquals(UPDATED_VALUE, factory.create().getField());
> }
> }
> {code}



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

[jira] [Commented] (IGNITE-7769) Persistence Problem

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-7769:
-

If you're experiencing difficulties when using Ignite, it's better to post a 
question on user list or StackOverflow: 
[https://ignite.apache.org/community/resources.html#ask]. Also please provide 
more details about the problem, it's really hard to tell anything having only 
the description you provided here.

Jira should be used only for bugs, improvements or features that have clear 
description, scope, etc. Closing this ticket.

> Persistence Problem
> ---
>
> Key: IGNITE-7769
> URL: https://issues.apache.org/jira/browse/IGNITE-7769
> Project: Ignite
>  Issue Type: Bug
>  Components: binary, persistence
>Affects Versions: 2.3
> Environment: *Summary:*
> *+-+*
> *| Active | true |*
> *| Total hosts | 5 |*
> *| Total nodes | 5 |*
> *| Total CPUs | 10 |*
> *| Avg. CPU load | 6.17 % |*
> *| Avg. free heap | 81.00 % |*
> *| Avg. Up time | 00:03:57 |*
> *| Snapshot time | 02/20/18, 16:36:01 |*
> *+-+*
>Reporter: Caner Önder
>Priority: Critical
>  Labels: usability
> Attachments: example-persistent-store.xml
>
>
> Hİ, i have persistency problem with the conf file which i already attached.
> When i reboot the cluster and activate it again, i lose data on every reboot 
> and also the old tables which i deleted before, appears again.
>  



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

[jira] [Closed] (IGNITE-7769) Persistence Problem

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko closed IGNITE-7769.
---

> Persistence Problem
> ---
>
> Key: IGNITE-7769
> URL: https://issues.apache.org/jira/browse/IGNITE-7769
> Project: Ignite
>  Issue Type: Bug
>  Components: binary, persistence
>Affects Versions: 2.3
> Environment: *Summary:*
> *+-+*
> *| Active | true |*
> *| Total hosts | 5 |*
> *| Total nodes | 5 |*
> *| Total CPUs | 10 |*
> *| Avg. CPU load | 6.17 % |*
> *| Avg. free heap | 81.00 % |*
> *| Avg. Up time | 00:03:57 |*
> *| Snapshot time | 02/20/18, 16:36:01 |*
> *+-+*
>Reporter: Caner Önder
>Priority: Critical
>  Labels: usability
> Attachments: example-persistent-store.xml
>
>
> Hİ, i have persistency problem with the conf file which i already attached.
> When i reboot the cluster and activate it again, i lose data on every reboot 
> and also the old tables which i deleted before, appears again.
>  



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

[jira] [Resolved] (IGNITE-7769) Persistence Problem

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko resolved IGNITE-7769.
-
Resolution: Not A Problem

> Persistence Problem
> ---
>
> Key: IGNITE-7769
> URL: https://issues.apache.org/jira/browse/IGNITE-7769
> Project: Ignite
>  Issue Type: Bug
>  Components: binary, persistence
>Affects Versions: 2.3
> Environment: *Summary:*
> *+-+*
> *| Active | true |*
> *| Total hosts | 5 |*
> *| Total nodes | 5 |*
> *| Total CPUs | 10 |*
> *| Avg. CPU load | 6.17 % |*
> *| Avg. free heap | 81.00 % |*
> *| Avg. Up time | 00:03:57 |*
> *| Snapshot time | 02/20/18, 16:36:01 |*
> *+-+*
>Reporter: Caner Önder
>Priority: Critical
>  Labels: usability
> Attachments: example-persistent-store.xml
>
>
> Hİ, i have persistency problem with the conf file which i already attached.
> When i reboot the cluster and activate it again, i lose data on every reboot 
> and also the old tables which i deleted before, appears again.
>  



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

[jira] [Updated] (IGNITE-4575) Implement in Ignite wrapper for enums based on H2 user value type

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-4575:

Fix Version/s: 2.5

> Implement in Ignite wrapper for enums based on H2 user value type
> -
>
> Key: IGNITE-4575
> URL: https://issues.apache.org/jira/browse/IGNITE-4575
> Project: Ignite
>  Issue Type: New Feature
>  Components: sql
>Reporter: Alexander Paschenko
>Assignee: Sergey Kalashnikov
>Priority: Major
> Fix For: 2.5
>
>




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

[jira] [Commented] (IGNITE-4575) Implement in Ignite wrapper for enums based on H2 user value type

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-4575:
-

Are there any plans to finalize this ticket and provide proper enum support in 
SQL? Also how will it look like from API point of view? Should we add 'ENUM' 
SQL type similar to other databases? For example: 
https://dev.mysql.com/doc/refman/5.7/en/enum.html

> Implement in Ignite wrapper for enums based on H2 user value type
> -
>
> Key: IGNITE-4575
> URL: https://issues.apache.org/jira/browse/IGNITE-4575
> Project: Ignite
>  Issue Type: New Feature
>  Components: sql
>Reporter: Alexander Paschenko
>Assignee: Sergey Kalashnikov
>Priority: Major
> Fix For: 2.5
>
>




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

[jira] [Comment Edited] (IGNITE-7767) Update WALMode configuration in .NET

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh edited comment on IGNITE-7767 at 2/20/18 9:43 PM:
---

As far as I understand, those failures happened because now there are no FSYNCs 
with default settings, and so WalFsyncTimeAverage == 0. I've added fix to my PR.


was (Author: ilantukh):
As far as I understand, those failures happened because now there are no FSYNCs 
with default settings, and so WalFsyncTimeAverage == 0. I added fix to my PR.

> Update WALMode configuration in .NET
> 
>
> Key: IGNITE-7767
> URL: https://issues.apache.org/jira/browse/IGNITE-7767
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> In https://issues.apache.org/jira/browse/IGNITE-7594 we changed values for 
> WALMode enum, but .NET code wasn't modified accordingly.



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

[jira] [Commented] (IGNITE-7767) Update WALMode configuration in .NET

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh commented on IGNITE-7767:
--

As far as I understand, those failures happened because now there are no FSYNCs 
with default settings, and so WalFsyncTimeAverage == 0. I added fix to my PR.

> Update WALMode configuration in .NET
> 
>
> Key: IGNITE-7767
> URL: https://issues.apache.org/jira/browse/IGNITE-7767
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> In https://issues.apache.org/jira/browse/IGNITE-7594 we changed values for 
> WALMode enum, but .NET code wasn't modified accordingly.



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

[jira] [Assigned] (IGNITE-7758) Update REST documentation

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-7758:
---

Assignee: Prachi Garg  (was: Denis Magda)

> Update REST documentation
> -
>
> Key: IGNITE-7758
> URL: https://issues.apache.org/jira/browse/IGNITE-7758
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Affects Versions: 2.5
>Reporter: Alexey Kuznetsov
>Assignee: Prachi Garg
>Priority: Major
> Fix For: 2.5
>
>
> RETS documentation need to be updated:
>  # GET_OR_CREATE_CACHE enhanced command with optional "templateName", 
> "backups", "cacheGroup", "dataRegion" and "writeSynchronizationMode" options.
>  #  Added support for Java built in types for put/get operations via 
> "keyType" and "valueType" optional parameters. List of supported types: 
>  * java.lang.Boolean (with alias boolean)
>  * java.lang.Byte (with alias byte)
>  * java.lang.Short (with alias short)
>  * java.lang.Integer (with aliases int, integer)
>  * java.lang.Long (with alias long)
>  * java.lang.Float (with alias float)
>  * java.lang.Double (with alias double)
>  * java.sql.Date (with alias date)
>  * java.sql.Time (with alias time)
>  * java.sql.Timestamp (with alias timestamp)
>  * java.util.UUUID (with alias uuid)
>  * org.apache.ignite.lang.IgniteUuid (with alias IgniteUuid)
> For Date, Time, Timestamp value should be in format as specified in 
> *valueOf(String)* methods of corresponding classes.
> Example for date: "2018-01-01" see 
> https://docs.oracle.com/javase/8/docs/api/java/sql/Date.html#valueOf-java.lang.String-
> Example for time: "01:01:01" see 
> https://docs.oracle.com/javase/8/docs/api/java/sql/Time.html#valueOf-java.lang.String-
> Example for timestamp: "2018-02-18%2001:01:01" see 
> https://docs.oracle.com/javase/8/docs/api/java/sql/Timestamp.html#valueOf-java.lang.String-
>  



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

[jira] [Updated] (IGNITE-7745) JDBC: Add a note about SSL connection to docs

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-7745:

Component/s: documentation

> JDBC: Add a note about SSL connection to docs
> -
>
> Key: IGNITE-7745
> URL: https://issues.apache.org/jira/browse/IGNITE-7745
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Taras Ledkov
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.5
>
>
> JDBC thin documentation must be updated according with: IGNITE-6625



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

[jira] [Commented] (IGNITE-7745) JDBC: Add a note about SSL connection to docs

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-7745:
-

[~tledkov-gridgain] , thanks. I'll do this by the end of the week.

> JDBC: Add a note about SSL connection to docs
> -
>
> Key: IGNITE-7745
> URL: https://issues.apache.org/jira/browse/IGNITE-7745
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.5
>
>
> JDBC thin documentation must be updated according with: IGNITE-6625



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

[jira] [Assigned] (IGNITE-7745) JDBC: Add a note about SSL connection to docs

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-7745:
---

Assignee: Denis Magda  (was: Taras Ledkov)

> JDBC: Add a note about SSL connection to docs
> -
>
> Key: IGNITE-7745
> URL: https://issues.apache.org/jira/browse/IGNITE-7745
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Taras Ledkov
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.5
>
>
> JDBC thin documentation must be updated according with: IGNITE-6625



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

[jira] [Updated] (IGNITE-7745) JDBC: Add a note about SSL connection to docs

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-7745:

Fix Version/s: 2.5

> JDBC: Add a note about SSL connection to docs
> -
>
> Key: IGNITE-7745
> URL: https://issues.apache.org/jira/browse/IGNITE-7745
> Project: Ignite
>  Issue Type: Task
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.5
>
>
> JDBC thin documentation must be updated according with: IGNITE-6625



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

[jira] [Commented] (IGNITE-7769) Persistence Problem

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-7769:


Hi [~Canon], could you please share ignite logs produced after start?

Or could you please provide reference to user list discussion?

> Persistence Problem
> ---
>
> Key: IGNITE-7769
> URL: https://issues.apache.org/jira/browse/IGNITE-7769
> Project: Ignite
>  Issue Type: Bug
>  Components: binary, persistence
>Affects Versions: 2.3
> Environment: *Summary:*
> *+-+*
> *| Active | true |*
> *| Total hosts | 5 |*
> *| Total nodes | 5 |*
> *| Total CPUs | 10 |*
> *| Avg. CPU load | 6.17 % |*
> *| Avg. free heap | 81.00 % |*
> *| Avg. Up time | 00:03:57 |*
> *| Snapshot time | 02/20/18, 16:36:01 |*
> *+-+*
>Reporter: Caner Önder
>Priority: Critical
>  Labels: usability
> Attachments: example-persistent-store.xml
>
>
> Hİ, i have persistency problem with the conf file which i already attached.
> When i reboot the cluster and activate it again, i lose data on every reboot 
> and also the old tables which i deleted before, appears again.
>  



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

[jira] [Updated] (IGNITE-7688) DDL does not working properly on sql queries.

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-7688:

Fix Version/s: 2.5

> DDL does not working properly on sql queries.
> -
>
> Key: IGNITE-7688
> URL: https://issues.apache.org/jira/browse/IGNITE-7688
> Project: Ignite
>  Issue Type: Bug
>  Components: 2.3
>Affects Versions: 2.3
> Environment: we have 5 node running on Ubuntu 16.04(VM). we 
> donwloaded binary dist. from download page. 
>Reporter: Muratcan TUKSAL
>Priority: Critical
>  Labels: persistant, persistence, persistence.xml
> Fix For: 2.5
>
> Attachments: buggy-config.xml
>
>
> * start ignite cluster persistent enabled mode (tried on 5 node)
>  * activate cluster via ignitevisor
>  * Create a table through jdbc 
>  * kill all nodes
>  * start all nodes again
>  * activate cluster via ignitevisor
>  * drop that specific table
>  * deactivate cluster(doesnt matter via top -deactivate or kill all nodes)
>  * activate cluster
>  * dropped table still there with no data



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

[jira] [Updated] (IGNITE-7688) DDL does not working properly on sql queries.

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-7688:

Priority: Critical  (was: Blocker)

> DDL does not working properly on sql queries.
> -
>
> Key: IGNITE-7688
> URL: https://issues.apache.org/jira/browse/IGNITE-7688
> Project: Ignite
>  Issue Type: Bug
>  Components: 2.3
>Affects Versions: 2.3
> Environment: we have 5 node running on Ubuntu 16.04(VM). we 
> donwloaded binary dist. from download page. 
>Reporter: Muratcan TUKSAL
>Priority: Critical
>  Labels: persistant, persistence, persistence.xml
> Fix For: 2.5
>
> Attachments: buggy-config.xml
>
>
> * start ignite cluster persistent enabled mode (tried on 5 node)
>  * activate cluster via ignitevisor
>  * Create a table through jdbc 
>  * kill all nodes
>  * start all nodes again
>  * activate cluster via ignitevisor
>  * drop that specific table
>  * deactivate cluster(doesnt matter via top -deactivate or kill all nodes)
>  * activate cluster
>  * dropped table still there with no data



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

[jira] [Updated] (IGNITE-5910) Method stopGrid(name) doesn't work in multiJvm mode

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur updated IGNITE-5910:
---
Labels: tests  (was: )

> Method stopGrid(name) doesn't work in multiJvm mode
> ---
>
> Key: IGNITE-5910
> URL: https://issues.apache.org/jira/browse/IGNITE-5910
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
>Priority: Major
>  Labels: tests
> Fix For: 2.5
>
>
> {code:title=Exception at call}
> java.lang.ClassCastException: 
> org.apache.ignite.testframework.junits.multijvm.IgniteProcessProxy cannot be 
> cast to org.apache.ignite.internal.IgniteKernal
> {code}
> {code:title=Reproducer snippet}
> /** {@inheritDoc} */
> @Override protected boolean isMultiJvm() {
> return true;
> }
> /**
>  * @throws Exception If failed.
>  */
> public void testGrid() throws Exception {
> try {
> startGrid(0);
> startGrid(1);
> }
> finally {
> stopGrid(1);
> stopGrid(0);
> }
> }
> {code}



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

[jira] [Commented] (IGNITE-5829) Writing entry contents to WAL only single time

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5829:


GitHub user Jokser opened a pull request:

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

IGNITE-5829 WAL Delta records optimizations.



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

$ git pull https://github.com/gridgain/apache-ignite ignite-5829-dual-mode

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

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


commit 5855257ce55e88e94ab61473547f1c25ecff6088
Author: Pavel Kovalenko 
Date:   2017-07-28T09:55:31Z

IGNITE-5829 Initial implementation.

commit 9a83f020e3c42cec6ee559a830388817d3288459
Author: Pavel Kovalenko 
Date:   2017-07-28T11:54:51Z

IGNITE-5829 Fixed creation CacheDataRowAdapter from LazyDataEntry.

commit bc18394f317ab6854c8fd75efe3f50f64bcfe64a
Author: Pavel Kovalenko 
Date:   2017-07-28T15:53:01Z

IGNITE-5829 Some changes.

commit 1e08c3fb5c02ec8acafd71b50b6ad3b749259f1a
Author: Andrey V. Mashenkov 
Date:   2017-07-31T11:14:56Z

IGNITE-4800: Lucene query may fails with NPE. This closes #2315.

commit 3fdf453e89a7bd76dff6b6d0646e3821ea3921d5
Author: Andrey V. Mashenkov 
Date:   2017-07-31T14:32:12Z

IGNITE-4800: Lucene query may fails with NPE.
Test fixed.

commit 739d8da94599c67c6ec9365019ed937cf05dbf32
Author: Pavel Kovalenko 
Date:   2017-08-02T11:58:08Z

IGNITE-5829 Passing WAL reference to CacheRow.

commit 1ca697ffcd8daf31a8ed1b2a078f40c688cb6b73
Author: Pavel Kovalenko 
Date:   2017-08-02T12:49:32Z

Merge branch 'ignite-2.1.4' into ignite-5829

commit a916d8bf9f5fbf9bb863913ee8de8414ddc5a303
Author: Pavel Kovalenko 
Date:   2017-08-02T12:53:59Z

IGNITE-5829 Fixed H2 rows.

commit 6895bce938efab7a30ded16e9e181f5f376c2728
Author: Pavel Kovalenko 
Date:   2017-08-02T12:55:49Z

IGNITE-5829 Code cleaning

commit 86f6fb19b1e2c7171f5cacf44a2f9246ced0177c
Author: Pavel Kovalenko 
Date:   2017-08-02T13:01:57Z

IGNITE-5829 Allocate non-direct buffer.

commit e255a564985a12113984ec02f15a4443495b8ffc
Author: Nikolay Izhikov 
Date:   2017-08-02T08:52:44Z

ignite-5712 Context switching for optimistic transactions

commit 772d462b68c7de8517d1f61e2e05ec8eefb18eac
Author: Alexey Kuznetsov 
Date:   2017-08-03T04:55:15Z

Merge branch ignite-2.1.3 into ignite-2.1.4

commit 72d706e6f3bad47d19846f0aba1f74431957fa69
Author: Pavel Kovalenko 
Date:   2017-08-03T11:29:59Z

IGNITE-5829 Minor changes.

commit 0f3b7ca25313083e4dc35e7842931a655abd
Author: tledkov-gridgain 
Date:   2017-08-04T08:46:14Z

IGNITE-5126: Batch support for this JDBC driver. This closes #2162.

commit d1a74a4be8744528e6ed23706174041ddb0f2618
Author: devozerov 
Date:   2017-08-04T09:04:38Z

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

commit 0b3a9a7176f5ae44a96ecf700c8147193dfbf064
Author: Igor Sapego 
Date:   2017-08-04T10:18:00Z

IGNITE-5923: ODBC: SQLGetTypeInfo now works with SQL_ALL_TYPES

(cherry picked from commit 48c914d)

commit 4e0385fbc0f50548f2da3407fdfdfe939b463c67
Author: Igor Sapego 
Date:   2017-08-04T15:34:27Z

IGNITE-5939: ODBC: SQLColAttributes now works with legacy attribute codes.

(cherry picked from commit 70ffa2c)

commit b4e3d661fc23a212660afd67f50159e135338aa9
Author: Pavel Kovalenko 
Date:   2017-08-04T16:47:20Z

IGNITE-5829 Final version without tests and backward compatibility.

commit c243fc1e7c5e9fe73715cb2b25ee55ee82eb1214
Author: Pavel Kovalenko 
Date:   2017-08-04T16:54:27Z

IGNITE-5829 Uncomment tests.

commit 93c4b9e3dbf5ef12dc95bdab20abaf40bbfc715c
Author: Pavel Kovalenko 
Date:   2017-08-06T16:34:58Z

IGNITE-5829 Code cleaning

commit 215a77687c88edc60dba055029ba6ac1642e1555
Author: Pavel Kovalenko 
Date:   2017-08-06T16:37:02Z

IGNITE-5829 Fixed cache size property for PayloadLinker.

commit 17e758dfc091ae4e416e1cca60ca2361ced8ffd0
Author: Pavel Kovalenko 
Date:   2017-08-06T18:30:35Z

IGNITE-5829 Fixed compilation.

commit 3b9b663a49064e301c1d619b06f3a581808ca66a
Author: Pavel Kovalenko 
Date:   2017-08-06T20:44:38Z

IGNITE-5829 Some logic changes in GridCacheMapEntry.

commit e3d033682e6ab4c28ed0bebd7c5fb22895456cb1
Author: Pavel Kovalenko 
Date:   2017-08-06T22:56:41Z

IGNITE-5829 Lookup pointer from WAL 

[jira] [Updated] (IGNITE-5555) Ignite PDS 1: JVM crash on teamcity (Rare)

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-:
---
Attachment: hs_err_pid7100.log.txt

> Ignite PDS 1: JVM crash on teamcity (Rare)
> --
>
> Key: IGNITE-
> URL: https://issues.apache.org/jira/browse/IGNITE-
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain, test-fail
> Fix For: 2.5
>
> Attachments: crash_report, hs_err_pid7100.log.txt, thread_dump
>
>
> Most recent crashes
> https://ci.ignite.apache.org/viewLog.html?buildId=1095007=IgniteTests24Java8_IgnitePds1=buildResultsDiv
> {noformat}
>Ignite PDS 1 [ tests 0 JVM CRASH ] 
>  BPlusTreeReuseListPageMemoryImplTest.testEmptyCursors (last started) 
> {noformat}
> https://ci.ignite.apache.org/viewLog.html?buildId=1086130=buildResultsDiv=IgniteTests24Java8_IgnitePds1
> {noformat}
>Ignite PDS 1 [ tests 0 JVM CRASH ] 
>  BPlusTreeReuseListPageMemoryImplTest.testEmptyCursors (last started) 
> {noformat}
> (older failure
> http://ci.ignite.apache.org/viewLog.html?buildId=675694=buildResultsDiv=Ignite20Tests_IgnitePds1#)
> Stacktrace indicates failure was in ignite code related to B+tree
> {noformat}J 34156 C2 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.readLockPage(JLorg/apache/ignite/internal/pagemem/FullPageId;ZZ)J
>  (88 bytes) @ 0x7f98cfc24a5a [0x7f98cfc24540+0x51a]
> J 34634 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run0(JJJLorg/apache/ignite/internal/processors/cache/persistence/tree/io/BPlusIO;Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Get;I)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
>  (380 bytes) @ 0x7f98d32dd524 [0x7f98d32dd100+0x424]
> J 34633 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readPage(Lorg/apache/ignite/internal/pagemem/PageMemory;IJJLorg/apache/ignite/internal/processors/cache/persistence/tree/util/PageLockListener;Lorg/apache/ignite/internal/processors/cache/persistence/tree/util/PageHandler;Ljava/lang/Object;ILjava/lang/Object;)Ljava/lang/Object;
>  (81 bytes) @ 0x7f98d2091c94 [0x7f98d2091a40+0x254]
> J 34888 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Invoke;JJJI)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
>  (561 bytes) @ 0x7f98d2ca146c [0x7f98d2ca1180+0x2ec]
> J 34888 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Invoke;JJJI)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
>  (561 bytes) @ 0x7f98d2ca17f8 [0x7f98d2ca1180+0x678]
> J 34888 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Invoke;JJJI)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
>  (561 bytes) @ 0x7f98d2ca17f8 [0x7f98d2ca1180+0x678]
> J 34888 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Invoke;JJJI)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
>  (561 bytes) @ 0x7f98d2ca17f8 [0x7f98d2ca1180+0x678]
> J 35053 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(Ljava/lang/Object;Ljava/lang/Object;Lorg/apache/ignite/internal/util/Igni
> {noformat}



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

[jira] [Commented] (IGNITE-5555) Ignite PDS 1: JVM crash on teamcity (Rare)

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-:


 Ignite Basic [ tests 0 JVM CRASH ]  
https://ci.ignite.apache.org/viewLog.html?buildId=1103446=IgniteTests24Java8_IgniteBasic=buildResultsDiv
 BPlusTreeFakeReuseSelfTest.testEmptyCursors (last started) 

> Ignite PDS 1: JVM crash on teamcity (Rare)
> --
>
> Key: IGNITE-
> URL: https://issues.apache.org/jira/browse/IGNITE-
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain, test-fail
> Fix For: 2.5
>
> Attachments: crash_report, thread_dump
>
>
> Most recent crashes
> https://ci.ignite.apache.org/viewLog.html?buildId=1095007=IgniteTests24Java8_IgnitePds1=buildResultsDiv
> {noformat}
>Ignite PDS 1 [ tests 0 JVM CRASH ] 
>  BPlusTreeReuseListPageMemoryImplTest.testEmptyCursors (last started) 
> {noformat}
> https://ci.ignite.apache.org/viewLog.html?buildId=1086130=buildResultsDiv=IgniteTests24Java8_IgnitePds1
> {noformat}
>Ignite PDS 1 [ tests 0 JVM CRASH ] 
>  BPlusTreeReuseListPageMemoryImplTest.testEmptyCursors (last started) 
> {noformat}
> (older failure
> http://ci.ignite.apache.org/viewLog.html?buildId=675694=buildResultsDiv=Ignite20Tests_IgnitePds1#)
> Stacktrace indicates failure was in ignite code related to B+tree
> {noformat}J 34156 C2 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.readLockPage(JLorg/apache/ignite/internal/pagemem/FullPageId;ZZ)J
>  (88 bytes) @ 0x7f98cfc24a5a [0x7f98cfc24540+0x51a]
> J 34634 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run0(JJJLorg/apache/ignite/internal/processors/cache/persistence/tree/io/BPlusIO;Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Get;I)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
>  (380 bytes) @ 0x7f98d32dd524 [0x7f98d32dd100+0x424]
> J 34633 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readPage(Lorg/apache/ignite/internal/pagemem/PageMemory;IJJLorg/apache/ignite/internal/processors/cache/persistence/tree/util/PageLockListener;Lorg/apache/ignite/internal/processors/cache/persistence/tree/util/PageHandler;Ljava/lang/Object;ILjava/lang/Object;)Ljava/lang/Object;
>  (81 bytes) @ 0x7f98d2091c94 [0x7f98d2091a40+0x254]
> J 34888 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Invoke;JJJI)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
>  (561 bytes) @ 0x7f98d2ca146c [0x7f98d2ca1180+0x2ec]
> J 34888 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Invoke;JJJI)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
>  (561 bytes) @ 0x7f98d2ca17f8 [0x7f98d2ca1180+0x678]
> J 34888 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Invoke;JJJI)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
>  (561 bytes) @ 0x7f98d2ca17f8 [0x7f98d2ca1180+0x678]
> J 34888 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Invoke;JJJI)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
>  (561 bytes) @ 0x7f98d2ca17f8 [0x7f98d2ca1180+0x678]
> J 35053 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(Ljava/lang/Object;Ljava/lang/Object;Lorg/apache/ignite/internal/util/Igni
> {noformat}



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

[jira] [Commented] (IGNITE-7767) Update WALMode configuration in .NET

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-7767:


Yes, this is unrelated.
That metrics check is quite pointless, I would simply remove 
{{Assert.Greater(metrics.WalFsyncTimeAverage, 0);}} line from 
{{PersistenceTest.cs}}

> Update WALMode configuration in .NET
> 
>
> Key: IGNITE-7767
> URL: https://issues.apache.org/jira/browse/IGNITE-7767
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> In https://issues.apache.org/jira/browse/IGNITE-7594 we changed values for 
> WALMode enum, but .NET code wasn't modified accordingly.



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

[jira] [Updated] (IGNITE-5910) Method stopGrid(name) doesn't work in multiJvm mode

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur updated IGNITE-5910:
---
Fix Version/s: 2.5

> Method stopGrid(name) doesn't work in multiJvm mode
> ---
>
> Key: IGNITE-5910
> URL: https://issues.apache.org/jira/browse/IGNITE-5910
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
>Priority: Major
> Fix For: 2.5
>
>
> {code:title=Exception at call}
> java.lang.ClassCastException: 
> org.apache.ignite.testframework.junits.multijvm.IgniteProcessProxy cannot be 
> cast to org.apache.ignite.internal.IgniteKernal
> {code}
> {code:title=Reproducer snippet}
> /** {@inheritDoc} */
> @Override protected boolean isMultiJvm() {
> return true;
> }
> /**
>  * @throws Exception If failed.
>  */
> public void testGrid() throws Exception {
> try {
> startGrid(0);
> startGrid(1);
> }
> finally {
> stopGrid(1);
> stopGrid(0);
> }
> }
> {code}



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

[jira] [Commented] (IGNITE-7767) Update WALMode configuration in .NET

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-7767:


[~ptupitsyn], it seems only 2 tests failing
https://ci.ignite.apache.org/viewLog.html?buildId=1103443=buildResultsDiv=IgniteTests24Java8_RunAllNet

I am not sure it is related to WAL mode
- PersistenceTest.TestCacheDataSurvivesNodeRestart   
- PersistenceTest.TestCacheDataSurvivesNodeRestart 

> Update WALMode configuration in .NET
> 
>
> Key: IGNITE-7767
> URL: https://issues.apache.org/jira/browse/IGNITE-7767
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> In https://issues.apache.org/jira/browse/IGNITE-7594 we changed values for 
> WALMode enum, but .NET code wasn't modified accordingly.



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

[jira] [Commented] (IGNITE-6083) Null value have appear in the entry processor, but the entry is existing

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6083:


GitHub user voipp opened a pull request:

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

IGNITE-6083 alternate fix version



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

$ git pull https://github.com/voipp/ignite ignite-6083-2

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

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


commit 236b63bb7f3ebd214a690b168edf14c6c1832c95
Author: voipp 
Date:   2018-02-20T16:09:12Z

IGNITE-6083 alternate fix version




> Null value have appear in the entry processor, but the entry is existing
> 
>
> Key: IGNITE-6083
> URL: https://issues.apache.org/jira/browse/IGNITE-6083
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Vladislav Pyatkov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Attachments: EntryProcessorInOptimisticTxTest.java
>
>
> In one thread load some data in a cache, after that I have execute 
> OPTIMISTIC, SERIALIZABLE transaction with two {{IgniteCache.invoke()}} 
> methods.
> The value had been corrected at first {{EntryProcessor}}, but it is NULL at 
> second.



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

[jira] [Commented] (IGNITE-7767) Update WALMode configuration in .NET

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-7767:


[~ilantukh], looks good to me. Please make sure TC passes.

> Update WALMode configuration in .NET
> 
>
> Key: IGNITE-7767
> URL: https://issues.apache.org/jira/browse/IGNITE-7767
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> In https://issues.apache.org/jira/browse/IGNITE-7594 we changed values for 
> WALMode enum, but .NET code wasn't modified accordingly.



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

[jira] [Created] (IGNITE-7773) Add getRebalanceClearingPartitionsLeft JMX metric to .NET

[Pavel Kovalenko (JIRA)]

Pavel Kovalenko created IGNITE-7773:
---

 Summary: Add getRebalanceClearingPartitionsLeft JMX metric to .NET
 Key: IGNITE-7773
 URL: https://issues.apache.org/jira/browse/IGNITE-7773
 Project: Ignite
  Issue Type: Task
  Components: platforms
Reporter: Pavel Kovalenko
 Fix For: 2.5


New metric is introduced in IGNITE-6113 .



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

[jira] [Comment Edited] (IGNITE-6083) Null value have appear in the entry processor, but the entry is existing

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov edited comment on IGNITE-6083 at 2/20/18 3:41 PM:
---

[~agoncharuk] when first entry processor is called in tx#enlistWriteEntry(), 
cache entry is pulled from cache by entry.innerGet(). 
 So first entry processor observes non-null value [see 
source|https://github.com/voipp/ignite/blob/49cd833eed456917b4435fc12ffcce6a689d/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/near/GridNearTxLocal.java#L1319].
 This value _*would not be saved*_ in IgniteTxEntry.

When entry processor is called a second time, it gets value from 
IgniteTxEntry#value , which is null, because we didn't set any value at first 
call [see 
source|https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/near/GridNearTxLocal.java#L1401]

 

PS. It seems odd, that entry processor is called multiple times : before 
transaction commit and during prepare phase(after locks are aquired).

And the value is set on finish phase in innerSet. I think, we can call only 
once : before commit, and save the value in Tx entry.


was (Author: alexey kuznetsov):
[~agoncharuk] when first entry processor is called in tx#enlistWriteEntry(), 
cache entry is pulled from cache by entry.innerGet(). 
 So first entry processor observes non-null value [see 
source|https://github.com/voipp/ignite/blob/49cd833eed456917b4435fc12ffcce6a689d/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/near/GridNearTxLocal.java#L1319].
 This value _*would not be saved*_ in IgniteTxEntry.

When entry processor is called a second time, it gets value from 
IgniteTxEntry#value , which is null, because we didn't set any value at first 
call.

 

PS. It seems odd, that entry processor is called multiple times : before 
transaction commit and during prepare phase(after locks are aquired).

And the value is set on finish phase in innerSet. I think, we can call only 
once : before commit, and save the value in Tx entry.

> Null value have appear in the entry processor, but the entry is existing
> 
>
> Key: IGNITE-6083
> URL: https://issues.apache.org/jira/browse/IGNITE-6083
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Vladislav Pyatkov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Attachments: EntryProcessorInOptimisticTxTest.java
>
>
> In one thread load some data in a cache, after that I have execute 
> OPTIMISTIC, SERIALIZABLE transaction with two {{IgniteCache.invoke()}} 
> methods.
> The value had been corrected at first {{EntryProcessor}}, but it is NULL at 
> second.



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

[jira] [Commented] (IGNITE-6083) Null value have appear in the entry processor, but the entry is existing

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov commented on IGNITE-6083:
--

[~agoncharuk] when first entry processor is called in tx#enlistWriteEntry(), 
cache entry is pulled from cache by entry.innerGet(). 
 So first entry processor observes non-null value [see 
source|https://github.com/voipp/ignite/blob/49cd833eed456917b4435fc12ffcce6a689d/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/near/GridNearTxLocal.java#L1319].
 This value _*would not be saved*_ in IgniteTxEntry.

When entry processor is called a second time, it gets value from 
IgniteTxEntry#value , which is null, because we didn't set any value at first 
call.

 

PS. It seems odd, that entry processor is called multiple times : before 
transaction commit and during prepare phase(after locks are aquired).

And the value is set on finish phase in innerSet. I think, we can call only 
once : before commit, and save the value in Tx entry.

> Null value have appear in the entry processor, but the entry is existing
> 
>
> Key: IGNITE-6083
> URL: https://issues.apache.org/jira/browse/IGNITE-6083
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Vladislav Pyatkov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Attachments: EntryProcessorInOptimisticTxTest.java
>
>
> In one thread load some data in a cache, after that I have execute 
> OPTIMISTIC, SERIALIZABLE transaction with two {{IgniteCache.invoke()}} 
> methods.
> The value had been corrected at first {{EntryProcessor}}, but it is NULL at 
> second.



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

[jira] [Assigned] (IGNITE-7427) Thin client Java API - failover

[Alexey Kukushkin (JIRA)]

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

Alexey Kukushkin reassigned IGNITE-7427:


Assignee: Alexey Kukushkin

> Thin client Java API - failover
> ---
>
> Key: IGNITE-7427
> URL: https://issues.apache.org/jira/browse/IGNITE-7427
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Alexey Kukushkin
>Assignee: Alexey Kukushkin
>Priority: Major
>  Labels: data, java, thin
>
> Implement failover in thin client Java API including unit and system tests 
> and samples.
> ClientConfiguration(failover configuration)



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

[jira] [Created] (IGNITE-7772) All critical system workers health should be covered

[Anton Vinogradov (JIRA)]

Anton Vinogradov created IGNITE-7772:


 Summary: All critical system workers health should be covered
 Key: IGNITE-7772
 URL: https://issues.apache.org/jira/browse/IGNITE-7772
 Project: Ignite
  Issue Type: Task
Reporter: Anton Vinogradov
Assignee: Dmitriy Sorokin






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

[jira] [Updated] (IGNITE-7772) All critical system workers health should be covered

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-7772:
-
Labels: iep-14  (was: )

> All critical system workers health should be covered
> 
>
> Key: IGNITE-7772
> URL: https://issues.apache.org/jira/browse/IGNITE-7772
> Project: Ignite
>  Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Dmitriy Sorokin
>Priority: Major
>  Labels: iep-14
>




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

[jira] [Updated] (IGNITE-6890) General way for handling Ignite failures

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-6890:
-
Labels: iep-14  (was: iep-)

> General way for handling Ignite failures
> 
>
> Key: IGNITE-6890
> URL: https://issues.apache.org/jira/browse/IGNITE-6890
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Anton Vinogradov
>Assignee: Dmitriy Sorokin
>Priority: Major
>  Labels: iep-14
> Fix For: 2.5
>
>
> Ignite failures which should be handled are:
>  # Topology segmentation;
>  # Exchange worker stop;
>  # Persistence errors.
> Proper behavior should be selected according to result of calling 
> IgniteFailureHandler instance, custom implementation of which can be provided 
> in IgniteConfiguration. It can be node stop, restart or nothing.



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

[jira] [Updated] (IGNITE-6890) General way for handling Ignite failures

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-6890:
-
Labels: iep-  (was: iep-7)

> General way for handling Ignite failures
> 
>
> Key: IGNITE-6890
> URL: https://issues.apache.org/jira/browse/IGNITE-6890
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Anton Vinogradov
>Assignee: Dmitriy Sorokin
>Priority: Major
>  Labels: iep-14
> Fix For: 2.5
>
>
> Ignite failures which should be handled are:
>  # Topology segmentation;
>  # Exchange worker stop;
>  # Persistence errors.
> Proper behavior should be selected according to result of calling 
> IgniteFailureHandler instance, custom implementation of which can be provided 
> in IgniteConfiguration. It can be node stop, restart or nothing.



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

[jira] [Commented] (IGNITE-7767) Update WALMode configuration in .NET

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh commented on IGNITE-7767:
--

PR: https://github.com/apache/ignite/pull/3544/files

> Update WALMode configuration in .NET
> 
>
> Key: IGNITE-7767
> URL: https://issues.apache.org/jira/browse/IGNITE-7767
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> In https://issues.apache.org/jira/browse/IGNITE-7594 we changed values for 
> WALMode enum, but .NET code wasn't modified accordingly.



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

[jira] [Commented] (IGNITE-7768) No description for org.apache.ignite.ml.nn.trainers.distributed

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7768:


Github user asfgit closed the pull request at:

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


> No description for org.apache.ignite.ml.nn.trainers.distributed
> ---
>
> Key: IGNITE-7768
> URL: https://issues.apache.org/jira/browse/IGNITE-7768
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, ml
>Affects Versions: 2.4
>Reporter: Ilya Suntsov
>Assignee: Artem Malykh
>Priority: Minor
> Fix For: 2.4
>
>
> We need to add description for package 
> org.apache.ignite.ml.nn.trainers.distributed



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

[jira] [Commented] (IGNITE-7768) No description for org.apache.ignite.ml.nn.trainers.distributed

[Yury Babak (JIRA)]

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

Yury Babak commented on IGNITE-7768:


Merged

> No description for org.apache.ignite.ml.nn.trainers.distributed
> ---
>
> Key: IGNITE-7768
> URL: https://issues.apache.org/jira/browse/IGNITE-7768
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, ml
>Affects Versions: 2.4
>Reporter: Ilya Suntsov
>Assignee: Artem Malykh
>Priority: Minor
> Fix For: 2.4
>
>
> We need to add description for package 
> org.apache.ignite.ml.nn.trainers.distributed



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

[jira] [Updated] (IGNITE-6891) Proper behavior on Persistence errors

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-6891:
-
Labels:   (was: iep-7)

> Proper behavior on Persistence errors 
> --
>
> Key: IGNITE-6891
> URL: https://issues.apache.org/jira/browse/IGNITE-6891
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Anton Vinogradov
>Assignee: Dmitriy Sorokin
>Priority: Major
> Fix For: 2.5
>
>
> Node should be stopped anyway, what we can provide is user callback, 
> something like beforeNodeStop'.



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

[jira] [Created] (IGNITE-7771) Names of Ignite JMX beans should not be quoted unless required

[Stanislav Lukyanov (JIRA)]

Stanislav Lukyanov created IGNITE-7771:
--

 Summary: Names of Ignite JMX beans should not be quoted unless 
required
 Key: IGNITE-7771
 URL: https://issues.apache.org/jira/browse/IGNITE-7771
 Project: Ignite
  Issue Type: Bug
Reporter: Stanislav Lukyanov
Assignee: Stanislav Lukyanov


Names of Ignite JMX beans and bean groups are currently quoted if they contain 
non-alphanumeric characters. This leads to names with spaces, e.g. Thread 
Pools, appearing as "Thread Pools". Moreover, Thread Pools and "Thread Pools" 
are recognized by JMX as distinct names, so code accessing that MBean needs to 
take that into account.

It would be better not to quote the bean and group names unless they contain 
specific control characters. That way users won't need to quote names in their 
JMX clients.



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

[jira] [Updated] (IGNITE-7768) No description for org.apache.ignite.ml.nn.trainers.distributed

[Yury Babak (JIRA)]

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

Yury Babak updated IGNITE-7768:
---
Component/s: ml

> No description for org.apache.ignite.ml.nn.trainers.distributed
> ---
>
> Key: IGNITE-7768
> URL: https://issues.apache.org/jira/browse/IGNITE-7768
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, ml
>Affects Versions: 2.4
>Reporter: Ilya Suntsov
>Assignee: Artem Malykh
>Priority: Minor
>
> We need to add description for package 
> org.apache.ignite.ml.nn.trainers.distributed



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

[jira] [Updated] (IGNITE-7427) Thin client Java API - failover

[Alexey Kukushkin (JIRA)]

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

Alexey Kukushkin updated IGNITE-7427:
-
Description: 
Implement failover in thin client Java API including unit and system tests and 
samples.

ClientConfiguration(failover configuration)

> Thin client Java API - failover
> ---
>
> Key: IGNITE-7427
> URL: https://issues.apache.org/jira/browse/IGNITE-7427
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Alexey Kukushkin
>Priority: Major
>  Labels: data, java, thin
>
> Implement failover in thin client Java API including unit and system tests 
> and samples.
> ClientConfiguration(failover configuration)



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

[jira] [Updated] (IGNITE-7427) Thin client Java API - failover

[Alexey Kukushkin (JIRA)]

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

Alexey Kukushkin updated IGNITE-7427:
-
Environment: (was: Implement failover in thin client Java API including 
unit and system tests and samples.

ClientConfiguration(failover configuration))

> Thin client Java API - failover
> ---
>
> Key: IGNITE-7427
> URL: https://issues.apache.org/jira/browse/IGNITE-7427
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Alexey Kukushkin
>Priority: Major
>  Labels: data, java, thin
>




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

[jira] [Updated] (IGNITE-7421) Thin client Java API - data grid API

[Alexey Kukushkin (JIRA)]

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

Alexey Kukushkin updated IGNITE-7421:
-
Description: 
Implement below Java bindings for the thin client protocol. The client 
configuration must support failover and encryption.

Cache
     JCache (limited)
         getName(): String
         put(key, val)
         get(key): V
         getAll(keys: Set): Map
         containsKey(key): boolean
         getAndPut(key, val): V
         getAndReplace(key, val): V
         getAndRemove(key): V
         putIfAbsent
         replace(key, val)
         replace(key, oldVal, newVal)
         putAll
         clear
         remove(key)
         remove(key, val)
         removeAll()
         removeAll(keys: Set)
         getConfiguration(clazz): Configuration
         close()
     size(modes: CachePeekMode...)
     query(qry: Query): QueryCursor
     query(qry: SqlFieldsQuery): FieldsQueryCursor
     withKeepBinary(): IgniteCache
 Ignite
     cache(name: String)
     cacheNames(): Collection
     binary(): IgniteBinary
     createCache(name): Cache
     getOrCreateCache(name): Cache
     destroyCache(name)
 Ignition
     startClient(:ClientConfiguration): Ignite
 ClientConfiguration(port, host, binaryConfiguration, sslConfiguration,
 etc...)

> Thin client Java API - data grid API
> 
>
> Key: IGNITE-7421
> URL: https://issues.apache.org/jira/browse/IGNITE-7421
> Project: Ignite
>  Issue Type: New Feature
>  Components: thin client
>Reporter: Alexey Kukushkin
>Priority: Major
>  Labels: data, java, thin
>
> Implement below Java bindings for the thin client protocol. The client 
> configuration must support failover and encryption.
> Cache
>      JCache (limited)
>          getName(): String
>          put(key, val)
>          get(key): V
>          getAll(keys: Set): Map
>          containsKey(key): boolean
>          getAndPut(key, val): V
>          getAndReplace(key, val): V
>          getAndRemove(key): V
>          putIfAbsent
>          replace(key, val)
>          replace(key, oldVal, newVal)
>          putAll
>          clear
>          remove(key)
>          remove(key, val)
>          removeAll()
>          removeAll(keys: Set)
>          getConfiguration(clazz): Configuration
>          close()
>      size(modes: CachePeekMode...)
>      query(qry: Query): QueryCursor
>      query(qry: SqlFieldsQuery): FieldsQueryCursor
>      withKeepBinary(): IgniteCache
>  Ignite
>      cache(name: String)
>      cacheNames(): Collection
>      binary(): IgniteBinary
>      createCache(name): Cache
>      getOrCreateCache(name): Cache
>      destroyCache(name)
>  Ignition
>      startClient(:ClientConfiguration): Ignite
>  ClientConfiguration(port, host, binaryConfiguration, sslConfiguration,
>  etc...)



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

[jira] [Updated] (IGNITE-7421) Thin client Java API - data grid API

[Alexey Kukushkin (JIRA)]

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

Alexey Kukushkin updated IGNITE-7421:
-
Environment: (was: Implement below Java bindings for the thin client 
protocol. The client configuration must support failover and encryption.

Cache
    JCache (limited)
        getName(): String
        put(key, val)
        get(key): V
        getAll(keys: Set): Map
        containsKey(key): boolean
        getAndPut(key, val): V
        getAndReplace(key, val): V
        getAndRemove(key): V
        putIfAbsent
        replace(key, val)
        replace(key, oldVal, newVal)
        putAll
        clear
        remove(key)
        remove(key, val)
        removeAll()
        removeAll(keys: Set)
        getConfiguration(clazz): Configuration
        close()
    size(modes: CachePeekMode...)
    query(qry: Query): QueryCursor
    query(qry: SqlFieldsQuery): FieldsQueryCursor
    withKeepBinary(): IgniteCache
Ignite
    cache(name: String)
    cacheNames(): Collection
    binary(): IgniteBinary
    createCache(name): Cache
    getOrCreateCache(name): Cache
    destroyCache(name)
Ignition
    startClient(:ClientConfiguration): Ignite
ClientConfiguration(port, host, binaryConfiguration, sslConfiguration,
etc...))

> Thin client Java API - data grid API
> 
>
> Key: IGNITE-7421
> URL: https://issues.apache.org/jira/browse/IGNITE-7421
> Project: Ignite
>  Issue Type: New Feature
>  Components: thin client
>Reporter: Alexey Kukushkin
>Priority: Major
>  Labels: data, java, thin
>




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

[jira] [Updated] (IGNITE-6467) Ignite cache 6: new tests CacheExchangeMergeTest.testConcurrentStartServersAndClients() and testDelayExchangeMessages() have flaky junit assertion after cache get

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-6467:
---
Description: 
Ignite cache 6: CacheExchangeMergeTest: 3 tests fails with probability >10% in 
master and in PRs
IgniteCacheTestSuite6: 
CacheExchangeMergeTest.testConcurrentStartServersAndClients() 
IgniteCacheTestSuite6: CacheExchangeMergeTest.testDelayExchangeMessages() 
IgniteCacheTestSuite6: CacheExchangeMergeTest.testMergeServersFail1_2 (fail 
rate 22,6%) 

https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=741151191800314619=testDetails

https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8990224019412265556=testDetails


latest failure from master
https://ci.ignite.apache.org/viewLog.html?buildId=843261=buildResultsDiv=Ignite20Tests_IgniteCache6#testNameId741151191800314619

{noformat}
Invalid value [node=distributed.CacheExchangeMergeTest0, client=false, order=1, 
cache=c1] expected:<0> but was:
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:188)
at 
org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.checkNodeCaches(CacheExchangeMergeTest.java:1343)
at 
org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.checkCaches0(CacheExchangeMergeTest.java:1213)
at 
org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.checkCaches(CacheExchangeMergeTest.java:1195)
at 
org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.concurrentStart(CacheExchangeMergeTest.java:446)
at 
org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.testConcurrentStartServersAndClients(CacheExchangeMergeTest.java:414)
Caused by: junit.framework.AssertionFailedError: Invalid value 
[node=distributed.CacheExchangeMergeTest0, client=false, order=1, cache=c1] 
expected:<0> but was:
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.CacheExchangeMergeTest$16.run(CacheExchangeMergeTest.java:1312)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}

  was:
Ignite cache 6: CacheExchangeMergeTest.testConcurrentStartServersAndClients 
fails with probability >10% in master and in PRs
IgniteCacheTestSuite6: CacheExchangeMergeTest.testMergeServersFail1_2 (fail 
rate 22,6%) 

https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=741151191800314619=testDetails

https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8990224019412265556=testDetails


latest failure from master
https://ci.ignite.apache.org/viewLog.html?buildId=843261=buildResultsDiv=Ignite20Tests_IgniteCache6#testNameId741151191800314619

{noformat}
Invalid value [node=distributed.CacheExchangeMergeTest0, client=false, order=1, 
cache=c1] expected:<0> but was:
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:188)
at 
org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.checkNodeCaches(CacheExchangeMergeTest.java:1343)
at 
org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.checkCaches0(CacheExchangeMergeTest.java:1213)
at 
org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.checkCaches(CacheExchangeMergeTest.java:1195)
at 
org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.concurrentStart(CacheExchangeMergeTest.java:446)
at 
org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.testConcurrentStartServersAndClients(CacheExchangeMergeTest.java:414)
Caused by: junit.framework.AssertionFailedError: Invalid value 
[node=distributed.CacheExchangeMergeTest0, client=false, order=1, cache=c1] 
expected:<0> but was:
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.CacheExchangeMergeTest$16.run(CacheExchangeMergeTest.java:1312)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 

[jira] [Updated] (IGNITE-6467) Ignite cache 6: new tests CacheExchangeMergeTest.testConcurrentStartServersAndClients() and testDelayExchangeMessages() have flaky junit assertion after cache get

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-6467:
---
Description: 
Ignite cache 6: CacheExchangeMergeTest.testConcurrentStartServersAndClients 
fails with probability >10% in master and in PRs
IgniteCacheTestSuite6: CacheExchangeMergeTest.testMergeServersFail1_2 (fail 
rate 22,6%) 

https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=741151191800314619=testDetails

https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8990224019412265556=testDetails


latest failure from master
https://ci.ignite.apache.org/viewLog.html?buildId=843261=buildResultsDiv=Ignite20Tests_IgniteCache6#testNameId741151191800314619

{noformat}
Invalid value [node=distributed.CacheExchangeMergeTest0, client=false, order=1, 
cache=c1] expected:<0> but was:
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:188)
at 
org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.checkNodeCaches(CacheExchangeMergeTest.java:1343)
at 
org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.checkCaches0(CacheExchangeMergeTest.java:1213)
at 
org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.checkCaches(CacheExchangeMergeTest.java:1195)
at 
org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.concurrentStart(CacheExchangeMergeTest.java:446)
at 
org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.testConcurrentStartServersAndClients(CacheExchangeMergeTest.java:414)
Caused by: junit.framework.AssertionFailedError: Invalid value 
[node=distributed.CacheExchangeMergeTest0, client=false, order=1, cache=c1] 
expected:<0> but was:
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.CacheExchangeMergeTest$16.run(CacheExchangeMergeTest.java:1312)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}

  was:
Ignite cache 6: CacheExchangeMergeTest.testConcurrentStartServersAndClients 
fails with probability >10% in master and in PRs

https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=741151191800314619=testDetails

latest failure from master
https://ci.ignite.apache.org/viewLog.html?buildId=843261=buildResultsDiv=Ignite20Tests_IgniteCache6#testNameId741151191800314619

{noformat}
Invalid value [node=distributed.CacheExchangeMergeTest0, client=false, order=1, 
cache=c1] expected:<0> but was:
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:188)
at 
org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.checkNodeCaches(CacheExchangeMergeTest.java:1343)
at 
org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.checkCaches0(CacheExchangeMergeTest.java:1213)
at 
org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.checkCaches(CacheExchangeMergeTest.java:1195)
at 
org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.concurrentStart(CacheExchangeMergeTest.java:446)
at 
org.apache.ignite.internal.processors.cache.distributed.CacheExchangeMergeTest.testConcurrentStartServersAndClients(CacheExchangeMergeTest.java:414)
Caused by: junit.framework.AssertionFailedError: Invalid value 
[node=distributed.CacheExchangeMergeTest0, client=false, order=1, cache=c1] 
expected:<0> but was:
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.CacheExchangeMergeTest$16.run(CacheExchangeMergeTest.java:1312)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}


> Ignite cache 6: new tests 
> CacheExchangeMergeTest.testConcurrentStartServersAndClients() and 
> 

[jira] [Resolved] (IGNITE-7426) Thin client Java API - encryption

[Alexey Kukushkin (JIRA)]

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

Alexey Kukushkin resolved IGNITE-7426.
--
Resolution: Fixed

> Thin client Java API - encryption
> -
>
> Key: IGNITE-7426
> URL: https://issues.apache.org/jira/browse/IGNITE-7426
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Alexey Kukushkin
>Assignee: Alexey Kukushkin
>Priority: Major
>  Labels: data, java, thin
>
> Implement SSL/TLS configuration client Java API including unit and system 
> tests and samples.
> ClientConfiguration(ssl configuration)



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

[jira] [Commented] (IGNITE-7640) Refactor DiscoveryDataClusterState to be immutable

[Alexander Menshikov (JIRA)]

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

Alexander Menshikov commented on IGNITE-7640:
-

Wow, we have a real mess in `GridClusterStateProcessor`. We use volatile field 
in `DiscoveryDataClusterState` for async passing value from 
`GridClusterStateProcessor#onStateFinishMessage` to 
`GridClusterStateProcessor#publicApiActiveState`. And also we use future as a 
latch for sync this passing...

Also, I think there is a bug in line:

```Java

GridFutureAdapter transitionFut = 
transitionFuts.remove(transitionRequestId);

```

Because of `remove` call. One thread can already see `remove` but doesn't see 
field setter yet.

> Refactor DiscoveryDataClusterState to be immutable
> --
>
> Key: IGNITE-7640
> URL: https://issues.apache.org/jira/browse/IGNITE-7640
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.4
>Reporter: Alexey Goncharuk
>Assignee: Alexander Menshikov
>Priority: Major
> Fix For: 2.5
>
>




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

[jira] [Created] (IGNITE-7770) Ignite Cache 6: testRandomMixedTxConfigurations failed probably after jsr166 removal

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-7770:
--

 Summary: Ignite Cache 6: testRandomMixedTxConfigurations failed 
probably after jsr166 removal
 Key: IGNITE-7770
 URL: https://issues.apache.org/jira/browse/IGNITE-7770
 Project: Ignite
  Issue Type: Task
Reporter: Dmitriy Pavlov
Assignee: Andrey Kuznetsov


Ignite Cache 6: testRandomMixedTxConfigurations failed probably after jsr166 
removal
After appying IGNITE-7518 Get rid of org.jsr166.LongAdder8, 
 IgniteCacheTestSuite6: 
TxRollbackOnTimeoutNearCacheTest.testRandomMixedTxConfigurations (fail rate 
38,6%) 

https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-3733584033131292028=%3Cdefault%3E=testDetails




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

[jira] [Comment Edited] (IGNITE-7745) JDBC: Add a note about SSL connection to docs

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-7745 at 2/20/18 1:55 PM:
---

[~dmagda], could you please primary review the 
[documentation|https://dash.readme.io/project/apacheignite-sql/v2.3/docs/jdbc-driver_25_hidden]
 

See new _Using SSL_  part and new properties at the tables:
-  JDBC driver's properties;
- {{ClientConnectorConfiguration}}'s properties.


was (Author: tledkov-gridgain):
[~dmagda], could you please primary review the 
[documentation|https://dash.readme.io/project/apacheignite-sql/v2.3/docs/jdbc-driver_25_hidden]
 (see new _Using SSL_  part and new properties at the tables of JDBC driver's 
properties and {{ClientConnectorConfiguration}}'s properties).

> JDBC: Add a note about SSL connection to docs
> -
>
> Key: IGNITE-7745
> URL: https://issues.apache.org/jira/browse/IGNITE-7745
> Project: Ignite
>  Issue Type: Task
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
>
> JDBC thin documentation must be updated according with: IGNITE-6625



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

[jira] [Comment Edited] (IGNITE-7745) JDBC: Add a note about SSL connection to docs

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-7745 at 2/20/18 1:54 PM:
---

[~dmagda], could you please primary review the 
[documentation|https://dash.readme.io/project/apacheignite-sql/v2.3/docs/jdbc-driver_25_hidden]
 (see new _Using SSL_  part and new properties at the tables of JDBC driver's 
properties and {{ClientConnectorConfiguration}}'s properties).


was (Author: tledkov-gridgain):
[~dmagda], could you please primary review the 
[documentation|https://dash.readme.io/project/apacheignite-sql/v2.3/docs/jdbc-driver_25_hidden]
 (see new `Using SSL` part and new properties at the tables of JDBC driver's 
properties and {{ClientConnectorConfiguration}}'s properties).

> JDBC: Add a note about SSL connection to docs
> -
>
> Key: IGNITE-7745
> URL: https://issues.apache.org/jira/browse/IGNITE-7745
> Project: Ignite
>  Issue Type: Task
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
>
> JDBC thin documentation must be updated according with: IGNITE-6625



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

[jira] [Commented] (IGNITE-7745) JDBC: Add a note about SSL connection to docs

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-7745:
--

[~dmagda], could you please primary review the 
[documentation|https://dash.readme.io/project/apacheignite-sql/v2.3/docs/jdbc-driver_25_hidden]
 (see new `Using SSL` part and new properties at the tables of JDBC driver's 
properties and {{ClientConnectorConfiguration}}'s properties).

> JDBC: Add a note about SSL connection to docs
> -
>
> Key: IGNITE-7745
> URL: https://issues.apache.org/jira/browse/IGNITE-7745
> Project: Ignite
>  Issue Type: Task
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
>
> JDBC thin documentation must be updated according with: IGNITE-6625



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

[jira] [Created] (IGNITE-7769) Persistence Problem

[JIRA]

Caner Önder created IGNITE-7769:
---

 Summary: Persistence Problem
 Key: IGNITE-7769
 URL: https://issues.apache.org/jira/browse/IGNITE-7769
 Project: Ignite
  Issue Type: Bug
  Components: binary, persistence
Affects Versions: 2.3
 Environment: *Summary:*
*+-+*
*| Active | true |*
*| Total hosts | 5 |*
*| Total nodes | 5 |*
*| Total CPUs | 10 |*
*| Avg. CPU load | 6.17 % |*
*| Avg. free heap | 81.00 % |*
*| Avg. Up time | 00:03:57 |*
*| Snapshot time | 02/20/18, 16:36:01 |*
*+-+*
Reporter: Caner Önder
 Attachments: example-persistent-store.xml

Hİ, i have persistency problem with the conf file which i already attached.

When i reboot the cluster and activate it again, i lose data on every reboot 
and also the old tables which i deleted before, appears again.

 



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

[jira] [Commented] (IGNITE-7768) No description for org.apache.ignite.ml.nn.trainers.distributed

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7768:


GitHub user artemmalykh opened a pull request:

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

IGNITE-7768: No description for 
org.apache.ignite.ml.nn.trainers.distributed.



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

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

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

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


commit 0f28f437e60b78a763a7eebc0d51565e0b0e0c80
Author: Artem Malykh 
Date:   2018-02-20T13:26:55Z

IGNITE-7768: Added package-info.




> No description for org.apache.ignite.ml.nn.trainers.distributed
> ---
>
> Key: IGNITE-7768
> URL: https://issues.apache.org/jira/browse/IGNITE-7768
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 2.4
>Reporter: Ilya Suntsov
>Assignee: Artem Malykh
>Priority: Minor
>
> We need to add description for package 
> org.apache.ignite.ml.nn.trainers.distributed



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

[jira] [Updated] (IGNITE-7767) Update WALMode configuration in .NET

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-7767:
---
Labels: MakeTeamcityGreenAgain  (was: )

> Update WALMode configuration in .NET
> 
>
> Key: IGNITE-7767
> URL: https://issues.apache.org/jira/browse/IGNITE-7767
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> In https://issues.apache.org/jira/browse/IGNITE-7594 we changed values for 
> WALMode enum, but .NET code wasn't modified accordingly.



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

[jira] [Commented] (IGNITE-7646) OSGI tests fail to unlock build directory causing following builds to fail to start

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-7646:


Hi [~vveider], 

Is this failure describes failure of 
https://ci.ignite.apache.org/viewLog.html?buildId=1086861=buildResultsDiv=IgniteTests24Java8_IgniteOSGi

and test  IgniteOsgiTestSuite: 
IgniteKarafFeaturesInstallationTest.testAllBundlesActiveAndFeaturesInstalled?

> OSGI tests fail to unlock build directory causing following builds to fail to 
> start
> ---
>
> Key: IGNITE-7646
> URL: https://issues.apache.org/jira/browse/IGNITE-7646
> Project: Ignite
>  Issue Type: Task
>Reporter: Peter Ivanov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain
>
> After running test suite [Ignite Tests 2.4+ \[Java 8\] Ignite 
> OSGi|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgniteOSGi]
>  under Windows based agent, following builds fail to start with error
> {code}
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle1\version0.0\bundle.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle2\version0.0\bundle.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle3\version0.0\bundle.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle4\version0.0\bundle.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle5\version0.0\bundle.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle6\version0.0\bundle.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle7\version0.0\bundle.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle8\version0.0\bundle.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\cache.lock
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\log\karaf.log
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\boot\org.apache.karaf.diagnostic.boot-4.0.2.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\boot\org.apache.karaf.jaas.boot-4.0.2.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\boot\org.apache.karaf.main-4.0.2.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\boot\org.osgi.core-6.0.0.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\javax.annotation-api-1.2.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.karaf.exception-4.0.2.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.bundles.xalan-2.7.2_2.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.bundles.xalan-serializer-2.7.2_1.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.specs.activation-api-1.1-2.5.0.jar
> [16:30:24]Failed to delete file: 
> 

[jira] [Updated] (IGNITE-7646) OSGI tests fail to unlock build directory causing following builds to fail to start

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-7646:
---
Labels: MakeTeamcityGreenAgain  (was: )

> OSGI tests fail to unlock build directory causing following builds to fail to 
> start
> ---
>
> Key: IGNITE-7646
> URL: https://issues.apache.org/jira/browse/IGNITE-7646
> Project: Ignite
>  Issue Type: Task
>Reporter: Peter Ivanov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain
>
> After running test suite [Ignite Tests 2.4+ \[Java 8\] Ignite 
> OSGi|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgniteOSGi]
>  under Windows based agent, following builds fail to start with error
> {code}
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle1\version0.0\bundle.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle2\version0.0\bundle.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle3\version0.0\bundle.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle4\version0.0\bundle.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle5\version0.0\bundle.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle6\version0.0\bundle.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle7\version0.0\bundle.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle8\version0.0\bundle.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\cache.lock
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\log\karaf.log
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\boot\org.apache.karaf.diagnostic.boot-4.0.2.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\boot\org.apache.karaf.jaas.boot-4.0.2.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\boot\org.apache.karaf.main-4.0.2.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\boot\org.osgi.core-6.0.0.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\javax.annotation-api-1.2.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.karaf.exception-4.0.2.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.bundles.xalan-2.7.2_2.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.bundles.xalan-serializer-2.7.2_1.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.specs.activation-api-1.1-2.5.0.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.specs.jaxb-api-2.2-2.5.0.jar
> [16:30:24]Failed to delete file: 
> C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.specs.jaxp-api-1.4-2.5.0.jar
> [16:30:24]Failed to delete file: 
> 

[jira] [Created] (IGNITE-7768) No description for org.apache.ignite.ml.nn.trainers.distributed

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-7768:


 Summary: No description for 
org.apache.ignite.ml.nn.trainers.distributed
 Key: IGNITE-7768
 URL: https://issues.apache.org/jira/browse/IGNITE-7768
 Project: Ignite
  Issue Type: Bug
  Components: documentation
Affects Versions: 2.4
Reporter: Ilya Suntsov
Assignee: Artem Malykh


We need to add description for package 
org.apache.ignite.ml.nn.trainers.distributed



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

[jira] [Created] (IGNITE-7767) Update WALMode configuration in .NET

[Ilya Lantukh (JIRA)]

Ilya Lantukh created IGNITE-7767:


 Summary: Update WALMode configuration in .NET
 Key: IGNITE-7767
 URL: https://issues.apache.org/jira/browse/IGNITE-7767
 Project: Ignite
  Issue Type: Bug
Reporter: Ilya Lantukh
Assignee: Ilya Lantukh


In https://issues.apache.org/jira/browse/IGNITE-7594 we changed values for 
WALMode enum, but .NET code wasn't modified accordingly.



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

[jira] [Created] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-7766:
--

 Summary: Ignite Queries 2: Test always failed 
IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
 Key: IGNITE-7766
 URL: https://issues.apache.org/jira/browse/IGNITE-7766
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Dmitriy Pavlov
Assignee: Alexei Scherbakov


   Ignite Queries 2  
 IgniteBinaryCacheQueryTestSuite2: 
IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%) 

IgniteCacheQueryNodeRestartTxSelfTest.testRestarts  
Current failure:refs/heads/master   #345No changes  
11 Feb 18 03:03
 
junit.framework.AssertionFailedError: On large page size must retry.
 
Last runs fails with 100% probability.



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

[jira] [Commented] (IGNITE-7648) Revert IGNITE_ENABLE_FORCIBLE_NODE_KILL system property.

[Alexei Scherbakov (JIRA)]

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

Alexei Scherbakov commented on IGNITE-7648:
---

[~gvvinblade],

The main point of the patch is to make grid more resilient to faulty 
situations. 

If we cannot connect to node via communication until failure detection 
threshold is reached (it's the main point of patch to try harder), it's not 
usable and can be safely removed from topology.

Look at [1] for details on how it's possible to come into situation then 
discovery is not enough for node removal. This is the reason the feature was 
enabled by default in first place.

It's also protects us from misbehaving nodes who pretend to be alive but do not 
provide valid response to handshakes.

As for proposed change, I think it makes sense. It will allow us to stay within 
failure detection time more precisely.

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






> Revert IGNITE_ENABLE_FORCIBLE_NODE_KILL system property.
> 
>
> Key: IGNITE-7648
> URL: https://issues.apache.org/jira/browse/IGNITE-7648
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.3
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
>Priority: Major
> Fix For: 2.5
>
>
> IGNITE_ENABLE_FORCIBLE_NODE_KILL system property was introduced in 
> IGNITE-5718 as a way to prevent unnecessary node drops in case of short 
> network problems.
> I suppose it's wrong decision to fix it in such way.
> We had faced some issues in our production due to lack of automatic kicking 
> of ill-behaving nodes (on example, hanging due to long GC pauses) until we 
> realised the necessity of changing default behavior via property.
> Right solution is to kick nodes only if failure threshold is reached. Such 
> behavior should be always enabled.
>  



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

[jira] [Commented] (IGNITE-7765) walSegmentSize can be negative in config

[Alexander Belyak (JIRA)]

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

Alexander Belyak commented on IGNITE-7765:
--

can be tested in FileWriteAheadLogmanager.checkWalConfiguration() method.

> walSegmentSize can be negative in config
> 
>
> Key: IGNITE-7765
> URL: https://issues.apache.org/jira/browse/IGNITE-7765
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.2
>Reporter: Alexander Belyak
>Priority: Trivial
>
> Grid use default (64Mb) DataStorageConfiguration.walSegmentSize without 
> warnings if negative value specified, for example if in xml specified 
> something like
>  (overflow)



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

[jira] [Created] (IGNITE-7765) walSegmentSize can be negative in config

[Alexander Belyak (JIRA)]

Alexander Belyak created IGNITE-7765:


 Summary: walSegmentSize can be negative in config
 Key: IGNITE-7765
 URL: https://issues.apache.org/jira/browse/IGNITE-7765
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.2
Reporter: Alexander Belyak


Grid use default (64Mb) DataStorageConfiguration.walSegmentSize without 
warnings if negative value specified, for example if in xml specified something 
like
 (overflow)



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

[jira] [Updated] (IGNITE-7764) MVCC TX: Locking protocol for Key-Value API

[Roman Kondakov (JIRA)]

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

Roman Kondakov updated IGNITE-7764:
---
Description: We need to implement an MVCC-compatible locking protocol for 
Key-Value API. At the moment during transactions with KV operations if entry we 
are going to change is unlocked we do not check if it has been changed by the 
previous transaction. See IGNITE-6935.  (was: We need to implement an 
MVCC-compatible locking protocol for Key-Value API. At the moment during 
transactions with KV operations if entry we are going to change is unlocked we 
do not check if it has been changed by the previous transaction.)

> MVCC TX: Locking protocol for Key-Value API
> ---
>
> Key: IGNITE-7764
> URL: https://issues.apache.org/jira/browse/IGNITE-7764
> Project: Ignite
>  Issue Type: New Feature
>  Components: sql
>Reporter: Roman Kondakov
>Priority: Major
>  Labels: mvcc, sql
>
> We need to implement an MVCC-compatible locking protocol for Key-Value API. 
> At the moment during transactions with KV operations if entry we are going to 
> change is unlocked we do not check if it has been changed by the previous 
> transaction. See IGNITE-6935.



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

[jira] [Created] (IGNITE-7764) MVCC TX: Locking protocol for Key-Value API

[Roman Kondakov (JIRA)]

Roman Kondakov created IGNITE-7764:
--

 Summary: MVCC TX: Locking protocol for Key-Value API
 Key: IGNITE-7764
 URL: https://issues.apache.org/jira/browse/IGNITE-7764
 Project: Ignite
  Issue Type: New Feature
  Components: sql
Reporter: Roman Kondakov


We need to implement an MVCC-compatible locking protocol for Key-Value API. At 
the moment during transactions with KV operations if entry we are going to 
change is unlocked we do not check if it has been changed by the previous 
transaction.



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

[jira] [Updated] (IGNITE-7756) Streamer fails if IgniteUuid is indexed

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov updated IGNITE-7756:

Labels: MakeTeamcityGreenAgain  (was: )

> Streamer fails if IgniteUuid is indexed
> ---
>
> Key: IGNITE-7756
> URL: https://issues.apache.org/jira/browse/IGNITE-7756
> Project: Ignite
>  Issue Type: Bug
>  Components: streaming
>Affects Versions: 2.3
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Minor
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> IgniteDataStreamer are failed to put data to the cache if IgniteUuid is 
> IndexedType.
> Spark tests in IGNITE-7227 are failed because of this issue.
> Reproducer:
> {code:java}
> public void testStreamer() throws Exception {
> Ignite client = grid("client");
> CacheConfiguration ccfg = new CacheConfiguration("UUID_CACHE");
> ccfg.setIndexedTypes(IgniteUuid.class, String.class);
> client.createCache(ccfg);
> try(IgniteDataStreamer cache =
> client.dataStreamer("UUID_CACHE")) {
> for(Integer i=0; i<2; i++)
> cache.addData(IgniteUuid.randomUuid(), i.toString());
> }
> }
> {code}
> Exception stack trace:
> {noformat}
> [23:43:35] (err) Failed to execute compound future reducer: 
> GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false, 
> cancelled=false, err=null, futs=[true, true]][23:43:35] (err) Failed to 
> execute compound future reducer: GridCompoundFuture [rdc=null, initFlag=1, 
> lsnrCalls=0, done=false, cancelled=false, err=null, futs=[true, true]]class 
> org.apache.ignite.IgniteCheckedException: DataStreamer request failed 
> [node=57961924-82ec-4d56-81eb-1a4109a0]
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.onResponse(DataStreamerImpl.java:1900)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$3.onMessage(DataStreamerImpl.java:344)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1554)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1182)
>   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:1089)
>   at 
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:499)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteException: Failed to set initial 
> value for cache entry
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:2135)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.localUpdate(DataStreamProcessor.java:397)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:302)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:59)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:89)
>   ... 6 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to update 
> index, incorrect key class [expCls=org.apache.ignite.lang.IgniteUuid, 
> actualCls=org.apache.ignite.internal.binary.BinaryObjectImpl]
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.typeByValue(GridQueryProcessor.java:1954)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:1877)
>   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:1343)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1207)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:345)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.storeValue(GridCacheMapEntry.java:3527)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:2735)
>   at 
> 

[jira] [Assigned] (IGNITE-7320) Multilevel header in admin panel looks wierd in Safari and Edge

[Alexander Kalinin (JIRA)]

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

Alexander Kalinin reassigned IGNITE-7320:
-

Assignee: Pavel Konstantinov  (was: Alexander Kalinin)

Fixed for Safari. For Edge this artifact still remains.

> Multilevel header in admin panel looks wierd in Safari and Edge
> ---
>
> Key: IGNITE-7320
> URL: https://issues.apache.org/jira/browse/IGNITE-7320
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Pavel Konstantinov
>Priority: Minor
> Attachments: Lk1YqS (1).jpg
>
>




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

[jira] [Commented] (IGNITE-6005) [Test failed] GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-6005:
-

[~dpavlov]

> would this change help to solve continious timeouts in ... 
> GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreSingleNodeFailure
>  (last started)

I have no experience in Team City log analysis, but 
{{GridCachePartitionedDataStructuresFailoverSelfTest extends 
GridCacheAbstractDataStructuresFailoverSelfTest}} so merge of this PR *may* 
help with suite timeouts.


> [Test failed] 
> GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe
> -
>
> Key: IGNITE-6005
> URL: https://issues.apache.org/jira/browse/IGNITE-6005
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> Example of fail
> https://ci.ignite.apache.org/viewLog.html?buildId=762788=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures
> Typical problem is 
> {code}
> org.apache.ignite.IgniteInterruptedException: Failed to wait for asynchronous 
> operation permit (thread got interrupted).
> at 
> org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:805)
> at 
> org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:803)
> at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:961)
> at 
> org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.close(GridCacheSemaphoreImpl.java:1026)
> at 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:458)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.InterruptedException: null
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1301)
> at java.util.concurrent.Semaphore.acquire(Semaphore.java:317)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOpAcquire(GridCacheAdapter.java:4314)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4177)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:196)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4509)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4490)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1324)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:329)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$5.applyx(DataStructuresProcessor.java:635)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.retryTopologySafe(DataStructuresProcessor.java:1519)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeDataStructure(DataStructuresProcessor.java:629)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeSemaphore(DataStructuresProcessor.java:1188)
> at 
> org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.close(GridCacheSemaphoreImpl.java:1023)
> at 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:458)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> 

[jira] [Created] (IGNITE-7763) Ignite CPP tests win32 failure

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-7763:
--

 Summary: Ignite CPP tests win32 failure
 Key: IGNITE-7763
 URL: https://issues.apache.org/jira/browse/IGNITE-7763
 Project: Ignite
  Issue Type: Task
Reporter: Dmitriy Pavlov
Assignee: Igor Sapego


https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePlatformCppWin32
 
aborted
std::exception: Failed to load JVM library.



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

[jira] [Commented] (IGNITE-6005) [Test failed] GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-6005:


[~agoncharuk], can we merge current changes since there is no response from 
[~agura]?

[~NIzhikov], would this change help to solve continious timeouts in 
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgniteDataStructures=%3Cdefault%3E=buildTypeStatusDiv
 

 
GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreSingleNodeFailure
 (last started) 
?

> [Test failed] 
> GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe
> -
>
> Key: IGNITE-6005
> URL: https://issues.apache.org/jira/browse/IGNITE-6005
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> Example of fail
> https://ci.ignite.apache.org/viewLog.html?buildId=762788=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures
> Typical problem is 
> {code}
> org.apache.ignite.IgniteInterruptedException: Failed to wait for asynchronous 
> operation permit (thread got interrupted).
> at 
> org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:805)
> at 
> org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:803)
> at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:961)
> at 
> org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.close(GridCacheSemaphoreImpl.java:1026)
> at 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:458)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.InterruptedException: null
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1301)
> at java.util.concurrent.Semaphore.acquire(Semaphore.java:317)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOpAcquire(GridCacheAdapter.java:4314)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4177)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:196)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4509)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4490)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1324)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:329)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$5.applyx(DataStructuresProcessor.java:635)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.retryTopologySafe(DataStructuresProcessor.java:1519)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeDataStructure(DataStructuresProcessor.java:629)
> at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeSemaphore(DataStructuresProcessor.java:1188)
> at 
> org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.close(GridCacheSemaphoreImpl.java:1023)
> at 
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:458)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> 

[jira] [Assigned] (IGNITE-7762) .NET: Add metrics for entry processor invocations to

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-7762:
--

Assignee: (was: Pavel Tupitsyn)

> .NET: Add metrics for entry processor invocations to
> 
>
> Key: IGNITE-7762
> URL: https://issues.apache.org/jira/browse/IGNITE-7762
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Alexey Kuznetsov
>Priority: Major
>  Labels: .NET, iep-6
>
> Need to add entry processor invocations metric to .Net side 



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

[jira] [Updated] (IGNITE-7762) .NET: Add metrics for entry processor invocations to

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-7762:
---
Description: Add entry processor invocations metric to .NET side   (was: 
Need to add entry processor invocations metric to .Net side )

> .NET: Add metrics for entry processor invocations to
> 
>
> Key: IGNITE-7762
> URL: https://issues.apache.org/jira/browse/IGNITE-7762
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Alexey Kuznetsov
>Priority: Major
>  Labels: .NET, iep-6
>
> Add entry processor invocations metric to .NET side 



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

[jira] [Commented] (IGNITE-7762) .NET: Add metrics for entry processor invocations to

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-7762:


Alexey, where are these metrics on Java side? Can you provide more details?

> .NET: Add metrics for entry processor invocations to
> 
>
> Key: IGNITE-7762
> URL: https://issues.apache.org/jira/browse/IGNITE-7762
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET, iep-6
>
> Need to add entry processor invocations metric to .Net side 



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

[jira] [Updated] (IGNITE-7762) .NET: Add metrics for entry processor invocations to

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-7762:
---
Labels: .NET iep-6  (was: iep-6)

> .NET: Add metrics for entry processor invocations to
> 
>
> Key: IGNITE-7762
> URL: https://issues.apache.org/jira/browse/IGNITE-7762
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET, iep-6
>
> Need to add entry processor invocations metric to .Net side 



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

[jira] [Updated] (IGNITE-7762) .NET: Add metrics for entry processor invocations to

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-7762:
---
Component/s: (was: cache)
 platforms

> .NET: Add metrics for entry processor invocations to
> 
>
> Key: IGNITE-7762
> URL: https://issues.apache.org/jira/browse/IGNITE-7762
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: iep-6
>
> Need to add entry processor invocations metric to .Net side 



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

[jira] [Updated] (IGNITE-7762) .NET: Add metrics for entry processor invocations to

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-7762:
---
Summary: .NET: Add metrics for entry processor invocations to  (was: Add 
metrics for entry processor invocations to .Net)

> .NET: Add metrics for entry processor invocations to
> 
>
> Key: IGNITE-7762
> URL: https://issues.apache.org/jira/browse/IGNITE-7762
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: iep-6
>
> Need to add entry processor invocations metric to .Net side 



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

[jira] [Commented] (IGNITE-6083) Null value have appear in the entry processor, but the entry is existing

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-6083:
--

[~Alexey Kuznetsov] I am not sure the fix is correct. Can you please explain 
how exactly the value becomes null and why only second entry processor observes 
the null value? 

> Null value have appear in the entry processor, but the entry is existing
> 
>
> Key: IGNITE-6083
> URL: https://issues.apache.org/jira/browse/IGNITE-6083
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Vladislav Pyatkov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Attachments: EntryProcessorInOptimisticTxTest.java
>
>
> In one thread load some data in a cache, after that I have execute 
> OPTIMISTIC, SERIALIZABLE transaction with two {{IgniteCache.invoke()}} 
> methods.
> The value had been corrected at first {{EntryProcessor}}, but it is NULL at 
> second.



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

[jira] [Updated] (IGNITE-7762) Add metrics for entry processor invocations to .Net

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-7762:
-
Description: Need to add entry processor invocations metric to .Net side 

> Add metrics for entry processor invocations to .Net
> ---
>
> Key: IGNITE-7762
> URL: https://issues.apache.org/jira/browse/IGNITE-7762
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: iep-6
>
> Need to add entry processor invocations metric to .Net side 



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

[jira] [Updated] (IGNITE-7762) Add metrics for entry processor invocation to .Net

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-7762:
-
Summary: Add metrics for entry processor invocation to .Net  (was: Add 
metrics for entry processor ibvocation to .Net)

> Add metrics for entry processor invocation to .Net
> --
>
> Key: IGNITE-7762
> URL: https://issues.apache.org/jira/browse/IGNITE-7762
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: iep-6
>




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

[jira] [Updated] (IGNITE-7762) Add metrics for entry processor invocations to .Net

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-7762:
-
Summary: Add metrics for entry processor invocations to .Net  (was: Add 
metrics for entry processor invocation to .Net)

> Add metrics for entry processor invocations to .Net
> ---
>
> Key: IGNITE-7762
> URL: https://issues.apache.org/jira/browse/IGNITE-7762
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: iep-6
>




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

[jira] [Created] (IGNITE-7762) Add metrics for entry processor ibvocation to .Net

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-7762:


 Summary: Add metrics for entry processor ibvocation to .Net
 Key: IGNITE-7762
 URL: https://issues.apache.org/jira/browse/IGNITE-7762
 Project: Ignite
  Issue Type: Sub-task
  Components: cache
Reporter: Alexey Kuznetsov
Assignee: Pavel Tupitsyn






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

[jira] [Commented] (IGNITE-7747) WAL manage getAndReserveWalFiles should not throw exception if segments not found

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7747:


Github user asfgit closed the pull request at:

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


> WAL manage getAndReserveWalFiles should not throw exception if segments not 
> found
> -
>
> Key: IGNITE-7747
> URL: https://issues.apache.org/jira/browse/IGNITE-7747
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Affects Versions: 2.3, 2.4
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.5
>
>
> [TC run| 
> https://ci.ignite.apache.org/viewLog.html?buildId=1101207=buildResultsDiv=IgniteTests24Java8_RunAll]



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

[jira] [Commented] (IGNITE-7263) Daemon-mode Ignite node should not open client port (10800)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7263:


Github user asfgit closed the pull request at:

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


> Daemon-mode Ignite node should not open client port (10800)
> --
>
> Key: IGNITE-7263
> URL: https://issues.apache.org/jira/browse/IGNITE-7263
> Project: Ignite
>  Issue Type: Bug
>  Components: thin client, visor
>Affects Versions: 2.1
>Reporter: Alexey Popov
>Assignee: Pavel Vinokurov
>Priority: Minor
> Fix For: 2.5
>
>
> When I run a Visor console with default configuration file it opens a default 
> port (10800) for ODBC driver connection (and for thin JDBC, and for new 
> "thin" client).
> Then I run several Ignite nodes.
> So after that, the ODBC driver with default settings goes directly to a Visor 
> (daemon-mode Ignite) and does not able to get any data (daemon-mode Ignite 
> does not keep any data)
> It is better to avoid such situation.



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