[jira] [Commented] (IGNITE-6095) Web console: In demo mode Implement configuration of key fields in domain model for SQL query

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-6095:
---

Please test.

> Web console: In demo mode Implement configuration of key fields in domain 
> model for SQL query
> -
>
> Key: IGNITE-6095
> URL: https://issues.apache.org/jira/browse/IGNITE-6095
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 2.3
>
>




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

[jira] [Assigned] (IGNITE-6095) Web console: In demo mode Implement configuration of key fields in domain model for SQL query

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-6095:
-

Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

> Web console: In demo mode Implement configuration of key fields in domain 
> model for SQL query
> -
>
> Key: IGNITE-6095
> URL: https://issues.apache.org/jira/browse/IGNITE-6095
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.3
>
>




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

[jira] [Commented] (IGNITE-6376) Web console: Enable task and job events in demo mode by default.

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-6376:
---

Please test

> Web console: Enable task and job events in demo mode by default.
> 
>
> Key: IGNITE-6376
> URL: https://issues.apache.org/jira/browse/IGNITE-6376
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
> Fix For: 2.3
>
>




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

[jira] [Assigned] (IGNITE-6376) Web console: Enable task and job events in demo mode by default.

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-6376:
-

Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

> Web console: Enable task and job events in demo mode by default.
> 
>
> Key: IGNITE-6376
> URL: https://issues.apache.org/jira/browse/IGNITE-6376
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 2.3
>
>




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

[jira] [Commented] (IGNITE-6095) Web console: In demo mode Implement configuration of key fields in domain model for SQL query

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-6095:
---

Added aliases for key fields of demo models.

> Web console: In demo mode Implement configuration of key fields in domain 
> model for SQL query
> -
>
> Key: IGNITE-6095
> URL: https://issues.apache.org/jira/browse/IGNITE-6095
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
>Priority: Minor
>




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

[jira] [Updated] (IGNITE-6095) Web console: In demo mode Implement configuration of key fields in domain model for SQL query

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-6095:
-
Fix Version/s: 2.3

> Web console: In demo mode Implement configuration of key fields in domain 
> model for SQL query
> -
>
> Key: IGNITE-6095
> URL: https://issues.apache.org/jira/browse/IGNITE-6095
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 2.3
>
>




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

[jira] [Assigned] (IGNITE-6095) Web console: In demo mode Implement configuration of key fields in domain model for SQL query

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-6095:
-

Assignee: Alexey Kuznetsov  (was: Vasiliy Sisko)

> Web console: In demo mode Implement configuration of key fields in domain 
> model for SQL query
> -
>
> Key: IGNITE-6095
> URL: https://issues.apache.org/jira/browse/IGNITE-6095
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
>Priority: Minor
>




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

[jira] [Assigned] (IGNITE-6376) Web console: Enable task and job events in demo mode by default.

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-6376:
-

Assignee: Alexey Kuznetsov  (was: Vasiliy Sisko)

> Web console: Enable task and job events in demo mode by default.
> 
>
> Key: IGNITE-6376
> URL: https://issues.apache.org/jira/browse/IGNITE-6376
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
> Fix For: 2.3
>
>




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

[jira] [Comment Edited] (IGNITE-6376) Web console: Enable task and job events in demo mode by default.

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko edited comment on IGNITE-6376 at 9/19/17 4:25 AM:


Implemented collecting of task events in demo mode.


was (Author: vsisko):
Incremented collecting of task events in demo mode.

> Web console: Enable task and job events in demo mode by default.
> 
>
> Key: IGNITE-6376
> URL: https://issues.apache.org/jira/browse/IGNITE-6376
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
> Fix For: 2.3
>
>




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

[jira] [Commented] (IGNITE-2786) SpringCache doesn't survive client reconnect

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-2786:
-

[~bbarin]
* https://apacheignite.readme.io/docs/events
* https://apacheignite.readme.io/docs/clients-vs-servers#client-reconnection

> SpringCache doesn't survive client reconnect
> 
>
> Key: IGNITE-2786
> URL: https://issues.apache.org/jira/browse/IGNITE-2786
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>
> After a client disconnects and reconnects with new ID, Spring caching can't 
> be used, because existing cache instance are closed.



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

[jira] [Commented] (IGNITE-2786) SpringCache doesn't survive client reconnect

[Bruno Barin (JIRA)]

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

Bruno Barin commented on IGNITE-2786:
-

CacheErrorHandler is the Spring's interface to handle cache errors. This could 
be instantiated and included in the ApplicationContext in SpringCacheManager 
class. If we only cleanup caches at SpringCacheManager class, the 
AbstractCacheInvoker will still hold a reference to cache map.

Could you please point me to an example to listen to Ignite events?

Cheers

> SpringCache doesn't survive client reconnect
> 
>
> Key: IGNITE-2786
> URL: https://issues.apache.org/jira/browse/IGNITE-2786
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>
> After a client disconnects and reconnects with new ID, Spring caching can't 
> be used, because existing cache instance are closed.



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

[jira] [Updated] (IGNITE-6421) Ignite WAL reader: add shell script to start converter

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-6421:
---
Description: 
Support simple startup for utility 
https://cwiki.apache.org/confluence/display/IGNITE/Ignite+WAL+reader by 
providing shell and bat files

Options which can be defined by command line
- Option A: Manual setup of directory paths.
 -- Page size (int)
 -- Path to WAL work directory (string)
 -- Path to WAL archive directory
 -- Path to marshaller cache
 -- Path to binary metadata
 -- Option to keep binary objects binary
 -- additional classpath for business classes (optional)

- Option B: Standard Ignite folders structure
 -- Page size (int)
 -- Path to Ignite work directory (string)
 -- Consistent ID (string)
 -- Option to keep binary objects binary
 -- additional classpath for business classes (optional)

Because of huge number of options it may be preferable to provide 
config(property) file. This file may be used to setup all options except 
classpath.

  was:Support simple startup for utility 
https://cwiki.apache.org/confluence/display/IGNITE/Ignite+WAL+reader by 
providing shell and bat files


> Ignite WAL reader: add shell script to start converter
> --
>
> Key: IGNITE-6421
> URL: https://issues.apache.org/jira/browse/IGNITE-6421
> Project: Ignite
>  Issue Type: Task
>  Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>
> Support simple startup for utility 
> https://cwiki.apache.org/confluence/display/IGNITE/Ignite+WAL+reader by 
> providing shell and bat files
> Options which can be defined by command line
> - Option A: Manual setup of directory paths.
>  -- Page size (int)
>  -- Path to WAL work directory (string)
>  -- Path to WAL archive directory
>  -- Path to marshaller cache
>  -- Path to binary metadata
>  -- Option to keep binary objects binary
>  -- additional classpath for business classes (optional)
> - Option B: Standard Ignite folders structure
>  -- Page size (int)
>  -- Path to Ignite work directory (string)
>  -- Consistent ID (string)
>  -- Option to keep binary objects binary
>  -- additional classpath for business classes (optional)
> Because of huge number of options it may be preferable to provide 
> config(property) file. This file may be used to setup all options except 
> classpath.



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

[jira] [Assigned] (IGNITE-6250) .NET: Thin client: Exception handling

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-6250:
---

Assignee: Vladimir Ozerov  (was: Pavel Tupitsyn)

> .NET: Thin client: Exception handling
> -
>
> Key: IGNITE-6250
> URL: https://issues.apache.org/jira/browse/IGNITE-6250
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Vladimir Ozerov
>  Labels: .NET
> Fix For: 2.3
>
>
> Exception handling in thin client: response includes a success flag. Define 
> exception format protocol in case of failure.



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

[jira] [Comment Edited] (IGNITE-6244) .NET: Thin client: ScanQuery

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov edited comment on IGNITE-6244 at 9/18/17 8:33 PM:
--

[~ptupitsyn], I fixed cursor handling. Please review my last commit. Need to 
verify that all client-related suites (.NET, ODBC, JDBC) are fine.


was (Author: vozerov):
[~ptupitsyn], I fixed cursor handling. Please review my last commit.

> .NET: Thin client: ScanQuery
> 
>
> Key: IGNITE-6244
> URL: https://issues.apache.org/jira/browse/IGNITE-6244
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.3
>
>
> Implement ScanQuery in thin client.
> Challenges:
> * Query cursor. This will require some kind of HandleRegistry on Java side, 
> so we can pass an ID back to client (see {{OdbcRequestHandler.qryCursors}} as 
> an example).
> * Predicate. Thin client is not .NET-specific. We need a way to support 
> predicates in (at least) Java and .NET, there should be some platform id.



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

[jira] [Commented] (IGNITE-6403) IgniteSqlNotNullConstraintTest.testTransactionalAddColumnNotNullCheckDmlInsertValues fails periodically

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6403:


Github user asfgit closed the pull request at:

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


> IgniteSqlNotNullConstraintTest.testTransactionalAddColumnNotNullCheckDmlInsertValues
>  fails periodically
> ---
>
> Key: IGNITE-6403
> URL: https://issues.apache.org/jira/browse/IGNITE-6403
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.3
>
>
> Looks like we have a bug in {{ALTER TABLE}} - column is not visible after 
> command is completed:
> {code}
> Caused by: org.h2.jdbc.JdbcSQLException: Column "NAME" not found; SQL 
> statement:
> INSERT INTO test(id, name, age) VALUES (1, 'ok', 1), (2, NULLIF('a', 'a'), 
> 2), (3, 'ok', 3) [42122-195]
> {code}



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

[jira] [Commented] (IGNITE-6403) IgniteSqlNotNullConstraintTest.testTransactionalAddColumnNotNullCheckDmlInsertValues fails periodically

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6403:


Github user devozerov closed the pull request at:

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


> IgniteSqlNotNullConstraintTest.testTransactionalAddColumnNotNullCheckDmlInsertValues
>  fails periodically
> ---
>
> Key: IGNITE-6403
> URL: https://issues.apache.org/jira/browse/IGNITE-6403
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.3
>
>
> Looks like we have a bug in {{ALTER TABLE}} - column is not visible after 
> command is completed:
> {code}
> Caused by: org.h2.jdbc.JdbcSQLException: Column "NAME" not found; SQL 
> statement:
> INSERT INTO test(id, name, age) VALUES (1, 'ok', 1), (2, NULLIF('a', 'a'), 
> 2), (3, 'ok', 3) [42122-195]
> {code}



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

[jira] [Commented] (IGNITE-6415) ALTER TABLE: investigate why descriptor is not updated from GridQueryProcessor#onLocalOperationFinished

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-6415:
-

[~al.psc], I tried to rework {{GridQueryProcessor}} to follow common code path, 
but {{ALTER TABLE}} tests started to fail. They check some internal state, so 
it is hard to tell whether tests are wrong or there is a bug in logic (which 
could affect {{CREATE INDEX}} command). Need to investigate it further.

> ALTER TABLE: investigate why descriptor is not updated from 
> GridQueryProcessor#onLocalOperationFinished
> ---
>
> Key: IGNITE-6415
> URL: https://issues.apache.org/jira/browse/IGNITE-6415
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.3
>
>
> For {{CREATE INDEX}} and {{DROP INDEX}} our DDL engine works as follows:
> 1) Update H2 structures from DDL worker thread
> 2) Then update type descriptor from 
> {{GridQueryProcessor#onLocalOperationFinished}}
> For some reason {{ALTER TABLE}} handled differently, and we first update 
> descriptor, then update H2. See 
> {{GridQueryProcessor#processSchemaOperationLocal}}. 
> Two questions:
> 1) Why descriptor is updated before H2? In this case we may endup in 
> inconsistent state if H2 failed for some reason
> 2) Why we decided not to follow {{CREATE/DROP INDEX}} approach?



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

[jira] [Commented] (IGNITE-2786) SpringCache doesn't survive client reconnect

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-2786:
-

[~bbarin] Are you saying that Spring does it's own caching anyway? If so, then 
I believe {{caches}} map can be removed altogether.

As for you solution: do I understand correctly that {{CacheErrorHandler}} has 
to be configured as a separate bean? If that's the case, I don't like it, as 
the discussed case has to be handled by {{SpringCacheManager}} automatically. I 
think it can be easily done in {{SpringCache}} class.

> SpringCache doesn't survive client reconnect
> 
>
> Key: IGNITE-2786
> URL: https://issues.apache.org/jira/browse/IGNITE-2786
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>
> After a client disconnects and reconnects with new ID, Spring caching can't 
> be used, because existing cache instance are closed.



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

[jira] [Assigned] (IGNITE-6403) IgniteSqlNotNullConstraintTest.testTransactionalAddColumnNotNullCheckDmlInsertValues fails periodically

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-6403:
---

Assignee: Vladimir Ozerov  (was: Alexander Paschenko)

> IgniteSqlNotNullConstraintTest.testTransactionalAddColumnNotNullCheckDmlInsertValues
>  fails periodically
> ---
>
> Key: IGNITE-6403
> URL: https://issues.apache.org/jira/browse/IGNITE-6403
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.3
>
>
> Looks like we have a bug in {{ALTER TABLE}} - column is not visible after 
> command is completed:
> {code}
> Caused by: org.h2.jdbc.JdbcSQLException: Column "NAME" not found; SQL 
> statement:
> INSERT INTO test(id, name, age) VALUES (1, 'ok', 1), (2, NULLIF('a', 'a'), 
> 2), (3, 'ok', 3) [42122-195]
> {code}



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

[jira] [Commented] (IGNITE-6403) IgniteSqlNotNullConstraintTest.testTransactionalAddColumnNotNullCheckDmlInsertValues fails periodically

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6403:


GitHub user devozerov opened a pull request:

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

IGNITE-6403



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

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

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

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


commit 9520f465c534cbd95d72ec0a3ae45b914efd047d
Author: devozerov 
Date:   2017-09-18T19:07:53Z

Attempt to fix.




> IgniteSqlNotNullConstraintTest.testTransactionalAddColumnNotNullCheckDmlInsertValues
>  fails periodically
> ---
>
> Key: IGNITE-6403
> URL: https://issues.apache.org/jira/browse/IGNITE-6403
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.3
>
>
> Looks like we have a bug in {{ALTER TABLE}} - column is not visible after 
> command is completed:
> {code}
> Caused by: org.h2.jdbc.JdbcSQLException: Column "NAME" not found; SQL 
> statement:
> INSERT INTO test(id, name, age) VALUES (1, 'ok', 1), (2, NULLIF('a', 'a'), 
> 2), (3, 'ok', 3) [42122-195]
> {code}



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

[jira] [Commented] (IGNITE-2786) SpringCache doesn't survive client reconnect

[Bruno Barin (JIRA)]

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

Bruno Barin commented on IGNITE-2786:
-

[~vkulichenko], if you really uses SpringCache with annotations, it will end up 
using AbstractCacheInvoker which holds references to the caches as well, as you 
can see in this stack trace on my application:

java.lang.IllegalStateException: Cache has been closed or destroyed: XYZ
…gnite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:164)
…ite.internal.processors.cache.IgniteCacheProxy.onEnter(IgniteCacheProxy.java:2727)
….ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:1189)

org.apache.ignite.cache.spring.SpringCache.get(SpringCache.java:57)
…framework.cache.interceptor.AbstractCacheInvoker.doGet(AbstractCacheInvoker.java:71)
…work.cache.interceptor.CacheAspectSupport.findInCaches(CacheAspectSupport.java:537)
…rk.cache.interceptor.CacheAspectSupport.findCachedItem(CacheAspectSupport.java:503)
…framework.cache.interceptor.CacheAspectSupport.execute(CacheAspectSupport.java:389)
…framework.cache.interceptor.CacheAspectSupport.execute(CacheAspectSupport.java:327)
…ingframework.cache.interceptor.CacheInterceptor.invoke(CacheInterceptor.java:61)

> SpringCache doesn't survive client reconnect
> 
>
> Key: IGNITE-2786
> URL: https://issues.apache.org/jira/browse/IGNITE-2786
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>
> After a client disconnects and reconnects with new ID, Spring caching can't 
> be used, because existing cache instance are closed.



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

[jira] [Commented] (IGNITE-6403) IgniteSqlNotNullConstraintTest.testTransactionalAddColumnNotNullCheckDmlInsertValues fails periodically

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-6403:
-

[~al.psc], please disregard my previous message, it is wrong. As far as I see 
we complete client future when {{SchemaFinishDiscoveryMessage}} is received. At 
this point all necessary changes should alread by applied to the client as 
message ordering is guaranteed, and se should have received relevant 
{{SchemaProposeDiscoveryMessage}} at this point.

> IgniteSqlNotNullConstraintTest.testTransactionalAddColumnNotNullCheckDmlInsertValues
>  fails periodically
> ---
>
> Key: IGNITE-6403
> URL: https://issues.apache.org/jira/browse/IGNITE-6403
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.3
>
>
> Looks like we have a bug in {{ALTER TABLE}} - column is not visible after 
> command is completed:
> {code}
> Caused by: org.h2.jdbc.JdbcSQLException: Column "NAME" not found; SQL 
> statement:
> INSERT INTO test(id, name, age) VALUES (1, 'ok', 1), (2, NULLIF('a', 'a'), 
> 2), (3, 'ok', 3) [42122-195]
> {code}



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

[jira] [Commented] (IGNITE-6403) IgniteSqlNotNullConstraintTest.testTransactionalAddColumnNotNullCheckDmlInsertValues fails periodically

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-6403:
-

[~al.psc], root cause of the problem is that client nodes receive custom 
discovery messages asynchronously. For this reason server node may complete 
operations and notify the client before changes are appled to client schema. As 
a result, we complete operations before local H2 is ready. To fix the problem 
we should do the following:
1) Client future must consist of two parts - server part and local part.
2) Server part is completed in the same way it is implemented now.
3) Client part is completed when changes are applied on the client.

> IgniteSqlNotNullConstraintTest.testTransactionalAddColumnNotNullCheckDmlInsertValues
>  fails periodically
> ---
>
> Key: IGNITE-6403
> URL: https://issues.apache.org/jira/browse/IGNITE-6403
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.3
>
>
> Looks like we have a bug in {{ALTER TABLE}} - column is not visible after 
> command is completed:
> {code}
> Caused by: org.h2.jdbc.JdbcSQLException: Column "NAME" not found; SQL 
> statement:
> INSERT INTO test(id, name, age) VALUES (1, 'ok', 1), (2, NULLIF('a', 'a'), 
> 2), (3, 'ok', 3) [42122-195]
> {code}



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

[jira] [Commented] (IGNITE-6403) IgniteSqlNotNullConstraintTest.testTransactionalAddColumnNotNullCheckDmlInsertValues fails periodically

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-6403:
-

[~al.psc], the fix is incorrect, unfortunately. Please change target test as 
follows to see that it still fails:
{code}
public void testTransactionalAddColumnNotNullCheckDmlInsertValues() throws 
Exception {
while (true) {

checkAddColumnNotNullCheckDmlInsertValues(CacheAtomicityMode.TRANSACTIONAL);

afterTest();
beforeTest();
}
}
{code}

> IgniteSqlNotNullConstraintTest.testTransactionalAddColumnNotNullCheckDmlInsertValues
>  fails periodically
> ---
>
> Key: IGNITE-6403
> URL: https://issues.apache.org/jira/browse/IGNITE-6403
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.3
>
>
> Looks like we have a bug in {{ALTER TABLE}} - column is not visible after 
> command is completed:
> {code}
> Caused by: org.h2.jdbc.JdbcSQLException: Column "NAME" not found; SQL 
> statement:
> INSERT INTO test(id, name, age) VALUES (1, 'ok', 1), (2, NULLIF('a', 'a'), 
> 2), (3, 'ok', 3) [42122-195]
> {code}



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

[jira] [Commented] (IGNITE-6391) JDBC thin driver: JdbcThinTcpIo.srvProtocolVer is not used

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6391:


Github user asfgit closed the pull request at:

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


> JDBC thin driver: JdbcThinTcpIo.srvProtocolVer is not used
> --
>
> Key: IGNITE-6391
> URL: https://issues.apache.org/jira/browse/IGNITE-6391
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.3
>
>
> Need to understand why it is so.



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

[jira] [Commented] (IGNITE-6099) ODBC: Implement SQLGetInfo for all info types

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6099:


GitHub user isapego opened a pull request:

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

IGNITE-6099: Fully implemented SQLGetInfo in ODBC driver.



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

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

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

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


commit d47cbcb77b287f700b337f97c9a27fe6f370f6c0
Author: Igor Sapego 
Date:   2017-08-17T17:08:46Z

IGNITE-6099: Minor refactoring

commit dbaa5307f017096499a67f4d73072f907ef8946c
Author: Igor Sapego 
Date:   2017-08-21T13:12:58Z

IGNITE-6099: Refactoring

commit 17bf12120a020c26d72d5e97ba5a19fd7299a270
Author: Igor Sapego 
Date:   2017-08-22T14:44:44Z

IGNITE-6099: More info supported

commit 3748d51aa49d3979e6a494109375946a378b34a6
Author: Igor Sapego 
Date:   2017-09-15T13:35:07Z

IGNITE-6099: Added support for more info attributes.

commit 68996edf4dae62adab6d55849169864c476a944f
Author: Igor Sapego 
Date:   2017-09-15T15:41:57Z

IGNITE-6099: Further progress.

commit c74c8db5eee0dfa83872f9500dd026d76ae9610b
Author: Igor Sapego 
Date:   2017-09-18T16:16:50Z

IGNITE-6099: Further progress.

commit bbbee5bd6fd8c606919d4a6c692329509ad17d92
Author: Igor Sapego 
Date:   2017-09-18T18:31:02Z

IGNITE-6099: Complete




> ODBC: Implement SQLGetInfo for all info types
> -
>
> Key: IGNITE-6099
> URL: https://issues.apache.org/jira/browse/IGNITE-6099
> Project: Ignite
>  Issue Type: Task
>  Components: odbc
>Affects Versions: 2.1
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: usability
> Fix For: 2.3
>
>
> Currently not all the info types supported for {{SQLGetInfo}}. Need to 
> implement fully. Details can be found here - 
> https://docs.microsoft.com/en-us/sql/odbc/reference/syntax/sqlgetinfo-function



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

[jira] [Commented] (IGNITE-6403) IgniteSqlNotNullConstraintTest.testTransactionalAddColumnNotNullCheckDmlInsertValues fails periodically

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6403:


GitHub user alexpaschenko opened a pull request:

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

IGNITE-6403 SchemaOperationManager fix

…tiated operation.

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

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

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

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


commit 6a95a845056e7d509ad3fcf78738f1d59f7cc892
Author: Alexander Paschenko 
Date:   2017-09-18T18:04:57Z

IGNITE-6403 SchemaOperationManager always waits for node that has initiated 
operation.




> IgniteSqlNotNullConstraintTest.testTransactionalAddColumnNotNullCheckDmlInsertValues
>  fails periodically
> ---
>
> Key: IGNITE-6403
> URL: https://issues.apache.org/jira/browse/IGNITE-6403
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.3
>
>
> Looks like we have a bug in {{ALTER TABLE}} - column is not visible after 
> command is completed:
> {code}
> Caused by: org.h2.jdbc.JdbcSQLException: Column "NAME" not found; SQL 
> statement:
> INSERT INTO test(id, name, age) VALUES (1, 'ok', 1), (2, NULLIF('a', 'a'), 
> 2), (3, 'ok', 3) [42122-195]
> {code}



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

[jira] [Created] (IGNITE-6430) CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime test fails periodically.

[Andrey Gura (JIRA)]

Andrey Gura created IGNITE-6430:
---

 Summary: 
CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime test fails 
periodically.
 Key: IGNITE-6430
 URL: https://issues.apache.org/jira/browse/IGNITE-6430
 Project: Ignite
  Issue Type: Bug
Reporter: Andrey Gura
 Fix For: 2.3


{{CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime}} test fails 
periodically.

{noformat}
[2017-09-18 15:18:20,073][ERROR][main][root] Test failed.
junit.framework.AssertionFailedError: Expected less 5000, Actual:-100969
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.TestCase.assertTrue(TestCase.java:192)
at 
org.apache.ignite.internal.processors.cache.CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime(CacheGroupsMetricsRebalanceTest.java:261)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745)
{noformat}

After fix test should be unmuted on TC.



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

[jira] [Created] (IGNITE-6429) GridCachePreloadingEvictionsSelfTest.testEvictions test fails periodically

[Andrey Gura (JIRA)]

Andrey Gura created IGNITE-6429:
---

 Summary: GridCachePreloadingEvictionsSelfTest.testEvictions test 
fails periodically 
 Key: IGNITE-6429
 URL: https://issues.apache.org/jira/browse/IGNITE-6429
 Project: Ignite
  Issue Type: Bug
Reporter: Andrey Gura
 Fix For: 2.3


{{GridCachePreloadingEvictionsSelfTest.testEvictions}} test fails periodically.

{noformat}
[2017-09-18 15:35:03,054][ERROR][main][root] Test failed.
java.lang.AssertionError: Sizes do not match [s1=5136, s2=5159]
at 
org.apache.ignite.internal.processors.cache.GridCachePreloadingEvictionsSelfTest.checkCachesConsistency(GridCachePreloadingEvictionsSelfTest.java:243)
at 
org.apache.ignite.internal.processors.cache.GridCachePreloadingEvictionsSelfTest.testEvictions(GridCachePreloadingEvictionsSelfTest.java:162)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745)
{noformat}

After fix test should be unmuted on TC.



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

[jira] [Commented] (IGNITE-5839) Unclear exception from BinaryObjectBuilder::build call when builder is reused

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-5839:
-

LGTM! Merged to master.

> Unclear exception from BinaryObjectBuilder::build call when builder is reused
> -
>
> Key: IGNITE-5839
> URL: https://issues.apache.org/jira/browse/IGNITE-5839
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Sergey Chugunov
>Assignee: Andrew Mashenkov
> Fix For: 2.3
>
>
> Simple test where {{BinaryObjectBuilder}} builder object is reused fails with 
> exception {noformat}org.apache.ignite.binary.BinaryObjectException: Wrong 
> value has been set [typeName=SimpleCls, fieldName=str, fieldType=String, 
> assignedValueType=Object]{noformat}
> {noformat}
> IgniteCache cache = /* obtain a reference to 
> withKeepBinary cache instance */;
> BinaryObjectBuilder bldr = grid(0).binary().builder("SimpleCls");
> bldr.setField("str", "abc");
> c.put(0, bldr.build());
> bldr.setField("str", null);
> c.put(1, bldr.build());
> bldr.setField("str", "def");
> c.put(2, bldr.build()); //exception will be thrown by call 
> bldr.build()
> {noformat}
> It can be fixed by simply recreating BinaryObjectBuilder instead of reusing 
> the same instance. 
> However reusing builder object must be either explicitly prohibited or 
> exception must be fixed.
> Right now documentation on builder class says nothing about reusing this 
> object.



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

[jira] [Commented] (IGNITE-2786) SpringCache doesn't survive client reconnect

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-2786:
-

[~bbarin], node restart is not needed because Ignite client reconnects 
automatically. The only issue here is that {{IgniteCache}} instance acquired 
before the disconnection can't be used after the reconnect. So in my view the 
only thing required is to clean up {{SpringCacheManager#caches}} map if 
disconnect happens (Ignite provides special event for this, so it's easy to 
create a listener).

> SpringCache doesn't survive client reconnect
> 
>
> Key: IGNITE-2786
> URL: https://issues.apache.org/jira/browse/IGNITE-2786
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>
> After a client disconnects and reconnects with new ID, Spring caching can't 
> be used, because existing cache instance are closed.



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

[jira] [Updated] (IGNITE-6423) PDS could be corrupted if partition have been evicted and owned again

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev updated IGNITE-6423:
--
Summary: PDS could be corrupted if partition have been evicted and owned 
again  (was: PDS could be corrupted if partition have been evicted and returned 
to node)

> PDS could be corrupted if partition have been evicted and owned again
> -
>
> Key: IGNITE-6423
> URL: https://issues.apache.org/jira/browse/IGNITE-6423
> Project: Ignite
>  Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Critical
> Fix For: 2.3
>
>
> So, what is going on? 
> Partition had been changed, its pages had been put to checkpoint pages.
> After it partition was evicted, checkpoint started.
> We are allocating a page and because it's already in checkpoint we copy the 
> empty page to copy it on disk.
> If we restart right now we will read the empty page from disk. Therefore 
> assertion error would be thrown etc.



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

[jira] [Updated] (IGNITE-6428) Timed out test IgnitePdsAtomicCacheRebalancingTest.testTopologyChangesWithConstantLoad

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-6428:
---
Affects Version/s: 2.1

> Timed out test 
> IgnitePdsAtomicCacheRebalancingTest.testTopologyChangesWithConstantLoad
> --
>
> Key: IGNITE-6428
> URL: https://issues.apache.org/jira/browse/IGNITE-6428
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Alexey Goncharuk
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> IgnitePdsAtomicCacheRebalancingTest.testTopologyChangesWithConstantLoad
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=7598445566789774358=testDetails_Ignite20Tests=%3Cdefault%3E
> Test was early fixed under following issues
> https://issues.apache.org/jira/browse/IGNITE-5514
> https://issues.apache.org/jira/browse/IGNITE-5692
>  
> But now it is still failed with:
> {noformat}
> [2017-09-18 
> 00:19:02,892][ERROR][sys-stripe-22-#10154%persistence.IgnitePdsAtomicCacheRebalancingTest4%][GridCacheIoManager]
>  Failed processing message [senderId=df3bec22-ebfb-4222-86d9-ab6117b1, 
> msg=GridDhtAtomicSingleUpdateRequest [key=KeyCacheObjectImpl [part=166, 
> val=8358, hasValBytes=true], 
> val=o.a.i.i.processors.cache.persistence.IgnitePdsCacheRebalancingAbstractTest$TestValue
>  [idHash=595564816, hash=-2080068327, v1=866013082, v2=381254132], 
> prevVal=null, super=GridDhtAtomicAbstractUpdateRequest [onRes=false, 
> nearNodeId=52c634c0-6675-44eb-bf52-d2d0f010, nearFutId=588085, 
> flags=hasRes]]]
> class org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Failed to 
> find a page for eviction [segmentCapacity=2545, loaded=458, 
> maxDirtyPages=640, dirtyPages=458, cpPages=0, pinnedInSegment=0, 
> failedToPrepare=459]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.tryToFindSequentially(PageMemoryImpl.java:1893)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.evictPage(PageMemoryImpl.java:1817)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.access$600(PageMemoryImpl.java:1550)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.allocatePage(PageMemoryImpl.java:414)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore$1.allocatePageNoReuse(GridCacheOffheapManager.java:925)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.allocatePage(DataStructure.java:105)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.addStripe(PagesList.java:416)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.getPageForPut(PagesList.java:518)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.put(PagesList.java:618)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.FreeListImpl$RemoveRowHandler.run(FreeListImpl.java:297)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.FreeListImpl$RemoveRowHandler.run(FreeListImpl.java:264)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writePage(PageHandler.java:277)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.write(DataStructure.java:223)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.FreeListImpl.removeDataRowByLink(FreeListImpl.java:526)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.RowStore.removeRow(RowStore.java:69)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:1371)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1209)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.invoke(GridCacheOffheapManager.java:1263)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:343)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:1693)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processDhtAtomicUpdateRequest(GridDhtAtomicCache.java:3220)
>   at 
> 

[jira] [Updated] (IGNITE-6428) Timed out test IgnitePdsAtomicCacheRebalancingTest.testTopologyChangesWithConstantLoad

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-6428:
---
Fix Version/s: 2.3

> Timed out test 
> IgnitePdsAtomicCacheRebalancingTest.testTopologyChangesWithConstantLoad
> --
>
> Key: IGNITE-6428
> URL: https://issues.apache.org/jira/browse/IGNITE-6428
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Alexey Goncharuk
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> IgnitePdsAtomicCacheRebalancingTest.testTopologyChangesWithConstantLoad
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=7598445566789774358=testDetails_Ignite20Tests=%3Cdefault%3E
> Test was early fixed under following issues
> https://issues.apache.org/jira/browse/IGNITE-5514
> https://issues.apache.org/jira/browse/IGNITE-5692
>  
> But now it is still failed with:
> {noformat}
> [2017-09-18 
> 00:19:02,892][ERROR][sys-stripe-22-#10154%persistence.IgnitePdsAtomicCacheRebalancingTest4%][GridCacheIoManager]
>  Failed processing message [senderId=df3bec22-ebfb-4222-86d9-ab6117b1, 
> msg=GridDhtAtomicSingleUpdateRequest [key=KeyCacheObjectImpl [part=166, 
> val=8358, hasValBytes=true], 
> val=o.a.i.i.processors.cache.persistence.IgnitePdsCacheRebalancingAbstractTest$TestValue
>  [idHash=595564816, hash=-2080068327, v1=866013082, v2=381254132], 
> prevVal=null, super=GridDhtAtomicAbstractUpdateRequest [onRes=false, 
> nearNodeId=52c634c0-6675-44eb-bf52-d2d0f010, nearFutId=588085, 
> flags=hasRes]]]
> class org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Failed to 
> find a page for eviction [segmentCapacity=2545, loaded=458, 
> maxDirtyPages=640, dirtyPages=458, cpPages=0, pinnedInSegment=0, 
> failedToPrepare=459]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.tryToFindSequentially(PageMemoryImpl.java:1893)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.evictPage(PageMemoryImpl.java:1817)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.access$600(PageMemoryImpl.java:1550)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.allocatePage(PageMemoryImpl.java:414)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore$1.allocatePageNoReuse(GridCacheOffheapManager.java:925)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.allocatePage(DataStructure.java:105)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.addStripe(PagesList.java:416)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.getPageForPut(PagesList.java:518)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.put(PagesList.java:618)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.FreeListImpl$RemoveRowHandler.run(FreeListImpl.java:297)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.FreeListImpl$RemoveRowHandler.run(FreeListImpl.java:264)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writePage(PageHandler.java:277)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.write(DataStructure.java:223)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.FreeListImpl.removeDataRowByLink(FreeListImpl.java:526)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.RowStore.removeRow(RowStore.java:69)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:1371)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1209)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.invoke(GridCacheOffheapManager.java:1263)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:343)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:1693)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processDhtAtomicUpdateRequest(GridDhtAtomicCache.java:3220)
>   at 
> 

[jira] [Created] (IGNITE-6428) Timed out test IgnitePdsAtomicCacheRebalancingTest.testTopologyChangesWithConstantLoad

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-6428:
--

 Summary: Timed out test 
IgnitePdsAtomicCacheRebalancingTest.testTopologyChangesWithConstantLoad
 Key: IGNITE-6428
 URL: https://issues.apache.org/jira/browse/IGNITE-6428
 Project: Ignite
  Issue Type: Bug
  Components: persistence
Reporter: Dmitriy Pavlov
Assignee: Alexey Goncharuk


IgnitePdsAtomicCacheRebalancingTest.testTopologyChangesWithConstantLoad
https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=7598445566789774358=testDetails_Ignite20Tests=%3Cdefault%3E
Test was early fixed under following issues
https://issues.apache.org/jira/browse/IGNITE-5514
https://issues.apache.org/jira/browse/IGNITE-5692
 
But now it is still failed with:
{noformat}
[2017-09-18 
00:19:02,892][ERROR][sys-stripe-22-#10154%persistence.IgnitePdsAtomicCacheRebalancingTest4%][GridCacheIoManager]
 Failed processing message [senderId=df3bec22-ebfb-4222-86d9-ab6117b1, 
msg=GridDhtAtomicSingleUpdateRequest [key=KeyCacheObjectImpl [part=166, 
val=8358, hasValBytes=true], 
val=o.a.i.i.processors.cache.persistence.IgnitePdsCacheRebalancingAbstractTest$TestValue
 [idHash=595564816, hash=-2080068327, v1=866013082, v2=381254132], 
prevVal=null, super=GridDhtAtomicAbstractUpdateRequest [onRes=false, 
nearNodeId=52c634c0-6675-44eb-bf52-d2d0f010, nearFutId=588085, 
flags=hasRes]]]
class org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Failed to find 
a page for eviction [segmentCapacity=2545, loaded=458, maxDirtyPages=640, 
dirtyPages=458, cpPages=0, pinnedInSegment=0, failedToPrepare=459]
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.tryToFindSequentially(PageMemoryImpl.java:1893)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.evictPage(PageMemoryImpl.java:1817)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.access$600(PageMemoryImpl.java:1550)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.allocatePage(PageMemoryImpl.java:414)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore$1.allocatePageNoReuse(GridCacheOffheapManager.java:925)
at 
org.apache.ignite.internal.processors.cache.persistence.DataStructure.allocatePage(DataStructure.java:105)
at 
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.addStripe(PagesList.java:416)
at 
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.getPageForPut(PagesList.java:518)
at 
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.put(PagesList.java:618)
at 
org.apache.ignite.internal.processors.cache.persistence.freelist.FreeListImpl$RemoveRowHandler.run(FreeListImpl.java:297)
at 
org.apache.ignite.internal.processors.cache.persistence.freelist.FreeListImpl$RemoveRowHandler.run(FreeListImpl.java:264)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writePage(PageHandler.java:277)
at 
org.apache.ignite.internal.processors.cache.persistence.DataStructure.write(DataStructure.java:223)
at 
org.apache.ignite.internal.processors.cache.persistence.freelist.FreeListImpl.removeDataRowByLink(FreeListImpl.java:526)
at 
org.apache.ignite.internal.processors.cache.persistence.RowStore.removeRow(RowStore.java:69)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:1371)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1209)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.invoke(GridCacheOffheapManager.java:1263)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:343)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:1693)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processDhtAtomicUpdateRequest(GridDhtAtomicCache.java:3220)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$600(GridDhtAtomicCache.java:130)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$7.apply(GridDhtAtomicCache.java:304)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$7.apply(GridDhtAtomicCache.java:299)
at 

[jira] [Updated] (IGNITE-6427) Ignite Cache 5 suite has timed out with CacheLateAffinityAssignmentTest.testRandomOperations()

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-6427:
---
Attachment: 
lastStartedTest_CacheLateAffinityAssignmentTest.testRandomOperations.log.zip

> Ignite Cache 5 suite has timed out with 
> CacheLateAffinityAssignmentTest.testRandomOperations()
> --
>
> Key: IGNITE-6427
> URL: https://issues.apache.org/jira/browse/IGNITE-6427
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
> Attachments: 
> lastStartedTest_CacheLateAffinityAssignmentTest.testRandomOperations.log.zip
>
>
> Ignite Cache 5 build has timed out with 
> CacheLateAffinityAssignmentTest.testRandomOperations():
>  
> https://ci.ignite.apache.org/viewLog.html?buildId=834721=buildResultsDiv=Ignite20Tests_IgniteCache5
>  
> {noformat}
>  [Step 4/5] [2017-09-17 22:41:23,619][INFO 
> ][sys-#49767%client-9%][GridDhtPartitionsExchangeFuture] Finish exchange 
> future [startVer=AffinityTopologyVersion [topVer=31, minorTopVer=0], 
> resVer=AffinityTopologyVersion [topVer=31, minorTopVer=0], err=null]
> [01:41:23]W:   [org.apache.ignite:ignite-core] [2017-09-17 
> 22:41:23,624][ERROR][sys-#49655%server-8%][GridDhtPartitionsExchangeFuture] 
> Failed to notify listener: 
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$5@56f46b92
> [01:41:23]W:   [org.apache.ignite:ignite-core] class 
> org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Not enough memory 
> allocated (consider increasing memory policy size or enabling evictions) 
> [policyName=default, size=104.9 MB]
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.allocatePage(PageMemoryNoStoreImpl.java:292)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.allocateForTree(IgniteCacheOffheapManagerImpl.java:806)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.createCacheDataStore0(IgniteCacheOffheapManagerImpl.java:903)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.createCacheDataStore(IgniteCacheOffheapManagerImpl.java:885)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.(GridDhtLocalPartition.java:205)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.createPartition(GridDhtPartitionTopologyImpl.java:724)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.createPartitions(GridDhtPartitionTopologyImpl.java:423)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.initPartitions0(GridDhtPartitionTopologyImpl.java:366)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.beforeExchange(GridDhtPartitionTopologyImpl.java:535)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processFullMessage(GridDhtPartitionsExchangeFuture.java:2776)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$1400(GridDhtPartitionsExchangeFuture.java:116)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$5.apply(GridDhtPartitionsExchangeFuture.java:2524)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$5.apply(GridDhtPartitionsExchangeFuture.java:2512)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:382)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> 

[jira] [Commented] (IGNITE-6209) .NET: Build NuGet packages for Apache-Ignite release on CI

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-6209:


Project created: 
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_IgniteRelease6BuildNuGetPackages

> .NET: Build NuGet packages for Apache-Ignite release on CI
> --
>
> Key: IGNITE-6209
> URL: https://issues.apache.org/jira/browse/IGNITE-6209
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Oleg Ostanin
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.3
>
>
> Create a suite to build Ignite.NET NuGet packages on TeamCity: 
> https://ci.ignite.apache.org/project.html?projectId=IgniteRelease



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

[jira] [Commented] (IGNITE-5865) TxOptimisticDeadlockDetectionTest.testDeadlocksPartitioned is failing

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-5865:


Hi [~VitaliyB], I've found tests were still muted. I've enabled tests.

> TxOptimisticDeadlockDetectionTest.testDeadlocksPartitioned is failing
> -
>
> Key: IGNITE-5865
> URL: https://issues.apache.org/jira/browse/IGNITE-5865
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Pavel Kovalenko
>Assignee: Vitaliy Biryukov
>  Labels: MakeTeamcityGreenAgain, Muted_test, test-failure
> Fix For: 2.3
>
>
> Test is flaky.
> Also there is always failing test in suite: 
> TxOptimisticDeadlockDetectionTest.testDeadlocksPartitionedNear
> TC build result: 
> http://ci.ignite.apache.org/viewLog.html?buildId=744109=buildResultsDiv=Ignite20Tests_IgniteCacheDeadlockDetection
> Stacktrace: 
> {noformat}
> [2017-07-28 
> 03:31:52,827][ERROR][grid-timeout-worker-#31%transactions.TxOptimisticDeadlockDetectionTest0%][IgniteTxHandler]
>  Failed to prepare DHT transaction: GridDhtTxLocal 
> [nearNodeId=d005de76-4378-4cd5-ad7e-f00593a2, 
> nearFutId=aab9f378d51-37ca90c9-03f5-417c-9731-2c29810e3cc0, nearMiniId=1, 
> nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion 
> [topVer=112692678, order=1501212673293, nodeOrder=3], 
> super=GridDhtTxLocalAdapter [nearOnOriginatingNode=false, nearNodes=[], 
> dhtNodes=[], explicitLock=false, super=IgniteTxLocalAdapter 
> [completedBase=null, sndTransformedVals=false, depEnabled=false, 
> txState=IgniteTxStateImpl [activeCacheIds=GridIntList [idx=1, 
> arr=[94416770]], recovery=false, txMap=[IgniteTxEntry 
> [key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=424974513, hash=-1228408719, id=1, name=KeyObject1], 
> cacheId=94416770, txKey=IgniteTxKey 
> [key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=424974513, hash=-1228408719, id=1, name=KeyObject1], 
> cacheId=94416770], val=[op=CREATE, val=CacheObjectImpl [val=null, 
> hasValBytes=true]], prevVal=[op=NOOP, val=null], oldVal=[op=NOOP, val=null], 
> entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1, conflictVer=null, 
> explicitVer=null, dhtVer=null, filters=[], filtersPassed=false, 
> filtersSet=false, entry=GridDhtCacheEntry [rdrs=[], part=694, 
> super=GridDistributedCacheEntry [super=GridCacheMapEntry 
> [key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=16030069, hash=-1228408719, id=1, name=KeyObject1], val=null, 
> startVer=1501212673290, ver=GridCacheVersion [topVer=112692678, 
> order=1501212673290, nodeOrder=1], hash=-1228408719, 
> extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc 
> [locs=[GridCacheMvccCandidate [nodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, 
> ver=GridCacheVersion [topVer=112692678, order=1501212673287, nodeOrder=1], 
> threadId=846, id=520, topVer=AffinityTopologyVersion [topVer=8, 
> minorTopVer=8], reentry=null, 
> otherNodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, otherVer=GridCacheVersion 
> [topVer=112692678, order=1501212673287, nodeOrder=1], mappedDhtNodes=null, 
> mappedNearNodes=null, ownerVer=null, serOrder=null, 
> key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=16030069, hash=-1228408719, id=1, name=KeyObject1], 
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
>  prevVer=null, nextVer=null], GridCacheMvccCandidate 
> [nodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, ver=GridCacheVersion 
> [topVer=112692678, order=1501212673314, nodeOrder=1], threadId=847, id=521, 
> topVer=AffinityTopologyVersion [topVer=8, minorTopVer=8], reentry=null, 
> otherNodeId=d005de76-4378-4cd5-ad7e-f00593a2, otherVer=GridCacheVersion 
> [topVer=112692678, order=1501212673293, nodeOrder=3], mappedDhtNodes=null, 
> mappedNearNodes=null, ownerVer=GridCacheVersion [topVer=112692678, 
> order=1501212673287, nodeOrder=1], serOrder=null, 
> key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=16030069, hash=-1228408719, id=1, name=KeyObject1], 
> masks=local=1|owner=0|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
>  prevVer=null, nextVer=null]], rmts=null]], flags=2]]], prepared=1, 
> locked=false, nodeId=null, locMapped=false, expiryPlc=null, 
> transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null, 
> xidVer=null]]], super=IgniteTxAdapter [xidVer=GridCacheVersion 
> [topVer=112692678, order=1501212673314, nodeOrder=1], writeVer=null, 
> implicit=false, loc=true, threadId=847, 

[jira] [Commented] (IGNITE-6209) .NET: Build NuGet packages for Apache-Ignite release on CI

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6209:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-6209 .NET: Build NuGet packages for Apache-Ignite release on CI



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

$ git pull https://github.com/ptupitsyn/ignite ignite-6209

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

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


commit 29818fc3b4807570dd30995ee88f9eac39ae21ed
Author: Pavel Tupitsyn 
Date:   2017-09-14T15:49:14Z

IGNITE-6209 .NET: Build NuGet packages for Apache-Ignite release on CI

commit 2e439a2d97fe106c6cca9b04fd96cd36dffc0940
Author: Pavel Tupitsyn 
Date:   2017-09-14T15:54:08Z

skipDotNet switch added

commit ae164e88221f10f18f7be6800f5eda0a764d2a64
Author: Pavel Tupitsyn 
Date:   2017-09-14T16:24:18Z

File copy script in progress

commit f642255051ca5cabb1aeb0c89f150c1a31017b09
Author: Pavel Tupitsyn 
Date:   2017-09-14T16:29:43Z

wip

commit 5f8d5c4fb1f9acfc437f48f0f06e514d506b8914
Author: Pavel Tupitsyn 
Date:   2017-09-14T16:31:55Z

packaging works!

commit 68a6caf92167be7cf1b4d7e5de8a84c1f8f41f6e
Author: Pavel Tupitsyn 
Date:   2017-09-18T14:50:25Z

Merge branch 'master' into ignite-6209

commit a14c97ae78442b3a0e360f6894235efc36b3065c
Author: Pavel Tupitsyn 
Date:   2017-09-18T15:55:48Z

Add asmDirs to build script

commit b68e6d7d191a639d9e9891de9f17402eb509f5ed
Author: Pavel Tupitsyn 
Date:   2017-09-18T16:02:09Z

remove extra script




> .NET: Build NuGet packages for Apache-Ignite release on CI
> --
>
> Key: IGNITE-6209
> URL: https://issues.apache.org/jira/browse/IGNITE-6209
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Oleg Ostanin
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.3
>
>
> Create a suite to build Ignite.NET NuGet packages on TeamCity: 
> https://ci.ignite.apache.org/project.html?projectId=IgniteRelease



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

[jira] [Updated] (IGNITE-6425) Races during transaction finalization

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev updated IGNITE-6425:
--
Description: 
I have found during stress-test (start-stop nodes during transactions running):
{code}
onDone(new IgniteCheckedException("Failed to commit transaction: " + 
CU.txString(tx)));
{code}


> Races during transaction finalization
> -
>
> Key: IGNITE-6425
> URL: https://issues.apache.org/jira/browse/IGNITE-6425
> Project: Ignite
>  Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>
> I have found during stress-test (start-stop nodes during transactions 
> running):
> {code}
> onDone(new IgniteCheckedException("Failed to commit transaction: " + 
> CU.txString(tx)));
> {code}



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

[jira] [Commented] (IGNITE-6427) Ignite Cache 5 suite has timed out with CacheLateAffinityAssignmentTest.testRandomOperations()

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6427:


GitHub user dspavlov opened a pull request:

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

IGNITE-6427: IgniteOOME in Cache5 test: Increase memory policy size



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

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

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

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


commit 241a4dfd67a734f86a431d2071c6a3c1a36119a2
Author: dpavlov 
Date:   2017-09-18T15:47:26Z

IGNITE-6427: IgniteOOME in Cache5 test: Increase memory policy size




> Ignite Cache 5 suite has timed out with 
> CacheLateAffinityAssignmentTest.testRandomOperations()
> --
>
> Key: IGNITE-6427
> URL: https://issues.apache.org/jira/browse/IGNITE-6427
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> Ignite Cache 5 build has timed out with 
> CacheLateAffinityAssignmentTest.testRandomOperations():
>  
> https://ci.ignite.apache.org/viewLog.html?buildId=834721=buildResultsDiv=Ignite20Tests_IgniteCache5
>  
> {noformat}
>  [Step 4/5] [2017-09-17 22:41:23,619][INFO 
> ][sys-#49767%client-9%][GridDhtPartitionsExchangeFuture] Finish exchange 
> future [startVer=AffinityTopologyVersion [topVer=31, minorTopVer=0], 
> resVer=AffinityTopologyVersion [topVer=31, minorTopVer=0], err=null]
> [01:41:23]W:   [org.apache.ignite:ignite-core] [2017-09-17 
> 22:41:23,624][ERROR][sys-#49655%server-8%][GridDhtPartitionsExchangeFuture] 
> Failed to notify listener: 
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$5@56f46b92
> [01:41:23]W:   [org.apache.ignite:ignite-core] class 
> org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Not enough memory 
> allocated (consider increasing memory policy size or enabling evictions) 
> [policyName=default, size=104.9 MB]
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.allocatePage(PageMemoryNoStoreImpl.java:292)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.allocateForTree(IgniteCacheOffheapManagerImpl.java:806)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.createCacheDataStore0(IgniteCacheOffheapManagerImpl.java:903)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.createCacheDataStore(IgniteCacheOffheapManagerImpl.java:885)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.(GridDhtLocalPartition.java:205)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.createPartition(GridDhtPartitionTopologyImpl.java:724)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.createPartitions(GridDhtPartitionTopologyImpl.java:423)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.initPartitions0(GridDhtPartitionTopologyImpl.java:366)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.beforeExchange(GridDhtPartitionTopologyImpl.java:535)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processFullMessage(GridDhtPartitionsExchangeFuture.java:2776)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$1400(GridDhtPartitionsExchangeFuture.java:116)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> 

[jira] [Assigned] (IGNITE-6228) Avoid closing page store file with ClosedByInterruptException when user thread is interrupted

[Alexei Scherbakov (JIRA)]

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

Alexei Scherbakov reassigned IGNITE-6228:
-

Assignee: Alexei Scherbakov  (was: Ivan Rakov)

> Avoid closing page store file with ClosedByInterruptException when user 
> thread is interrupted
> -
>
> Key: IGNITE-6228
> URL: https://issues.apache.org/jira/browse/IGNITE-6228
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Ivan Rakov
>Assignee: Alexei Scherbakov
> Fix For: 2.3
>
> Attachments: RestartGridTest.java
>
>
> If cache proxy is in synchronous mode, user thread may be interrupted during 
> read from file page store file. This will cause closing of partition file 
> with ClosedByInterruptException.
> Example stacktrace:
> {noformat}
> class org.apache.ignite.IgniteCheckedException: Runtime failure on lookup 
> row: 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$SearchRow@717729d
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findOne(BPlusTree.java:1070)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.find(IgniteCacheOffheapManagerImpl.java:1476)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.find(GridCacheOffheapManager.java:1276)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.read(IgniteCacheOffheapManagerImpl.java:394)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.unswap(GridCacheMapEntry.java:371)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.onTtlExpired(GridCacheMapEntry.java:2952)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager$1.applyx(GridCacheTtlManager.java:61)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager$1.applyx(GridCacheTtlManager.java:52)
>   at 
> org.apache.ignite.internal.util.lang.IgniteInClosure2X.apply(IgniteInClosure2X.java:38)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.expire(IgniteCacheOffheapManagerImpl.java:1012)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:198)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.unwindEvicts(GridCacheUtils.java:868)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheGateway.leaveNoLock(GridCacheGateway.java:240)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheGateway.leave(GridCacheGateway.java:225)
>   at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.onLeave(GatewayProtectedCacheProxy.java:1680)
>   at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:875)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.db.RestartGridTest$TestService.execute(RestartGridTest.java:160)
>   at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor$2.run(GridServiceProcessor.java:1160)
>   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: class org.apache.ignite.IgniteCheckedException: Read error
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStore.read(FilePageStore.java:356)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:287)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:272)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:570)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:488)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.acquirePage(DataStructure.java:129)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.treeMeta(BPlusTree.java:822)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$7700(BPlusTree.java:81)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Get.init(BPlusTree.java:2392)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doFind(BPlusTree.java:1099)
>   at 

[jira] [Created] (IGNITE-6427) Ignite Cache 5 suite has timed out with CacheLateAffinityAssignmentTest.testRandomOperations()

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-6427:
--

 Summary: Ignite Cache 5 suite has timed out with 
CacheLateAffinityAssignmentTest.testRandomOperations()
 Key: IGNITE-6427
 URL: https://issues.apache.org/jira/browse/IGNITE-6427
 Project: Ignite
  Issue Type: Bug
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov


Ignite Cache 5 build has timed out with 
CacheLateAffinityAssignmentTest.testRandomOperations():
 
https://ci.ignite.apache.org/viewLog.html?buildId=834721=buildResultsDiv=Ignite20Tests_IgniteCache5
 
{noformat}
 [Step 4/5] [2017-09-17 22:41:23,619][INFO 
][sys-#49767%client-9%][GridDhtPartitionsExchangeFuture] Finish exchange future 
[startVer=AffinityTopologyVersion [topVer=31, minorTopVer=0], 
resVer=AffinityTopologyVersion [topVer=31, minorTopVer=0], err=null]
[01:41:23]W: [org.apache.ignite:ignite-core] [2017-09-17 
22:41:23,624][ERROR][sys-#49655%server-8%][GridDhtPartitionsExchangeFuture] 
Failed to notify listener: 
o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$5@56f46b92
[01:41:23]W: [org.apache.ignite:ignite-core] class 
org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Not enough memory 
allocated (consider increasing memory policy size or enabling evictions) 
[policyName=default, size=104.9 MB]
[01:41:23]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.allocatePage(PageMemoryNoStoreImpl.java:292)
[01:41:23]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.allocateForTree(IgniteCacheOffheapManagerImpl.java:806)
[01:41:23]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.createCacheDataStore0(IgniteCacheOffheapManagerImpl.java:903)
[01:41:23]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.createCacheDataStore(IgniteCacheOffheapManagerImpl.java:885)
[01:41:23]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.(GridDhtLocalPartition.java:205)
[01:41:23]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.createPartition(GridDhtPartitionTopologyImpl.java:724)
[01:41:23]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.createPartitions(GridDhtPartitionTopologyImpl.java:423)
[01:41:23]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.initPartitions0(GridDhtPartitionTopologyImpl.java:366)
[01:41:23]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.beforeExchange(GridDhtPartitionTopologyImpl.java:535)
[01:41:23]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processFullMessage(GridDhtPartitionsExchangeFuture.java:2776)
[01:41:23]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$1400(GridDhtPartitionsExchangeFuture.java:116)
[01:41:23]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$5.apply(GridDhtPartitionsExchangeFuture.java:2524)
[01:41:23]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$5.apply(GridDhtPartitionsExchangeFuture.java:2512)
[01:41:23]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:382)
[01:41:23]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:352)
[01:41:23]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveFullMessage(GridDhtPartitionsExchangeFuture.java:2512)
[01:41:23]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processFullPartitionUpdate(GridCachePartitionExchangeManager.java:1433)
[01:41:23]W: [org.apache.ignite:ignite-core]at 

[jira] [Updated] (IGNITE-6427) Ignite Cache 5 suite has timed out with CacheLateAffinityAssignmentTest.testRandomOperations()

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-6427:
---
Fix Version/s: 2.3

> Ignite Cache 5 suite has timed out with 
> CacheLateAffinityAssignmentTest.testRandomOperations()
> --
>
> Key: IGNITE-6427
> URL: https://issues.apache.org/jira/browse/IGNITE-6427
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> Ignite Cache 5 build has timed out with 
> CacheLateAffinityAssignmentTest.testRandomOperations():
>  
> https://ci.ignite.apache.org/viewLog.html?buildId=834721=buildResultsDiv=Ignite20Tests_IgniteCache5
>  
> {noformat}
>  [Step 4/5] [2017-09-17 22:41:23,619][INFO 
> ][sys-#49767%client-9%][GridDhtPartitionsExchangeFuture] Finish exchange 
> future [startVer=AffinityTopologyVersion [topVer=31, minorTopVer=0], 
> resVer=AffinityTopologyVersion [topVer=31, minorTopVer=0], err=null]
> [01:41:23]W:   [org.apache.ignite:ignite-core] [2017-09-17 
> 22:41:23,624][ERROR][sys-#49655%server-8%][GridDhtPartitionsExchangeFuture] 
> Failed to notify listener: 
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$5@56f46b92
> [01:41:23]W:   [org.apache.ignite:ignite-core] class 
> org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Not enough memory 
> allocated (consider increasing memory policy size or enabling evictions) 
> [policyName=default, size=104.9 MB]
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.allocatePage(PageMemoryNoStoreImpl.java:292)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.allocateForTree(IgniteCacheOffheapManagerImpl.java:806)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.createCacheDataStore0(IgniteCacheOffheapManagerImpl.java:903)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.createCacheDataStore(IgniteCacheOffheapManagerImpl.java:885)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.(GridDhtLocalPartition.java:205)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.createPartition(GridDhtPartitionTopologyImpl.java:724)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.createPartitions(GridDhtPartitionTopologyImpl.java:423)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.initPartitions0(GridDhtPartitionTopologyImpl.java:366)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.beforeExchange(GridDhtPartitionTopologyImpl.java:535)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processFullMessage(GridDhtPartitionsExchangeFuture.java:2776)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$1400(GridDhtPartitionsExchangeFuture.java:116)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$5.apply(GridDhtPartitionsExchangeFuture.java:2524)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$5.apply(GridDhtPartitionsExchangeFuture.java:2512)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:382)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:352)
> [01:41:23]W:   [org.apache.ignite:ignite-core]at 
> 

[jira] [Updated] (IGNITE-5860) Client disconnects if server it is connected to goes unresponsive

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev updated IGNITE-5860:

Attachment: testAlivesClient.patch

GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient fails after this commit.

It was failing even before, see how to fix it.

> Client disconnects if server it is connected to goes unresponsive 
> --
>
> Key: IGNITE-5860
> URL: https://issues.apache.org/jira/browse/IGNITE-5860
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Evgenii Zhuravlev
>Assignee: Denis Mekhanikov
> Fix For: 2.3
>
> Attachments: testAlivesClient.patch
>
>
> Scenario is the following:
> # Start at least two server nodes.
> # Start a client node.
> # Detect server node client is connected to in discovery SPI.
> # Suspend that server (^Z in terminal or 'kill -SIGSTOP ').
> # It's expected that client will drop connection with this server and 
> connect to another one.
> # However, a client gets dropped from topology and disconnects.
> A client should reconnect cluster before the timeout and without 
> EVT_CLIENT_NODE_RECONNECTED event.
> In ClientImpl.Reconnector in joinTopology method it gets all addresses from 
> discoverySpi and addresses of the server that was suspended on top of this 
> list.
> *Proposed solution:*
> Move addresses of the suspended server to the end of the list for the join.



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

[jira] [Comment Edited] (IGNITE-5865) TxOptimisticDeadlockDetectionTest.testDeadlocksPartitioned is failing

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov edited comment on IGNITE-5865 at 9/18/17 3:21 PM:
-

Hi [~VitaliyB], were tests umuted on Teamcity? Or it is still required to 
unmute?


was (Author: dpavlov):
Hi, were tests umuted on Teamcity?

> TxOptimisticDeadlockDetectionTest.testDeadlocksPartitioned is failing
> -
>
> Key: IGNITE-5865
> URL: https://issues.apache.org/jira/browse/IGNITE-5865
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Pavel Kovalenko
>Assignee: Vitaliy Biryukov
>  Labels: MakeTeamcityGreenAgain, Muted_test, test-failure
> Fix For: 2.3
>
>
> Test is flaky.
> Also there is always failing test in suite: 
> TxOptimisticDeadlockDetectionTest.testDeadlocksPartitionedNear
> TC build result: 
> http://ci.ignite.apache.org/viewLog.html?buildId=744109=buildResultsDiv=Ignite20Tests_IgniteCacheDeadlockDetection
> Stacktrace: 
> {noformat}
> [2017-07-28 
> 03:31:52,827][ERROR][grid-timeout-worker-#31%transactions.TxOptimisticDeadlockDetectionTest0%][IgniteTxHandler]
>  Failed to prepare DHT transaction: GridDhtTxLocal 
> [nearNodeId=d005de76-4378-4cd5-ad7e-f00593a2, 
> nearFutId=aab9f378d51-37ca90c9-03f5-417c-9731-2c29810e3cc0, nearMiniId=1, 
> nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion 
> [topVer=112692678, order=1501212673293, nodeOrder=3], 
> super=GridDhtTxLocalAdapter [nearOnOriginatingNode=false, nearNodes=[], 
> dhtNodes=[], explicitLock=false, super=IgniteTxLocalAdapter 
> [completedBase=null, sndTransformedVals=false, depEnabled=false, 
> txState=IgniteTxStateImpl [activeCacheIds=GridIntList [idx=1, 
> arr=[94416770]], recovery=false, txMap=[IgniteTxEntry 
> [key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=424974513, hash=-1228408719, id=1, name=KeyObject1], 
> cacheId=94416770, txKey=IgniteTxKey 
> [key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=424974513, hash=-1228408719, id=1, name=KeyObject1], 
> cacheId=94416770], val=[op=CREATE, val=CacheObjectImpl [val=null, 
> hasValBytes=true]], prevVal=[op=NOOP, val=null], oldVal=[op=NOOP, val=null], 
> entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1, conflictVer=null, 
> explicitVer=null, dhtVer=null, filters=[], filtersPassed=false, 
> filtersSet=false, entry=GridDhtCacheEntry [rdrs=[], part=694, 
> super=GridDistributedCacheEntry [super=GridCacheMapEntry 
> [key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=16030069, hash=-1228408719, id=1, name=KeyObject1], val=null, 
> startVer=1501212673290, ver=GridCacheVersion [topVer=112692678, 
> order=1501212673290, nodeOrder=1], hash=-1228408719, 
> extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc 
> [locs=[GridCacheMvccCandidate [nodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, 
> ver=GridCacheVersion [topVer=112692678, order=1501212673287, nodeOrder=1], 
> threadId=846, id=520, topVer=AffinityTopologyVersion [topVer=8, 
> minorTopVer=8], reentry=null, 
> otherNodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, otherVer=GridCacheVersion 
> [topVer=112692678, order=1501212673287, nodeOrder=1], mappedDhtNodes=null, 
> mappedNearNodes=null, ownerVer=null, serOrder=null, 
> key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=16030069, hash=-1228408719, id=1, name=KeyObject1], 
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
>  prevVer=null, nextVer=null], GridCacheMvccCandidate 
> [nodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, ver=GridCacheVersion 
> [topVer=112692678, order=1501212673314, nodeOrder=1], threadId=847, id=521, 
> topVer=AffinityTopologyVersion [topVer=8, minorTopVer=8], reentry=null, 
> otherNodeId=d005de76-4378-4cd5-ad7e-f00593a2, otherVer=GridCacheVersion 
> [topVer=112692678, order=1501212673293, nodeOrder=3], mappedDhtNodes=null, 
> mappedNearNodes=null, ownerVer=GridCacheVersion [topVer=112692678, 
> order=1501212673287, nodeOrder=1], serOrder=null, 
> key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=16030069, hash=-1228408719, id=1, name=KeyObject1], 
> masks=local=1|owner=0|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
>  prevVer=null, nextVer=null]], rmts=null]], flags=2]]], prepared=1, 
> locked=false, nodeId=null, locMapped=false, expiryPlc=null, 
> transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null, 
> xidVer=null]]], super=IgniteTxAdapter [xidVer=GridCacheVersion 
> 

[jira] [Commented] (IGNITE-5865) TxOptimisticDeadlockDetectionTest.testDeadlocksPartitioned is failing

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-5865:


Hi, were tests umuted on Teamcity?

> TxOptimisticDeadlockDetectionTest.testDeadlocksPartitioned is failing
> -
>
> Key: IGNITE-5865
> URL: https://issues.apache.org/jira/browse/IGNITE-5865
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Pavel Kovalenko
>Assignee: Vitaliy Biryukov
>  Labels: MakeTeamcityGreenAgain, Muted_test, test-failure
> Fix For: 2.3
>
>
> Test is flaky.
> Also there is always failing test in suite: 
> TxOptimisticDeadlockDetectionTest.testDeadlocksPartitionedNear
> TC build result: 
> http://ci.ignite.apache.org/viewLog.html?buildId=744109=buildResultsDiv=Ignite20Tests_IgniteCacheDeadlockDetection
> Stacktrace: 
> {noformat}
> [2017-07-28 
> 03:31:52,827][ERROR][grid-timeout-worker-#31%transactions.TxOptimisticDeadlockDetectionTest0%][IgniteTxHandler]
>  Failed to prepare DHT transaction: GridDhtTxLocal 
> [nearNodeId=d005de76-4378-4cd5-ad7e-f00593a2, 
> nearFutId=aab9f378d51-37ca90c9-03f5-417c-9731-2c29810e3cc0, nearMiniId=1, 
> nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion 
> [topVer=112692678, order=1501212673293, nodeOrder=3], 
> super=GridDhtTxLocalAdapter [nearOnOriginatingNode=false, nearNodes=[], 
> dhtNodes=[], explicitLock=false, super=IgniteTxLocalAdapter 
> [completedBase=null, sndTransformedVals=false, depEnabled=false, 
> txState=IgniteTxStateImpl [activeCacheIds=GridIntList [idx=1, 
> arr=[94416770]], recovery=false, txMap=[IgniteTxEntry 
> [key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=424974513, hash=-1228408719, id=1, name=KeyObject1], 
> cacheId=94416770, txKey=IgniteTxKey 
> [key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=424974513, hash=-1228408719, id=1, name=KeyObject1], 
> cacheId=94416770], val=[op=CREATE, val=CacheObjectImpl [val=null, 
> hasValBytes=true]], prevVal=[op=NOOP, val=null], oldVal=[op=NOOP, val=null], 
> entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1, conflictVer=null, 
> explicitVer=null, dhtVer=null, filters=[], filtersPassed=false, 
> filtersSet=false, entry=GridDhtCacheEntry [rdrs=[], part=694, 
> super=GridDistributedCacheEntry [super=GridCacheMapEntry 
> [key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=16030069, hash=-1228408719, id=1, name=KeyObject1], val=null, 
> startVer=1501212673290, ver=GridCacheVersion [topVer=112692678, 
> order=1501212673290, nodeOrder=1], hash=-1228408719, 
> extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc 
> [locs=[GridCacheMvccCandidate [nodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, 
> ver=GridCacheVersion [topVer=112692678, order=1501212673287, nodeOrder=1], 
> threadId=846, id=520, topVer=AffinityTopologyVersion [topVer=8, 
> minorTopVer=8], reentry=null, 
> otherNodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, otherVer=GridCacheVersion 
> [topVer=112692678, order=1501212673287, nodeOrder=1], mappedDhtNodes=null, 
> mappedNearNodes=null, ownerVer=null, serOrder=null, 
> key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=16030069, hash=-1228408719, id=1, name=KeyObject1], 
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
>  prevVer=null, nextVer=null], GridCacheMvccCandidate 
> [nodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, ver=GridCacheVersion 
> [topVer=112692678, order=1501212673314, nodeOrder=1], threadId=847, id=521, 
> topVer=AffinityTopologyVersion [topVer=8, minorTopVer=8], reentry=null, 
> otherNodeId=d005de76-4378-4cd5-ad7e-f00593a2, otherVer=GridCacheVersion 
> [topVer=112692678, order=1501212673293, nodeOrder=3], mappedDhtNodes=null, 
> mappedNearNodes=null, ownerVer=GridCacheVersion [topVer=112692678, 
> order=1501212673287, nodeOrder=1], serOrder=null, 
> key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=16030069, hash=-1228408719, id=1, name=KeyObject1], 
> masks=local=1|owner=0|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
>  prevVer=null, nextVer=null]], rmts=null]], flags=2]]], prepared=1, 
> locked=false, nodeId=null, locMapped=false, expiryPlc=null, 
> transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null, 
> xidVer=null]]], super=IgniteTxAdapter [xidVer=GridCacheVersion 
> [topVer=112692678, order=1501212673314, nodeOrder=1], writeVer=null, 
> implicit=false, loc=true, threadId=847, startTime=1501212712015, 
> 

[jira] [Created] (IGNITE-6426) Add support for variable length numbers in raw readers/writers.

[Alexei Scherbakov (JIRA)]

Alexei Scherbakov created IGNITE-6426:
-

 Summary: Add support for variable length numbers in raw 
readers/writers.
 Key: IGNITE-6426
 URL: https://issues.apache.org/jira/browse/IGNITE-6426
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Alexei Scherbakov
Assignee: Alexei Scherbakov
 Fix For: 2.3


This is useful for implementing custom efficient compression.



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

[jira] [Commented] (IGNITE-6355) Calculating cache size during cache stop sporadically fails with ClusterGroupEmptyCheckedException

[Ivan Rakov (JIRA)]

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

Ivan Rakov commented on IGNITE-6355:


Returning ticket back to development as per another data race is found.

> Calculating cache size during cache stop sporadically fails with 
> ClusterGroupEmptyCheckedException
> --
>
> Key: IGNITE-6355
> URL: https://issues.apache.org/jira/browse/IGNITE-6355
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Ivan Rakov
>Assignee: Ivan Rakov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> Example stacktrace:
> {noformat}
> [16:21:06,343][ERROR][main][root] Test failed.
> javax.cache.CacheException: class 
> org.apache.ignite.cluster.ClusterGroupEmptyException: Topology projection is 
> empty.
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1327)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1672)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.size(IgniteCacheProxyImpl.java:762)
>   at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.size(GatewayProtectedCacheProxy.java:508)
>   at 
> org.gridgain.grid.internal.processors.cache.database.IgniteDbSnapshotSelfTest.testReuseCacheProxyAfterRestore(IgniteDbSnapshotSelfTest.java:1793)
>   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:2000)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.cluster.ClusterGroupEmptyException: 
> Topology projection is empty.
>   at 
> org.apache.ignite.internal.util.IgniteUtils$6.apply(IgniteUtils.java:823)
>   at 
> org.apache.ignite.internal.util.IgniteUtils$6.apply(IgniteUtils.java:821)
>   ... 14 more
> Caused by: class 
> org.apache.ignite.internal.cluster.ClusterGroupEmptyCheckedException: 
> Topology projection is empty.
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.getTaskTopology(GridTaskWorker.java:665)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:500)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:758)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:454)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:410)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.sizeAsync(GridCacheAdapter.java:3747)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.size(GridCacheAdapter.java:3704)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.size(IgniteCacheProxyImpl.java:759)
>   ... 11 more
> {noformat}
> Data race stems from here (GridCacheAdapter#sizeAsync):
> {noformat}
> Group grp = modes.near ? cluster.forCacheNodes(name(), true, true, 
> false) : cluster.forDataNodes(name());
> Collection nodes = grp.nodes();
> if (nodes.isEmpty())
> return new GridFinishedFuture<>(0);
> ctx.kernalContext().task().setThreadContext(TC_SUBGRID, nodes);
> return ctx.kernalContext().task().execute(
> new SizeTask(ctx.name(), 
> ctx.affinity().affinityTopologyVersion(), peekModes), null);
> {noformat}
> Method grp.nodes() returns PredicateCollectionView, which size depends on 
> Ignite state. It can pass nodes.isEmpty() check and become empty later.



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

[jira] [Created] (IGNITE-6425) Races during transaction finalization

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-6425:
-

 Summary: Races during transaction finalization
 Key: IGNITE-6425
 URL: https://issues.apache.org/jira/browse/IGNITE-6425
 Project: Ignite
  Issue Type: Bug
Reporter: Eduard Shangareev






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

[jira] [Assigned] (IGNITE-6425) Races during transaction finalization

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev reassigned IGNITE-6425:
-

Assignee: Eduard Shangareev

> Races during transaction finalization
> -
>
> Key: IGNITE-6425
> URL: https://issues.apache.org/jira/browse/IGNITE-6425
> Project: Ignite
>  Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>




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

[jira] [Created] (IGNITE-6424) .NET: IgniteConfiguration.ServiceConfiguration

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-6424:
--

 Summary: .NET: IgniteConfiguration.ServiceConfiguration
 Key: IGNITE-6424
 URL: https://issues.apache.org/jira/browse/IGNITE-6424
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn


Add {{ServiceConfiguration[] IgniteConfiguration.ServiceConfiguration}} to be 
able to deploy services on start via config (XML or code).



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

[jira] [Comment Edited] (IGNITE-2786) SpringCache doesn't survive client reconnect

[Bruno Barin (JIRA)]

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

Bruno Barin edited comment on IGNITE-2786 at 9/18/17 2:32 PM:
--

Hey, 

Wouldn't be enough to implement CacheErrorHandler with something like this:

{code:java}
public class IgniteCacheErrorHandler implements CacheErrorHandler {

private final SpringCacheManager springCacheManager;

public IgniteCacheErrorHandler(SpringCacheManager springCacheManager) {
this.springCacheManager = springCacheManager;
}

@Override
public void handleCacheGetError(RuntimeException e, Cache cache, Object o) {
if (e instanceof IllegalStateException) {
logger.error("Failed to retrieve value from Cache, node seems to be 
in an inconsistent state. Restarting node.", e);
springCacheManager.restartNode();
} else {
throw e;
}
}

@Override
public void handleCachePutError(RuntimeException e, Cache cache, Object o, 
Object o1) {
throw e;
}

@Override
public void handleCacheEvictError(RuntimeException e, Cache cache, Object 
o) {
throw e;
}

@Override
public void handleCacheClearError(RuntimeException e, Cache cache) {
throw e;
}
{code}


And on SpringCacheManager add a restart method:

{code:java}
public void restartNode() {
caches.entrySet().forEach(entry -> {
caches.get(entry.getKey()).clear();
caches.remove(entry.getKey());
ignite.destroyCache(entry.getKey());
});

try {
restart();
} catch (IgniteCheckedException e) {
logger.error("Failed to restart ignite node",e);
}
}
private void restart() throws IgniteCheckedException {
stop();
start();
}

private void start() throws IgniteCheckedException {
if (cfgPath != null && cfg != null) {
throw new IllegalArgumentException("Both 'configurationPath' and 
'configuration' are " +
"provided. Set only one of these properties if you need to 
start a Ignite node inside of " +
"SpringCacheManager. If you already have a node running, 
omit both of them and set" +
"'igniteInstanceName' property.");
}

if (cfgPath != null)
ignite = IgniteSpring.start(cfgPath, springCtx);
else if (cfg != null)
ignite = IgniteSpring.start(cfg, springCtx);
else
ignite = Ignition.ignite(igniteInstanceName);
}

private void stop() {
ignite.close();
}

{code}

Let me know if that would work. If so, I will open a PR


was (Author: bbarin):
Hey, 

Wouldn't be enough to implement CacheErrorHandler with something like this:

{code:java}
public class IgniteCacheErrorHandler implements CacheErrorHandler {

private final SpringCacheManager springCacheManager;

public IgniteCacheErrorHandler(SpringCacheManager springCacheManager) {
this.springCacheManager = springCacheManager;
}

@Override
public void handleCacheGetError(RuntimeException e, Cache cache, Object o) {
if (e instanceof IllegalStateException) {
logger.error("Failed to retrieve value from Cache, node seems to be 
in an inconsistent state. Restarting node.", e);
springCacheManager.restartNode();
} else {
throw e;
}
}

@Override
public void handleCachePutError(RuntimeException e, Cache cache, Object o, 
Object o1) {
throw e;
}

@Override
public void handleCacheEvictError(RuntimeException e, Cache cache, Object 
o) {
throw e;
}

@Override
public void handleCacheClearError(RuntimeException e, Cache cache) {
throw e;
}
{code}


And on SpringCacheManager add a restart method:

{code:java}
public void restartNode() {
caches.entrySet().forEach(entry -> {
caches.get(entry.getKey()).clear();
caches.remove(entry.getKey());
ignite.destroyCache(entry.getKey());
});

try {
restart();
} catch (IgniteCheckedException e) {
logger.error("Failed to restart ignite node",e);
}
}
private void restart() throws IgniteCheckedException {
stop();
start();
}

private void start() throws IgniteCheckedException {
if (cfgPath != null && cfg != null) {
throw new IllegalArgumentException("Both 'configurationPath' and 
'configuration' are " +
"provided. Set only one of these properties if you need to 
start a Ignite node inside of " +
"SpringCacheManager. If you already have a node running, 
omit both of them and set" +
"'igniteInstanceName' property.");
}

if (cfgPath != null)
   

[jira] [Commented] (IGNITE-2786) SpringCache doesn't survive client reconnect

[Bruno Barin (JIRA)]

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

Bruno Barin commented on IGNITE-2786:
-

Hey, 

Wouldn't be enough to implement CacheErrorHandler with something like this:

{code:java}
public class IgniteCacheErrorHandler implements CacheErrorHandler {

private final SpringCacheManager springCacheManager;

public IgniteCacheErrorHandler(SpringCacheManager springCacheManager) {
this.springCacheManager = springCacheManager;
}

@Override
public void handleCacheGetError(RuntimeException e, Cache cache, Object o) {
if (e instanceof IllegalStateException) {
logger.error("Failed to retrieve value from Cache, node seems to be 
in an inconsistent state. Restarting node.", e);
springCacheManager.restartNode();
} else {
throw e;
}
}

@Override
public void handleCachePutError(RuntimeException e, Cache cache, Object o, 
Object o1) {
throw e;
}

@Override
public void handleCacheEvictError(RuntimeException e, Cache cache, Object 
o) {
throw e;
}

@Override
public void handleCacheClearError(RuntimeException e, Cache cache) {
throw e;
}
{code}


And on SpringCacheManager add a restart method:

{code:java}
public void restartNode() {
caches.entrySet().forEach(entry -> {
caches.get(entry.getKey()).clear();
caches.remove(entry.getKey());
ignite.destroyCache(entry.getKey());
});

try {
restart();
} catch (IgniteCheckedException e) {
logger.error("Failed to restart ignite node",e);
}
}
private void restart() throws IgniteCheckedException {
stop();
start();
}

private void start() throws IgniteCheckedException {
if (cfgPath != null && cfg != null) {
throw new IllegalArgumentException("Both 'configurationPath' and 
'configuration' are " +
"provided. Set only one of these properties if you need to 
start a Ignite node inside of " +
"SpringCacheManager. If you already have a node running, 
omit both of them and set" +
"'igniteInstanceName' property.");
}

if (cfgPath != null)
ignite = IgniteSpring.start(cfgPath, springCtx);
else if (cfg != null)
ignite = IgniteSpring.start(cfg, springCtx);
else
ignite = Ignition.ignite(igniteInstanceName);
}

private void stop() {
ignite.close();
}

{code}

> SpringCache doesn't survive client reconnect
> 
>
> Key: IGNITE-2786
> URL: https://issues.apache.org/jira/browse/IGNITE-2786
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>
> After a client disconnects and reconnects with new ID, Spring caching can't 
> be used, because existing cache instance are closed.



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

[jira] [Updated] (IGNITE-6423) PDS could be corrupted if partition have been evicted and returned to node

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev updated IGNITE-6423:
--
Summary: PDS could be corrupted if partition have been evicted and returned 
to node  (was: LFD could be corrupted if partition have been evicted and 
returned to node)

> PDS could be corrupted if partition have been evicted and returned to node
> --
>
> Key: IGNITE-6423
> URL: https://issues.apache.org/jira/browse/IGNITE-6423
> Project: Ignite
>  Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Critical
> Fix For: 2.3
>
>
> So, what is going on? 
> Partition had been changed, its pages had been put to checkpoint pages.
> After it partition was evicted, checkpoint started.
> We are allocating a page and because it's already in checkpoint we copy the 
> empty page to copy it on disk.
> If we restart right now we will read the empty page from disk. Therefore 
> assertion error would be thrown etc.



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

[jira] [Created] (IGNITE-6423) LFD could be corrupted if partition have been evicted and returned to node

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-6423:
-

 Summary: LFD could be corrupted if partition have been evicted and 
returned to node
 Key: IGNITE-6423
 URL: https://issues.apache.org/jira/browse/IGNITE-6423
 Project: Ignite
  Issue Type: Bug
Reporter: Eduard Shangareev
Priority: Critical


So, what is going on? 
Partition had been changed, its pages had been put to checkpoint pages.
After it partition was evicted, checkpoint started.
We are allocating a page and because it's already in checkpoint we copy the 
empty page to copy it on disk.
If we restart right now we will read the empty page from disk. Therefore 
assertion error would be thrown etc.



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

[jira] [Assigned] (IGNITE-6423) LFD could be corrupted if partition have been evicted and returned to node

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev reassigned IGNITE-6423:
-

Assignee: Eduard Shangareev

> LFD could be corrupted if partition have been evicted and returned to node
> --
>
> Key: IGNITE-6423
> URL: https://issues.apache.org/jira/browse/IGNITE-6423
> Project: Ignite
>  Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Critical
> Fix For: 2.3
>
>
> So, what is going on? 
> Partition had been changed, its pages had been put to checkpoint pages.
> After it partition was evicted, checkpoint started.
> We are allocating a page and because it's already in checkpoint we copy the 
> empty page to copy it on disk.
> If we restart right now we will read the empty page from disk. Therefore 
> assertion error would be thrown etc.



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

[jira] [Updated] (IGNITE-6423) LFD could be corrupted if partition have been evicted and returned to node

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev updated IGNITE-6423:
--
Fix Version/s: 2.3

> LFD could be corrupted if partition have been evicted and returned to node
> --
>
> Key: IGNITE-6423
> URL: https://issues.apache.org/jira/browse/IGNITE-6423
> Project: Ignite
>  Issue Type: Bug
>Reporter: Eduard Shangareev
>Priority: Critical
> Fix For: 2.3
>
>
> So, what is going on? 
> Partition had been changed, its pages had been put to checkpoint pages.
> After it partition was evicted, checkpoint started.
> We are allocating a page and because it's already in checkpoint we copy the 
> empty page to copy it on disk.
> If we restart right now we will read the empty page from disk. Therefore 
> assertion error would be thrown etc.



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

[jira] [Commented] (IGNITE-5865) TxOptimisticDeadlockDetectionTest.testDeadlocksPartitioned is failing

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-5865:
-

LGTM! Thanks for your contribution! Merged to master branch.

> TxOptimisticDeadlockDetectionTest.testDeadlocksPartitioned is failing
> -
>
> Key: IGNITE-5865
> URL: https://issues.apache.org/jira/browse/IGNITE-5865
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Pavel Kovalenko
>Assignee: Vitaliy Biryukov
>  Labels: MakeTeamcityGreenAgain, Muted_test, test-failure
> Fix For: 2.3
>
>
> Test is flaky.
> Also there is always failing test in suite: 
> TxOptimisticDeadlockDetectionTest.testDeadlocksPartitionedNear
> TC build result: 
> http://ci.ignite.apache.org/viewLog.html?buildId=744109=buildResultsDiv=Ignite20Tests_IgniteCacheDeadlockDetection
> Stacktrace: 
> {noformat}
> [2017-07-28 
> 03:31:52,827][ERROR][grid-timeout-worker-#31%transactions.TxOptimisticDeadlockDetectionTest0%][IgniteTxHandler]
>  Failed to prepare DHT transaction: GridDhtTxLocal 
> [nearNodeId=d005de76-4378-4cd5-ad7e-f00593a2, 
> nearFutId=aab9f378d51-37ca90c9-03f5-417c-9731-2c29810e3cc0, nearMiniId=1, 
> nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion 
> [topVer=112692678, order=1501212673293, nodeOrder=3], 
> super=GridDhtTxLocalAdapter [nearOnOriginatingNode=false, nearNodes=[], 
> dhtNodes=[], explicitLock=false, super=IgniteTxLocalAdapter 
> [completedBase=null, sndTransformedVals=false, depEnabled=false, 
> txState=IgniteTxStateImpl [activeCacheIds=GridIntList [idx=1, 
> arr=[94416770]], recovery=false, txMap=[IgniteTxEntry 
> [key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=424974513, hash=-1228408719, id=1, name=KeyObject1], 
> cacheId=94416770, txKey=IgniteTxKey 
> [key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=424974513, hash=-1228408719, id=1, name=KeyObject1], 
> cacheId=94416770], val=[op=CREATE, val=CacheObjectImpl [val=null, 
> hasValBytes=true]], prevVal=[op=NOOP, val=null], oldVal=[op=NOOP, val=null], 
> entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1, conflictVer=null, 
> explicitVer=null, dhtVer=null, filters=[], filtersPassed=false, 
> filtersSet=false, entry=GridDhtCacheEntry [rdrs=[], part=694, 
> super=GridDistributedCacheEntry [super=GridCacheMapEntry 
> [key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=16030069, hash=-1228408719, id=1, name=KeyObject1], val=null, 
> startVer=1501212673290, ver=GridCacheVersion [topVer=112692678, 
> order=1501212673290, nodeOrder=1], hash=-1228408719, 
> extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc 
> [locs=[GridCacheMvccCandidate [nodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, 
> ver=GridCacheVersion [topVer=112692678, order=1501212673287, nodeOrder=1], 
> threadId=846, id=520, topVer=AffinityTopologyVersion [topVer=8, 
> minorTopVer=8], reentry=null, 
> otherNodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, otherVer=GridCacheVersion 
> [topVer=112692678, order=1501212673287, nodeOrder=1], mappedDhtNodes=null, 
> mappedNearNodes=null, ownerVer=null, serOrder=null, 
> key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=16030069, hash=-1228408719, id=1, name=KeyObject1], 
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
>  prevVer=null, nextVer=null], GridCacheMvccCandidate 
> [nodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, ver=GridCacheVersion 
> [topVer=112692678, order=1501212673314, nodeOrder=1], threadId=847, id=521, 
> topVer=AffinityTopologyVersion [topVer=8, minorTopVer=8], reentry=null, 
> otherNodeId=d005de76-4378-4cd5-ad7e-f00593a2, otherVer=GridCacheVersion 
> [topVer=112692678, order=1501212673293, nodeOrder=3], mappedDhtNodes=null, 
> mappedNearNodes=null, ownerVer=GridCacheVersion [topVer=112692678, 
> order=1501212673287, nodeOrder=1], serOrder=null, 
> key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=16030069, hash=-1228408719, id=1, name=KeyObject1], 
> masks=local=1|owner=0|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
>  prevVer=null, nextVer=null]], rmts=null]], flags=2]]], prepared=1, 
> locked=false, nodeId=null, locMapped=false, expiryPlc=null, 
> transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null, 
> xidVer=null]]], super=IgniteTxAdapter [xidVer=GridCacheVersion 
> [topVer=112692678, order=1501212673314, nodeOrder=1], writeVer=null, 
> implicit=false, loc=true, threadId=847, startTime=1501212712015, 
> 

[jira] [Commented] (IGNITE-6391) JDBC thin driver: JdbcThinTcpIo.srvProtocolVer is not used

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6391:


GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-6391 JDBC thin driver: remove unused JdbcThinTcpIo.srvProtocolVer



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

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

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

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


commit 654b456957acde951a910450f5c8eb8ccefecad0
Author: tledkov-gridgain 
Date:   2017-09-18T14:24:10Z

IGNITE-6391 JDBC thin driver: remove unused JdbcThinTcpIo.srvProtocolVer




> JDBC thin driver: JdbcThinTcpIo.srvProtocolVer is not used
> --
>
> Key: IGNITE-6391
> URL: https://issues.apache.org/jira/browse/IGNITE-6391
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.3
>
>
> Need to understand why it is so.



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

[jira] [Commented] (IGNITE-6244) .NET: Thin client: ScanQuery

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-6244:


[~vozerov] done.

Added basic error handling to {{ClientResponse}} via a boolean flag so we can 
test maxCursors logic. Proper exception propagation will be done in IGNITE-6250.

> .NET: Thin client: ScanQuery
> 
>
> Key: IGNITE-6244
> URL: https://issues.apache.org/jira/browse/IGNITE-6244
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.3
>
>
> Implement ScanQuery in thin client.
> Challenges:
> * Query cursor. This will require some kind of HandleRegistry on Java side, 
> so we can pass an ID back to client (see {{OdbcRequestHandler.qryCursors}} as 
> an example).
> * Predicate. Thin client is not .NET-specific. We need a way to support 
> predicates in (at least) Java and .NET, there should be some platform id.



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

[jira] [Created] (IGNITE-6422) In visorcmd "cache on nodes" statistics mixes together primary and backup entries

[Ilya Kasnacheev (JIRA)]

Ilya Kasnacheev created IGNITE-6422:
---

 Summary: In visorcmd "cache on nodes" statistics mixes together 
primary and backup entries
 Key: IGNITE-6422
 URL: https://issues.apache.org/jira/browse/IGNITE-6422
 Project: Ignite
  Issue Type: Bug
  Components: visor
Affects Versions: 2.3
Reporter: Ilya Kasnacheev
Assignee: Vasiliy Sisko


Suppose we have a cache, with 1000 entries, one backup and eviction after 500 
entries. Then, off-heap entries are doubled in visorcmd, while on-heap entries 
are not:

{code}
+-+
| Name(@) | EmployeesCache(@c0)   |
| Nodes   | 2 |
| Total size Min/Avg/Max  | 1500 / 1500.00 / 1500 |
|   Heap size Min/Avg/Max | 500 / 500.00 / 500|
|   Off-heap size Min/Avg/Max | 1000 / 1000.00 / 1000 |
+-+

Nodes for: EmployeesCache(@c0)
+=+
|  Node ID8(@), IP  | CPUs | Heap Used | CPU Load |   Up Time|  
   Size | Hi/Mi/Rd/Wr |
+=+
| 37333BC6(@n0), 172.16.9.1 | 8| 4.47 %| 0.40 %   | 00:00:47:154 | 
Total: 1500  | Hi: 0   |
|   |  |   |  |  |   
Heap: 500  | Mi: 0   |
|   |  |   |  |  |   
Off-Heap: 1000 | Rd: 0   |
|   |  |   |  |  |   
Off-Heap Memory: 0 | Wr: 0   |
+---+--+---+--+--+--+-+
| 26FD4343(@n1), 172.16.9.1 | 8| 3.09 %| 0.23 %   | 00:00:41:602 | 
Total: 1500  | Hi: 0   |
|   |  |   |  |  |   
Heap: 500  | Mi: 0   |
|   |  |   |  |  |   
Off-Heap: 1000 | Rd: 0   |
|   |  |   |  |  |   
Off-Heap Memory: 0 | Wr: 0   |
+-+
'Hi' - Number of cache hits.
{code}

By contrast, on 1.9 it looks like this:
{code}
Cache 'EmployeesCache(@c0)':
+-+
| Name(@) | EmployeesCache(@c0)   |
| Nodes   | 2 |
| Total size Min/Avg/Max  | 1000 / 1000.00 / 1000 |
|   Heap size Min/Avg/Max | 500 / 500.00 / 500|
|   Off-heap size Min/Avg/Max | 500 / 500.00 / 500|
+-+

Nodes for: EmployeesCache(@c0)
++
|  Node ID8(@), IP  | CPUs | Heap Used | CPU Load |   Up Time|  
Size   | Hi/Mi/Rd/Wr |
++
| 3229FABE(@n0), 172.16.9.1 | 8| 1.25 %| 0.23 %   | 00:00:43:111 | 
Total: 1000 | Hi: 0   |
|   |  |   |  |  |   
Heap: 500 | Mi: 0   |
|   |  |   |  |  |   
Off-Heap: 500 | Rd: 0   |
|   |  |   |  |  |   
Off-Heap Memory: 88kb | Wr: 0   |
+---+--+---+--+--+-+-+
| 58FA742B(@n1), 172.16.9.1 | 8| 1.15 %| 0.47 %   | 00:00:38:828 | 
Total: 1000 | Hi: 0   |
|   |  |   |  |  |   
Heap: 500 | Mi: 0   |
|   |  |   |  |  |   
Off-Heap: 500 | Rd: 0   |
|   |  |   |  |  |   
Off-Heap Memory: 88kb | Wr: 0   |
++
{code}

NB: It might be feasible to keep number of backup entries displayed in 
visorcmd, but without adding them up with primary entries. Another dedicated 
line perhaps? Should also probably be consistent with other memory kinds.



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

[jira] [Commented] (IGNITE-6355) Calculating cache size during cache stop sporadically fails with ClusterGroupEmptyCheckedException

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6355:


Github user asfgit closed the pull request at:

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


> Calculating cache size during cache stop sporadically fails with 
> ClusterGroupEmptyCheckedException
> --
>
> Key: IGNITE-6355
> URL: https://issues.apache.org/jira/browse/IGNITE-6355
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Ivan Rakov
>Assignee: Ivan Rakov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> Example stacktrace:
> {noformat}
> [16:21:06,343][ERROR][main][root] Test failed.
> javax.cache.CacheException: class 
> org.apache.ignite.cluster.ClusterGroupEmptyException: Topology projection is 
> empty.
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1327)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1672)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.size(IgniteCacheProxyImpl.java:762)
>   at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.size(GatewayProtectedCacheProxy.java:508)
>   at 
> org.gridgain.grid.internal.processors.cache.database.IgniteDbSnapshotSelfTest.testReuseCacheProxyAfterRestore(IgniteDbSnapshotSelfTest.java:1793)
>   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:2000)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.cluster.ClusterGroupEmptyException: 
> Topology projection is empty.
>   at 
> org.apache.ignite.internal.util.IgniteUtils$6.apply(IgniteUtils.java:823)
>   at 
> org.apache.ignite.internal.util.IgniteUtils$6.apply(IgniteUtils.java:821)
>   ... 14 more
> Caused by: class 
> org.apache.ignite.internal.cluster.ClusterGroupEmptyCheckedException: 
> Topology projection is empty.
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.getTaskTopology(GridTaskWorker.java:665)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:500)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:758)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:454)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:410)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.sizeAsync(GridCacheAdapter.java:3747)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.size(GridCacheAdapter.java:3704)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.size(IgniteCacheProxyImpl.java:759)
>   ... 11 more
> {noformat}
> Data race stems from here (GridCacheAdapter#sizeAsync):
> {noformat}
> Group grp = modes.near ? cluster.forCacheNodes(name(), true, true, 
> false) : cluster.forDataNodes(name());
> Collection nodes = grp.nodes();
> if (nodes.isEmpty())
> return new GridFinishedFuture<>(0);
> ctx.kernalContext().task().setThreadContext(TC_SUBGRID, nodes);
> return ctx.kernalContext().task().execute(
> new SizeTask(ctx.name(), 
> ctx.affinity().affinityTopologyVersion(), peekModes), null);
> {noformat}
> Method grp.nodes() returns PredicateCollectionView, which size depends on 
> Ignite state. It can pass nodes.isEmpty() check and become empty later.



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

[jira] [Updated] (IGNITE-6421) Ignite WAL reader: add shell script to start converter

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-6421:
---
Issue Type: Task  (was: Bug)

> Ignite WAL reader: add shell script to start converter
> --
>
> Key: IGNITE-6421
> URL: https://issues.apache.org/jira/browse/IGNITE-6421
> Project: Ignite
>  Issue Type: Task
>  Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>
> Support simple startup for utility 
> https://cwiki.apache.org/confluence/display/IGNITE/Ignite+WAL+reader by 
> providing shell and bat files



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

[jira] [Created] (IGNITE-6421) Ignite WAL reader: add shell script to start converter

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-6421:
--

 Summary: Ignite WAL reader: add shell script to start converter
 Key: IGNITE-6421
 URL: https://issues.apache.org/jira/browse/IGNITE-6421
 Project: Ignite
  Issue Type: Bug
  Components: persistence
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov


Support simple startup for utility 
https://cwiki.apache.org/confluence/display/IGNITE/Ignite+WAL+reader by 
providing shell and bat files



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

[jira] [Commented] (IGNITE-6014) Add transaction prepare and commit markers to WAL

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6014:


Github user asfgit closed the pull request at:

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


> Add transaction prepare and commit markers to WAL
> -
>
> Key: IGNITE-6014
> URL: https://issues.apache.org/jira/browse/IGNITE-6014
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Ilya Lantukh
> Fix For: 2.3
>
>
> This may be useful for various recovery procedures in the future



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

[jira] [Assigned] (IGNITE-6355) Calculating cache size during cache stop sporadically fails with ClusterGroupEmptyCheckedException

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev reassigned IGNITE-6355:
-

Assignee: Ivan Rakov  (was: Alexey Goncharuk)

> Calculating cache size during cache stop sporadically fails with 
> ClusterGroupEmptyCheckedException
> --
>
> Key: IGNITE-6355
> URL: https://issues.apache.org/jira/browse/IGNITE-6355
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Ivan Rakov
>Assignee: Ivan Rakov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> Example stacktrace:
> {noformat}
> [16:21:06,343][ERROR][main][root] Test failed.
> javax.cache.CacheException: class 
> org.apache.ignite.cluster.ClusterGroupEmptyException: Topology projection is 
> empty.
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1327)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1672)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.size(IgniteCacheProxyImpl.java:762)
>   at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.size(GatewayProtectedCacheProxy.java:508)
>   at 
> org.gridgain.grid.internal.processors.cache.database.IgniteDbSnapshotSelfTest.testReuseCacheProxyAfterRestore(IgniteDbSnapshotSelfTest.java:1793)
>   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:2000)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.cluster.ClusterGroupEmptyException: 
> Topology projection is empty.
>   at 
> org.apache.ignite.internal.util.IgniteUtils$6.apply(IgniteUtils.java:823)
>   at 
> org.apache.ignite.internal.util.IgniteUtils$6.apply(IgniteUtils.java:821)
>   ... 14 more
> Caused by: class 
> org.apache.ignite.internal.cluster.ClusterGroupEmptyCheckedException: 
> Topology projection is empty.
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.getTaskTopology(GridTaskWorker.java:665)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:500)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:758)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:454)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:410)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.sizeAsync(GridCacheAdapter.java:3747)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.size(GridCacheAdapter.java:3704)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.size(IgniteCacheProxyImpl.java:759)
>   ... 11 more
> {noformat}
> Data race stems from here (GridCacheAdapter#sizeAsync):
> {noformat}
> Group grp = modes.near ? cluster.forCacheNodes(name(), true, true, 
> false) : cluster.forDataNodes(name());
> Collection nodes = grp.nodes();
> if (nodes.isEmpty())
> return new GridFinishedFuture<>(0);
> ctx.kernalContext().task().setThreadContext(TC_SUBGRID, nodes);
> return ctx.kernalContext().task().execute(
> new SizeTask(ctx.name(), 
> ctx.affinity().affinityTopologyVersion(), peekModes), null);
> {noformat}
> Method grp.nodes() returns PredicateCollectionView, which size depends on 
> Ignite state. It can pass nodes.isEmpty() check and become empty later.



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

[jira] [Commented] (IGNITE-5865) TxOptimisticDeadlockDetectionTest.testDeadlocksPartitioned is failing

[Vitaliy Biryukov (JIRA)]

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

Vitaliy Biryukov commented on IGNITE-5865:
--

[~agura], Done. Please, take a look.

Thanks.

> TxOptimisticDeadlockDetectionTest.testDeadlocksPartitioned is failing
> -
>
> Key: IGNITE-5865
> URL: https://issues.apache.org/jira/browse/IGNITE-5865
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Pavel Kovalenko
>Assignee: Vitaliy Biryukov
>  Labels: MakeTeamcityGreenAgain, Muted_test, test-failure
> Fix For: 2.3
>
>
> Test is flaky.
> Also there is always failing test in suite: 
> TxOptimisticDeadlockDetectionTest.testDeadlocksPartitionedNear
> TC build result: 
> http://ci.ignite.apache.org/viewLog.html?buildId=744109=buildResultsDiv=Ignite20Tests_IgniteCacheDeadlockDetection
> Stacktrace: 
> {noformat}
> [2017-07-28 
> 03:31:52,827][ERROR][grid-timeout-worker-#31%transactions.TxOptimisticDeadlockDetectionTest0%][IgniteTxHandler]
>  Failed to prepare DHT transaction: GridDhtTxLocal 
> [nearNodeId=d005de76-4378-4cd5-ad7e-f00593a2, 
> nearFutId=aab9f378d51-37ca90c9-03f5-417c-9731-2c29810e3cc0, nearMiniId=1, 
> nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion 
> [topVer=112692678, order=1501212673293, nodeOrder=3], 
> super=GridDhtTxLocalAdapter [nearOnOriginatingNode=false, nearNodes=[], 
> dhtNodes=[], explicitLock=false, super=IgniteTxLocalAdapter 
> [completedBase=null, sndTransformedVals=false, depEnabled=false, 
> txState=IgniteTxStateImpl [activeCacheIds=GridIntList [idx=1, 
> arr=[94416770]], recovery=false, txMap=[IgniteTxEntry 
> [key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=424974513, hash=-1228408719, id=1, name=KeyObject1], 
> cacheId=94416770, txKey=IgniteTxKey 
> [key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=424974513, hash=-1228408719, id=1, name=KeyObject1], 
> cacheId=94416770], val=[op=CREATE, val=CacheObjectImpl [val=null, 
> hasValBytes=true]], prevVal=[op=NOOP, val=null], oldVal=[op=NOOP, val=null], 
> entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1, conflictVer=null, 
> explicitVer=null, dhtVer=null, filters=[], filtersPassed=false, 
> filtersSet=false, entry=GridDhtCacheEntry [rdrs=[], part=694, 
> super=GridDistributedCacheEntry [super=GridCacheMapEntry 
> [key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=16030069, hash=-1228408719, id=1, name=KeyObject1], val=null, 
> startVer=1501212673290, ver=GridCacheVersion [topVer=112692678, 
> order=1501212673290, nodeOrder=1], hash=-1228408719, 
> extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc 
> [locs=[GridCacheMvccCandidate [nodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, 
> ver=GridCacheVersion [topVer=112692678, order=1501212673287, nodeOrder=1], 
> threadId=846, id=520, topVer=AffinityTopologyVersion [topVer=8, 
> minorTopVer=8], reentry=null, 
> otherNodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, otherVer=GridCacheVersion 
> [topVer=112692678, order=1501212673287, nodeOrder=1], mappedDhtNodes=null, 
> mappedNearNodes=null, ownerVer=null, serOrder=null, 
> key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=16030069, hash=-1228408719, id=1, name=KeyObject1], 
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
>  prevVer=null, nextVer=null], GridCacheMvccCandidate 
> [nodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, ver=GridCacheVersion 
> [topVer=112692678, order=1501212673314, nodeOrder=1], threadId=847, id=521, 
> topVer=AffinityTopologyVersion [topVer=8, minorTopVer=8], reentry=null, 
> otherNodeId=d005de76-4378-4cd5-ad7e-f00593a2, otherVer=GridCacheVersion 
> [topVer=112692678, order=1501212673293, nodeOrder=3], mappedDhtNodes=null, 
> mappedNearNodes=null, ownerVer=GridCacheVersion [topVer=112692678, 
> order=1501212673287, nodeOrder=1], serOrder=null, 
> key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=16030069, hash=-1228408719, id=1, name=KeyObject1], 
> masks=local=1|owner=0|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
>  prevVer=null, nextVer=null]], rmts=null]], flags=2]]], prepared=1, 
> locked=false, nodeId=null, locMapped=false, expiryPlc=null, 
> transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null, 
> xidVer=null]]], super=IgniteTxAdapter [xidVer=GridCacheVersion 
> [topVer=112692678, order=1501212673314, nodeOrder=1], writeVer=null, 
> implicit=false, loc=true, threadId=847, startTime=1501212712015, 
> 

[jira] [Assigned] (IGNITE-6405) Deadlock is not detected if timed out on client.

[Andrey Gura (JIRA)]

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

Andrey Gura reassigned IGNITE-6405:
---

Assignee: Andrey Gura

> Deadlock is not detected if timed out on client.
> 
>
> Key: IGNITE-6405
> URL: https://issues.apache.org/jira/browse/IGNITE-6405
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Alexei Scherbakov
>Assignee: Andrey Gura
>Priority: Minor
> Fix For: 2.3
>
>
> Timeout exception is thrown instead.
> Reproducer:
> {noformat}
> /*
>  * Licensed to the Apache Software Foundation (ASF) under one or more
>  * contributor license agreements.  See the NOTICE file distributed with
>  * this work for additional information regarding copyright ownership.
>  * The ASF licenses this file to You under the Apache License, Version 2.0
>  * (the "License"); you may not use this file except in compliance with
>  * the License.  You may obtain a copy of the License at
>  *
>  *  http://www.apache.org/licenses/LICENSE-2.0
>  *
>  * Unless required by applicable law or agreed to in writing, software
>  * distributed under the License is distributed on an "AS IS" BASIS,
>  * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
>  * See the License for the specific language governing permissions and
>  * limitations under the License.
>  */
> package org.apache.ignite.internal.processors.cache.transactions;
> import java.util.Collections;
> import java.util.concurrent.CountDownLatch;
> import javax.cache.CacheException;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.configuration.TransactionConfiguration;
> import org.apache.ignite.internal.IgniteInternalFuture;
> import org.apache.ignite.internal.util.typedef.internal.U;
> import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> import org.apache.ignite.transactions.Transaction;
> import org.apache.ignite.transactions.TransactionDeadlockException;
> import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL;
> import static 
> org.apache.ignite.transactions.TransactionConcurrency.PESSIMISTIC;
> import static 
> org.apache.ignite.transactions.TransactionIsolation.REPEATABLE_READ;
> /**
>  * Tests an ability to eagerly rollback timed out transactions.
>  */
> public class TxPessimisticDeadlockDetectionClient extends 
> GridCommonAbstractTest {
> /** */
> private static final long TX_MIN_TIMEOUT = 1;
> /** */
> private static final long TX_TIMEOUT = 300;
> /** */
> private static final long TX_DEFAULT_TIMEOUT = 3_000;
> /** */
> private static final String CACHE_NAME = "test";
> /** IP finder. */
> private static final TcpDiscoveryVmIpFinder IP_FINDER = new 
> TcpDiscoveryVmIpFinder(true);
> /** */
> private static final int GRID_CNT = 3;
> /** */
> private final CountDownLatch blocked = new CountDownLatch(1);
> /** */
> private final CountDownLatch unblocked = new CountDownLatch(1);
> /** {@inheritDoc} */
> @Override protected IgniteConfiguration getConfiguration(String 
> igniteInstanceName) throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
> cfg.setClientMode("client".equals(igniteInstanceName));
> ((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER);
> TransactionConfiguration txCfg = new TransactionConfiguration();
> txCfg.setDefaultTxTimeout(TX_DEFAULT_TIMEOUT);
> cfg.setTransactionConfiguration(txCfg);
> CacheConfiguration ccfg = new CacheConfiguration(CACHE_NAME);
> ccfg.setAtomicityMode(TRANSACTIONAL);
> ccfg.setBackups(2);
> cfg.setCacheConfiguration(ccfg);
> return cfg;
> }
> /** {@inheritDoc} */
> @Override protected void beforeTest() throws Exception {
> super.beforeTest();
> startGridsMultiThreaded(GRID_CNT);
> }
> /** {@inheritDoc} */
> @Override protected void afterTest() throws Exception {
> super.afterTest();
> stopAllGrids();
> }
> /** */
> protected void validateException(Exception e) {
> assertEquals("Deadlock report is expected",
> TransactionDeadlockException.class, 
> e.getCause().getCause().getClass());
> }
> /**
>  * Tests if deadlock is resolved on timeout with correct message.
>  *
>  * @throws Exception If failed.
>  */
> public void testDeadlockUnblockedOnTimeout() throws Exception {
> Ignite 

[jira] [Updated] (IGNITE-6405) Deadlock is not detected if timed out on client.

[Alexei Scherbakov (JIRA)]

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

Alexei Scherbakov updated IGNITE-6405:
--
Description: 
Timeout exception is thrown instead.

Reproducer:

{noformat}
/*
 * Licensed to the Apache Software Foundation (ASF) under one or more
 * contributor license agreements.  See the NOTICE file distributed with
 * this work for additional information regarding copyright ownership.
 * The ASF licenses this file to You under the Apache License, Version 2.0
 * (the "License"); you may not use this file except in compliance with
 * the License.  You may obtain a copy of the License at
 *
 *  http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

package org.apache.ignite.internal.processors.cache.transactions;

import java.util.Collections;
import java.util.concurrent.CountDownLatch;
import javax.cache.CacheException;
import org.apache.ignite.Ignite;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.configuration.TransactionConfiguration;
import org.apache.ignite.internal.IgniteInternalFuture;
import org.apache.ignite.internal.util.typedef.internal.U;
import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
import org.apache.ignite.transactions.Transaction;
import org.apache.ignite.transactions.TransactionDeadlockException;

import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL;
import static org.apache.ignite.transactions.TransactionConcurrency.PESSIMISTIC;
import static 
org.apache.ignite.transactions.TransactionIsolation.REPEATABLE_READ;

/**
 * Tests an ability to eagerly rollback timed out transactions.
 */
public class TxPessimisticDeadlockDetectionClient extends 
GridCommonAbstractTest {
/** */
private static final long TX_MIN_TIMEOUT = 1;

/** */
private static final long TX_TIMEOUT = 300;

/** */
private static final long TX_DEFAULT_TIMEOUT = 3_000;

/** */
private static final String CACHE_NAME = "test";

/** IP finder. */
private static final TcpDiscoveryVmIpFinder IP_FINDER = new 
TcpDiscoveryVmIpFinder(true);

/** */
private static final int GRID_CNT = 3;

/** */
private final CountDownLatch blocked = new CountDownLatch(1);

/** */
private final CountDownLatch unblocked = new CountDownLatch(1);

/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String 
igniteInstanceName) throws Exception {
IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);

cfg.setClientMode("client".equals(igniteInstanceName));

((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER);

TransactionConfiguration txCfg = new TransactionConfiguration();
txCfg.setDefaultTxTimeout(TX_DEFAULT_TIMEOUT);

cfg.setTransactionConfiguration(txCfg);

CacheConfiguration ccfg = new CacheConfiguration(CACHE_NAME);
ccfg.setAtomicityMode(TRANSACTIONAL);
ccfg.setBackups(2);

cfg.setCacheConfiguration(ccfg);

return cfg;
}

/** {@inheritDoc} */
@Override protected void beforeTest() throws Exception {
super.beforeTest();

startGridsMultiThreaded(GRID_CNT);
}

/** {@inheritDoc} */
@Override protected void afterTest() throws Exception {
super.afterTest();

stopAllGrids();
}

/** */
protected void validateException(Exception e) {
assertEquals("Deadlock report is expected",
TransactionDeadlockException.class, 
e.getCause().getCause().getClass());
}

/**
 * Tests if deadlock is resolved on timeout with correct message.
 *
 * @throws Exception If failed.
 */
public void testDeadlockUnblockedOnTimeout() throws Exception {
Ignite client = startGrid("client");

testDeadlockUnblockedOnTimeout0(client, ignite(0));
}

/**
 * Tests if deadlock is resolved on timeout with correct message.
 * @throws Exception
 */
private void testDeadlockUnblockedOnTimeout0(final Ignite node1, final 
Ignite node2) throws Exception {
final CountDownLatch l = new CountDownLatch(2);

IgniteInternalFuture fut1 = multithreadedAsync(new Runnable() {
@Override public void run() {
try {
try (Transaction tx = node1.transactions().txStart()) {
   

[jira] [Commented] (IGNITE-6317) JDBC thick driver: SQLSTATE error codes

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6317:


Github user asfgit closed the pull request at:

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


> JDBC thick driver: SQLSTATE error codes
> ---
>
> Key: IGNITE-6317
> URL: https://issues.apache.org/jira/browse/IGNITE-6317
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.3
>
>
> We need to implement SQLSTATE management in "thick" JDBC driver:
> 1) Make sure that server-side error codes are propagated
> 2) Rework client-side {{SQLException}}s and add error codes to them as well



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

[jira] [Commented] (IGNITE-6307) If getAll() fails with NPE, onHeap entry is not removed, for local cache

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-6307:
-

[~avinogradov] I got the numbers and it seems OK.
Can you review and merge my fix?

> If getAll() fails with NPE, onHeap entry is not removed, for local cache
> 
>
> Key: IGNITE-6307
> URL: https://issues.apache.org/jira/browse/IGNITE-6307
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.0
>Reporter: Dmitriy Govorukhin
>Assignee: Nikolay Izhikov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> GridCacheLocalFullApiSelfTest.testGetAllWithNulls
> {code}
> final Set c = new HashSet<>();
> c.add("key1");
> c.add(null);
> GridTestUtils.assertThrows(log, new Callable() {
> @Override public Void call() throws Exception {
> cache.getAll(c);
> return null;
> }
> }, NullPointerException.class, null);
> {code}
> After getAll, entry with "key1" will be in heap map, it is dependent of order 
> in collection for getAll();



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

[jira] [Commented] (IGNITE-6200) org.dom4j.QName can't be serialized

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-6200:
-

LGTM. Merged to master branch.

> org.dom4j.QName can't be serialized
> ---
>
> Key: IGNITE-6200
> URL: https://issues.apache.org/jira/browse/IGNITE-6200
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Alexei Scherbakov
>Assignee: Andrey Gura
> Fix For: 2.3
>
>
> Exception:
> {noformat}
> class org.apache.ignite.binary.BinaryObjectException: Failed to marshal 
> object with optimized marshaller: org.dom4j.QName@364492 [name: test 
> namespace: "org.dom4j.Namespace@e20 [Namespace: prefix qq mapped to URI ""]"]
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:186)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:248)
>   at 
> org.apache.ignite.internal.binary.BinaryMarshaller.marshal0(BinaryMarshaller.java:82)
>   at 
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)
>   at 
> org.apache.ignite.internal.processors.cache.MarshallerTest.test(MarshallerTest.java:160)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to 
> serialize object: org.dom4j.QName@364492 [name: test namespace: 
> "org.dom4j.Namespace@e20 [Namespace: prefix qq mapped to URI ""]"]
>   at 
> org.apache.ignite.internal.marshaller.optimized.OptimizedMarshaller.marshal0(OptimizedMarshaller.java:206)
>   at 
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9836)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:179)
>   ... 15 more
> Caused by: java.io.IOException: java.io.NotActiveException: Not in 
> writeObject() call.
>   at 
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:324)
>   at 
> org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:827)
>   at 
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:224)
>   at 
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObjectOverride(OptimizedObjectOutputStream.java:152)
>   at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344)
>   at 
> org.apache.ignite.internal.marshaller.optimized.OptimizedMarshaller.marshal0(OptimizedMarshaller.java:201)
>   ... 18 more
> Caused by: java.io.NotActiveException: Not in writeObject() call.
>   at 
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.defaultWriteObject(OptimizedObjectOutputStream.java:684)
>   at org.dom4j.QName.writeObject(QName.java:239)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at 
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:318)
>   ... 23 more
> {noformat}
> Reproducer:
> {noformat}
> public void test() throws Exception {
> try {
> IgniteEx ex = startGrid(0);
> QName qName = new QName("test", new Namespace("qq", null), "q");
> byte[] marshal = 
> ex.configuration().getMarshaller().marshal(qName);
> } finally {
> stopAllGrids();
> }
> }
> {noformat}



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

[jira] [Created] (IGNITE-6420) Time metrics (CacheMetrics.getAverage###Time) should be calculated on primary node in case of ATOMIC cache

[Vyacheslav Koptilin (JIRA)]

Vyacheslav Koptilin created IGNITE-6420:
---

 Summary: Time metrics (CacheMetrics.getAverage###Time) should be 
calculated on primary node in case of ATOMIC cache
 Key: IGNITE-6420
 URL: https://issues.apache.org/jira/browse/IGNITE-6420
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.6
Reporter: Vyacheslav Koptilin
Assignee: Vyacheslav Koptilin






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

[jira] [Commented] (IGNITE-6355) Calculating cache size during cache stop sporadically fails with ClusterGroupEmptyCheckedException

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev commented on IGNITE-6355:
---

Looks good for me.

> Calculating cache size during cache stop sporadically fails with 
> ClusterGroupEmptyCheckedException
> --
>
> Key: IGNITE-6355
> URL: https://issues.apache.org/jira/browse/IGNITE-6355
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Ivan Rakov
>Assignee: Ivan Rakov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> Example stacktrace:
> {noformat}
> [16:21:06,343][ERROR][main][root] Test failed.
> javax.cache.CacheException: class 
> org.apache.ignite.cluster.ClusterGroupEmptyException: Topology projection is 
> empty.
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1327)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1672)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.size(IgniteCacheProxyImpl.java:762)
>   at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.size(GatewayProtectedCacheProxy.java:508)
>   at 
> org.gridgain.grid.internal.processors.cache.database.IgniteDbSnapshotSelfTest.testReuseCacheProxyAfterRestore(IgniteDbSnapshotSelfTest.java:1793)
>   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:2000)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.cluster.ClusterGroupEmptyException: 
> Topology projection is empty.
>   at 
> org.apache.ignite.internal.util.IgniteUtils$6.apply(IgniteUtils.java:823)
>   at 
> org.apache.ignite.internal.util.IgniteUtils$6.apply(IgniteUtils.java:821)
>   ... 14 more
> Caused by: class 
> org.apache.ignite.internal.cluster.ClusterGroupEmptyCheckedException: 
> Topology projection is empty.
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.getTaskTopology(GridTaskWorker.java:665)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:500)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:758)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:454)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:410)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.sizeAsync(GridCacheAdapter.java:3747)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.size(GridCacheAdapter.java:3704)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.size(IgniteCacheProxyImpl.java:759)
>   ... 11 more
> {noformat}
> Data race stems from here (GridCacheAdapter#sizeAsync):
> {noformat}
> Group grp = modes.near ? cluster.forCacheNodes(name(), true, true, 
> false) : cluster.forDataNodes(name());
> Collection nodes = grp.nodes();
> if (nodes.isEmpty())
> return new GridFinishedFuture<>(0);
> ctx.kernalContext().task().setThreadContext(TC_SUBGRID, nodes);
> return ctx.kernalContext().task().execute(
> new SizeTask(ctx.name(), 
> ctx.affinity().affinityTopologyVersion(), peekModes), null);
> {noformat}
> Method grp.nodes() returns PredicateCollectionView, which size depends on 
> Ignite state. It can pass nodes.isEmpty() check and become empty later.



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

[jira] [Assigned] (IGNITE-6355) Calculating cache size during cache stop sporadically fails with ClusterGroupEmptyCheckedException

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev reassigned IGNITE-6355:
-

Assignee: Alexey Goncharuk  (was: Ivan Rakov)

> Calculating cache size during cache stop sporadically fails with 
> ClusterGroupEmptyCheckedException
> --
>
> Key: IGNITE-6355
> URL: https://issues.apache.org/jira/browse/IGNITE-6355
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Ivan Rakov
>Assignee: Alexey Goncharuk
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> Example stacktrace:
> {noformat}
> [16:21:06,343][ERROR][main][root] Test failed.
> javax.cache.CacheException: class 
> org.apache.ignite.cluster.ClusterGroupEmptyException: Topology projection is 
> empty.
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1327)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1672)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.size(IgniteCacheProxyImpl.java:762)
>   at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.size(GatewayProtectedCacheProxy.java:508)
>   at 
> org.gridgain.grid.internal.processors.cache.database.IgniteDbSnapshotSelfTest.testReuseCacheProxyAfterRestore(IgniteDbSnapshotSelfTest.java:1793)
>   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:2000)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.cluster.ClusterGroupEmptyException: 
> Topology projection is empty.
>   at 
> org.apache.ignite.internal.util.IgniteUtils$6.apply(IgniteUtils.java:823)
>   at 
> org.apache.ignite.internal.util.IgniteUtils$6.apply(IgniteUtils.java:821)
>   ... 14 more
> Caused by: class 
> org.apache.ignite.internal.cluster.ClusterGroupEmptyCheckedException: 
> Topology projection is empty.
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.getTaskTopology(GridTaskWorker.java:665)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:500)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:758)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:454)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:410)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.sizeAsync(GridCacheAdapter.java:3747)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.size(GridCacheAdapter.java:3704)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.size(IgniteCacheProxyImpl.java:759)
>   ... 11 more
> {noformat}
> Data race stems from here (GridCacheAdapter#sizeAsync):
> {noformat}
> Group grp = modes.near ? cluster.forCacheNodes(name(), true, true, 
> false) : cluster.forDataNodes(name());
> Collection nodes = grp.nodes();
> if (nodes.isEmpty())
> return new GridFinishedFuture<>(0);
> ctx.kernalContext().task().setThreadContext(TC_SUBGRID, nodes);
> return ctx.kernalContext().task().execute(
> new SizeTask(ctx.name(), 
> ctx.affinity().affinityTopologyVersion(), peekModes), null);
> {noformat}
> Method grp.nodes() returns PredicateCollectionView, which size depends on 
> Ignite state. It can pass nodes.isEmpty() check and become empty later.



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

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

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-5979:
--

[~javaller]
I still see failures:
https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=6248548165747570497=testDetails_Ignite20Tests=%3Cdefault%3E

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



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

[jira] [Commented] (IGNITE-6396) SQL: Support SQLSTATE error code for "NOT NULL" constraint

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6396:


Github user asfgit closed the pull request at:

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


> SQL: Support SQLSTATE error code for "NOT NULL" constraint
> --
>
> Key: IGNITE-6396
> URL: https://issues.apache.org/jira/browse/IGNITE-6396
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Sergey Kalashnikov
> Fix For: 2.3
>
>
> Respective SQLSTATE: 20004.



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

[jira] [Created] (IGNITE-6419) Thin client: pass user agent string

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-6419:
--

 Summary: Thin client: pass user agent string
 Key: IGNITE-6419
 URL: https://issues.apache.org/jira/browse/IGNITE-6419
 Project: Ignite
  Issue Type: Improvement
  Components: thin client
Reporter: Pavel Tupitsyn


Include a string field in handshake for something like "user agent". Print this 
in the server log.



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

[jira] [Resolved] (IGNITE-6008) CacheRemoveAllSelfTest.testRemoveAll fails sometimes

[Aleksei Zaitsev (JIRA)]

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

Aleksei Zaitsev resolved IGNITE-6008.
-
Resolution: Cannot Reproduce

> CacheRemoveAllSelfTest.testRemoveAll fails sometimes
> 
>
> Key: IGNITE-6008
> URL: https://issues.apache.org/jira/browse/IGNITE-6008
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>Assignee: Aleksei Zaitsev
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> {noformat}
> [2017-08-09 01:18:15,172][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: Local size: 58
> On heap: 58
> Off heap: 58
> Primary: 58
> Backup: 14 expected:<0> but was:<58>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.TestCase.assertEquals(TestCase.java:401)
> at 
> org.apache.ignite.internal.processors.cache.CacheRemoveAllSelfTest.testRemoveAll(CacheRemoveAllSelfTest.java:71)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}



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

[jira] [Comment Edited] (IGNITE-6418) Binary: optionally write integer datatypes with varint encoding

[Mikhail Lipkovich (JIRA)]

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

Mikhail Lipkovich edited comment on IGNITE-6418 at 9/18/17 11:07 AM:
-

Hi Vladimir,
seems like a doable task for a newbie. If there are no objections I would like 
to work on it.
What about reusing this Varint implementation?
https://github.com/apache/mahout/blob/master/hdfs/src/main/java/org/apache/mahout/math/Varint.java

Regarding to annotation - do you mean annotation of classes being marshalled 
themselves? We could create additional {code}BinaryWriteMode{code} for varints 
which will be identified in 
{code}BinaryUtils#mode(cls){code} but the problems is that user will have no 
control over annotation of ignite's internal classes. Or my understanding of 
your suggestion is wrong?


was (Author: mlipkovich):
Hi Vladimir,
seems like a doable task for a newbie. If there are no objections I would like 
to work on it.
What about reusing this Varint implementation?
https://github.com/apache/mahout/blob/master/hdfs/src/main/java/org/apache/mahout/math/Varint.java

Regarding to annotation - do you mean annotation of classes being marshalled 
themselves? We could create additional `BinaryWriteMode` for varints which will 
be identified in `BinaryUtils#mode(cls)` but the problems is that user will 
have no control over annotation of ignite's internal classes. Or my 
understanding of your suggestion is wrong?

> Binary: optionally write integer datatypes with varint encoding
> ---
>
> Key: IGNITE-6418
> URL: https://issues.apache.org/jira/browse/IGNITE-6418
> Project: Ignite
>  Issue Type: Task
>  Components: binary
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>  Labels: iep-2
>
> Currently all integer data types are written as is. {{Integer}} always takes 
> 4 bytes, {{Long}} - 8 bytes, etc.
> There is well-known technique called "varint encoding" which can compress 
> integer values [1]. When used, {{Integer}} can take 1-5 bytes, {{Long}} - 
> 1-10 bytes. So when values are small enough we can save a lot of space. 
> But this technique is not unversal, as big encoded values might require more 
> bytes comparing to plain form. Also it might cause slowdowns in SQL engine. 
> So this approach cannot be applied globally. Instead, we should allow users 
> to control whether they want to use this technique or not.
> One possible approach is to add some annotation and several new methods to 
> {{BinaryWriter}} and {{BinaryReader}}, which will control whether varint is 
> used or not.
> [1] https://developers.google.com/protocol-buffers/docs/encoding#varints



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

[jira] [Comment Edited] (IGNITE-6418) Binary: optionally write integer datatypes with varint encoding

[Mikhail Lipkovich (JIRA)]

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

Mikhail Lipkovich edited comment on IGNITE-6418 at 9/18/17 11:07 AM:
-

Hi Vladimir,
seems like a doable task for a newbie. If there are no objections I would like 
to work on it.
What about reusing this Varint implementation?
https://github.com/apache/mahout/blob/master/hdfs/src/main/java/org/apache/mahout/math/Varint.java

Regarding to annotation - do you mean annotation of classes being marshalled 
themselves? We could create additional {{BinaryWriteMode}} for varints which 
will be identified in 
{{BinaryUtils#mode(cls)}} but the problems is that user will have no control 
over annotation of ignite's internal classes. Or my understanding of your 
suggestion is wrong?


was (Author: mlipkovich):
Hi Vladimir,
seems like a doable task for a newbie. If there are no objections I would like 
to work on it.
What about reusing this Varint implementation?
https://github.com/apache/mahout/blob/master/hdfs/src/main/java/org/apache/mahout/math/Varint.java

Regarding to annotation - do you mean annotation of classes being marshalled 
themselves? We could create additional {code}BinaryWriteMode{code} for varints 
which will be identified in 
{code}BinaryUtils#mode(cls){code} but the problems is that user will have no 
control over annotation of ignite's internal classes. Or my understanding of 
your suggestion is wrong?

> Binary: optionally write integer datatypes with varint encoding
> ---
>
> Key: IGNITE-6418
> URL: https://issues.apache.org/jira/browse/IGNITE-6418
> Project: Ignite
>  Issue Type: Task
>  Components: binary
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>  Labels: iep-2
>
> Currently all integer data types are written as is. {{Integer}} always takes 
> 4 bytes, {{Long}} - 8 bytes, etc.
> There is well-known technique called "varint encoding" which can compress 
> integer values [1]. When used, {{Integer}} can take 1-5 bytes, {{Long}} - 
> 1-10 bytes. So when values are small enough we can save a lot of space. 
> But this technique is not unversal, as big encoded values might require more 
> bytes comparing to plain form. Also it might cause slowdowns in SQL engine. 
> So this approach cannot be applied globally. Instead, we should allow users 
> to control whether they want to use this technique or not.
> One possible approach is to add some annotation and several new methods to 
> {{BinaryWriter}} and {{BinaryReader}}, which will control whether varint is 
> used or not.
> [1] https://developers.google.com/protocol-buffers/docs/encoding#varints



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

[jira] [Commented] (IGNITE-6418) Binary: optionally write integer datatypes with varint encoding

[Mikhail Lipkovich (JIRA)]

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

Mikhail Lipkovich commented on IGNITE-6418:
---

Hi Vladimir,
seems like a doable task for a newbie. If there are no objections I would like 
to work on it.
What about reusing this Varint implementation?
https://github.com/apache/mahout/blob/master/hdfs/src/main/java/org/apache/mahout/math/Varint.java

Regarding to annotation - do you mean annotation of classes being marshalled 
themselves? We could create additional `BinaryWriteMode` for varints which will 
be identified in `BinaryUtils#mode(cls)` but the problems is that user will 
have no control over annotation of ignite's internal classes. Or my 
understanding of your suggestion is wrong?

> Binary: optionally write integer datatypes with varint encoding
> ---
>
> Key: IGNITE-6418
> URL: https://issues.apache.org/jira/browse/IGNITE-6418
> Project: Ignite
>  Issue Type: Task
>  Components: binary
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>  Labels: iep-2
>
> Currently all integer data types are written as is. {{Integer}} always takes 
> 4 bytes, {{Long}} - 8 bytes, etc.
> There is well-known technique called "varint encoding" which can compress 
> integer values [1]. When used, {{Integer}} can take 1-5 bytes, {{Long}} - 
> 1-10 bytes. So when values are small enough we can save a lot of space. 
> But this technique is not unversal, as big encoded values might require more 
> bytes comparing to plain form. Also it might cause slowdowns in SQL engine. 
> So this approach cannot be applied globally. Instead, we should allow users 
> to control whether they want to use this technique or not.
> One possible approach is to add some annotation and several new methods to 
> {{BinaryWriter}} and {{BinaryReader}}, which will control whether varint is 
> used or not.
> [1] https://developers.google.com/protocol-buffers/docs/encoding#varints



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

[jira] [Commented] (IGNITE-5865) TxOptimisticDeadlockDetectionTest.testDeadlocksPartitioned is failing

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-5865:
-

[~VitaliyB] LGTM, but I don't like changes in {{GridCommonAbstractTest}} 
because :

1. {{IncrementalTestObject}} interface actually is needed only for deadlock 
detection tests
2. Generalized {{findKeys}} method supports only {{Integer}} and 
implementations of {{IncrementalTestObject}} interface. It's very strange 
utility method from developer point of view and can confuse.

Could you please revert changes in {{GridCommonAbstractTest}} and implement 
this functionality in package that contains deadlock detection tests?

Thanks.

> TxOptimisticDeadlockDetectionTest.testDeadlocksPartitioned is failing
> -
>
> Key: IGNITE-5865
> URL: https://issues.apache.org/jira/browse/IGNITE-5865
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Pavel Kovalenko
>Assignee: Vitaliy Biryukov
>  Labels: MakeTeamcityGreenAgain, Muted_test, test-failure
> Fix For: 2.3
>
>
> Test is flaky.
> Also there is always failing test in suite: 
> TxOptimisticDeadlockDetectionTest.testDeadlocksPartitionedNear
> TC build result: 
> http://ci.ignite.apache.org/viewLog.html?buildId=744109=buildResultsDiv=Ignite20Tests_IgniteCacheDeadlockDetection
> Stacktrace: 
> {noformat}
> [2017-07-28 
> 03:31:52,827][ERROR][grid-timeout-worker-#31%transactions.TxOptimisticDeadlockDetectionTest0%][IgniteTxHandler]
>  Failed to prepare DHT transaction: GridDhtTxLocal 
> [nearNodeId=d005de76-4378-4cd5-ad7e-f00593a2, 
> nearFutId=aab9f378d51-37ca90c9-03f5-417c-9731-2c29810e3cc0, nearMiniId=1, 
> nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion 
> [topVer=112692678, order=1501212673293, nodeOrder=3], 
> super=GridDhtTxLocalAdapter [nearOnOriginatingNode=false, nearNodes=[], 
> dhtNodes=[], explicitLock=false, super=IgniteTxLocalAdapter 
> [completedBase=null, sndTransformedVals=false, depEnabled=false, 
> txState=IgniteTxStateImpl [activeCacheIds=GridIntList [idx=1, 
> arr=[94416770]], recovery=false, txMap=[IgniteTxEntry 
> [key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=424974513, hash=-1228408719, id=1, name=KeyObject1], 
> cacheId=94416770, txKey=IgniteTxKey 
> [key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=424974513, hash=-1228408719, id=1, name=KeyObject1], 
> cacheId=94416770], val=[op=CREATE, val=CacheObjectImpl [val=null, 
> hasValBytes=true]], prevVal=[op=NOOP, val=null], oldVal=[op=NOOP, val=null], 
> entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1, conflictVer=null, 
> explicitVer=null, dhtVer=null, filters=[], filtersPassed=false, 
> filtersSet=false, entry=GridDhtCacheEntry [rdrs=[], part=694, 
> super=GridDistributedCacheEntry [super=GridCacheMapEntry 
> [key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=16030069, hash=-1228408719, id=1, name=KeyObject1], val=null, 
> startVer=1501212673290, ver=GridCacheVersion [topVer=112692678, 
> order=1501212673290, nodeOrder=1], hash=-1228408719, 
> extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc 
> [locs=[GridCacheMvccCandidate [nodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, 
> ver=GridCacheVersion [topVer=112692678, order=1501212673287, nodeOrder=1], 
> threadId=846, id=520, topVer=AffinityTopologyVersion [topVer=8, 
> minorTopVer=8], reentry=null, 
> otherNodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, otherVer=GridCacheVersion 
> [topVer=112692678, order=1501212673287, nodeOrder=1], mappedDhtNodes=null, 
> mappedNearNodes=null, ownerVer=null, serOrder=null, 
> key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=16030069, hash=-1228408719, id=1, name=KeyObject1], 
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
>  prevVer=null, nextVer=null], GridCacheMvccCandidate 
> [nodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, ver=GridCacheVersion 
> [topVer=112692678, order=1501212673314, nodeOrder=1], threadId=847, id=521, 
> topVer=AffinityTopologyVersion [topVer=8, minorTopVer=8], reentry=null, 
> otherNodeId=d005de76-4378-4cd5-ad7e-f00593a2, otherVer=GridCacheVersion 
> [topVer=112692678, order=1501212673293, nodeOrder=3], mappedDhtNodes=null, 
> mappedNearNodes=null, ownerVer=GridCacheVersion [topVer=112692678, 
> order=1501212673287, nodeOrder=1], serOrder=null, 
> key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=16030069, hash=-1228408719, id=1, name=KeyObject1], 
> 

[jira] [Commented] (IGNITE-6413) Thin client: add tests for ODBC and SQL config conversions

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6413:


Github user asfgit closed the pull request at:

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


> Thin client: add tests for ODBC and SQL config conversions
> --
>
> Key: IGNITE-6413
> URL: https://issues.apache.org/jira/browse/IGNITE-6413
> Project: Ignite
>  Issue Type: Task
>  Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.3
>
>




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

[jira] [Resolved] (IGNITE-6404) Failures in .NET test suite

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-6404.

Resolution: Fixed

> Failures in .NET test suite
> ---
>
> Key: IGNITE-6404
> URL: https://issues.apache.org/jira/browse/IGNITE-6404
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.3
>
>
> A kind of NPE. Affected tests:
> {code}
> ConsoleRedirectTest.TestStartupJavaError  
> ExceptionsTest.TestExceptions 
> ExceptionsTest.TestInvalidSpringUrl   
> LifecycleTest.TestError   
> MarshallerTest.TestInvalidMarshaller 
> CustomLoggerTest.TestStartupDotNetError   
> CustomLoggerTest.TestStartupJavaError 
> {code}



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

[jira] [Updated] (IGNITE-6404) Failures in .NET test suite

[Pavel Tupitsyn (JIRA)]

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

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

> Failures in .NET test suite
> ---
>
> Key: IGNITE-6404
> URL: https://issues.apache.org/jira/browse/IGNITE-6404
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.3
>
>
> A kind of NPE. Affected tests:
> {code}
> ConsoleRedirectTest.TestStartupJavaError  
> ExceptionsTest.TestExceptions 
> ExceptionsTest.TestInvalidSpringUrl   
> LifecycleTest.TestError   
> MarshallerTest.TestInvalidMarshaller 
> CustomLoggerTest.TestStartupDotNetError   
> CustomLoggerTest.TestStartupJavaError 
> {code}



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

[jira] [Commented] (IGNITE-6404) Failures in .NET test suite

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-6404:


Merged to master: {{22002141a1d594556f1b72fa0dd139ab0a1414aa}}

> Failures in .NET test suite
> ---
>
> Key: IGNITE-6404
> URL: https://issues.apache.org/jira/browse/IGNITE-6404
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
> Fix For: 2.3
>
>
> A kind of NPE. Affected tests:
> {code}
> ConsoleRedirectTest.TestStartupJavaError  
> ExceptionsTest.TestExceptions 
> ExceptionsTest.TestInvalidSpringUrl   
> LifecycleTest.TestError   
> MarshallerTest.TestInvalidMarshaller 
> CustomLoggerTest.TestStartupDotNetError   
> CustomLoggerTest.TestStartupJavaError 
> {code}



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

[jira] [Commented] (IGNITE-6317) JDBC thick driver: SQLSTATE error codes

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6317:


GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-6317 JDBC thick driver: SQLSTATE error codes



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

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

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

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


commit 5c0874281e1daecf72dbe7f3eb62221515e5d566
Author: Alexander Paschenko 
Date:   2017-08-28T17:18:29Z

IGNITE-5620 Began sorting out errors.

commit 71c3bb261ad9c80948fc797865dfe3583cee372e
Author: Alexander Paschenko 
Date:   2017-08-29T15:57:34Z

IGNITE-5620 contd

commit 2bb7ca19787d27b1c35ad2a1a9904a6ae0d84944
Author: Alexander Paschenko 
Date:   2017-08-29T15:59:58Z

Merge remote-tracking branch 'apache/master' into ignite-5620

commit 5a909c68e31e6280fde5b0fa7bd9e01aa4b6b0f8
Author: Alexander Paschenko 
Date:   2017-08-29T19:07:04Z

IGNITE-5620 JDBC error tests - started

commit d907d785814b73f353d736895d063158ff1bb578
Author: Alexander Paschenko 
Date:   2017-08-30T16:47:11Z

Thin JDBC - errors

commit d2b1d454aad70ba8f817dc2030df443258024e5d
Author: Alexander Paschenko 
Date:   2017-08-31T14:33:04Z

IGNITE-5620 Errors propagation + tests.

commit e948325a40b9c727e676b9434d0fb4177e5dbb1a
Author: Alexander Paschenko 
Date:   2017-08-31T14:36:06Z

Added tests to suite.

commit 92413cf5bb6643d89da092ff25d2977bef119d73
Author: Alexander Paschenko 
Date:   2017-08-31T14:43:51Z

Merge remote-tracking branch 'apache/master' into ignite-5620

commit 002e747459677f64f3c533db0ca5e69f8ce3e469
Author: devozerov 
Date:   2017-09-05T11:05:41Z

Merge branch 'master' into ignite-5620

commit fae838e6bdeca976f4c12ced4f7f2169ee6bfe26
Author: Alexander Paschenko 
Date:   2017-09-05T11:21:48Z

Merge remote-tracking branch 'apache/master' into ignite-5620

commit e4f630f72f28109020bb2da3b0d21428f0e00e24
Author: Alexander Paschenko 
Date:   2017-09-05T12:12:47Z

Review fixes 1

commit 48982c61bad440efc5b7ae7f2567cc27b87fccda
Author: Alexander Paschenko 
Date:   2017-09-05T13:07:06Z

Merge remote-tracking branch 'origin/ignite-5620' into ignite-5620

commit 99cdffc19f938e99444085ab81fb8b4859a573b6
Author: Alexander Paschenko 
Date:   2017-09-06T13:04:36Z

Merge remote-tracking branch 'apache/master' into ignite-5620

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/odbc/SqlListenerNioListener.java

commit db493b11d2c1bb2a8cfc6d2908a5bee77a44fd75
Author: Alexander Paschenko 
Date:   2017-09-06T15:20:42Z

Merge remote-tracking branch 'apache/master' into ignite-5620

commit 8376518edaa050e4fce89080948e42bd9cec2b74
Author: Alexander Paschenko 
Date:   2017-09-06T17:45:42Z

Fixes

commit 60792ae572575734f2f0676b52d9263e3e416628
Author: Alexander Paschenko 
Date:   2017-09-07T09:26:14Z

Merge remote-tracking branch 'apache/master' into ignite-5620

commit 11c9b947cfd0e5421146606340f809496412c3d3
Author: Alexander Paschenko 
Date:   2017-09-07T20:34:47Z

IGNITE-5620 review fixes

commit bb015909b8ec12786221ddd922c4bc9d287c030f
Author: Alexander Paschenko 
Date:   2017-09-08T10:11:36Z

Merge remote-tracking branch 'apache/master' into ignite-5620

commit 5070e91d77ca1849fc7e9eaf5caf0e12af1fdc57
Author: Alexander Paschenko 
Date:   2017-09-08T12:33:35Z

IGNITE-5620 tests

commit 8649f91ba90ed161318865320d225eb53ab45b71
Author: Alexander Paschenko 
Date:   2017-09-11T11:43:50Z

Merge remote-tracking branch 'apache/master' into ignite-5620

commit 37db2767fbd7f01cbc958973e0cdfc69206d3ab0
Author: Alexander Paschenko 
Date:   2017-09-11T18:18:44Z

Review fixes - 1.

commit 3b0ebc3c8afe2871622fcb97d2b18b6bfb639bff
Author: Alexander Paschenko 
Date:   2017-09-12T10:31:49Z

Merge 

[jira] [Commented] (IGNITE-6396) SQL: Support SQLSTATE error code for "NOT NULL" constraint

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov commented on IGNITE-6396:


Correct code is 22004 and it is already provided in the error for NOT NULL 
case. Thus, I only added a test {{JdbcErrorsSelfTest.testNotNullViolation}}.

> SQL: Support SQLSTATE error code for "NOT NULL" constraint
> --
>
> Key: IGNITE-6396
> URL: https://issues.apache.org/jira/browse/IGNITE-6396
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Sergey Kalashnikov
> Fix For: 2.3
>
>
> Respective SQLSTATE: 20004.



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

[jira] [Created] (IGNITE-6418) Binary: optionally write integer datatypes with varint encoding

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6418:
---

 Summary: Binary: optionally write integer datatypes with varint 
encoding
 Key: IGNITE-6418
 URL: https://issues.apache.org/jira/browse/IGNITE-6418
 Project: Ignite
  Issue Type: Task
  Components: binary
Affects Versions: 2.1
Reporter: Vladimir Ozerov


Currently all integer data types are written as is. {{Integer}} always takes 4 
bytes, {{Long}} - 8 bytes, etc.

There is well-known technique called "varint encoding" which can compress 
integer values [1]. When used, {{Integer}} can take 1-5 bytes, {{Long}} - 1-10 
bytes. So when values are small enough we can save a lot of space. 

But this technique is not unversal, as big encoded values might require more 
bytes comparing to plain form. Also it might cause slowdowns in SQL engine. So 
this approach cannot be applied globally. Instead, we should allow users to 
control whether they want to use this technique or not.

One possible approach is to add some annotation and several new methods to 
{{BinaryWriter}} and {{BinaryReader}}, which will control whether varint is 
used or not.

[1] https://developers.google.com/protocol-buffers/docs/encoding#varints



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

[jira] [Updated] (IGNITE-6418) Binary: optionally write integer datatypes with varint encoding

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6418:

Labels: iep-2  (was: )

> Binary: optionally write integer datatypes with varint encoding
> ---
>
> Key: IGNITE-6418
> URL: https://issues.apache.org/jira/browse/IGNITE-6418
> Project: Ignite
>  Issue Type: Task
>  Components: binary
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>  Labels: iep-2
>
> Currently all integer data types are written as is. {{Integer}} always takes 
> 4 bytes, {{Long}} - 8 bytes, etc.
> There is well-known technique called "varint encoding" which can compress 
> integer values [1]. When used, {{Integer}} can take 1-5 bytes, {{Long}} - 
> 1-10 bytes. So when values are small enough we can save a lot of space. 
> But this technique is not unversal, as big encoded values might require more 
> bytes comparing to plain form. Also it might cause slowdowns in SQL engine. 
> So this approach cannot be applied globally. Instead, we should allow users 
> to control whether they want to use this technique or not.
> One possible approach is to add some annotation and several new methods to 
> {{BinaryWriter}} and {{BinaryReader}}, which will control whether varint is 
> used or not.
> [1] https://developers.google.com/protocol-buffers/docs/encoding#varints



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

[jira] [Commented] (IGNITE-6396) SQL: Support SQLSTATE error code for "NOT NULL" constraint

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6396:


GitHub user skalashnikov opened a pull request:

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

IGNITE-6396: Added test for SQL state error code for NOT NULL violation



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

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

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

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


commit 01a39a396574678c4199f7711757c7cea9220b07
Author: skalashnikov 
Date:   2017-09-18T09:23:36Z

IGNITE-6396: Added test for error code for NOT NULL violation




> SQL: Support SQLSTATE error code for "NOT NULL" constraint
> --
>
> Key: IGNITE-6396
> URL: https://issues.apache.org/jira/browse/IGNITE-6396
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Sergey Kalashnikov
> Fix For: 2.3
>
>
> Respective SQLSTATE: 20004.



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

[jira] [Updated] (IGNITE-6128) Binary: offsets might be skipped for constant-length fields

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6128:

Labels: iep-2 performance  (was: performance)

> Binary: offsets might be skipped for constant-length fields
> ---
>
> Key: IGNITE-6128
> URL: https://issues.apache.org/jira/browse/IGNITE-6128
> Project: Ignite
>  Issue Type: Task
>  Components: binary
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>  Labels: iep-2, performance
> Fix For: 2.3
>
>
> Currently we write offsets for every field. It could take 1, 2 or 4 bytes 
> depending on the data length of the object. Now suppose we have the following 
> class:
> {code}
> class MyClass {
> int a;
> String c;
> long b;
> int d;
> int e;
> }
> {code}
> Fields are always sorted in alphabetical order, so we will write them as 
> follows {{[a, b, c, d, e]}}, and their offsets would always be {{[0, 5, 14, 
> X, X+5]}}. As you see, instead of writing 5 offsets, it is enough to write 
> only one offset of a field, which follows another variable-length field. The 
> rest offsets could be saved to metadata.



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

[jira] [Updated] (IGNITE-2894) Binary object inside of Externalizable still serialized with OptimizedMarshaller

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2894:

Component/s: (was: general)
 binary

> Binary object inside of Externalizable still serialized with 
> OptimizedMarshaller
> 
>
> Key: IGNITE-2894
> URL: https://issues.apache.org/jira/browse/IGNITE-2894
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Amelchev Nikita
>Priority: Critical
>  Labels: community, customer, iep-2
> Fix For: 2.3
>
>
> When binary marshaller meets an Externalizable object, it switches to 
> optimized marshaller. And if there is a regular object inside, it's still 
> serialized with optimized, even if its type is declared in binary 
> configuration with custom mapper, etc.
> Essentially, binary marshaller should fully support Java serialization, 
> including {{Externalizable}} and {{writeObject}}/{{readObject}}.



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

[jira] [Updated] (IGNITE-5097) BinaryMarshaller should write ints in "varint" encoding where it makes sense

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5097:

Component/s: (was: general)
 binary

> BinaryMarshaller should write ints in "varint" encoding where it makes sense
> 
>
> Key: IGNITE-5097
> URL: https://issues.apache.org/jira/browse/IGNITE-5097
> Project: Ignite
>  Issue Type: Task
>  Components: binary
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Daradur
>  Labels: iep-2, performance
> Fix For: 2.3
>
>
> There are a lot of places in the code where we write integers for some 
> special purposes. Quite often their value will be vary small, so that 
> applying "varint" format could save a lot of space at the cost of very low 
> additional CPU overhead. 
> Specifically:
> 1) Array/collection/map lengths
> 2) BigDecimal's (usually will save ~6 bytes)
> 3) Strings
> 4) Enum ordinals



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

[jira] [Updated] (IGNITE-2894) Binary object inside of Externalizable still serialized with OptimizedMarshaller

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2894:

Labels: community customer iep-2  (was: community customer)

> Binary object inside of Externalizable still serialized with 
> OptimizedMarshaller
> 
>
> Key: IGNITE-2894
> URL: https://issues.apache.org/jira/browse/IGNITE-2894
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Amelchev Nikita
>Priority: Critical
>  Labels: community, customer, iep-2
> Fix For: 2.3
>
>
> When binary marshaller meets an Externalizable object, it switches to 
> optimized marshaller. And if there is a regular object inside, it's still 
> serialized with optimized, even if its type is declared in binary 
> configuration with custom mapper, etc.
> Essentially, binary marshaller should fully support Java serialization, 
> including {{Externalizable}} and {{writeObject}}/{{readObject}}.



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

[jira] [Updated] (IGNITE-5097) BinaryMarshaller should write ints in "varint" encoding where it makes sense

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5097:

Labels: iep-2 performance  (was: important performance)

> BinaryMarshaller should write ints in "varint" encoding where it makes sense
> 
>
> Key: IGNITE-5097
> URL: https://issues.apache.org/jira/browse/IGNITE-5097
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Daradur
>  Labels: iep-2, performance
> Fix For: 2.3
>
>
> There are a lot of places in the code where we write integers for some 
> special purposes. Quite often their value will be vary small, so that 
> applying "varint" format could save a lot of space at the cost of very low 
> additional CPU overhead. 
> Specifically:
> 1) Array/collection/map lengths
> 2) BigDecimal's (usually will save ~6 bytes)
> 3) Strings
> 4) Enum ordinals



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

[jira] [Updated] (IGNITE-3939) Compact long zero values binary representation

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3939:

Labels: iep-2 performance  (was: important performance)

> Compact long zero values binary representation
> --
>
> Key: IGNITE-3939
> URL: https://issues.apache.org/jira/browse/IGNITE-3939
> Project: Ignite
>  Issue Type: Improvement
>  Components: binary
>Affects Versions: 1.7
>Reporter: Andrew Mashenkov
>Assignee: Taras Ledkov
>  Labels: iep-2, performance
> Fix For: 2.3
>
>
> We can use separate type for Long zero values and exclude 8-byte value from 
> binary representation. This will reduce memory footprint and network load.
> Compatibility with previous versions MUST be preserved.



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

[jira] [Updated] (IGNITE-5655) Introduce pluggable string encoder/decoder

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5655:

Labels: iep-2  (was: )

> Introduce pluggable string encoder/decoder
> --
>
> Key: IGNITE-5655
> URL: https://issues.apache.org/jira/browse/IGNITE-5655
> Project: Ignite
>  Issue Type: New Feature
>  Components: binary
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
>Assignee: Andrey Kuznetsov
>  Labels: iep-2
> Fix For: 2.3
>
>
> Currently binary marshaller encodes strings in UTF-8. However, sometimes it 
> makes sense to serialize strings with different encodings to save space. 
> Let's add global property to control String encoding and customize our binary 
> protocol to support it. For instance, we can add another flag 
> {{ENCODED_STRING}}, which will write strings as follows:
> [flag][encoding_flag][str_len][str_bytes]
> First implementation should set preferred encoding for strings in 
> BinaryConfiguration. This setting is optional, default encoding is UTF-8. 
> Currently, the same BinaryConfiguration is used for all cluster nodes, thus 
> no encoding clashes are possible.



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