[jira] [Commented] (IGNITE-5444) Collections.singletonList is not properly serialized by binary marshaller

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-5444:
-

BTW, before submitting for review, don't forget to move ticket to Patch 
Available.

> Collections.singletonList is not properly serialized by binary marshaller
> -
>
> Key: IGNITE-5444
> URL: https://issues.apache.org/jira/browse/IGNITE-5444
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
>Assignee: William Do
> Fix For: 2.1
>
> Attachments: BinaryObjectSingletonList.java
>
>
> Test attached. {{Collections.singletonList}} is apparently serialized by 
> optimized marshaller, because when deserialized, it doesn't return collection 
> of binary objects, but rather collection of deserialized objects.
> Most likely the reason for this is that {{Collections.singletonList}} is not 
> recognized by {{BinaryUtils.knownCollection}} method.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5444) Collections.singletonList is not properly serialized by binary marshaller

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-5444:
-

Hi William. I left a comment in Upsource: 
http://reviews.ignite.apache.org/ignite/review/IGNT-CR-206

> Collections.singletonList is not properly serialized by binary marshaller
> -
>
> Key: IGNITE-5444
> URL: https://issues.apache.org/jira/browse/IGNITE-5444
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
>Assignee: William Do
> Fix For: 2.1
>
> Attachments: BinaryObjectSingletonList.java
>
>
> Test attached. {{Collections.singletonList}} is apparently serialized by 
> optimized marshaller, because when deserialized, it doesn't return collection 
> of binary objects, but rather collection of deserialized objects.
> Most likely the reason for this is that {{Collections.singletonList}} is not 
> recognized by {{BinaryUtils.knownCollection}} method.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5352) Improve ML main page documentation

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-5352:

Description: 
[~chief], please work with [~nivanov] to enhance the existing ML documentation 
we have on the main page:
https://apacheignite.readme.io/v2.1/docs/machine-learning

Here is the following should be listed:
* main goals of the lib.
* how it's implemented and why it's better than others.
* use cases.
* etc.?

  was:
[~chief], please work with [~nivanov] to enhance the existing ML documentation 
we have on the main page:
https://apacheignite.readme.io/v2.0/docs/machine-learning-beta-21

Here is the following should be listed:
* main goals of the lib.
* how it's implemented and why it's better than others.
* use cases.
* etc.?


> Improve ML main page documentation
> --
>
> Key: IGNITE-5352
> URL: https://issues.apache.org/jira/browse/IGNITE-5352
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Yury Babak
> Fix For: 2.1
>
>
> [~chief], please work with [~nivanov] to enhance the existing ML 
> documentation we have on the main page:
> https://apacheignite.readme.io/v2.1/docs/machine-learning
> Here is the following should be listed:
> * main goals of the lib.
> * how it's implemented and why it's better than others.
> * use cases.
> * etc.?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5346) Document SQL Changes: CREATE/DROP, global schema, persistence

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-5346:

Description: 
We need to document the new features to be added to DDL in 2.1:
* CREATE and DROP table.
* Global default schema. 
* Configuration persistence during restarts.

In addition, the limitations have to be listed as well:
* no way to set a schema.
* ALTER TABLE is to be supported.
* something?

Summary of all the changes are here:
http://apache-ignite-developers.2346864.n4.nabble.com/Summary-of-SQL-changes-in-2-1-td18278.html

Here is a page copy for 2.1:
https://apacheignite.readme.io/v2.1/docs/distributed-ddl

Plus, since the schema becomes global it makes sense to revisit all the 
examples we have where a cache name is used as schema (JOINS). Apply the 
changes on 2.1 page if needed:
https://apacheignite.readme.io/v2.1/docs/sql-queries

  was:
We need to document the new features to be added to DDL in 2.1:
* CREATE and DROP table.
* Global default schema. 
* Configuration persistence during restarts.

In addition, the limitations have to be listed as well:
* no way to set a schema.
* ALTER TABLE is to be supported.
* something?

Summary of all the changes are here:
http://apache-ignite-developers.2346864.n4.nabble.com/Summary-of-SQL-changes-in-2-1-td18278.html

Here is a page copy for 2.1:
https://apacheignite.readme.io/v2.0/docs/distributed-ddl-21

Plus, since the schema becomes global it makes sense to revisit all the 
examples we have where a cache name is used as schema (JOINS). Apply the 
changes on 2.1 page if needed:
https://apacheignite.readme.io/v2.0/docs/distributed-queries-21


> Document SQL Changes: CREATE/DROP, global schema, persistence 
> --
>
> Key: IGNITE-5346
> URL: https://issues.apache.org/jira/browse/IGNITE-5346
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> We need to document the new features to be added to DDL in 2.1:
> * CREATE and DROP table.
> * Global default schema. 
> * Configuration persistence during restarts.
> In addition, the limitations have to be listed as well:
> * no way to set a schema.
> * ALTER TABLE is to be supported.
> * something?
> Summary of all the changes are here:
> http://apache-ignite-developers.2346864.n4.nabble.com/Summary-of-SQL-changes-in-2-1-td18278.html
> Here is a page copy for 2.1:
> https://apacheignite.readme.io/v2.1/docs/distributed-ddl
> Plus, since the schema becomes global it makes sense to revisit all the 
> examples we have where a cache name is used as schema (JOINS). Apply the 
> changes on 2.1 page if needed:
> https://apacheignite.readme.io/v2.1/docs/sql-queries



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5346) Document SQL Changes: CREATE/DROP, global schema, persistence

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-5346:
-

[~vozerov], I've created version 2.1 for the overall documentation. Feel free 
to edit the pages directly but make sure you're on version `2.1` of the doc!

> Document SQL Changes: CREATE/DROP, global schema, persistence 
> --
>
> Key: IGNITE-5346
> URL: https://issues.apache.org/jira/browse/IGNITE-5346
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> We need to document the new features to be added to DDL in 2.1:
> * CREATE and DROP table.
> * Global default schema. 
> * Configuration persistence during restarts.
> In addition, the limitations have to be listed as well:
> * no way to set a schema.
> * ALTER TABLE is to be supported.
> * something?
> Summary of all the changes are here:
> http://apache-ignite-developers.2346864.n4.nabble.com/Summary-of-SQL-changes-in-2-1-td18278.html
> Here is a page copy for 2.1:
> https://apacheignite.readme.io/v2.0/docs/distributed-ddl-21
> Plus, since the schema becomes global it makes sense to revisit all the 
> examples we have where a cache name is used as schema (JOINS). Apply the 
> changes on 2.1 page if needed:
> https://apacheignite.readme.io/v2.0/docs/distributed-queries-21



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5345) Update JDBC driver documentation considering the new implementation

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-5345:
-

Folks, I've created version 2.1 for the overall documentation. Feel free to 
edit this page directly:
https://apacheignite.readme.io/v2.1/docs/jdbc-driver

Make sure that you're on version `2.1` of the doc!

> Update JDBC driver documentation considering the new implementation
> ---
>
> Key: IGNITE-5345
> URL: https://issues.apache.org/jira/browse/IGNITE-5345
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> The next version of the JDBC driver is to be released in 2.1. We need to 
> refine the existing documentation explaining:
> * how to connect to the cluster.
> * what's the schema format and options.
> * move the legacy driver versions (like the Ignite client based) to the end 
> of the documentation.
> Here is a documentation page for 2.1:
> https://apacheignite.readme.io/v2.1/docs/jdbc-driver
> [~vozerov], let's discuss how to format the page if needed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5345) Update JDBC driver documentation considering the new implementation

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-5345:

Description: 
The next version of the JDBC driver is to be released in 2.1. We need to refine 
the existing documentation explaining:
* how to connect to the cluster.
* what's the schema format and options.
* move the legacy driver versions (like the Ignite client based) to the end of 
the documentation.

Here is a documentation page for 2.1:
https://apacheignite.readme.io/v2.1/docs/jdbc-driver

[~vozerov], let's discuss how to format the page if needed.

  was:
The next version of the JDBC driver is to be released in 2.1. We need to refine 
the existing documentation explaining:
* how to connect to the cluster.
* what's the schema format and options.
* move the legacy driver versions (like the Ignite client based) to the end of 
the documentation.

Here is a hidden documentation page for 2.1:
https://apacheignite.readme.io/v2.0/docs/jdbc-driver-21

[~vozerov], let's discuss how to format the page if needed.


> Update JDBC driver documentation considering the new implementation
> ---
>
> Key: IGNITE-5345
> URL: https://issues.apache.org/jira/browse/IGNITE-5345
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> The next version of the JDBC driver is to be released in 2.1. We need to 
> refine the existing documentation explaining:
> * how to connect to the cluster.
> * what's the schema format and options.
> * move the legacy driver versions (like the Ignite client based) to the end 
> of the documentation.
> Here is a documentation page for 2.1:
> https://apacheignite.readme.io/v2.1/docs/jdbc-driver
> [~vozerov], let's discuss how to format the page if needed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5157) Document Page Memory Defragmentation

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-5157:

Description: Document how the durable memory deals with memory 
fragmentation.  (was: Document how the page memory deal with memory 
fragmentation:
https://apacheignite.readme.io/docs/page-memory)

> Document Page Memory Defragmentation
> 
>
> Key: IGNITE-5157
> URL: https://issues.apache.org/jira/browse/IGNITE-5157
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.1
>
>
> Document how the durable memory deals with memory fragmentation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5294) Document Persistent Store

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-5294:
-

Here is a new page for the persistent store documentation:
https://apacheignite.readme.io/v2.1/docs/distributed-persistent-store

> Document Persistent Store
> -
>
> Key: IGNITE-5294
> URL: https://issues.apache.org/jira/browse/IGNITE-5294
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.1
>
>
> Document the Persistent Store. Use these wiki pages as reference:
> https://cwiki.apache.org/confluence/display/IGNITE/Persistent+Store+Overview
> https://cwiki.apache.org/confluence/display/IGNITE/Persistent+Store+Internal+Design
> Pages to fill out or update:
> * Enhance the data loading page: 
> https://apacheignite.readme.io/v2.0/docs/data-loading
> * Rework the existing persistent store page: 
> https://apacheignite.readme.io/v2.0/docs/persistent-store
> * Create the page for the Ignite's distributed persistent store: 
> https://apacheignite.readme.io/v2.0/docs/distributed-persistent-store
> * Create an overview page. Describe the difference between all the storages 
> Ignite supports.
> * Add a link to Hadoop as a persistent store alternative.
> * Update the page memory documentation adding a paragraph about the 
> persistent store: https://apacheignite.readme.io/v2.0/docs/page-memory
> * Update the eviction documentation telling more about the persistent store: 
> https://apacheignite.readme.io/v2.0/docs/evictions



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-5285) Update metrics documentation

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-5285:
---

Assignee: Prachi Garg  (was: Denis Magda)

> Update metrics documentation
> 
>
> Key: IGNITE-5285
> URL: https://issues.apache.org/jira/browse/IGNITE-5285
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Prachi Garg
> Fix For: 2.1
>
>
> 1) Describe new metrics related to the Persistent Store.
> 2) Update the existing metrics: 
> https://issues.apache.org/jira/browse/IGNITE-5124



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5285) Update metrics documentation

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-5285:
-

[~pgarg], please review this doc and close the ticket:
https://apacheignite.readme.io/v2.1/docs/memory-metrics

> Update metrics documentation
> 
>
> Key: IGNITE-5285
> URL: https://issues.apache.org/jira/browse/IGNITE-5285
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.1
>
>
> 1) Describe new metrics related to the Persistent Store.
> 2) Update the existing metrics: 
> https://issues.apache.org/jira/browse/IGNITE-5124



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5491) .NET: PersistentStoreMetrics

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5491:
---
Summary: .NET: PersistentStoreMetrics  (was: .NET: PersistenceMetrics)

> .NET: PersistentStoreMetrics
> 
>
> Key: IGNITE-5491
> URL: https://issues.apache.org/jira/browse/IGNITE-5491
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> * {{PersistentStoreConfiguration.EnableMetrics}}, {{RateTimeInterval}}, 
> {{SubIntervals}} properties
> * {{PersistenceMetrics}} class
> * {{IIgnite.GetPersistenceMetrics()}} method



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5491) .NET: PersistentStoreMetrics

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5491:


Proper name is "PersistentStoreMetrics".

> .NET: PersistentStoreMetrics
> 
>
> Key: IGNITE-5491
> URL: https://issues.apache.org/jira/browse/IGNITE-5491
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> * {{PersistentStoreConfiguration.EnableMetrics}}, {{RateTimeInterval}}, 
> {{SubIntervals}} properties
> * {{PersistenceMetrics}} class
> * {{IIgnite.GetPersistenceMetrics()}} method



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5719) .NET: Exception in StreamReceiver is not propagated to caller

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5719:
--

 Summary: .NET: Exception in StreamReceiver is not propagated to 
caller
 Key: IGNITE-5719
 URL: https://issues.apache.org/jira/browse/IGNITE-5719
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 2.0
Reporter: Pavel Tupitsyn
 Fix For: 2.2


When exception is thrown in user-defined StreamReceiver, .NET stack trace is 
lost, only Java traces are available.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (IGNITE-5716) .NET: Negative field offset values can be observed on 2-byte offsets

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-5716.

Resolution: Fixed

> .NET: Negative field offset values can be observed on 2-byte offsets
> 
>
> Key: IGNITE-5716
> URL: https://issues.apache.org/jira/browse/IGNITE-5716
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Blocker
>  Labels: .NET
> Fix For: 2.1
>
>
> {{BinaryObjectSchemaSerializer.WriteSchema}} uses {{ushort.MaxValue}} as a 
> boundary for 2-byte offsets. {{ReadSchema}} uses {{ReadShort}}, which returns 
> negative offsets for anything above {{short.MaxValue}}.
> * Ensure that all offsets are always non-negative (use uint in 
> {{BinaryObjectSchemaField}} probably)
> * Check how Java handles this
> * Add tests for all edge cases



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5716) .NET: Negative field offset values can be observed on 2-byte offsets

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5716:


Fixed in {{ignite-2.1}}: {{82e5f8a6553323e793c01c54e24dda6d47188ce6}}

> .NET: Negative field offset values can be observed on 2-byte offsets
> 
>
> Key: IGNITE-5716
> URL: https://issues.apache.org/jira/browse/IGNITE-5716
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Blocker
>  Labels: .NET
> Fix For: 2.1
>
>
> {{BinaryObjectSchemaSerializer.WriteSchema}} uses {{ushort.MaxValue}} as a 
> boundary for 2-byte offsets. {{ReadSchema}} uses {{ReadShort}}, which returns 
> negative offsets for anything above {{short.MaxValue}}.
> * Ensure that all offsets are always non-negative (use uint in 
> {{BinaryObjectSchemaField}} probably)
> * Check how Java handles this
> * Add tests for all edge cases



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-5369) Add possibility to generate alias for primary key in WebConsole

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-5369:


   Resolution: Fixed
 Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)
Fix Version/s: 2.1

Please test in 2.1

> Add possibility to generate alias for primary key in WebConsole
> ---
>
> Key: IGNITE-5369
> URL: https://issues.apache.org/jira/browse/IGNITE-5369
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.0
>Reporter: Evgenii Zhuravlev
>Assignee: Pavel Konstantinov
> Fix For: 2.1
>
>
> Add field with alias name for primary key, that wiil be used in 
> QueryEntity.setKeyFieldName
> Automatically assign key field alias on import of model.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-4831) Add an option to disable MBeans

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4831:


GitHub user AMashenkov opened a pull request:

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

IGNITE-4831: Option to disable MBeans.



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

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

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

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


commit cfc3d0f1ea61eabc75bb4d13699958495edfdfd2
Author: Andrey V. Mashenkov 
Date:   2017-07-04T15:21:10Z

WIP.

commit a93c5fb8b6841c6f9cc5196b5cc6dd20390cb18b
Author: Andrey V. Mashenkov 
Date:   2017-07-04T15:21:10Z

WIP.

commit 18c5d5ead54cb5ca1db0cdd20cc64f85e58403b1
Author: Andrey V. Mashenkov 
Date:   2017-07-04T17:24:52Z

WIP.

commit 552c32e5387c94a403228931d5625ce1a53d871d
Author: Andrey V. Mashenkov 
Date:   2017-07-07T16:01:22Z

Tests added

commit 731dcdfef81fc1f24ad98cf9ee98475df920d820
Author: Andrey V. Mashenkov 
Date:   2017-07-07T16:03:22Z

Tests added




> Add an option to disable MBeans
> ---
>
> Key: IGNITE-4831
> URL: https://issues.apache.org/jira/browse/IGNITE-4831
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.8
>Reporter: Valentin Kulichenko
>Assignee: Andrew Mashenkov
> Fix For: 2.2
>
>
> There are multiple MBeans registered by Ignite and there is no way to avoid 
> their registration (in case they're not allowed for security reasons for 
> example). We should have a system property that will disable MBeans.
> In addition, if MBean registration throws a {{RuntimeException}}, this 
> exception is not properly handled. For example, if it happens during cache 
> creation, {{createCache}} method hangs forever.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4756) Print info about partition distribution to log

[Taras Ledkov (JIRA)]

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

Taras Ledkov updated IGNITE-4756:
-
Description: 
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to print warn message only when nodes count differs more then 
threshold;
# The statistic is calculated and printed only for the local node;
# Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and 
calculated for new {{idealAssignment}}.
# Message format is
{noformat}
Local node affinity assignment distribution is not ideal [cache=, 
expectedPrimary=, 
exectedBackups=, primary=, 
backups=].
{noformat}
e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
{noformat}
Local node affinity assignment distribution is not ideal [cache=test, 
expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%), 
backups=4(100%)].
{noformat}

  was:
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to print warn message only when nodes count differs more then 
threshold;
# The statistic is calculated and printed only for the local node;
# Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and 
calculated for new {{idealAssignment}}.
# Message format is
{noformat}
Local node affinity assignment distribution is not ideal [cache=, 
expectedPrimary=, 
exectedBackups=, primary=, 
backups=].
{noformat}
e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
{noformat}
Local node affinity assignment distribution is not ideal [cache=test, 
expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%), 
backups= 4(100%)].
{noformat}


> Print info about partition distribution to log 
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
>  Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even 
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
> value 0.1 to print warn message only when nodes count differs more then 
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and 
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=, 
> expectedPrimary=, 
> exectedBackups=, 
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test, 
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%), 
> backups=4(100%)].
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4756) Print info about partition distribution to log

[Taras Ledkov (JIRA)]

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

Taras Ledkov updated IGNITE-4756:
-
Description: 
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to print warn message only when nodes count differs more then 
threshold;
# The statistic is calculated and printed only for the local node;
# Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and 
calculated for new {{idealAssignment}}.
# Message format is
{noformat}
Local node affinity assignment distribution is not ideal [cache=, 
expectedPrimary=, 
exectedBackups=, primary=, 
backups=].
{noformat}
e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
{noformat}
Local node affinity assignment distribution is not ideal [cache=test, 
expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%), 
backups= 4(100%)].
{noformat}

  was:
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to print warn message only when nodes count differs more then 
threshold;
# The statistic is calculated and printed only for the local node;
# Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and 
calculated for new {{idealAssignment}}.
# Message format is
{noformat}
Local node affinity assignment distribution is not ideal [cache=, 
expectedPrimary=, 
exectedBackups=, primary=, 
backups=].
{noformat}
e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
{noformat}
Local node affinity assignment distribution is not ideal [cache=test, 
expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%), 
backups= 4(100 %)].
{noformat}


> Print info about partition distribution to log 
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
>  Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even 
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
> value 0.1 to print warn message only when nodes count differs more then 
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and 
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=, 
> expectedPrimary=, 
> exectedBackups=, 
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test, 
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%), 
> backups= 4(100%)].
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4756) Print info about partition distribution to log

[Taras Ledkov (JIRA)]

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

Taras Ledkov updated IGNITE-4756:
-
Description: 
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to print warn message only when nodes count differs more then 
threshold;
# The statistic is calculated and printed only for the local node;
# Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and 
calculated for new {{idealAssignment}}.
# Message format is
{noformat}
Local node affinity assignment distribution is not ideal [cache=, 
expectedPrimary=, 
exectedBackups=, primary=, 
backups=].
{noformat}
e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
{noformat}
Local node affinity assignment distribution is not ideal [cache=test, 
expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%), 
backups= 4(100 %)].
{noformat}

  was:
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to print warn message only when nodes count differs more then 
threshold;
# The statistic is calculated and printed only for the local node;
# Message format is
{noformat}
Local node affinity assignment distribution is not ideal [cache=, 
expected=, found=[, 
 ..., ]].
{noformat}
e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
{noformat}
Local node affinity assignment distribution is not ideal [cache=test, 
expected=1.33 (33.3%), found=[1 (25%), 2 (50%), 3(75%)]].
{noformat}


> Print info about partition distribution to log 
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
>  Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even 
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
> value 0.1 to print warn message only when nodes count differs more then 
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and 
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=, 
> expectedPrimary=, 
> exectedBackups=, 
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test, 
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%), 
> backups= 4(100 %)].
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5694) IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover() fails sometimes

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk updated IGNITE-5694:
-
Fix Version/s: 2.1

> IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover() 
> fails sometimes
> -
>
> Key: IGNITE-5694
> URL: https://issues.apache.org/jira/browse/IGNITE-5694
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>Assignee: Alexey Goncharuk
>  Labels: test-fail
> Fix For: 2.1
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5701) Some nodes have partitionUpdateCounter == 0 after rebalancing

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk updated IGNITE-5701:
-
Fix Version/s: 2.1

> Some nodes have partitionUpdateCounter == 0 after rebalancing
> -
>
> Key: IGNITE-5701
> URL: https://issues.apache.org/jira/browse/IGNITE-5701
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>Assignee: Alexey Goncharuk
> Fix For: 2.1
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (IGNITE-5716) .NET: Negative field offset values can be observed on 2-byte offsets

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5716:
---
Comment: was deleted

(was: Found another problem in {{BinaryReader.ReadSchema}}: {{ReadInt}} is 
always used for offsets, which is not correct.)

> .NET: Negative field offset values can be observed on 2-byte offsets
> 
>
> Key: IGNITE-5716
> URL: https://issues.apache.org/jira/browse/IGNITE-5716
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Blocker
>  Labels: .NET
> Fix For: 2.1
>
>
> {{BinaryObjectSchemaSerializer.WriteSchema}} uses {{ushort.MaxValue}} as a 
> boundary for 2-byte offsets. {{ReadSchema}} uses {{ReadShort}}, which returns 
> negative offsets for anything above {{short.MaxValue}}.
> * Ensure that all offsets are always non-negative (use uint in 
> {{BinaryObjectSchemaField}} probably)
> * Check how Java handles this
> * Add tests for all edge cases



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5087) Enum comparison fails after marshal-unmarshal with BinaryMarshaller.

[Amelchev Nikita (JIRA)]

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

Amelchev Nikita commented on IGNITE-5087:
-

[~amashenkov]  I done it. It seems there are no problems at latest master.

> Enum comparison fails after marshal-unmarshal with BinaryMarshaller.
> 
>
> Key: IGNITE-5087
> URL: https://issues.apache.org/jira/browse/IGNITE-5087
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 1.9
>Reporter: Andrew Mashenkov
>Assignee: Amelchev Nikita
> Fix For: 2.2
>
> Attachments: EnumBinaryMarshallerBug.java
>
>
> PFA repro.
> It fails on 1.9 and on 2.0-snapshot as well.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5711) SQL: It should be possible to execute SQL queries over cache with no indexed types

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5711:


GitHub user alexpaschenko opened a pull request:

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

IGNITE-5711 Allowed to run queries on caches without query entities.



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

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

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

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


commit 817c102d46abea236199a7f161a6f18403014f99
Author: Alexander Paschenko 
Date:   2017-07-07T15:30:09Z

IGNITE-5711 Allowed to run queries on caches without query entities.




> SQL: It should be possible to execute SQL queries over cache with no indexed 
> types
> --
>
> Key: IGNITE-5711
> URL: https://issues.apache.org/jira/browse/IGNITE-5711
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.1
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4756) Print info about partition distribution to log

[Taras Ledkov (JIRA)]

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

Taras Ledkov updated IGNITE-4756:
-
Description: 
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to print warn message only when nodes count differs more then 
threshold;
# The statistic is calculated and printed only for the local node;
# Message format is
{noformat}
Local node affinity assignment distribution is not ideal [cache=, 
expected=, found=[, 
 ..., ]].
{noformat}
e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
{noformat}
Local node affinity assignment distribution is not ideal [cache=test, 
expected=1.33 (33.3%), found=[1 (25%), 2 (50%), 3(75%)]].
{noformat}

  was:
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to print warn message only when nodes count differs more then 
threshold;
# The statistic is calculated and printed only for the local node;
# Message format is
{noformat}
Local node affinity assignment distribution is not ideal [cache=, 
expected=, found=[, 
 ..., ]].
{noformat}
e.g. for cache with name "test", 2 backups and (partitions count / nodes count) 
== 100 :
{noformat}
Local node affinity assignment distribution is not ideal [cache=test, 
expected=100 (10%), found=[100 (10%), 150 (15%), 500 (50%)]].
{noformat}


> Print info about partition distribution to log 
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
>  Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even 
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
> value 0.1 to print warn message only when nodes count differs more then 
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=, 
> expected=, found=[, 
>  ..., ]].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test, 
> expected=1.33 (33.3%), found=[1 (25%), 2 (50%), 3(75%)]].
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4756) Print info about partition distribution to log

[Taras Ledkov (JIRA)]

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

Taras Ledkov updated IGNITE-4756:
-
Description: 
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to print warn message only when nodes count differs more then 
threshold;
# The statistic is calculated and printed only for the local node;
# Message format is
{noformat}
Local node affinity assignment distribution is not ideal [cache=, 
expected=, found=[, 
 ..., ]].
{noformat}
e.g. for cache with name "test", 2 backups and (partitions count / nodes count) 
== 100 :
{noformat}
Local node affinity assignment distribution is not ideal [cache=test, 
expected=100 (10%), found=[100 (10%), 150 (15%), 500 (50%)]].
{noformat}

  was:
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to print warn message only when nodes count differs more then 
threshold;
# The statistic is calculated and printed only for the local node;
# Message format is
{noformat}
Affinity assignment distribution is uneven [cache=, 
ideal=, distribution=[, 
 ..., ]].
{noformat}
e.g. for cache with name "test", 2 backups and (partitions count / nodes count) 
== 100 :
{noformat}
Affinity assignment distribution is uneven [cache=test, ideal=100 (10%), 
distribution=[100 (10%), 150 (15%), 500 (50%)]].
{noformat}


> Print info about partition distribution to log 
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
>  Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even 
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
> value 0.1 to print warn message only when nodes count differs more then 
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=, 
> expected=, found=[, 
>  ..., ]].
> {noformat}
> e.g. for cache with name "test", 2 backups and (partitions count / nodes 
> count) == 100 :
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test, 
> expected=100 (10%), found=[100 (10%), 150 (15%), 500 (50%)]].
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4756) Print info about partition distribution to log

[Taras Ledkov (JIRA)]

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

Taras Ledkov updated IGNITE-4756:
-
Description: 
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to print warn message only when nodes count differs more then 
threshold;
# The statistic is calculated and printed only for the local node;
# Message format is
{noformat}
Affinity assignment distribution is uneven [cache=, 
ideal=, distribution=[, 
 ..., ]].
{noformat}
e.g. for cache with name "test", 2 backups and (partitions count / nodes count) 
== 100 :
{noformat}
Affinity assignment distribution is uneven [cache=test, ideal=100 (10%), 
distribution=[100 (10%), 150 (15%), 500 (50%)]].
{noformat}

  was:
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to print warn message only when nodes count differs more then 
threshold;
# The statistic is calculated and printed only for the local node;
# Message format is
{noformat}
Affinity assignment distribution is not even [cache=, 
ideal=, distribution=[, 
 ..., ]].
{noformat}
e.g. for cache with name "test", 2 backups and (partitions count / nodes count) 
== 100 :
{noformat}
Affinity assignment distribution is not even [cache=test, ideal=100 (10%), 
distribution=[100 (10%), 150 (15%), 500 (50%)]].
{noformat}


> Print info about partition distribution to log 
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
>  Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even 
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
> value 0.1 to print warn message only when nodes count differs more then 
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Message format is
> {noformat}
> Affinity assignment distribution is uneven [cache=, 
> ideal=, distribution=[, 
>  ..., ]].
> {noformat}
> e.g. for cache with name "test", 2 backups and (partitions count / nodes 
> count) == 100 :
> {noformat}
> Affinity assignment distribution is uneven [cache=test, ideal=100 (10%), 
> distribution=[100 (10%), 150 (15%), 500 (50%)]].
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4756) Print info about partition distribution to log

[Taras Ledkov (JIRA)]

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

Taras Ledkov updated IGNITE-4756:
-
Description: 
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to print warn message only when nodes count differs more then 
threshold;
# The statistic is calculated and printed only for the local node;
# Message format is
{noformat}
Affinity assignment distribution is not even [cache=, 
ideal=, distribution=[, 
 ..., ]].
{noformat}
e.g. for cache with name "test", 2 backups and (partitions count / nodes count) 
== 100 :
{noformat}
Affinity assignment distribution is not even [cache=test, ideal=100 (10%), 
distribution=[100 (10%), 150 (15%), 500 (50%)]].
{noformat}

  was:
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to print warn message only when nodes count differs more then 
threshold;
# The statistic is calculated and printed only for the local node;
# Message format is
{noformat}
Affinity assignment distribution is not even [cache=, 
even=, distribution=[, 
 ..., ]].
{noformat}
e.g. for cache with name "test", 2 backups and (partitions count / nodes count) 
== 100 :
{noformat}
Affinity assignment distribution is not even [cache=test, even=100 (10%), 
distribution=[100 (10%), 150 (15%), 500 (50%)]].
{noformat}


> Print info about partition distribution to log 
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
>  Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even 
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
> value 0.1 to print warn message only when nodes count differs more then 
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Message format is
> {noformat}
> Affinity assignment distribution is not even [cache=, 
> ideal=, distribution=[, 
>  ..., ]].
> {noformat}
> e.g. for cache with name "test", 2 backups and (partitions count / nodes 
> count) == 100 :
> {noformat}
> Affinity assignment distribution is not even [cache=test, ideal=100 (10%), 
> distribution=[100 (10%), 150 (15%), 500 (50%)]].
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4756) Print info about partition distribution to log

[Taras Ledkov (JIRA)]

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

Taras Ledkov updated IGNITE-4756:
-
Description: 
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to print warn message only when nodes count differs more then 
threshold;
# The statistic is calculated and printed only for the local node;
# Message format is
{noformat}
Affinity assignment distribution is not even [cache=, 
even=, distribution=[, 
 ..., ]].
{noformat}
e.g. for cache with name "test", 2 backups and (partitions count / nodes count) 
== 100 :
{noformat}
Affinity assignment distribution is not even [cache=test, even=100 (10%), 
distribution=[100 (10%), 150 (15%), 500 (50%)]].
{noformat}

  was:
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to print warn message only when nodes count differs more then 
threshold;
# The statistic is calculated and printed only for the local node;
# Message format is
{noformat}
Affinity assignment distribution not even [cache=, 
even=, distribution=[, 
 ..., ]].
{noformat}
e.g. for cache with name "test", 2 backups and (partitions count / nodes count) 
== 100 :
{noformat}
Affinity assignment distribution not even [cache=test, even=100 (10%), 
distribution=[100 (10%), 150 (15%), 500 (50%)]].
{noformat}


> Print info about partition distribution to log 
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
>  Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even 
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
> value 0.1 to print warn message only when nodes count differs more then 
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Message format is
> {noformat}
> Affinity assignment distribution is not even [cache=, 
> even=, distribution=[, 
>  ..., ]].
> {noformat}
> e.g. for cache with name "test", 2 backups and (partitions count / nodes 
> count) == 100 :
> {noformat}
> Affinity assignment distribution is not even [cache=test, even=100 (10%), 
> distribution=[100 (10%), 150 (15%), 500 (50%)]].
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (IGNITE-5554) ServiceProcessor may process failed reassignments in timeout thread

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov resolved IGNITE-5554.
---
Resolution: Fixed

> ServiceProcessor may process failed reassignments in timeout thread
> ---
>
> Key: IGNITE-5554
> URL: https://issues.apache.org/jira/browse/IGNITE-5554
> Project: Ignite
>  Issue Type: Bug
>  Components: managed services
>Affects Versions: 1.7
>Reporter: Alexey Goncharuk
>Assignee: Mikhail Cherkasov
> Fix For: 2.1
>
>
> The following parts of GridServiceProcessor look wrong to me: 
> In GridServiceProcessor.TopologyListener#onReassignmentFailed
> {code}
> @Override public void onTimeout() {
> onReassignmentFailed(topVer, retries);
> }
> {code}
> And in GridServiceProcessor#onDeployment
> {code}
> @Override public void onTimeout() {
> .
> // Try again.
> onDeployment(dep, topVer);
> }
> {code}
> The rest of ServiceProcessor relies on the deployments being processed in a 
> single thread, while this code will be executed in the timeout processor 
> thread. Not only can it take a lot of time to reassign, which will stall the 
> timeout thread, but it may also break the service assignment logic.
> The corresponding calls should be wrapped to runnables and submitted to the 
> depExe.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5467) Exception in communication SPI can stall the cluster

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5467:


GitHub user ezhuravl opened a pull request:

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

IGNITE-5467 Exception in communication SPI can stall the cluster



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

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

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

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


commit 76060a8f6609948aa03910196710dc314a8abbb6
Author: Evgenii Zhuravlev 
Date:   2017-07-07T14:43:37Z

IGNITE-5467 Exception in communication SPI can stall the cluster




> Exception in communication SPI can stall the cluster
> 
>
> Key: IGNITE-5467
> URL: https://issues.apache.org/jira/browse/IGNITE-5467
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
>Assignee: Evgenii Zhuravlev
> Fix For: 2.2
>
> Attachments: MessageSendExceptionTest.java
>
>
> Test attached.
> If there is an exception in {{CommunicationSpi#sendMessage}} while sending 
> response for a cache operation, it can stall whole cluster forever (operation 
> doesn't complete, new nodes can't join, etc.).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-4756) Print info about partition distribution to log

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-4756 at 7/7/17 2:43 PM:
--

[~javaller], my comments:
# You mustn't initialize {{log}} member at the 
{{RendezvousAffinityFunctionSimpleBenchmark#beforeTestsStarted}}. It have been 
initialized early.
# Then Log4JLogger dependency is not needed. Please remove it from the {{core}} 
module.



was (Author: tledkov-gridgain):
[~javaller], my comments:
# You mustn't initialize {log} member at the 
{{RendezvousAffinityFunctionSimpleBenchmark#beforeTestsStarted}}. It have been 
initialized early.
# Then Log4JLogger dependency is not needed. Please remove it from the {{core}} 
module.


> Print info about partition distribution to log 
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
>  Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even 
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
> value 0.1 to print warn message only when nodes count differs more then 
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Message format is
> {noformat}
> Affinity assignment distribution not even [cache=, 
> even=, distribution=[, 
>  ..., ]].
> {noformat}
> e.g. for cache with name "test", 2 backups and (partitions count / nodes 
> count) == 100 :
> {noformat}
> Affinity assignment distribution not even [cache=test, even=100 (10%), 
> distribution=[100 (10%), 150 (15%), 500 (50%)]].
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4756) Print info about partition distribution to log

[Taras Ledkov (JIRA)]

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

Taras Ledkov updated IGNITE-4756:
-
Description: 
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to print warn message only when nodes count differs more then 
threshold;
# The statistic is calculated and printed only for the local node;
# Message format is
{noformat}
Affinity assignment distribution not even [cache=, 
even=, distribution=[, 
 ..., ]].
{noformat}
e.g. for cache with name "test", 2 backups and (partitions count / nodes count) 
== 100 :
{noformat}
Affinity assignment distribution not even [cache=test, even=100 (10%), 
distribution=[100 (10%), 150 (15%), 500 (50%)]].
{noformat}

  was:
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to print warn message only when nodes count differs more then 
threshold;
# The statistic is calculated and printed only for the local node;
# Message format is
{noformat}
Affinity assignment distribution not even [cache=, 
even=, distribution=[, 
 ..., ]].
e.g.:
Affinity assignment distribution not even [cache=test, even=100 (10%), 
distribution=[100 (10%), 150 (15%), 500 (50%)]].
{noformat}


> Print info about partition distribution to log 
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
>  Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even 
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
> value 0.1 to print warn message only when nodes count differs more then 
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Message format is
> {noformat}
> Affinity assignment distribution not even [cache=, 
> even=, distribution=[, 
>  ..., ]].
> {noformat}
> e.g. for cache with name "test", 2 backups and (partitions count / nodes 
> count) == 100 :
> {noformat}
> Affinity assignment distribution not even [cache=test, even=100 (10%), 
> distribution=[100 (10%), 150 (15%), 500 (50%)]].
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-4756) Print info about partition distribution to log

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-4756:
--

[~javaller], my comments:
# You mustn't initialize {log} member at the 
{{RendezvousAffinityFunctionSimpleBenchmark#beforeTestsStarted}}. It have been 
initialized early.
# Then Log4JLogger dependency is not needed. Please remove it from the {{core}} 
module.


> Print info about partition distribution to log 
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
>  Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even 
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
> value 0.1 to print warn message only when nodes count differs more then 
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Message format is
> {noformat}
> Affinity assignment distribution not even [cache=, 
> even=, distribution=[, 
>  ..., ]].
> e.g.:
> Affinity assignment distribution not even [cache=test, even=100 (10%), 
> distribution=[100 (10%), 150 (15%), 500 (50%)]].
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-5686) Endless partition eviction during node shutdown

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov edited comment on IGNITE-5686 at 7/7/17 2:31 PM:
--

{noformat}
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.reserve(GridDhtLocalPartition.java:542)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.scanIterator(GridCacheQueryManager.java:853)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.scanQueryLocal(GridCacheQueryManager.java:1452)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter$ScanQueryFallbackClosableIterator.init(GridCacheQueryAdapter.java:717)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter$ScanQueryFallbackClosableIterator.(GridCacheQueryAdapter.java:680)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter$ScanQueryFallbackClosableIterator.(GridCacheQueryAdapter.java:624)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter.executeScanQuery(GridCacheQueryAdapter.java:541)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy$1.applyx(IgniteCacheProxy.java:561)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy$1.applyx(IgniteCacheProxy.java:559)
at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2293)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:558)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:799)
at org.apache.ignite.spark.IgniteRDD.compute(IgniteRDD.scala:65)
at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:323)
at org.apache.spark.rdd.RDD.iterator(RDD.scala:287)
at 
org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:38)
at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:323)
at org.apache.spark.rdd.RDD.iterator(RDD.scala:287)
at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:87)
at org.apache.spark.scheduler.Task.run(Task.scala:99)
at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:282)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
{noformat}


was (Author: gvvinblade):
{noformat}
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.add(GridDhtLocalPartition.java:598)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.reserve(GridDhtLocalPartition.java:542)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.scanIterator(GridCacheQueryManager.java:853)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.scanQueryLocal(GridCacheQueryManager.java:1452)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter$ScanQueryFallbackClosableIterator.init(GridCacheQueryAdapter.java:717)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter$ScanQueryFallbackClosableIterator.(GridCacheQueryAdapter.java:680)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter$ScanQueryFallbackClosableIterator.(GridCacheQueryAdapter.java:624)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter.executeScanQuery(GridCacheQueryAdapter.java:541)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy$1.applyx(IgniteCacheProxy.java:561)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy$1.applyx(IgniteCacheProxy.java:559)
at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2293)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:558)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:799)
at org.apache.ignite.spark.IgniteRDD.compute(IgniteRDD.scala:65)
at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:323)
at org.apache.spark.rdd.RDD.iterator(RDD.scala:287)
at 
org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:38)
at 

[jira] [Commented] (IGNITE-5686) Endless partition eviction during node shutdown

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov commented on IGNITE-5686:
--

The stack trace shows that partition is reserved for scan query invokation, but 
seems that nobody closes the query

> Endless partition eviction during node shutdown
> ---
>
> Key: IGNITE-5686
> URL: https://issues.apache.org/jira/browse/IGNITE-5686
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Igor Seliverstov
> Fix For: 2.1
>
> Attachments: dump.txt
>
>
> Observed the following behavior on TC:
> A node cannot stop because system threads are continuously trying to clean 
> partitions.
> http://ci.ignite.apache.org/viewLog.html?buildId=702633=Ignite20Tests_IgniteRdd=buildResultsDiv
> Attached is a thread dump from the test



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-5686) Endless partition eviction during node shutdown

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov edited comment on IGNITE-5686 at 7/7/17 2:30 PM:
--

The stack trace shows that partition is reserved for scan query invocation, but 
seems that nobody closes the query


was (Author: gvvinblade):
The stack trace shows that partition is reserved for scan query invokation, but 
seems that nobody closes the query

> Endless partition eviction during node shutdown
> ---
>
> Key: IGNITE-5686
> URL: https://issues.apache.org/jira/browse/IGNITE-5686
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Igor Seliverstov
> Fix For: 2.1
>
> Attachments: dump.txt
>
>
> Observed the following behavior on TC:
> A node cannot stop because system threads are continuously trying to clean 
> partitions.
> http://ci.ignite.apache.org/viewLog.html?buildId=702633=Ignite20Tests_IgniteRdd=buildResultsDiv
> Attached is a thread dump from the test



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4756) Print info about partition distribution to log

[Taras Ledkov (JIRA)]

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

Taras Ledkov updated IGNITE-4756:
-
Description: 
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to print warn message only when nodes count differs more then 
threshold;
# The statistic is calculated and printed only for the local node;
# Message format is
{noformat}
Affinity assignment distribution not even [cache=, 
even=, distribution=[, 
 ..., ]].
e.g.:
Affinity assignment distribution not even [cache=test, even=100 (10%), 
distribution=[100 (10%), 150 (15%), 500 (50%)]].
{noformat}

  was:
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to print warn message only when nodes count differs more then 
threshold;
# The statistic is calculated and printed only for the local node;
# Message format is
{noformat}
Affinity assignment distribution not even [cache=, 
even=, distribution=[, 
 ..., ]].
e.g.:
Affinity assignment distribution not even [cache=test, even=100 (10%), 
distribution=[100 (10%), 150 (15%), 500 (50%)]].


> Print info about partition distribution to log 
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
>  Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even 
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
> value 0.1 to print warn message only when nodes count differs more then 
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Message format is
> {noformat}
> Affinity assignment distribution not even [cache=, 
> even=, distribution=[, 
>  ..., ]].
> e.g.:
> Affinity assignment distribution not even [cache=test, even=100 (10%), 
> distribution=[100 (10%), 150 (15%), 500 (50%)]].
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4756) Print info about partition distribution to log

[Taras Ledkov (JIRA)]

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

Taras Ledkov updated IGNITE-4756:
-
Description: 
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to print warn message only when nodes count differs more then 
threshold;
# The statistic is calculated and printed only for the local node;
# Message format is
{noformat}
Affinity assignment distribution not even [cache=, 
even=, distribution=[, 
 ..., ]].
e.g.:
Affinity assignment distribution not even [cache=test, even=100 (10%), 
distribution=[100 (10%), 150 (15%), 500 (50%)]].

  was:
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to 


{noformat}
: primary, [, , 
], ...,  [, , 
]
: backup_0, [, , 
], ...,  [, , 
]
...
: backup_N, [, , 
], ...,  [, , 
]
{noformat}


> Print info about partition distribution to log 
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
>  Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even 
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
> value 0.1 to print warn message only when nodes count differs more then 
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Message format is
> {noformat}
> Affinity assignment distribution not even [cache=, 
> even=, distribution=[, 
>  ..., ]].
> e.g.:
> Affinity assignment distribution not even [cache=test, even=100 (10%), 
> distribution=[100 (10%), 150 (15%), 500 (50%)]].



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5686) Endless partition eviction during node shutdown

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov commented on IGNITE-5686:
--

{noformat}
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.add(GridDhtLocalPartition.java:598)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.reserve(GridDhtLocalPartition.java:542)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.scanIterator(GridCacheQueryManager.java:853)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.scanQueryLocal(GridCacheQueryManager.java:1452)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter$ScanQueryFallbackClosableIterator.init(GridCacheQueryAdapter.java:717)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter$ScanQueryFallbackClosableIterator.(GridCacheQueryAdapter.java:680)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter$ScanQueryFallbackClosableIterator.(GridCacheQueryAdapter.java:624)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter.executeScanQuery(GridCacheQueryAdapter.java:541)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy$1.applyx(IgniteCacheProxy.java:561)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy$1.applyx(IgniteCacheProxy.java:559)
at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2293)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:558)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:799)
at org.apache.ignite.spark.IgniteRDD.compute(IgniteRDD.scala:65)
at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:323)
at org.apache.spark.rdd.RDD.iterator(RDD.scala:287)
at 
org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:38)
at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:323)
at org.apache.spark.rdd.RDD.iterator(RDD.scala:287)
at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:87)
at org.apache.spark.scheduler.Task.run(Task.scala:99)
at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:282)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
{noformat}

> Endless partition eviction during node shutdown
> ---
>
> Key: IGNITE-5686
> URL: https://issues.apache.org/jira/browse/IGNITE-5686
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Igor Seliverstov
> Fix For: 2.1
>
> Attachments: dump.txt
>
>
> Observed the following behavior on TC:
> A node cannot stop because system threads are continuously trying to clean 
> partitions.
> http://ci.ignite.apache.org/viewLog.html?buildId=702633=Ignite20Tests_IgniteRdd=buildResultsDiv
> Attached is a thread dump from the test



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-4756) Print info about partition distribution to log

[Vadim Opolski (JIRA)]

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

Vadim Opolski commented on IGNITE-4756:
---

[~tledkov-gridgain] [~avinogradov]

Removed initialization from constructor - 
https://github.com/vadopolski/ignite/pull/3/files. Trying to use 
IgniteMockWithLocalNode.

> Print info about partition distribution to log 
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
>  Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even 
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
> value 0.1 to 
> {noformat}
> : primary, [, , 
> ], ...,  [, , 
> ]
> : backup_0, [, , 
> ], ...,  [, , 
> ]
> ...
> : backup_N, [, , 
> ], ...,  [, , 
> ]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4756) Print info about partition distribution to log

[Taras Ledkov (JIRA)]

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

Taras Ledkov updated IGNITE-4756:
-
Description: 
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

# Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
value 0.1 to 


{noformat}
: primary, [, , 
], ...,  [, , 
]
: backup_0, [, , 
], ...,  [, , 
]
...
: backup_N, [, , 
], ...,  [, , 
]
{noformat}

  was:
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

#


{noformat}
: primary, [, , 
], ...,  [, , 
]
: backup_0, [, , 
], ...,  [, , 
]
...
: backup_N, [, , 
], ...,  [, , 
]
{noformat}


> Print info about partition distribution to log 
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
>  Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even 
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default 
> value 0.1 to 
> {noformat}
> : primary, [, , 
> ], ...,  [, , 
> ]
> : backup_0, [, , 
> ], ...,  [, , 
> ]
> ...
> : backup_N, [, , 
> ], ...,  [, , 
> ]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-3142) When remote filter is set, event is not send, if primary node has left grid.

[Vadim Opolski (JIRA)]

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

Vadim Opolski commented on IGNITE-3142:
---

[~avinogradov] [~v.pyatkov] I checked the test in Ignite 1.6, there was not 
exception. Also I checked the attached project there was exception in Ignite 
1.6 and it was not in ignite 2.0. I'm compare test and project to find 
differences to recreate exception in Ignite 1.6 in test.

> When remote filter is set, event is not send, if primary node has left grid.
> 
>
> Key: IGNITE-3142
> URL: https://issues.apache.org/jira/browse/IGNITE-3142
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Vladislav Pyatkov
>Assignee: Vadim Opolski
> Fix For: 2.2
>
> Attachments: EventsListenerTest.java, Ignite-Events - Copy.zip
>
>
> If you try to start one server node and another then. After update of 
> topology, you can stop the first node and get the exception:
> {noformat}
> [12:25:25] (err) Failed to execute compound future reducer: 
> GridNearTxFinishFuture 
> [futId=fbe41e8b451-b79beebc-da21-4cfc-a83e-e1cb4b34151b, tx=GridNearTxLocal 
> [mappings=IgniteTxMappingsSingleImpl [mapping=GridDistributedTxMapping 
> [entries=[IgniteTxEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey 
> [typeId=887264644], hasValBytes=true], cacheId=-2100569601, partId=-1, 
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [val=BinaryMetadataKey 
> [typeId=887264644], hasValBytes=true], cacheId=-2100569601], 
> val=[op=TRANSFORM, val=null], prevVal=[op=NOOP, val=null], 
> entryProcessorsCol=[IgniteBiTuple [val1=MetadataProcessor 
> [newMeta=BinaryMetadata [typeId=887264644, 
> typeName=org.jsr166.ConcurrentLinkedDeque8, fields=null, 
> affKeyFieldName=null, isEnum=false]], val2=[Ljava.lang.Object;@4807a494]], 
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null, 
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true, 
> entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry 
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey 
> [typeId=887264644], hasValBytes=true], val=null, startVer=1463390656382, 
> ver=GridCacheVersion [topVer=74870619, time=1463390725860, 
> order=1463390656382, nodeOrder=3], hash=887264644, extras=null, flags=0]]], 
> prepared=0, locked=false, nodeId=5f3be800-b89a-419b-8d7e-ba5adbb36fab, 
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0, 
> partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=74870619, 
> time=1463390725845, order=1463390656380, nodeOrder=3]]], explicitLock=false, 
> dhtVer=null, last=false, near=false, clientFirst=false, 
> node=5f3be800-b89a-419b-8d7e-ba5adbb36fab]], nearLocallyMapped=false, 
> colocatedLocallyMapped=false, needCheckBackup=false, hasRemoteLocks=false, 
> thread=sys-#20%null%, mappings=IgniteTxMappingsSingleImpl 
> [mapping=GridDistributedTxMapping [entries=[IgniteTxEntry 
> [key=KeyCacheObjectImpl [val=BinaryMetadataKey [typeId=887264644], 
> hasValBytes=true], cacheId=-2100569601, partId=-1, txKey=IgniteTxKey 
> [key=KeyCacheObjectImpl [val=BinaryMetadataKey [typeId=887264644], 
> hasValBytes=true], cacheId=-2100569601], val=[op=TRANSFORM, val=null], 
> prevVal=[op=NOOP, val=null], entryProcessorsCol=[IgniteBiTuple 
> [val1=MetadataProcessor [newMeta=BinaryMetadata [typeId=887264644, 
> typeName=org.jsr166.ConcurrentLinkedDeque8, fields=null, 
> affKeyFieldName=null, isEnum=false]], val2=[Ljava.lang.Object;@4807a494]], 
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null, 
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true, 
> entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry 
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey 
> [typeId=887264644], hasValBytes=true], val=null, startVer=1463390656382, 
> ver=GridCacheVersion [topVer=74870619, time=1463390725860, 
> order=1463390656382, nodeOrder=3], hash=887264644, extras=null, flags=0]]], 
> prepared=0, locked=false, nodeId=5f3be800-b89a-419b-8d7e-ba5adbb36fab, 
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0, 
> partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=74870619, 
> time=1463390725845, order=1463390656380, nodeOrder=3]]], explicitLock=false, 
> dhtVer=null, last=false, near=false, clientFirst=false, 
> node=5f3be800-b89a-419b-8d7e-ba5adbb36fab]], super=GridDhtTxLocalAdapter 
> [nearOnOriginatingNode=false, nearNodes=[], dhtNodes=[], explicitLock=false, 
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false, 
> depEnabled=false, txState=IgniteTxImplicitSingleStateImpl [init=true], 
> super=IgniteTxAdapter [xidVer=GridCacheVersion [topVer=74870619, 
> time=1463390725845, 

[jira] [Updated] (IGNITE-4756) Print info about partition distribution to log

[Taras Ledkov (JIRA)]

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

Taras Ledkov updated IGNITE-4756:
-
Description: 
Summarize discussions:
Add log message in case partitions distribution is not close to even 
distribution:

#


{noformat}
: primary, [, , 
], ...,  [, , 
]
: backup_0, [, , 
], ...,  [, , 
]
...
: backup_N, [, , 
], ...,  [, , 
]
{noformat}

  was:
Print information about affinity assignment to log.
e.g.: 

{noformat}
: primary, [, , 
], ...,  [, , 
]
: backup_0, [, , 
], ...,  [, , 
]
...
: backup_N, [, , 
], ...,  [, , 
]
{noformat}


> Print info about partition distribution to log 
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
>  Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even 
> distribution:
> #
> {noformat}
> : primary, [, , 
> ], ...,  [, , 
> ]
> : backup_0, [, , 
> ], ...,  [, , 
> ]
> ...
> : backup_N, [, , 
> ], ...,  [, , 
> ]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5087) Enum comparison fails after marshal-unmarshal with BinaryMarshaller.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov commented on IGNITE-5087:
--

[~NSAmelchev],
.NET test fails due to timeout. I see it was failed in master earlier, but 
looks fixed right now.
Would you please merge your PR with lastest master and check .NET test again?

The rest tests looks perfect.

> Enum comparison fails after marshal-unmarshal with BinaryMarshaller.
> 
>
> Key: IGNITE-5087
> URL: https://issues.apache.org/jira/browse/IGNITE-5087
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 1.9
>Reporter: Andrew Mashenkov
>Assignee: Amelchev Nikita
> Fix For: 2.2
>
> Attachments: EnumBinaryMarshallerBug.java
>
>
> PFA repro.
> It fails on 1.9 and on 2.0-snapshot as well.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-5712) Context switching for optimistic transactions

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov edited comment on IGNITE-5712 at 7/7/17 2:05 PM:
--

The following tests performed for one node cluster, and for a couple of nodes : 
client and server nodes.
Keys reside on server node(server node is a primary node), put operation 
performed on client node.

||Scenarion||Result||
|Start transaction, perform some put operations, resume in another thread, 
commit. |New keys are in cache|
|Start transaction, perform some put operations, resume in another thread. Then 
suspend it and continue to original thread, commit it |New keys are in cache|
|Like the first test, but with a couple of different cache put(cross cache 
transaction)|New keys are in cache|
|Like the second test, but with a couple of different cache put(cross cache 
transaction)|New keys are in cache|
|Start transaction, perform some put operations, resume in another thread, 
rollback. |No new keys are in cache|

The following tests performed for a couple of nodes.
||Scenarion||Result||
|Start 10 transactions in one thread, write the only key, suspend them by 
order. The next step is resume, commit by order |The last write is persisted 
only|
|Start tx, write key and suspend. The next is resume in another thread, suspend 
before commit. Start new tx in the first thread, make commit. Resume first tx 
and commit it. |The first tx result is persisted|
|Pessimistic tx write key , suspend forever. Start new pessimistic tx, try to 
write the same key | The second tx hangs waiting for unblock on the key|
|Pessimistic tx write key , suspend forever. Trying to put cache lock on the 
key.| Cache lock hangs waiting for unblock on the key(Will not include in PR)|
|When one transaction is suspending, others - concurrently perform 
suspend,resume,end etc. |New key is in cache, other transactions failed with 
exception|
|When one transaction is resuming, others - concurrently perform 
suspend,resume,end etc.|New key is in cache, other transactions failed with 
exception|
|When one transaction is committing, others - concurrently perform 
suspend,resume,end etc.|New key is in cache, other transactions failed with 
exception|
|When one transaction is rollbacking, others - concurrently perform 
suspend,resume,end etc.|New key is in cache, other transactions failed with 
exception|
|When one transaction is closing, others - concurrently perform 
suspend,resume,end etc.|New key is in cache, other transactions failed with 
exception|

The following failover tests performed for a couple of nodes.
||Scenarion||Result||
|Starting transaction on server node, suspend it. 
Then primary node got broken, 
resuming transaction and committing leads to exception.|Proper exception is 
thrown(depends on transaction concurrency), 
either new values persisted on some cluster node 
or not(depends on transaction concurrency)|
|Starting transaction on client node, suspend it. 
Then primary node got broken, resuming transaction 
and committing leads to exception.|Proper exception is thrown(depends on 
transaction concurrency),
 either new values persisted on some cluster node 
or not(depends on transaction concurrency)|
|Starting transaction, suspend it. 
Then initiating node got broken, resuming transaction 
and committing leads to exception.|Proper exception is thrown(depends on 
transaction concurrency),
 no new values persisted on cluster nodes|
|Suspend pessimistic transaction|Unsupported op exception arise|
|Resume pessimistic transaction|Unsupported op exception arise|


was (Author: alexey kuznetsov):
The following tests performed for one node cluster, and for a couple of nodes : 
client and server nodes.
Keys reside on server node(server node is a primary node), put operation 
performed on client node.

||Scenarion||Result||
|Start transaction, perform some put operations, resume in another thread, 
commit. |New keys are in cache|
|Start transaction, perform some put operations, resume in another thread. Then 
suspend it and continue to original thread, commit it |New keys are in cache|
|Like the first test, but with a couple of different cache put(cross cache 
transaction)|New keys are in cache|
|Like the second test, but with a couple of different cache put(cross cache 
transaction)|New keys are in cache|
|Start transaction, perform some put operations, resume in another thread, 
rollback. |No new keys are in cache|

The following tests performed for a couple of nodes.
||Scenarion||Result||
|Start 10 transactions in one thread, write the only key, suspend them by 
order. The next step is resume, commit by order |The last write is persisted 
only|
|Start tx, write key and suspend. The next is resume in another thread, suspend 
before commit. Start new tx in the first thread, make commit. Resume first tx 
and commit it. |The first tx 

[jira] [Commented] (IGNITE-5582) CPP: Implement Compute::Broadcast() for Ignite C++

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5582:


Github user isapego closed the pull request at:

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


> CPP: Implement Compute::Broadcast() for Ignite C++
> --
>
> Key: IGNITE-5582
> URL: https://issues.apache.org/jira/browse/IGNITE-5582
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: cpp
> Fix For: 2.1
>
>
> Need to implement method {{Compute::Broadcast}} and 
> {{Compute::BroadcastAsync}} for Ignite C++.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-5701) Some nodes have partitionUpdateCounter == 0 after rebalancing

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh reassigned IGNITE-5701:


Assignee: Alexey Goncharuk  (was: Ilya Lantukh)

> Some nodes have partitionUpdateCounter == 0 after rebalancing
> -
>
> Key: IGNITE-5701
> URL: https://issues.apache.org/jira/browse/IGNITE-5701
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>Assignee: Alexey Goncharuk
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5701) Some nodes have partitionUpdateCounter == 0 after rebalancing

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh commented on IGNITE-5701:
--

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

> Some nodes have partitionUpdateCounter == 0 after rebalancing
> -
>
> Key: IGNITE-5701
> URL: https://issues.apache.org/jira/browse/IGNITE-5701
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>Assignee: Ilya Lantukh
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5473) Create ignite troubleshooting logger

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5473:


GitHub user AMashenkov opened a pull request:

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

IGNITE-5473: Create ignite troubleshooting logger.

Partial fix.

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

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

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

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


commit 6abe8ec92f016a18883332de2bc177fbab30a4c1
Author: Alexey Goncharuk 
Date:   2017-06-14T18:37:54Z

WIP.

commit 4ab6d52cfa2f0dda6170ad1dff80d4a42c2a0706
Author: Andrey V. Mashenkov 
Date:   2017-06-30T11:45:18Z

WIP.




> Create ignite troubleshooting logger
> 
>
> Key: IGNITE-5473
> URL: https://issues.apache.org/jira/browse/IGNITE-5473
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 2.0
>Reporter: Alexey Goncharuk
>Priority: Critical
>  Labels: important, observability
> Fix For: 2.2
>
>
> Currently, we have two extremes of logging - either INFO wich logs almost 
> nothing, or DEBUG, which will pollute logs with too verbose messages.
> We should create a 'troubleshooting' logger, which should be easily enabled 
> (via a system property, for example) and log all stability-critical node and 
> cluster events:
>  * Connection events (both communication and discovery), handshake status
>  * ALL ignored messages and skipped actions (even those we assume are safe to 
> ignore)
>  * Partition exchange stages and timings
>  * Verbose discovery state changes (this should make it easy to understand 
> the reason for 'Node has not been connected to the topology')
>  * Transaction failover stages and actions
>  * All unlogged exceptions
>  * Responses that took more than N milliseconds when in normal they should 
> return right away
>  * Long discovery SPI messages processing times
>  * Managed service deployment stages
>  * Marshaller mappings registration and notification
>  * Binary metadata registration and notification
>  * Continuous query registration / notification
> (add more)
> The amount of logging should be chosen accurately so that it would be safe to 
> enable this logger in production clusters.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-5718) Forcible node drop makes cluster instable in some cases.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov reassigned IGNITE-5718:


Assignee: Andrew Mashenkov

> Forcible node drop makes cluster instable in some cases.
> 
>
> Key: IGNITE-5718
> URL: https://issues.apache.org/jira/browse/IGNITE-5718
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.0
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 2.2
>
>
> Communication SPI can drop nodes from topology due to short network issues 
> regardless failureDetectionTimout.
> Also, we throw IgniteCheckedExcpetion in safeHandshake method without any 
> retry
> if remote node close connection (possibly by timeout) due to short network 
> issues. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5437) SQL: Incorrect partition is derived from query when argument type differs from column type

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5437:

Flags:   (was: Important)

> SQL: Incorrect partition is derived from query when argument type differs 
> from column type
> --
>
> Key: IGNITE-5437
> URL: https://issues.apache.org/jira/browse/IGNITE-5437
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.1
>Reporter: Sergey Kalashnikov
>Assignee: Sergey Kalashnikov
> Fix For: 2.1
>
> Attachments: BugReproducer5437.java
>
>
> Ignite SQL attempts to derive partition from the query in certain cases and 
> sends the map queries only to nodes which have those calculated partitions.
> Such queries are limited to contain equality conditions over key or affinity 
> key columns at the left and constant or parameter at the right.
> When the type of argument does not match the column type, the calculation 
> leads to wrong result.
> For example, the following query produces incomplete results when _key column 
> is INTEGER and the argument is CHAR. 
> select * from test where _key = ?
> However, this is valid and resultive query for H2, which does implicit 
> conversion in such cases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5087) Enum comparison fails after marshal-unmarshal with BinaryMarshaller.

[Amelchev Nikita (JIRA)]

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

Amelchev Nikita commented on IGNITE-5087:
-

[~amashenkov] Yesterday I checked all tests and compared with master. I dont 
see any problems.

> Enum comparison fails after marshal-unmarshal with BinaryMarshaller.
> 
>
> Key: IGNITE-5087
> URL: https://issues.apache.org/jira/browse/IGNITE-5087
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 1.9
>Reporter: Andrew Mashenkov
>Assignee: Amelchev Nikita
> Fix For: 2.2
>
> Attachments: EnumBinaryMarshallerBug.java
>
>
> PFA repro.
> It fails on 1.9 and on 2.0-snapshot as well.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5718) Forcible node drop makes cluster instable in some cases.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5718:


GitHub user AMashenkov opened a pull request:

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

IGNITE-5718: Forcible node drop makes cluster instable in some cases.



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

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

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

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


commit 5574c14d166173b73f2892ca1228e3c2da194238
Author: Andrey V. Mashenkov 
Date:   2017-07-07T13:01:44Z

Forcible node drop makes cluster unstable in some cases. Disable forcible 
node drop by default.

commit 0729eb909db9ea4d253e32f79aba95597f6e1016
Author: Andrey V. Mashenkov 
Date:   2017-07-07T13:02:21Z

Fix tests.




> Forcible node drop makes cluster instable in some cases.
> 
>
> Key: IGNITE-5718
> URL: https://issues.apache.org/jira/browse/IGNITE-5718
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.0
>Reporter: Andrew Mashenkov
> Fix For: 2.2
>
>
> Communication SPI can drop nodes from topology due to short network issues 
> regardless failureDetectionTimout.
> Also, we throw IgniteCheckedExcpetion in safeHandshake method without any 
> retry
> if remote node close connection (possibly by timeout) due to short network 
> issues. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5718) Forcible node drop makes cluster instable in some cases.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-5718:


 Summary: Forcible node drop makes cluster instable in some cases.
 Key: IGNITE-5718
 URL: https://issues.apache.org/jira/browse/IGNITE-5718
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.0
Reporter: Andrew Mashenkov
 Fix For: 2.2


Communication SPI can drop nodes from topology due to short network issues 
regardless failureDetectionTimout.
Also, we throw IgniteCheckedExcpetion in safeHandshake method without any retry
if remote node close connection (possibly by timeout) due to short network 
issues. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5087) Enum comparison fails after marshal-unmarshal with BinaryMarshaller.

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-5087:
--

[~amashenkov], 
Nikita checked TC, could you please recheck to make sure we did not miss 
something?

In case everything is ok please let me know and I'll merge changes to master.

> Enum comparison fails after marshal-unmarshal with BinaryMarshaller.
> 
>
> Key: IGNITE-5087
> URL: https://issues.apache.org/jira/browse/IGNITE-5087
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 1.9
>Reporter: Andrew Mashenkov
>Assignee: Amelchev Nikita
> Fix For: 2.2
>
> Attachments: EnumBinaryMarshallerBug.java
>
>
> PFA repro.
> It fails on 1.9 and on 2.0-snapshot as well.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5567) Make benchmark Ignite.reentrantLock vs IgniteCache.lock

[Alexander Menshikov (JIRA)]

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

Alexander Menshikov commented on IGNITE-5567:
-

[~avinogradov]
Thank you for review. I have fixed all problems. Also, I have added yardstick 
benchmark.

> Make benchmark Ignite.reentrantLock vs IgniteCache.lock
> ---
>
> Key: IGNITE-5567
> URL: https://issues.apache.org/jira/browse/IGNITE-5567
> Project: Ignite
>  Issue Type: Sub-task
>  Components: data structures
>Reporter: Alexander Menshikov
>Assignee: Alexander Menshikov
> Fix For: 2.3
>
>
> Ignite.reentrantLock slower than IgniteCache.lock. First of all, we must 
> create a benchmark for agreeing about use-case which we want to test.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5582) CPP: Implement Compute::Broadcast() for Ignite C++

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5582:


Looks good to me. If there is no way to verify remote execution, let's merge it 
as is.

> CPP: Implement Compute::Broadcast() for Ignite C++
> --
>
> Key: IGNITE-5582
> URL: https://issues.apache.org/jira/browse/IGNITE-5582
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: cpp
> Fix For: 2.1
>
>
> Need to implement method {{Compute::Broadcast}} and 
> {{Compute::BroadcastAsync}} for Ignite C++.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5562) Assertions in TCP discovery SPI when NTP is moving time backwards

[Vyacheslav Koptilin (JIRA)]

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

Vyacheslav Koptilin commented on IGNITE-5562:
-

Hi [~agoncharuk],
Could you please take a look at the pull-request: 
https://github.com/apache/ignite/pull/2259 ?

> Assertions in TCP discovery SPI when NTP is moving time backwards
> -
>
> Key: IGNITE-5562
> URL: https://issues.apache.org/jira/browse/IGNITE-5562
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.7
>Reporter: Alexey Goncharuk
>Assignee: Vyacheslav Koptilin
> Fix For: 2.1
>
>
> In several places in TcpDiscoverySPI, when metrics are updated, we assert 
> that time is not negative. However, in some cases, this invariant may fail 
> because of time adjustments. 
> Since a missed metric is not critical for us, we should remove these 
> assertions and replace negative time with 0.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-5204) The Unicode character in the value of a field which are included in an un-unique index will cause "stack overhead" exception

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov edited comment on IGNITE-5204 at 7/7/17 12:27 PM:
--

Is it fine that UTF8 converting method may return null?


was (Author: vozerov):
Is it fine that UTF8 convering method may return null?

> The Unicode character in the value of a field which are included in an 
> un-unique index will cause "stack overhead" exception
> 
>
> Key: IGNITE-5204
> URL: https://issues.apache.org/jira/browse/IGNITE-5204
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, sql
>Affects Versions: 2.0
> Environment: windows server 2012, JDK 1.8, X64
>Reporter: Chris Wang
>Assignee: Sergey Kalashnikov
>Priority: Critical
> Fix For: 2.1
>
> Attachments: IgniteSqlIssue5204Test.java
>
>
> When put  "草DX009090" as the value of BillId, which is a field of entity 
> Bill. If I define a index includes the BillId, and execute the query like 
> "select * from Bill where BillId=’草DX009090‘ in the H2 debug console, there 
> throws an exception by the H2 with a code 5000. 
> another scenario is, I have two entities, "Bill" and "Detail", both have 
> field "BillId". If either of them have value like "草DX009090" and execute the 
> query like "select bill.* from bill left join detail on 
> bill.billid=detail.billid", the whole ignite cache node will halt ( suppose 
> there should be an stack overhead exception, dead loop).
> ==
> I think the issue should relate to hash computing on the unicode character.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5204) The Unicode character in the value of a field which are included in an un-unique index will cause "stack overhead" exception

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-5204:
-

Is it fine that UTF8 convering method may return null?

> The Unicode character in the value of a field which are included in an 
> un-unique index will cause "stack overhead" exception
> 
>
> Key: IGNITE-5204
> URL: https://issues.apache.org/jira/browse/IGNITE-5204
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, sql
>Affects Versions: 2.0
> Environment: windows server 2012, JDK 1.8, X64
>Reporter: Chris Wang
>Assignee: Sergey Kalashnikov
>Priority: Critical
> Fix For: 2.1
>
> Attachments: IgniteSqlIssue5204Test.java
>
>
> When put  "草DX009090" as the value of BillId, which is a field of entity 
> Bill. If I define a index includes the BillId, and execute the query like 
> "select * from Bill where BillId=’草DX009090‘ in the H2 debug console, there 
> throws an exception by the H2 with a code 5000. 
> another scenario is, I have two entities, "Bill" and "Detail", both have 
> field "BillId". If either of them have value like "草DX009090" and execute the 
> query like "select bill.* from bill left join detail on 
> bill.billid=detail.billid", the whole ignite cache node will halt ( suppose 
> there should be an stack overhead exception, dead loop).
> ==
> I think the issue should relate to hash computing on the unicode character.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5204) The Unicode character in the value of a field which are included in an un-unique index will cause "stack overhead" exception

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-5204:
-

[~agoncharuk], could you please take a look at the patch?

> The Unicode character in the value of a field which are included in an 
> un-unique index will cause "stack overhead" exception
> 
>
> Key: IGNITE-5204
> URL: https://issues.apache.org/jira/browse/IGNITE-5204
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, sql
>Affects Versions: 2.0
> Environment: windows server 2012, JDK 1.8, X64
>Reporter: Chris Wang
>Assignee: Sergey Kalashnikov
>Priority: Critical
> Fix For: 2.1
>
> Attachments: IgniteSqlIssue5204Test.java
>
>
> When put  "草DX009090" as the value of BillId, which is a field of entity 
> Bill. If I define a index includes the BillId, and execute the query like 
> "select * from Bill where BillId=’草DX009090‘ in the H2 debug console, there 
> throws an exception by the H2 with a code 5000. 
> another scenario is, I have two entities, "Bill" and "Detail", both have 
> field "BillId". If either of them have value like "草DX009090" and execute the 
> query like "select bill.* from bill left join detail on 
> bill.billid=detail.billid", the whole ignite cache node will halt ( suppose 
> there should be an stack overhead exception, dead loop).
> ==
> I think the issue should relate to hash computing on the unicode character.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5717) MemoryPolicy configuration and documentation improvements

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5717:


.NET tests fixed (reduced MaxSize) with TODO and this ticket number for now 
(merged to ignite-2.1).

> MemoryPolicy configuration and documentation improvements
> -
>
> Key: IGNITE-5717
> URL: https://issues.apache.org/jira/browse/IGNITE-5717
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Sergey Chugunov
>
> After introducing MemoryPolicy concept and related settings to Ignite there 
> were several cases when users run into problems with default configuration.
> It seems that approach with allocating 80% of available physical memory 
> causes confusion among users sitting on 32bit systems including versions of 
> JMV (example [1]) and also hurts stability of TeamCity.
> We need to rethink these settings and make them easier to use.
> Also it turned out that memory allocation process differs in cases of PDS on 
> and off; it must be properly documented.
> [1] 
> http://apache-ignite-users.70518.x6.nabble.com/Ignite2-0-memory-policy-limit-td12840.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5607) HttpSessionBindingListener is not supported for clustered web session

[Yuci Gou (JIRA)]

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

Yuci Gou commented on IGNITE-5607:
--

I can not assign this issue to myself. Probably I don't have the permission.

> HttpSessionBindingListener is not supported for clustered web session
> -
>
> Key: IGNITE-5607
> URL: https://issues.apache.org/jira/browse/IGNITE-5607
> Project: Ignite
>  Issue Type: Bug
>  Components: websession
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
>
> Ignite's implementation of {{HttpSession}} ignores values implementing 
> {{HttpSessionBindingListener}}.
> {{WebSession#setAttribute}} and {{WebSession#removeAttribute}} should be 
> modified accordingly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-2190) ScanQuery without a filter triggers object's deserialization on the server side

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-2190:
-

PR - https://github.com/apache/ignite/pull/2256
Tests - 
http://ci.ignite.apache.org/viewModification.html?modId=239462=false=1=vcsModificationBuilds

> ScanQuery without a filter triggers object's deserialization on the server 
> side
> ---
>
> Key: IGNITE-2190
> URL: https://issues.apache.org/jira/browse/IGNITE-2190
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Nikolay Izhikov
>Priority: Critical
>  Labels: newbie
> Fix For: 2.1
>
> Attachments: ScanQueryBug.java
>
>
> The issue is reproduced on version 1.4 where legacy PortableMarshaller is 
> used. However, I'm quiet sure that the issue happens when BinaryMarshaller is 
> used as well in 1.5.
> 1) Start a server using ignite.sh/bat
> 2) Create a simple app, that uses binary or portable marshaller, creates a 
> cache dynamically and executes a ScanQuery like below
> {{int size=employees1.query(new ScanQuery()).getAll().size();}}
> 3) As you see the query doesn't use any filters. However on the server side 
> some filter is still being checked 
> {{org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$5.checkPredicate(GridCacheQueryManager.java:963)}}
>  which makes the server to deserialize a value.
> According to the stack trace there is some internal filter that triggered 
> checkPredicate function - 
> filter=o.a.i.i.processors.cache.IgniteCacheProxy$1@3224ff7b.
> {noformat}
> [11:05:22,725][SEVERE][ignite-#25%sys-null%][GridCacheDistributedQueryManager]
>   Failed to run query [qry=GridCacheQueryInfo [loc=false, 
> trans=null, rdc=null, qry=GridCacheQueryAdapter [type=SCAN, clsName=null, 
> clause=null, filter=o.a.i.i.processors.cache.IgniteCacheProxy$1@3224ff7b, 
> part=null, incMeta=false, metrics=null, pageSize=1024, timeout=0, 
> keepAll=false, incBackups=false, dedup=false, prj=null, keepPortable=false, 
> subjId=c6aeb542-1693-4b5f-89db-96db50e3435f, taskHash=0], locFut=null, 
> sndId=c6aeb542-1693-4b5f-89db-96db50e3435f, reqId=14, incMeta=false, 
> all=false], node=209c237a-9e33-4d05-abe4-bbc14f93c439]
> class org.apache.ignite.IgniteCheckedException: 
> **.SubMessageB
> at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6979)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
> at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$CachedResult.iterator(GridCacheQueryManager.java:2784)
> at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.runQuery(GridCacheQueryManager.java:1376)
> at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.processQueryRequest(GridCacheDistributedQueryManager.java:226)
> at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$2.apply(GridCacheDistributedQueryManager.java:105)
> at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$2.apply(GridCacheDistributedQueryManager.java:103)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:580)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:280)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:198)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:77)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:160)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException: 
> **.SubMessageB
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at 

[jira] [Updated] (IGNITE-5078) Partition lost event is fired only on coordinator when partition loss policy is IGNORE

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5078:
---
Fix Version/s: (was: 2.2)
   2.1

> Partition lost event is fired only on coordinator when partition loss policy 
> is IGNORE
> --
>
> Key: IGNITE-5078
> URL: https://issues.apache.org/jira/browse/IGNITE-5078
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.0
>Reporter: Alexey Goncharuk
>Assignee: Dmitriy Pavlov
>  Labels: Muted_test, test-fail
> Fix For: 2.1
>
>
> Problem is demonstrated in test 
> org.apache.ignite.internal.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest#testIgnore()



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5332) Add toString() to GridNearAtomicAbstractSingleUpdateRequest and it's inheritors

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5332:


GitHub user Desperus opened a pull request:

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

IGNITE-5332 added toString() method where it was missing



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

$ git pull https://github.com/Desperus/ignite ignite-5332

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

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


commit fd6e61b5eb9ba9084a093377b871e541220ac8b3
Author: Aleksandr_Meterko 
Date:   2017-07-07T11:29:25Z

ignite-5332 added toString() method where it was missing




> Add toString() to GridNearAtomicAbstractSingleUpdateRequest and it's 
> inheritors
> ---
>
> Key: IGNITE-5332
> URL: https://issues.apache.org/jira/browse/IGNITE-5332
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Dmitry Karachentsev
>Assignee: Aleksandr Meterko
>  Labels: newbie
> Fix For: 1.9
>
>
> GridNearAtomicAbstractSingleUpdateRequest and all his inheritors should 
> implement toString() method.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5716) .NET: Negative field offset values can be observed on 2-byte offsets

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5716:


Found another problem in {{BinaryReader.ReadSchema}}: {{ReadInt}} is always 
used for offsets, which is not correct.

> .NET: Negative field offset values can be observed on 2-byte offsets
> 
>
> Key: IGNITE-5716
> URL: https://issues.apache.org/jira/browse/IGNITE-5716
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Blocker
>  Labels: .NET
> Fix For: 2.1
>
>
> {{BinaryObjectSchemaSerializer.WriteSchema}} uses {{ushort.MaxValue}} as a 
> boundary for 2-byte offsets. {{ReadSchema}} uses {{ReadShort}}, which returns 
> negative offsets for anything above {{short.MaxValue}}.
> * Ensure that all offsets are always non-negative (use uint in 
> {{BinaryObjectSchemaField}} probably)
> * Check how Java handles this
> * Add tests for all edge cases



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5681) IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover fails

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5681:
---
Labels: test-fail  (was: test-fail test-failure)

> IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover 
> fails
> -
>
> Key: IGNITE-5681
> URL: https://issues.apache.org/jira/browse/IGNITE-5681
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Reporter: Vladimir Ozerov
>Assignee: Alexey Goncharuk
>  Labels: test-fail
> Fix For: 2.1
>
>
> This is a regression introduced during persistent store migration.
> {code}
> [2017-07-04 11:20:46,993][ERROR][main][root] Test failed.
> class org.apache.ignite.IgniteException: Failed to update keys (retry update 
> if possible).: [GridCacheQueueHeaderKey [name=q-3]]
>   at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:957)
>   at org.apache.ignite.internal.IgniteKernal.queue(IgniteKernal.java:3648)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest$2.apply(IgniteAtomicLongChangingTopologySelfTest.java:164)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest$2.apply(IgniteAtomicLongChangingTopologySelfTest.java:155)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest.testFailoverWithClient(IgniteAtomicLongChangingTopologySelfTest.java:221)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover(IgniteAtomicLongChangingTopologySelfTest.java:155)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class 
> org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
>  Failed to update keys (retry update if possible).: [GridCacheQueueHeaderKey 
> [name=q-3]]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:398)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onNodeLeft(GridNearAtomicSingleUpdateFuture.java:155)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$4.onEvent(GridCacheMvccManager.java:266)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager$LocalListenerWrapper.onEvent(GridEventStorageManager.java:1353)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:895)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record0(GridEventStorageManager.java:344)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:311)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:2401)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:2598)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:2430)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   ... 1 more
>   Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to 
> update keys on primary node.
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.UpdateErrors.addFailedKeys(UpdateErrors.java:124)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKeys(GridNearAtomicUpdateResponse.java:342)
>   at 
> 

[jira] [Assigned] (IGNITE-5681) IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover fails

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov reassigned IGNITE-5681:
--

Assignee: Dmitriy Pavlov  (was: Alexey Goncharuk)

> IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover 
> fails
> -
>
> Key: IGNITE-5681
> URL: https://issues.apache.org/jira/browse/IGNITE-5681
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Reporter: Vladimir Ozerov
>Assignee: Dmitriy Pavlov
>  Labels: test-fail
> Fix For: 2.1
>
>
> This is a regression introduced during persistent store migration.
> {code}
> [2017-07-04 11:20:46,993][ERROR][main][root] Test failed.
> class org.apache.ignite.IgniteException: Failed to update keys (retry update 
> if possible).: [GridCacheQueueHeaderKey [name=q-3]]
>   at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:957)
>   at org.apache.ignite.internal.IgniteKernal.queue(IgniteKernal.java:3648)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest$2.apply(IgniteAtomicLongChangingTopologySelfTest.java:164)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest$2.apply(IgniteAtomicLongChangingTopologySelfTest.java:155)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest.testFailoverWithClient(IgniteAtomicLongChangingTopologySelfTest.java:221)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover(IgniteAtomicLongChangingTopologySelfTest.java:155)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class 
> org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
>  Failed to update keys (retry update if possible).: [GridCacheQueueHeaderKey 
> [name=q-3]]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:398)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onNodeLeft(GridNearAtomicSingleUpdateFuture.java:155)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$4.onEvent(GridCacheMvccManager.java:266)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager$LocalListenerWrapper.onEvent(GridEventStorageManager.java:1353)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:895)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record0(GridEventStorageManager.java:344)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:311)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:2401)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:2598)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:2430)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   ... 1 more
>   Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to 
> update keys on primary node.
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.UpdateErrors.addFailedKeys(UpdateErrors.java:124)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKeys(GridNearAtomicUpdateResponse.java:342)
>   at 
> 

[jira] [Updated] (IGNITE-5582) CPP: Implement Compute::Broadcast() for Ignite C++

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5582:
---
Summary: CPP: Implement Compute::Broadcast() for Ignite C++  (was: CPP: 
Implement Compute::Broabcast() for Ignite C++)

> CPP: Implement Compute::Broadcast() for Ignite C++
> --
>
> Key: IGNITE-5582
> URL: https://issues.apache.org/jira/browse/IGNITE-5582
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: cpp
> Fix For: 2.1
>
>
> Need to implement method {{Compute::Broadcast}} and 
> {{Compute::BroadcastAsync}} for Ignite C++.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5606) .NET: Enums do not work as a messaging topic or message

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5606:
---
Fix Version/s: 2.2

> .NET: Enums do not work as a messaging topic or message
> ---
>
> Key: IGNITE-5606
> URL: https://issues.apache.org/jira/browse/IGNITE-5606
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.2
>
>
> Trying to use .NET enum in {{IMessaging}} causes "unknown pair" exception in 
> Java. May be we are missing binary mode somewhere.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (IGNITE-3176) Need to create gc log for each client separately [ yardstick-ignite ]

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov resolved IGNITE-3176.
--
Resolution: Fixed

> Need to create gc log for each client separately [ yardstick-ignite ]
> -
>
> Key: IGNITE-3176
> URL: https://issues.apache.org/jira/browse/IGNITE-3176
> Project: Ignite
>  Issue Type: Bug
>  Components: clients, general
>Affects Versions: 1.6
>Reporter: Ilya Suntsov
>Assignee: Chandresh Pancholi
>Priority: Critical
> Fix For: 2.1
>
> Attachments: benchmark.properties
>
>
> In case when started more than one client/server on one host yardstick 
> re-write GC logs.
> GC options contain in *.properties files:
> {noformat}
> now0=`date +'%H%M%S'`
> # JVM options.
> JVM_OPTS=${JVM_OPTS}" -DIGNITE_QUIET=false"
> # Uncomment to enable concurrent garbage collection (GC) if you encounter 
> long GC pauses.
> JVM_OPTS=${JVM_OPTS}" \
> -Xloggc:./gc${now0}.log \
> -XX:+PrintGCDetails \
> -verbose:gc \
> -XX:+UseParNewGC \
> -XX:+UseConcMarkSweepGC \
> -XX:+UseTLAB \
> -XX:NewSize=128m \
> -XX:MaxNewSize=128m \
> -XX:MaxTenuringThreshold=0 \
> -XX:SurvivorRatio=1024 \
> -XX:+UseCMSInitiatingOccupancyOnly \
> -XX:CMSInitiatingOccupancyFraction=60 \
> {noformat}
> As you can see here will be created 1 log file and if you start another 
> driver/server with the same properties file will be re-write.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (IGNITE-3176) Need to create gc log for each client separately [ yardstick-ignite ]

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov closed IGNITE-3176.

Assignee: (was: Chandresh Pancholi)

> Need to create gc log for each client separately [ yardstick-ignite ]
> -
>
> Key: IGNITE-3176
> URL: https://issues.apache.org/jira/browse/IGNITE-3176
> Project: Ignite
>  Issue Type: Bug
>  Components: clients, general
>Affects Versions: 1.6
>Reporter: Ilya Suntsov
>Priority: Critical
> Fix For: 2.1
>
> Attachments: benchmark.properties
>
>
> In case when started more than one client/server on one host yardstick 
> re-write GC logs.
> GC options contain in *.properties files:
> {noformat}
> now0=`date +'%H%M%S'`
> # JVM options.
> JVM_OPTS=${JVM_OPTS}" -DIGNITE_QUIET=false"
> # Uncomment to enable concurrent garbage collection (GC) if you encounter 
> long GC pauses.
> JVM_OPTS=${JVM_OPTS}" \
> -Xloggc:./gc${now0}.log \
> -XX:+PrintGCDetails \
> -verbose:gc \
> -XX:+UseParNewGC \
> -XX:+UseConcMarkSweepGC \
> -XX:+UseTLAB \
> -XX:NewSize=128m \
> -XX:MaxNewSize=128m \
> -XX:MaxTenuringThreshold=0 \
> -XX:SurvivorRatio=1024 \
> -XX:+UseCMSInitiatingOccupancyOnly \
> -XX:CMSInitiatingOccupancyFraction=60 \
> {noformat}
> As you can see here will be created 1 log file and if you start another 
> driver/server with the same properties file will be re-write.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (IGNITE-5470) Web Console: Model import should generate QueryEntity.KeyFieldName for _key

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko closed IGNITE-5470.
-
Assignee: Alexey Kuznetsov  (was: Vasiliy Sisko)

> Web Console: Model import should generate QueryEntity.KeyFieldName for _key
> ---
>
> Key: IGNITE-5470
> URL: https://issues.apache.org/jira/browse/IGNITE-5470
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 2.0
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
> Fix For: 2.2
>
>
> DTO did not have "id", because it was detected to be a KEY. So, it Web 
> Console converted it to "_key" - a special field that treated as key. (Ignite 
> is a key-value storage!)
> To overcome this issue since Ignite 2.0 QueryEntity.KeyFieldName property 
> introduced - we need to generate this field on model import.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (IGNITE-5470) Web Console: Model import should generate QueryEntity.KeyFieldName for _key

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko resolved IGNITE-5470.
---
Resolution: Duplicate

Duplicate of IGNITE-5369

> Web Console: Model import should generate QueryEntity.KeyFieldName for _key
> ---
>
> Key: IGNITE-5470
> URL: https://issues.apache.org/jira/browse/IGNITE-5470
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 2.0
>Reporter: Alexey Kuznetsov
>Assignee: Vasiliy Sisko
> Fix For: 2.2
>
>
> DTO did not have "id", because it was detected to be a KEY. So, it Web 
> Console converted it to "_key" - a special field that treated as key. (Ignite 
> is a key-value storage!)
> To overcome this issue since Ignite 2.0 QueryEntity.KeyFieldName property 
> introduced - we need to generate this field on model import.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-5435) JDBC thin: support statement close on completion

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-5435:
---

Assignee: Taras Ledkov

> JDBC thin: support statement close on completion
> 
>
> Key: IGNITE-5435
> URL: https://issues.apache.org/jira/browse/IGNITE-5435
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc
>Affects Versions: 2.0
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> The methods of JDBC {Statement} must be supported:
> - {{closeOnCompletion(boolean)}};
> - {{isCloseOnCompletion}};



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-5512) AssertionError: GridDhtPartitionsExchangeFuture

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-5512:
---

Assignee: Semen Boikov

> AssertionError: GridDhtPartitionsExchangeFuture
> ---
>
> Key: IGNITE-5512
> URL: https://issues.apache.org/jira/browse/IGNITE-5512
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Semen Boikov
> Fix For: 2.1
>
>
> Reproducer: {{IgniteDynamicCacheStartSelfTest.testStartStopWithClientJoin}}
> Sample log: 
> http://ci.ignite.apache.org/viewLog.html?buildId=664862=buildResultsDiv=Ignite20Tests_IgniteCache4
> Stack trace:
> {code}
> [17:30:52]W:   [org.apache.ignite:ignite-core] Exception in thread 
> "exchange-worker-#12653%cache.IgniteDynamicCacheStartSelfTest3%" 
> java.lang.AssertionError: GridDhtPartitionsExchangeFuture [dummy=false, 
> forcePreload=false, reassign=false, discoEvt=DiscoveryCustomEvent 
> [customMsg=null, affTopVer=AffinityTopologyVersion [topVer=30, 
> minorTopVer=2], super=DiscoveryEvent [evtNode=TcpDiscoveryNode 
> [id=94a7350b-cae3-4381-a458-55e55001, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:47501], discPort=47501, order=2, intOrder=2, 
> lastExchangeTime=1497537052792, loc=false, ver=2.1.0#19700101-sha1:, 
> isClient=false], topVer=30, nodeId8=24ab11ae, msg=null, 
> type=DISCOVERY_CUSTOM_EVT, tstamp=1497537052823]], crd=TcpDiscoveryNode 
> [id=1d00ae44-d805-4edc-a49f-e4630c70, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
> lastExchangeTime=1497537052792, loc=false, ver=2.1.0#19700101-sha1:, 
> isClient=false], exchId=GridDhtPartitionExchangeId 
> [topVer=AffinityTopologyVersion [topVer=30, minorTopVer=2], nodeId=94a7350b, 
> evt=DISCOVERY_CUSTOM_EVT], added=true, initFut=GridFutureAdapter 
> [ignoreInterrupts=false, state=DONE, res=false, hash=1608702177], init=false, 
> lastVer=null, partReleaseFut=null, exchActions=null, affChangeMsg=null, 
> skipPreload=true, clientOnlyExchange=false, initTs=1497537052823, 
> centralizedAff=false, changeGlobalStateE=null, 
> exchangeOnChangeGlobalState=false, forcedRebFut=null, done=true, evtLatch=0, 
> remaining=[1d00ae44-d805-4edc-a49f-e4630c70, 
> e0eb00f0-1f63-4aa6-8c70-60a4b352, 94a7350b-cae3-4381-a458-55e55001], 
> super=GridFutureAdapter [ignoreInterrupts=false, state=DONE, res=class 
> org.apache.ignite.internal.IgniteInterruptedCheckedException: Node is 
> stopping: cache.IgniteDynamicCacheStartSelfTest3, hash=1631759081]]
> [17:30:52]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:569)
> [17:30:52]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1858)
> [17:30:52]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> [17:30:52]W:   [org.apache.ignite:ignite-core]at 
> java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5712) Context switching for optimistic transactions

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5712:


GitHub user voipp opened a pull request:

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

IGNITE-5712 Context switching between threads for optimistic transact…

…ions

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

$ git pull https://github.com/voipp/ignite IGNITE-5712

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

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


commit f8f9a2c16b81a9afa6cb5ccbf5f283a8af9103fc
Author: voipp 
Date:   2017-06-30T15:06:53Z

IGNITE-5712 Context switching between threads for optimistic transactions




> Context switching for optimistic transactions
> -
>
> Key: IGNITE-5712
> URL: https://issues.apache.org/jira/browse/IGNITE-5712
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>
> Implement context switching between threads for optimistic transactions



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-3878) Add isPrimary() and isBackup() methods on CacheQUeryEntryEvent

[Maksim Kozlov (JIRA)]

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

Maksim Kozlov updated IGNITE-3878:
--
Fix Version/s: (was: 2.1)
   2.2

> Add isPrimary() and isBackup() methods on CacheQUeryEntryEvent
> --
>
> Key: IGNITE-3878
> URL: https://issues.apache.org/jira/browse/IGNITE-3878
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 1.7
>Reporter: Nikolay Tikhonov
>Assignee: Maksim Kozlov
>Priority: Minor
> Fix For: 2.2
>
>
> In some cases useful know where (on primary or backup nodes) was invoked  a 
> continuous query filter.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5401) Investigate hangs in JDBC driver testIndexState()

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5401:


Github user asfgit closed the pull request at:

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


> Investigate hangs in JDBC driver testIndexState()
> -
>
> Key: IGNITE-5401
> URL: https://issues.apache.org/jira/browse/IGNITE-5401
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc, sql
>Reporter: Vladimir Ozerov
>Assignee: Sergey Chugunov
> Fix For: 2.1
>
>
> Two JDBC tests hang from time to time. Root cause is the same as tests are 
> similar.
> 1) 
> org.apache.ignite.jdbc.thin.JdbcThinDynamicIndexAbstractSelfTest#testIndexState
> 2) 
> org.apache.ignite.internal.jdbc2.JdbcDynamicIndexAbstractSelfTest#testIndexState
> Failures are noly happen in ATOMIC PARTITIONED cache (with and without 
> "near").
> Stack trace:
> {noformat}
> [17:37:00] :   [Step 4/5] Thread 
> [name="test-runner-#22990%thin.JdbcThinDynamicIndexAtomicPartitionedSelfTest%",
>  id=29018, state=WAITING, blockCnt=0, waitCnt=4]
> [17:37:00] :   [Step 4/5] at sun.misc.Unsafe.park(Native Method)
> [17:37:00] :   [Step 4/5] at 
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:315)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:176)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.MarshallerContextImpl.registerClassName(MarshallerContextImpl.java:262)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:780)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:757)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.binary.BinaryContext.descriptorForClass(BinaryContext.java:628)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:164)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:248)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.processors.cache.binary.CacheObjectBinaryProcessorImpl.marshalToBinary(CacheObjectBinaryProcessorImpl.java:371)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.processors.cache.binary.CacheObjectBinaryProcessorImpl.toBinary(CacheObjectBinaryProcessorImpl.java:849)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.processors.cache.binary.CacheObjectBinaryProcessorImpl.toCacheObject(CacheObjectBinaryProcessorImpl.java:799)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.processors.cache.GridCacheContext.toCacheObject(GridCacheContext.java:1769)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapSingleUpdate(GridNearAtomicSingleUpdateFuture.java:546)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:451)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:440)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1161)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put0(GridDhtAtomicCache.java:650)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2329)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.processors.cache.distributed.near.GridNearAtomicCache.put(GridNearAtomicCache.java:444)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2306)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.i.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1494)
> [17:37:00] :   [Step 4/5] at 
> o.a.i.jdbc.thin.JdbcThinDynamicIndexAbstractSelfTest.testIndexState(JdbcThinDynamicIndexAbstractSelfTest.java:273)
> [17:37:00] :   [Step 4/5] at 
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 

[jira] [Commented] (IGNITE-5187) Dynamic index create/drop tests are flaky

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5187:


Github user asfgit closed the pull request at:

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


> Dynamic index create/drop tests are flaky
> -
>
> Key: IGNITE-5187
> URL: https://issues.apache.org/jira/browse/IGNITE-5187
> Project: Ignite
>  Issue Type: Test
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.1
>
>
> Currently we rely on {{Thread.sleep}}. Probably we need something more 
> reliable.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5424) GridServiceProxy does not unwraps exception message from InvocationTargetException

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5424:


Github user asfgit closed the pull request at:

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


> GridServiceProxy does not unwraps exception message from 
> InvocationTargetException
> --
>
> Key: IGNITE-5424
> URL: https://issues.apache.org/jira/browse/IGNITE-5424
> Project: Ignite
>  Issue Type: Bug
>  Components: managed services
>Affects Versions: 2.1
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
> Fix For: 2.1
>
>
> Instead of correct message 'null' passed.
> {noformat}
> class org.apache.ignite.IgniteException: null
>   at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:957)
>   at 
> org.apache.ignite.internal.processors.service.GridServiceProxy.invokeMethod(GridServiceProxy.java:208)
>   at 
> org.apache.ignite.internal.processors.service.GridServiceProxy$ProxyInvocationHandler.invoke(GridServiceProxy.java:356)
>   at org.apache.ignite.internal.processors.service.$Proxy25.go(Unknown 
> Source)
>   at 
> org.apache.ignite.internal.processors.service.GridServiceProcessorProxySelfTest.testException(GridServiceProcessorProxySelfTest.java:78)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1979)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:130)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1894)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException: null
>   at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7262)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:258)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:189)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
>   at 
> org.apache.ignite.internal.processors.service.GridServiceProxy.invokeMethod(GridServiceProxy.java:197)
>   ... 12 more
> Caused by: java.lang.reflect.InvocationTargetException
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.ignite.internal.processors.service.GridServiceProxy$ServiceProxyCallable.call(GridServiceProxy.java:417)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1847)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:566)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6641)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:560)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at 
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1180)
>   at 
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1907)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1550)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1178)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:124)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1095)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   ... 1 more
> Caused by: 

[jira] [Commented] (IGNITE-5528) IS_EVICT_DISABLED flag is not cleared when cache store throws an exception

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5528:


Github user asfgit closed the pull request at:

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


> IS_EVICT_DISABLED flag is not cleared when cache store throws an exception
> --
>
> Key: IGNITE-5528
> URL: https://issues.apache.org/jira/browse/IGNITE-5528
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Alexey Goncharuk
>Assignee: Andrew Mashenkov
> Fix For: 2.1
>
> Attachments: GridCachePartitionEvictionDuringReadThroughSelfTest.java
>
>
> Below is an observation from a live system:
> On a large cluster with occasional topology changes, there is a sporadic hang 
> which manifests itself with "Failed to evict partition message" for one of 
> the caches with enabled cache store. I managed to take a heap dump and found 
> out that on the hanging node there was a single entry with IS_EVICT_DISABLED 
> flag set and no other threads were doing store load operation. Earlier in the 
> logs I saw that the cache store threw a CacheLoaderException due to 
> interrupted connection with a database.
> Currently, the flag is set before the cache store load and it is cleared 
> after the load.
> Looks like if the store throws an exception, this leads to the leaked flag 
> set and the entry cannot be cleared from the partition. As a result, on the 
> next topology change partition exchange will be freezed with "Failed to wait 
> for partition eviction" error message.
> Attached is the test reproducing this issue (note that the message appears 
> after one minute)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5558) Add ability to read WAL outside of an Ignite node

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5558:


Github user asfgit closed the pull request at:

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


> Add ability to read WAL outside of an Ignite node
> -
>
> Key: IGNITE-5558
> URL: https://issues.apache.org/jira/browse/IGNITE-5558
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Dmitriy Pavlov
> Fix For: 2.1
>
>
> Currently, the WAL iterator can be obtained from the WAL manager when an 
> Ignite node is up and running.
> However, it may be extremely useful to read WAL in an 'offline' mode, when a 
> node is not started up. This may be required for crash analysis or to export 
> committed data to some external systems.
> In the future we can make this even a public interface, however as a starting 
> point, I would like to keep it in private package because moving to the 
> public package will require Iterator and records to be public too.
> So, as a starting point, we need:
>  * An object that will allow us to get WALIterator instances (probably, 
> should be closeable)
>  * A method on this object which will create an iterator by a file name or 
> file names
> Using this object should not require an active Ignite instance running.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5604) Activate fails in case node was stopped with cancel=true and big objects in cache

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5604:


Github user asfgit closed the pull request at:

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


> Activate fails in case node was stopped with cancel=true and big objects in 
> cache
> -
>
> Key: IGNITE-5604
> URL: https://issues.apache.org/jira/browse/IGNITE-5604
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Taras Ledkov
>Assignee: Dmitriy Govorukhin
> Fix For: 2.1
>
>
> Please take a look at the test 
> {{IgniteWalRecoveryTest#testWalBigObjectNodeCancel}}.
> The test is available at the [pull 
> request|https://github.com/apache/ignite/pull/2211].
> The error is:
> {code}
> [2017-06-28 15:50:46,020][ERROR][main][root] Test failed.
> class org.apache.ignite.IgniteException: Fail activate
>   at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:957)
>   at 
> org.apache.ignite.internal.IgniteKernal.active(IgniteKernal.java:3408)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.db.wal.IgniteWalRecoveryTest.testWalBigObjectNodeCancel(IgniteWalRecoveryTest.java:249)
>   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:1995)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1910)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException: Fail activate
>   Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to 
> restore memory state (checkpoint marker is present on disk, but checkpoint 
> record is missed in WAL) [cpStatus=CheckpointStatus [cpStartTs=1498654243491, 
> cpStartId=7f873e0b-b1ee-4bd6-8605-b139b82898c9, startPtr=FileWALPointer 
> [idx=0, fileOffset=8657376, len=2425, forceFlush=false], 
> cpEndId=----, endPtr=FileWALPointer [idx=0, 
> fileOffset=0, len=0, forceFlush=false]], lastRead=FileWALPointer [idx=0, 
> fileOffset=4340447, len=39, forceFlush=false]]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreMemory(GridCacheDatabaseSharedManager.java:1471)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readCheckpointAndRestoreMemory(GridCacheDatabaseSharedManager.java:578)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.initCachesAndRestoreMemory(GridCacheDatabaseSharedManager.java:492)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.onActivate(GridCacheDatabaseSharedManager.java:508)
>   at 
> org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onActivate(GridClusterStateProcessor.java:747)
>   at 
> org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onChangeGlobalState(GridClusterStateProcessor.java:655)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:719)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:563)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1872)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5702) Investigate H2DynamicIndexingComplexTest.testOperations failures on replicated caches

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5702:


Github user asfgit closed the pull request at:

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


> Investigate H2DynamicIndexingComplexTest.testOperations failures on 
> replicated caches
> -
>
> Key: IGNITE-5702
> URL: https://issues.apache.org/jira/browse/IGNITE-5702
> Project: Ignite
>  Issue Type: Test
>  Components: sql
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 2.1
>
>
> {{org.apache.ignite.internal.processors.cache.index.H2DynamicIndexingComplexTest#testOperations}}
>  fails in variations with replicated caches.
> This happens because with {{REPLICATED}} template we don't set proper write 
> mode when cache is created.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5592) Remove IgniteCache#localEvict method

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5592:


Github user asfgit closed the pull request at:

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


> Remove IgniteCache#localEvict method
> 
>
> Key: IGNITE-5592
> URL: https://issues.apache.org/jira/browse/IGNITE-5592
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
>Assignee: Aleksandr Meterko
> Fix For: 2.1
>
>
> The method doesn't make much sense in 2.0. Before 2.0 it could be used to 
> evict from on-heap memory to off-heap or swap. Currently off-heap always has 
> the data and there is no swap, so the method should be removed to avoid 
> confusion.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5441) .NET: Stack trace is lost for exceptions in ICacheStore

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5441:


Github user asfgit closed the pull request at:

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


> .NET: Stack trace is lost for exceptions in ICacheStore
> ---
>
> Key: IGNITE-5441
> URL: https://issues.apache.org/jira/browse/IGNITE-5441
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 2.2
>
>
> When exception happens during cache store invocation ({{Write}} method in 
> particular), Java stack trace is lost, original .NET stack trace is lost, 
> exception is quite useless. See {{CheckCustomStoreError}} in 
> {{TestLoadCache}}, this test should be improved to make sure we preserve all 
> information.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5426) JDBC thin: support readOnly

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5426:


Github user asfgit closed the pull request at:

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


> JDBC thin: support readOnly
> ---
>
> Key: IGNITE-5426
> URL: https://issues.apache.org/jira/browse/IGNITE-5426
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc
>Affects Versions: 2.0
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> The {{is/setReadOnly}} methods must be supported by the JDBC {{Connection}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5340) AssertionError in index name check

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5340:


Github user asfgit closed the pull request at:

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


> AssertionError in index name check
> --
>
> Key: IGNITE-5340
> URL: https://issues.apache.org/jira/browse/IGNITE-5340
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Vladislav Pyatkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> The exception will be got when index name manual assign with "#" symbol, 
> through the method {{org.apache.ignite.cache.QueryIndex#setName()}}
> {noformat}
> java.lang.AssertionError: null
>  at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.escapeName(IgniteH2Indexing.java:1980)
>  
>  at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$TableDescriptor.createUserIndex(IgniteH2Indexing.java:3214)
>  
>  at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$TableDescriptor.createUserIndexes(IgniteH2Indexing.java:3199)
>  
>  at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createTable(IgniteH2Indexing.java:2041)
>  
>  at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:1909)
>  
>  at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.registerCache0(GridQueryProcessor.java:1298)
>  
>  at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:751)
>  
>  at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:809)
>  
>  at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1261)
>  
>  at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1930)
>  
>  at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1817)
>  
>  at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:384)
>  
>  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:764)
>  
>  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:556)
>  
>  at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1824)
>  at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>  at java.lang.Thread.run(Thread.java:745)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5533) CREATE INDEX failed if table has been re-created

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5533:


Github user asfgit closed the pull request at:

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


> CREATE INDEX failed if table has been re-created
> 
>
> Key: IGNITE-5533
> URL: https://issues.apache.org/jira/browse/IGNITE-5533
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Sergey Kozlov
>Assignee: Alexander Paschenko
>Priority: Critical
> Fix For: 2.1
>
>
> The brief scenario:
> create table t1 - ok
> insert t1 - ok
> create index t1 - ok
> drop table t1 - ok
> create table t1 - ok
> insert t1 - ok
> create index t1 - fail
> {noformat}
> [21:13:46,190][SEVERE][sql-connector-#239%null%][JdbcRequestHandler] Failed 
> to execute SQL query [reqId=25, req=JdbcQueryExecuteRequest [schemaName=nu
> ll, pageSize=1024, maxRows=0, sqlQry=create index on "PUBLIC".t1 (b desc), 
> args=[]]]
> class org.apache.ignite.internal.processors.query.IgniteSQLException: Schema 
> change operation failed: Failed to execute SQL statement on internal H2 d
> atabase: CREATE INDEX "t1_b_desc_idx" ON "PUBLIC"."T1" ("B" DESC, "_KEY" ASC)
> at 
> org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.convert(DdlStatementsProcessor.java:277)
> at 
> org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.runDdlStatement(DdlStatementsProcessor.java:221)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1331)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1856)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1852)
> at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2293)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1860)
> at 
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:188)
> at 
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:122)
> at 
> org.apache.ignite.internal.processors.odbc.SqlListenerNioListener.onMessage(SqlListenerNioListener.java:152)
> at 
> org.apache.ignite.internal.processors.odbc.SqlListenerNioListener.onMessage(SqlListenerNioListener.java:44)
> at 
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
> at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at 
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at 
> org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
> 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}
> {code:title=repoducer.java|borderStyle=solid}
> Connection conn = 
> DriverManager.getConnection("jdbc:ignite:thin://127.0.0.1");
> Statement stmt = conn.createStatement();
> for (int i=0; i < 2; i++) {
> String t = Integer.toString(1);
> print(t);
> stmt.execute("drop table if exists \"PUBLIC\".t" + t);
> stmt.execute("create table \"PUBLIC\".t" + t + " (a int 
> primary key, b varchar(30))");
> for (int j=1; j < 10; j++) {
> String s = Integer.toString(j);
> stmt.execute("insert into \"PUBLIC\".t" + t + " (a,b) 
> values (" + s + ", '" + s + "')");
> }
> stmt.execute("create index on \"PUBLIC\".t" + t + " (b 
> desc)");
> stmt.execute("drop table \"PUBLIC\".t" + t);
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5552) ServiceProcessor recalculates all service assignments even if there is a pending topology change

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5552:


Github user asfgit closed the pull request at:

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


> ServiceProcessor recalculates all service assignments even if there is a 
> pending topology change
> 
>
> Key: IGNITE-5552
> URL: https://issues.apache.org/jira/browse/IGNITE-5552
> Project: Ignite
>  Issue Type: Improvement
>  Components: managed services
>Affects Versions: 1.7
>Reporter: Alexey Goncharuk
>Assignee: Andrew Mashenkov
> Fix For: 2.1
>
>
> This behavior was observed in a real cluster of hundreds of nodes and 
> hundreds of services.
> After a ~30 new nodes startup, we expected node singletons to be deployed 
> immediately, but the services were deployed with ~4hr delay on last nodes. 
> The reason for this is the fact that ALL service deployments are recalculated 
> on ALL discovery events. In this case, a single discovery event was processed 
> in a time span of 2-5 minutes, which with the lateAffinityAssignment=true 
> yielded a 4hr delay for the last node.
> The quick change that may improve things a lot is aborting current assignment 
> calculations if there is a pending discovery event needs to be processed.
> The rest of the optimizations are put to 
> https://issues.apache.org/jira/browse/IGNITE-5551



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5712) Context switching for optimistic transactions

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov commented on IGNITE-5712:
--

The following tests performed for one node cluster, and for a couple of nodes : 
client and server nodes.
Keys reside on server node(server node is a primary node), put operation 
performed on client node.

||Scenarion||Result||
|Start transaction, perform some put operations, resume in another thread, 
commit. |New keys are in cache|
|Start transaction, perform some put operations, resume in another thread. Then 
suspend it and continue to original thread, commit it |New keys are in cache|
|Like the first test, but with a couple of different cache put(cross cache 
transaction)|New keys are in cache|
|Like the second test, but with a couple of different cache put(cross cache 
transaction)|New keys are in cache|
|Start transaction, perform some put operations, resume in another thread, 
rollback. |No new keys are in cache|

The following tests performed for a couple of nodes.
||Scenarion||Result||
|Start 10 transactions in one thread, write the only key, suspend them by 
order. The next step is resume, commit by order |The last write is persisted 
only|
|Start tx, write key and suspend. The next is resume in another thread, suspend 
before commit. Start new tx in the first thread, make commit. Resume first tx 
and commit it. |The first tx result is persisted|
|Pessimistic tx write key , suspend forever. Start new pessimistic tx, try to 
write the same key | The second tx hangs waiting for unblock on the key|
|Pessimistic tx write key , suspend forever. Trying to put cache lock on the 
key.| Cache lock hangs waiting for unblock on the key(Will not include in PR)|
|When one transaction is suspending, others - concurrently perform 
suspend,resume,end etc. |New key is in cache, other transactions failed with 
exception|
|When one transaction is resuming, others - concurrently perform 
suspend,resume,end etc.|New key is in cache, other transactions failed with 
exception|
|When one transaction is committing, others - concurrently perform 
suspend,resume,end etc.|New key is in cache, other transactions failed with 
exception|
|When one transaction is rollbacking, others - concurrently perform 
suspend,resume,end etc.|New key is in cache, other transactions failed with 
exception|
|When one transaction is closing, others - concurrently perform 
suspend,resume,end etc.|New key is in cache, other transactions failed with 
exception|

The following failover tests performed for a couple of nodes.
||Scenarion||Result||
|Starting transaction on server node, suspend it. 
Then primary node got broken, 
resuming transaction and committing leads to exception.|Proper exception is 
thrown(depends on transaction concurrency), 
either new values persisted on some cluster node 
or not(depends on transaction concurrency)|
|Starting transaction on client node, suspend it. 
Then primary node got broken, resuming transaction 
and committing leads to exception.|Proper exception is thrown(depends on 
transaction concurrency),
 either new values persisted on some cluster node 
or not(depends on transaction concurrency)|
|Starting transaction, suspend it. 
Then initiating node got broken, resuming transaction 
and committing leads to exception.|Proper exception is thrown(depends on 
transaction concurrency),
 no new values persisted on cluster nodes|

> Context switching for optimistic transactions
> -
>
> Key: IGNITE-5712
> URL: https://issues.apache.org/jira/browse/IGNITE-5712
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>
> Implement context switching between threads for optimistic transactions



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-4188) Savepoints support inside of Ignite Transactions

[Semen Boikov (JIRA)]

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

Semen Boikov edited comment on IGNITE-4188 at 7/7/17 9:16 AM:
--

[~SomeFire], I think now there is no ready code to unlock transactional locks. 
Look at GridNearTransactionalCache.unlockAll, maybe this code can be reused for 
your purpose. Also we need carefully handle case when you try do unlock but 
primary node failed at this point, definitely need add tests for this scenario.

Thanks


was (Author: sboikov):
[~SomeFire], I think now there is no ready code to unlock transactional locks. 
Look at GridNearTransactionalCache.unlockAll, maybe this code can be reused for 
your purpose. Also we need carefully handle case when you try do unlock but 
primary node failed at this point, definitely need at tests for this scenario.

Thanks

> Savepoints support inside of Ignite Transactions
> 
>
> Key: IGNITE-4188
> URL: https://issues.apache.org/jira/browse/IGNITE-4188
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
>Assignee: Ryabov Dmitrii
> Fix For: 2.2
>
>
> A savepoint is a special mark inside a transaction that allows all commands 
> that are executed after it was established to be rolled back, restoring the 
> transaction state to what it was at the time of the savepoint.
> Here is a reference to the similar functionality implemented by some of RDBMs 
> vendors.
> https://www.postgresql.org/docs/8.1/static/sql-savepoint.html
> https://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_10001.htm
> http://dev.mysql.com/doc/refman/5.7/en/savepoint.html
> Consider the following example.
> {code}
> BEGIN;
> INSERT INTO table1 VALUES (1); 
> SAVEPOINT my_savepoint; 
> INSERT INTO table1 VALUES (2); 
> ROLLBACK TO SAVEPOINT my_savepoint; 
> INSERT INTO table1 VALUES (3); 
> COMMIT;
> {code}
> The execution result must guarantee that only values 1 and 3 are inserted 
> into table1.
> In Ignite, it should be supported this way (preserving the same behavior as 
> above).
> {code}
> Ignite ignite = ;
> IgniteCache c = ;
> try (Transaction tx = ignite.transactions().txStart()) {
> c.put(1, 1);
> 
> tx.savepoint("mysavepoint");
> 
> c.put(2, 2);
> 
> tx.rollbackToSavepoint("mysavepoint");
> 
> c.put(3, 3);
> 
> tx.commit();
> }
> {code}
> As a summary the following has to be supported on Ignite side:
> - The {{savepoint}} method which will set a named transaction savepoint with 
> a name of an identifier.
> - Multiple savepoints defined within a transaction. The names of the 
> savepoints have to differ from each other. If the current transaction has a 
> savepoint with the same name, the old savepoint is deleted and a new one is 
> set.
> - The {{rollbackToSavepoint}} method that will roll back all the changes done 
> after a specific checkpoint establishment.
> - The {{releaseCheckpoint}} method that will destroy a savepoint, keeping the 
> effects of commands executed after it was established.
> - Full support of the behavior listed above at the level of ODBC and JDBC 
> drivers and DML (will be handled under separate tickets).
> - The behavior has to be support for all transactional modes.
> Original proposal on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/TX-savepoints-td12041.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5716) .NET: Negative field offset values can be observed on 2-byte offsets

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5716:
--

 Summary: .NET: Negative field offset values can be observed on 
2-byte offsets
 Key: IGNITE-5716
 URL: https://issues.apache.org/jira/browse/IGNITE-5716
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.9
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Priority: Blocker
 Fix For: 2.1


{{BinaryObjectSchemaSerializer.WriteSchema}} uses {{ushort.MaxValue}} as a 
boundary for 2-byte offsets. {{ReadSchema}} uses {{ReadShort}}, which returns 
negative offsets for anything above {{short.MaxValue}}.

* Ensure that all offsets are always non-negative (use uint in 
{{BinaryObjectSchemaField}} probably)
* Check how Java handles this
* Add tests for all edge cases



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5709) Node stopped on OutOfMemoryException with persistence

[Alexei Scherbakov (JIRA)]

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

Alexei Scherbakov updated IGNITE-5709:
--
Affects Version/s: (was: 2.1)
   2.2

> Node stopped on OutOfMemoryException with persistence
> -
>
> Key: IGNITE-5709
> URL: https://issues.apache.org/jira/browse/IGNITE-5709
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.2
>Reporter: Alexander Belyak
>Priority: Critical
>
> In long heavy (100%) load node with configured persistence can stop with 
> "org.apache.ignite.internal.mem.OutOfMemoryException: Failed to find a page 
> for eviction" exception. In my test it fail after 23 hour of 100% load while 
> expiration outdated entries (by CreatedExpiryPolicy).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-5710) Web console: H2 version in pom file depends from Ignite version

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-5710:
-

Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

Please test version of H2 in case when cache store configured, or JDBC 
discovery configured, or checkpoint SPI configured.

> Web console: H2 version in pom file depends from Ignite version
> ---
>
> Key: IGNITE-5710
> URL: https://issues.apache.org/jira/browse/IGNITE-5710
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.0
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 2.1
>
>
> 1.4.191 for 1.x version and 1.4.195 for 2.x version.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)