[jira] [Updated] (IGNITE-5926) Puts on near cache hangs

[Dmitriy Setrakyan (JIRA)]

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

Dmitriy Setrakyan updated IGNITE-5926:
--
Fix Version/s: 2.2

> Puts on near cache hangs
> 
>
> Key: IGNITE-5926
> URL: https://issues.apache.org/jira/browse/IGNITE-5926
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0, 2.1
>Reporter: vinay
> Fix For: 2.2
>
> Attachments: IgniteNearCacheProblem.java
>
>
> Cache puts on near cache on client node hangs after putting same number of 
> keys (if keys and values are same during test). Most probably problem occurs 
> when cache on server reaches max memory and starts page eviction. *Attaching 
> java class with main method to reproduce problem*. If near cache is not used 
> then the same test works fine.
> Steps to reproduce
> # Start a server node with one memory region with max size 100 MB. Page 
> Evction Strategy as RANDOM_LRU. Set this memory region as default. Create a 
> REPLICATED cache as part of server's IgniteConfiguration.
> # Start a client node and create a near cache for the cache created on 
> server. Keep near cache init size and max size 1000 with eviction policy LRU.
> # Start a infinite while loop to put objects in near cache.



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

[jira] [Commented] (IGNITE-5897) Ignite Cache Full API Multi JVM: 7 test failed in master

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-5897:


https://ci.ignite.apache.org/viewLog.html?buildId=755007=buildResultsDiv=Ignite20Tests_RunAll

> Ignite Cache Full API Multi JVM: 7 test failed in master
> 
>
> Key: IGNITE-5897
> URL: https://issues.apache.org/jira/browse/IGNITE-5897
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Dmitriy Pavlov
>Assignee: Nikolay Izhikov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Failure on TC: 
> http://ci.ignite.apache.org/viewLog.html?buildId=749671=buildResultsDiv=Ignite20Tests_IgniteCacheFullApiMultiJvm#testNameId-6305397409161667157
> org.apache.ignite.internal.processors.cache.multijvm (7)
> - 
> GridCachePartitionedNearDisabledMultiJvmFullApiSelfTest.testTransformResourceInjection
>   
> - 
> GridCachePartitionedNearDisabledMultiJvmP2PDisabledFullApiSelfTest.testTransformResourceInjection
>
> - 
> GridCachePartitionedNearDisabledOnheapMultiJvmFullApiSelfTest.testTransformResourceInjection
> 
> - GridCacheReplicatedMultiJvmFullApiSelfTest.testTransformResourceInjection   
> - 
> GridCacheReplicatedMultiJvmP2PDisabledFullApiSelfTest.testTransformResourceInjection
> 
> - 
> GridCacheReplicatedNearOnlyMultiJvmFullApiSelfTest.testTransformResourceInjection
>
> - 
> GridCacheReplicatedOnheapMultiJvmFullApiSelfTest.testTransformResourceInjection
>  
> Stable reproducible locally
> First failure changes:
> http://ci.ignite.apache.org/viewLog.html?buildId=727280=buildChangesDiv=Ignite20Tests_IgniteCacheFullApiMultiJvm
> {noformat}
> IGNITE-5753: CPP Memory leak fixed.   Igor Sapego 
> IGNITE-5444: Collections.singletonList is not properly serialized by binary 
> marshaller. This closes #2217.andrey.mashenkov 
> ignite-5722 Cache entries stay in onheap after scan query execution for 
> OFFHEAP_TIRED cache with expiry policyAndrey Gura 
> ignite-5489 Fixed possible connection leaks when loadPreviousValue set to 
> truetikhonovnicolay 
> IGNITE-4831: Add an option to disable MBeans. This closes #2265.  
> andrey.mashenkov   
> {noformat}
> Stacktrace: 
> {noformat}
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea] class 
> org.apache.ignite.IgniteCheckedException: java.lang.NullPointerException
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadFromStore(GridCacheStoreManagerAdapter.java:327)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.load(GridCacheStoreManagerAdapter.java:282)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.readThrough(GridCacheMapEntry.java:445)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerGet0(GridCacheMapEntry.java:699)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerGet(GridCacheMapEntry.java:461)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.onEntriesLocked(GridDhtTxPrepareFuture.java:389)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare0(GridDhtTxPrepareFuture.java:1213)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.mapIfLocked(GridDhtTxPrepareFuture.java:668)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare(GridDhtTxPrepareFuture.java:1034)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.prepareAsync(GridDhtTxLocal.java:410)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareNearTx(IgniteTxHandler.java:459)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest(IgniteTxHandler.java:121)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> 

[jira] [Commented] (IGNITE-5927) .NET: DataTable can't be serialized

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5927:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-5927 .NET: Fix DataTable serialization



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

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

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

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






> .NET: DataTable can't be serialized
> ---
>
> Key: IGNITE-5927
> URL: https://issues.apache.org/jira/browse/IGNITE-5927
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.2
>
>
> {{System.Data.DataTable}} can't be serialized:
> {code}
> cache.Put(1, new DataTable());
> {code}
> results in exception:
> {code}
> System.InvalidCastException: Unable to cast object of type 
> 'Apache.Ignite.Core.Impl.Binary.BinaryWriter' to type 'System.IConvertible'.
>at System.Convert.ToBoolean(Object value, IFormatProvider provider)
>at System.Data.DataTable.GetObjectData(SerializationInfo info, 
> StreamingContext context)
>at Apache.Ignite.Core.Impl.Binary.SerializableSerializer.WriteBinary[T](T 
> obj, BinaryWriter writer) in 
> S:\W\incubator-ignite\modules\platforms\dotnet\Apache.Ignite.Core\Impl\Binary\SerializableSerializer.cs:line
>  64
>at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj) in 
> S:\W\incubator-ignite\modules\platforms\dotnet\Apache.Ignite.Core\Impl\Binary\BinaryWriter.cs:line
>  1224
>at Apache.Ignite.Core.Impl.Binary.Marshaller.Marshal[T](T val, 
> IBinaryStream stream) in 
> S:\W\incubator-ignite\modules\platforms\dotnet\Apache.Ignite.Core\Impl\Binary\Marshaller.cs:line
>  159
>at Apache.Ignite.Core.Impl.Binary.Marshaller.Marshal[T](T val) in 
> S:\W\incubator-ignite\modules\platforms\dotnet\Apache.Ignite.Core\Impl\Binary\Marshaller.cs:line
>  144
> {code}
> StackOverflow question: 
> https://stackoverflow.com/questions/45490249/how-to-store-datatable-in-apache-ignite



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

[jira] [Updated] (IGNITE-3084) Spark Data Frames Support in Apache Ignite

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-3084:

Labels: bigdata  (was: bigdata gsoc2017)

> Spark Data Frames Support in Apache Ignite
> --
>
> Key: IGNITE-3084
> URL: https://issues.apache.org/jira/browse/IGNITE-3084
> Project: Ignite
>  Issue Type: Task
>  Components: spark
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Valentin Kulichenko
>  Labels: bigdata
> Fix For: 2.2
>
>
> Apache Spark already benefits from integration with Apache Ignite. The latter 
> provides shared RDDs, an implementation of Spark RDD, that help Spark to 
> share a state between Spark workers and execute SQL queries much faster. The 
> next logical step is to enable support for modern Spark Data Frames API in a 
> similar way.
> As a contributor, you will be fully in charge of the integration of Spark 
> Data Frame API and Apache Ignite.



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

[jira] [Commented] (IGNITE-5927) .NET: DataTable can't be serialized

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5927:


I've reproduced the issue, and I would say that this is a bug in 
{{System.Data.DataTable}}. Here is the code:

{code}
public virtual void GetObjectData(SerializationInfo info, StreamingContext 
context) {
SerializationFormat remotingFormat = RemotingFormat;
bool isSingleTable = context.Context != null ? 
Convert.ToBoolean(context.Context, CultureInfo.InvariantCulture) : true;
SerializeDataTable(info, context, isSingleTable, remotingFormat);
}
{code}

Exception comes from {{Convert.ToBoolean(context.Context, 
CultureInfo.InvariantCulture)}}

The assumption that {{Context}} can be converted to bool does not look correct, 
see MSDN https://msdn.microsoft.com/en-us/library/h58hxyt6(v=vs.110).aspx:

{code}additional: Any additional information to be associated with the 
StreamingContext.{code}

Anyway, .NET framework is not going to be fixed, so we have to get rid of 
{{BinaryWriter}} in that context. 

> .NET: DataTable can't be serialized
> ---
>
> Key: IGNITE-5927
> URL: https://issues.apache.org/jira/browse/IGNITE-5927
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.2
>
>
> {{System.Data.DataTable}} can't be serialized:
> {code}
> cache.Put(1, new DataTable());
> {code}
> results in exception:
> {code}
> System.InvalidCastException: Unable to cast object of type 
> 'Apache.Ignite.Core.Impl.Binary.BinaryWriter' to type 'System.IConvertible'.
>at System.Convert.ToBoolean(Object value, IFormatProvider provider)
>at System.Data.DataTable.GetObjectData(SerializationInfo info, 
> StreamingContext context)
>at Apache.Ignite.Core.Impl.Binary.SerializableSerializer.WriteBinary[T](T 
> obj, BinaryWriter writer) in 
> S:\W\incubator-ignite\modules\platforms\dotnet\Apache.Ignite.Core\Impl\Binary\SerializableSerializer.cs:line
>  64
>at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj) in 
> S:\W\incubator-ignite\modules\platforms\dotnet\Apache.Ignite.Core\Impl\Binary\BinaryWriter.cs:line
>  1224
>at Apache.Ignite.Core.Impl.Binary.Marshaller.Marshal[T](T val, 
> IBinaryStream stream) in 
> S:\W\incubator-ignite\modules\platforms\dotnet\Apache.Ignite.Core\Impl\Binary\Marshaller.cs:line
>  159
>at Apache.Ignite.Core.Impl.Binary.Marshaller.Marshal[T](T val) in 
> S:\W\incubator-ignite\modules\platforms\dotnet\Apache.Ignite.Core\Impl\Binary\Marshaller.cs:line
>  144
> {code}
> StackOverflow question: 
> https://stackoverflow.com/questions/45490249/how-to-store-datatable-in-apache-ignite



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

[jira] [Updated] (IGNITE-5926) Puts on near cache hangs

[vinay (JIRA)]

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

vinay updated IGNITE-5926:
--
Description: 
Cache puts on near cache on client node hangs after putting same number of keys 
(if keys and values are same during test). Most probably problem occurs when 
cache on server reaches max memory and starts page eviction. *Attaching java 
class with main method to reproduce problem*. If near cache is not used then 
the same test works fine.



Steps to reproduce
# Start a server node with one memory region with max size 100 MB. Page Evction 
Strategy as RANDOM_LRU. Set this memory region as default. Create a REPLICATED 
cache as part of server's IgniteConfiguration.
# Start a client node and create a near cache for the cache created on server. 
Keep near cache init size and max size 1000 with eviction policy LRU.
# Start a infinite while loop to put objects in near cache.

  was:
Cache puts on near cache on client node hangs after putting same number of keys 
(if keys and values are same during test). Most probably problem occurs when 
cache on server reaches max memory and starts page eviction. Attaching java 
class with main method to reproduce problem. If near cache is not used the the 
same test works fine.



Steps to reproduce
# Start a server node with one memory region with max size 100 MB. Page Evction 
Strategy as RANDOM_LRU. Set this memory region as default. Create a REPLICATED 
cache as part of server's IgniteConfiguration.
# Start a client node and create a near cache for the cache created on server. 
Keep near cache init size and max size 1000 with eviction policy LRU.
# Start a infinite while loop to put objects in near cache.


> Puts on near cache hangs
> 
>
> Key: IGNITE-5926
> URL: https://issues.apache.org/jira/browse/IGNITE-5926
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0, 2.1
>Reporter: vinay
> Attachments: IgniteNearCacheProblem.java
>
>
> Cache puts on near cache on client node hangs after putting same number of 
> keys (if keys and values are same during test). Most probably problem occurs 
> when cache on server reaches max memory and starts page eviction. *Attaching 
> java class with main method to reproduce problem*. If near cache is not used 
> then the same test works fine.
> Steps to reproduce
> # Start a server node with one memory region with max size 100 MB. Page 
> Evction Strategy as RANDOM_LRU. Set this memory region as default. Create a 
> REPLICATED cache as part of server's IgniteConfiguration.
> # Start a client node and create a near cache for the cache created on 
> server. Keep near cache init size and max size 1000 with eviction policy LRU.
> # Start a infinite while loop to put objects in near cache.



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

[jira] [Updated] (IGNITE-5926) Puts on near cache hangs

[vinay (JIRA)]

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

vinay updated IGNITE-5926:
--
Attachment: IgniteNearCacheProblem.java

> Puts on near cache hangs
> 
>
> Key: IGNITE-5926
> URL: https://issues.apache.org/jira/browse/IGNITE-5926
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0, 2.1
>Reporter: vinay
> Attachments: IgniteNearCacheProblem.java
>
>
> Cache puts on near cache on client node hangs after putting same number of 
> keys (if keys and values are same during test). Most probably problem occurs 
> when cache on server reaches max memory and starts page eviction. Attaching 
> java class with main method to reproduce problem. If near cache is not used 
> the the same test works fine.
> Steps to reproduce
> # Start a server node with one memory region with max size 100 MB. Page 
> Evction Strategy as RANDOM_LRU. Set this memory region as default. Create a 
> REPLICATED cache as part of server's IgniteConfiguration.
> # Start a client node and create a near cache for the cache created on 
> server. Keep near cache init size and max size 1000 with eviction policy LRU.
> # Start a infinite while loop to put objects in near cache.



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

[jira] [Created] (IGNITE-5926) Puts on near cache hangs

[vinay (JIRA)]

vinay created IGNITE-5926:
-

 Summary: Puts on near cache hangs
 Key: IGNITE-5926
 URL: https://issues.apache.org/jira/browse/IGNITE-5926
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1, 2.0
Reporter: vinay


Cache puts on near cache on client node hangs after putting same number of keys 
(if keys and values are same during test). Most probably problem occurs when 
cache on server reaches max memory and starts page eviction. Attaching java 
class with main method to reproduce problem. If near cache is not used the the 
same test works fine.



Steps to reproduce
# Start a server node with one memory region with max size 100 MB. Page Evction 
Strategy as RANDOM_LRU. Set this memory region as default. Create a REPLICATED 
cache as part of server's IgniteConfiguration.
# Start a client node and create a near cache for the cache created on server. 
Keep near cache init size and max size 1000 with eviction policy LRU.
# Start a infinite while loop to put objects in near cache.



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

[jira] [Commented] (IGNITE-5880) BLAS integration phase 2

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5880:


GitHub user ybabak opened a pull request:

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

IGNITE-5880: BLAS integration phase 2



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

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

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

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


commit e7d7684b0551b36f47a356feab577c89685df35a
Author: Yury Babak 
Date:   2017-08-02T23:44:03Z

IGNITE-5880: BLAS integration phase 2
wip

commit b8438aa3d36f513820142f5e00058c7572e8e22f
Author: Yury Babak 
Date:   2017-08-02T23:44:03Z

IGNITE-5880: BLAS integration phase 2
- fixed some failed tests.

commit ee8c3c4cc91f2c6c6087ab7bedd13fd07700a514
Author: Yury Babak 
Date:   2017-08-03T17:29:55Z

Merge remote-tracking branch 'professional/ignite-5880' into ignite-5880

# Conflicts:
#   
modules/ml/src/main/java/org/apache/ignite/ml/math/impls/storage/vector/MatrixVectorStorage.java




> BLAS integration phase 2
> 
>
> Key: IGNITE-5880
> URL: https://issues.apache.org/jira/browse/IGNITE-5880
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Reporter: Yury Babak
>Assignee: Yury Babak
> Fix For: 2.2
>
>
> The second phase of BLAS integration.



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

[jira] [Created] (IGNITE-5925) Get row/col for matrices

[Yury Babak (JIRA)]

Yury Babak created IGNITE-5925:
--

 Summary: Get row/col for matrices
 Key: IGNITE-5925
 URL: https://issues.apache.org/jira/browse/IGNITE-5925
 Project: Ignite
  Issue Type: Improvement
  Components: ml
Reporter: Yury Babak
 Fix For: 2.2


It should be useful to have this api for any matrix especially in BLAS and 
decompositions.



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

[jira] [Commented] (IGNITE-5738) Add support of batch requests for jdbc2

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5738:


GitHub user skalashnikov opened a pull request:

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

IGNITE-5738: SQL: Added support for batching for jdbc2 driver



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

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

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

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


commit 986026be8ca55af05dd4a24da7a510a33dd476c0
Author: skalashnikov 
Date:   2017-07-28T14:33:51Z

IGNITE-5738: WIP (ported changes made by AlexP)

commit ba6a4b08267468c156892c0b31814c352347fbd7
Author: skalashnikov 
Date:   2017-08-01T08:59:27Z

Merge branch 'master' of https://github.com/apache/ignite into ignite-5738

commit 89df4085552fdf5fc85a74b1255609408a13fce6
Author: skalashnikov 
Date:   2017-08-03T15:41:05Z

IGNITE-5738: Added support for statement batching

commit 1ae9c481b239eb72ba325c1b4e66f9edcfefad34
Author: skalashnikov 
Date:   2017-08-03T15:42:29Z

Merge branch 'master' of https://github.com/apache/ignite into ignite-5738

commit e22d4bcc9f266ebce97ec787b8d8d67ecc44d583
Author: skalashnikov 
Date:   2017-08-03T15:50:44Z

IGNITE-5738: cleanup




> Add support of batch requests for jdbc2
> ---
>
> Key: IGNITE-5738
> URL: https://issues.apache.org/jira/browse/IGNITE-5738
> Project: Ignite
>  Issue Type: New Feature
>  Components: jdbc
>Reporter: Evgenii Zhuravlev
>Assignee: Sergey Kalashnikov
> Fix For: 2.2
>
>




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

[jira] [Created] (IGNITE-5924) .NET: Decouple Marshaller from Ignite

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5924:
--

 Summary: .NET: Decouple Marshaller from Ignite
 Key: IGNITE-5924
 URL: https://issues.apache.org/jira/browse/IGNITE-5924
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.2


{{Marshaller}} class has {{Ignite}} property, which is used everywhere as a 
convenient accessor.
With thin client we don't have an {{Ignite}} instance ({{IgniteClient}} is 
there instead). 
Also, {{Marshaller}} itself only needs {{Ignite.BinaryProcessor}}, which is 
also tied to JNI.

So the plan is:
* Add {{IBinaryProcessor}} interface
* Replace {{Marshaller.Ignite}} with {{Marshaller.BinaryProcessor}}
* Fix external {{Marshaller.Ignite}} usages in some way



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

[jira] [Commented] (IGNITE-5813) Inconsistent cache store state when originating node fails on commit.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov commented on IGNITE-5813:
--

[~sboikov],

Would you please look at PR. 2.x code is much differs and I'm not sure this is 
complete fix.
However, TC test looks fine.

> Inconsistent cache store state when originating node fails on commit.
> -
>
> Key: IGNITE-5813
> URL: https://issues.apache.org/jira/browse/IGNITE-5813
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 2.2
>
> Attachments: IgniteTxRecoveryAfterStoreCommitSelfTest.java
>
>
> Same tx can be rolled back by cache and commited by CacheStore.
> It is possible when originating tx node commit tx successfully, but fails to 
> notify other nodes. 
> PFA reproducer.



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

[jira] [Commented] (IGNITE-5813) Inconsistent cache store state when originating node fails on commit.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov commented on IGNITE-5813:
--

In 1.x versions tx salvage looks like this:
tx.prepare -> tx.invalidate -> tx.commit 
and with store configured tx manager RELOAD value on commit what was changed in 
tx.

In 2.0 tx salvage is just tx.rollback with no concern of consistency with store.

> Inconsistent cache store state when originating node fails on commit.
> -
>
> Key: IGNITE-5813
> URL: https://issues.apache.org/jira/browse/IGNITE-5813
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 2.2
>
> Attachments: IgniteTxRecoveryAfterStoreCommitSelfTest.java
>
>
> Same tx can be rolled back by cache and commited by CacheStore.
> It is possible when originating tx node commit tx successfully, but fails to 
> notify other nodes. 
> PFA reproducer.



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

[jira] [Commented] (IGNITE-5842) ODBC: Make sure ODBC driver works correctly with RazorSQL.

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-5842:
-

Found an issue - IGNITE-5923

> ODBC: Make sure ODBC driver works correctly with RazorSQL.
> --
>
> Key: IGNITE-5842
> URL: https://issues.apache.org/jira/browse/IGNITE-5842
> Project: Ignite
>  Issue Type: Improvement
>  Components: odbc
>Affects Versions: 2.0
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: odbc
> Fix For: 2.2
>
>
> Users often try to use ODBC driver to connect to Ignite with RazorSQL. 
> However, it can't be used with our driver, as it tries to configure driver to 
> act according to unsupported ODBC version. Here is the log:
> {noformat}
> razorsql12d8-1374 ENTER SQLAllocEnv 
>   HENV *  0x2FBEECB0
> razorsql12d8-1374 EXIT  SQLAllocEnv  with return code 0 
> (SQL_SUCCESS)
>   HENV *  0x2FBEECB0 ( 0x003DE650)
> razorsql12d8-1374 ENTER SQLAllocConnect 
>   HENV0x003DE650
>   HDBC *  0x2FBEEC10
> razorsql12d8-1374 EXIT  SQLAllocConnect  with return code 0 
> (SQL_SUCCESS)
>   HENV0x003DE650
>   HDBC *  0x2FBEEC10 ( 0x003DE6D0)
> razorsql12d8-1374 ENTER SQLSetConnectOption 
>   HDBC0x003DE6D0
>   SQLINTEGER 103 
>   SQLPOINTER35
> razorsql12d8-1374 EXIT  SQLSetConnectOption  with return code 0 
> (SQL_SUCCESS)
>   HDBC0x003DE6D0
>   SQLINTEGER 103 
>   SQLPOINTER35
> razorsql12d8-1374 ENTER SQLDriverConnectW 
>   HDBC0x003DE6D0
>   HWND0x
>   WCHAR * 0x6F861F7C [  -3] "**\ 0"
>   SWORD   -3 
>   WCHAR * 0x6F861F7C 
>   SWORD   -3 
>   SWORD * 0x
>   UWORD0 
> razorsql12d8-1374 EXIT  SQLDriverConnectW  with return code -1 
> (SQL_ERROR)
>   HDBC0x003DE6D0
>   HWND0x
>   WCHAR * 0x6F861F7C [  -3] "**\ 0"
>   SWORD   -3 
>   WCHAR * 0x6F861F7C 
>   SWORD   -3 
>   SWORD * 0x
>   UWORD0 
>   DIAG [S1000] ODBC version is not supported. (0) 
>   DIAG [08001] Failed to establish connection with the host. (0) 
> razorsql12d8-1374 ENTER SQLErrorW 
>   HENV0x
>   HDBC0x003DE6D0
>   HSTMT   0x
>   WCHAR * 0x2FBEEAF4
>   SDWORD *0x2FBEEB3C
>   WCHAR * 0x2FBEE6F4 
>   SWORD  300 
>   SWORD * 0x2FBEEB38
> razorsql12d8-1374 EXIT  SQLErrorW  with return code 0 
> (SQL_SUCCESS)
>   HENV0x
>   HDBC0x003DE6D0
>   HSTMT   0x
>   WCHAR * 0x2FBEEAF4 [   5] "S1000"
>   SDWORD *0x2FBEEB3C (0)
>   WCHAR * 0x2FBEE6F4 [  30] "ODBC version is not 
> supported."
>   SWORD  300 
>   SWORD * 0x2FBEEB38 (30)
> razorsql12d8-1374 ENTER SQLErrorW 
>   HENV0x
>   HDBC0x003DE6D0
>   HSTMT   0x
>   WCHAR * 0x2FBEEAF4
>   SDWORD *0x2FBEEB3C
>   WCHAR * 0x2FBEE6F4 
>   SWORD  300 
>   SWORD * 0x2FBEEB38
> razorsql12d8-1374 EXIT  SQLErrorW  with return code 0 
> (SQL_SUCCESS)
>   HENV0x
>   HDBC0x003DE6D0
>   HSTMT   0x
>   WCHAR * 0x2FBEEAF4 [   5] "08001"
>   SDWORD *0x2FBEEB3C (0)
>   WCHAR * 0x2FBEE6F4 [  45] "Failed to establish 
> connection with the host."
>   SWORD  300 
>  

[jira] [Commented] (IGNITE-5920) CacheClientBinaryQueryExample return different results if we add nodes to grid

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5920:


GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-5920: Fix the example. Set CacheKeyConfiguration explicitly to…

… enable affinity co-location.

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

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

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

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


commit 46f493aeb7beb9923d18b6ef1da3ba3009164d8b
Author: tledkov-gridgain 
Date:   2017-08-03T15:23:07Z

IGNITE-5920: Fix the example. Set CacheKeyConfiguration explicitly to 
enable affinity co-location.




> CacheClientBinaryQueryExample return different results if we add nodes to grid
> --
>
> Key: IGNITE-5920
> URL: https://issues.apache.org/jira/browse/IGNITE-5920
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Aleksey Chetaev
>Assignee: Taras Ledkov
> Fix For: 2.2
>
>
> 1. Start CacheClientBinaryQueryExample without external nodes. Section ">>> 
> Employees working for GridGain" isn't empty.
> 2. Start 3 node and after that start example. section ">>> Employees working 
> for GridGain" is empty.



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

[jira] [Commented] (IGNITE-5920) CacheClientBinaryQueryExample return different results if we add nodes to grid

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-5920:
--

Root cause: {{CacheTypeMetadata}} was replaced with {{QueryEntity}} but 
QueryEntity doesn't contain information about affinity keys collocation.
Fix: set {{CacheKeyConfiguration}} explicitly.

> CacheClientBinaryQueryExample return different results if we add nodes to grid
> --
>
> Key: IGNITE-5920
> URL: https://issues.apache.org/jira/browse/IGNITE-5920
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Aleksey Chetaev
>Assignee: Taras Ledkov
> Fix For: 2.2
>
>
> 1. Start CacheClientBinaryQueryExample without external nodes. Section ">>> 
> Employees working for GridGain" isn't empty.
> 2. Start 3 node and after that start example. section ">>> Employees working 
> for GridGain" is empty.



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

[jira] [Updated] (IGNITE-5813) Inconsistent cache store state when originating node fails on commit.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-5813:
-
Attachment: IgniteTxRecoveryAfterStoreCommitSelfTest.java

> Inconsistent cache store state when originating node fails on commit.
> -
>
> Key: IGNITE-5813
> URL: https://issues.apache.org/jira/browse/IGNITE-5813
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 2.2
>
> Attachments: IgniteTxRecoveryAfterStoreCommitSelfTest.java
>
>
> Same tx can be rolled back by cache and commited by CacheStore.
> It is possible when originating tx node commit tx successfully, but fails to 
> notify other nodes. 
> PFA reproducer.



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

[jira] [Updated] (IGNITE-5813) Inconsistent cache store state when originating node fails on commit.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-5813:
-
Attachment: (was: 
IgniteTxOriginatingNodeFailsAfterStoreCommitSelfTest.java)

> Inconsistent cache store state when originating node fails on commit.
> -
>
> Key: IGNITE-5813
> URL: https://issues.apache.org/jira/browse/IGNITE-5813
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 2.2
>
>
> Same tx can be rolled back by cache and commited by CacheStore.
> It is possible when originating tx node commit tx successfully, but fails to 
> notify other nodes. 
> PFA reproducer.



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

[jira] [Updated] (IGNITE-5922) Improve FifoCollisionSpi doc - ParallelJobsNumber should be less than PublicThreadPoolSize

[Evgenii Zhuravlev (JIRA)]

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

Evgenii Zhuravlev updated IGNITE-5922:
--
Summary: Improve FifoCollisionSpi doc - ParallelJobsNumber should be less 
than PublicThreadPoolSize  (was: Improve collisionSpi doc - ParallelJobsNumber 
should be less than PublicThreadPoolSize)

> Improve FifoCollisionSpi doc - ParallelJobsNumber should be less than 
> PublicThreadPoolSize
> --
>
> Key: IGNITE-5922
> URL: https://issues.apache.org/jira/browse/IGNITE-5922
> Project: Ignite
>  Issue Type: Improvement
>  Components: documentation
>Reporter: Evgenii Zhuravlev
>Priority: Minor
>




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

[jira] [Created] (IGNITE-5923) ODBC: SQLGetTypeInfo does not work with SQL_ALL_TYPES

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-5923:
---

 Summary: ODBC: SQLGetTypeInfo does not work with SQL_ALL_TYPES
 Key: IGNITE-5923
 URL: https://issues.apache.org/jira/browse/IGNITE-5923
 Project: Ignite
  Issue Type: Bug
  Components: odbc
Affects Versions: 2.1
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 2.2


ODBC function {{SQLGetTypeInfo}} does not work if given an {{SQL_ALL_TYPES}} as 
the {{DataType}} argument value.



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

[jira] [Commented] (IGNITE-5211) Classes based constructor for QueryEntities

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-5211:
--

Fixed. [~vozerov], please take a look.

> Classes based constructor for QueryEntities
> ---
>
> Key: IGNITE-5211
> URL: https://issues.apache.org/jira/browse/IGNITE-5211
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Denis Magda
>Assignee: Taras Ledkov
>Priority: Critical
> Fix For: 2.2
>
>
> We need to add constructor {{QueryEntity(Class keyType, Class valueType)}} to 
> query entities class and deprecate {{CacheConfiguration.setIndexedTypes(…)}} 
> method.
> Otherwise, there is no easy way for people who define SQL scheme with the 
> annotations to do advanced settings like names of key and value objects, 
> table name, etc.
> See this discussion for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/SQL-setting-key-field-name-for-types-registered-via-CacheConfiguration-setIndexedTypes-td17603.html



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

[jira] [Updated] (IGNITE-5890) Add estimated time to rebalance completion and time to rebalance start to MXBean

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-5890:
---
Labels:   (was: impro)

> Add estimated time to rebalance completion and time to rebalance start to 
> MXBean
> 
>
> Key: IGNITE-5890
> URL: https://issues.apache.org/jira/browse/IGNITE-5890
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Dmitriy Govorukhin
> Fix For: 2.2
>
>
> We already have rebalance speed metrics on MXBean, would be nice to see time 
> to rebalance start (when delayed rebalancing is used) and estimated time to 
> rebalance completion.



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

[jira] [Updated] (IGNITE-5890) Add estimated time to rebalance completion and time to rebalance start to MXBean

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-5890:
---
Labels: impro  (was: )

> Add estimated time to rebalance completion and time to rebalance start to 
> MXBean
> 
>
> Key: IGNITE-5890
> URL: https://issues.apache.org/jira/browse/IGNITE-5890
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Dmitriy Govorukhin
>  Labels: impro
> Fix For: 2.2
>
>
> We already have rebalance speed metrics on MXBean, would be nice to see time 
> to rebalance start (when delayed rebalancing is used) and estimated time to 
> rebalance completion.



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

[jira] [Commented] (IGNITE-5211) Classes based constructor for QueryEntities

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5211:


GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-5211 Classes based constructor for QueryEntities



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

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

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

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


commit f027c03167183254768c24c0aca4a8ddc33b985a
Author: tledkov-gridgain 
Date:   2017-08-03T14:36:23Z

IGNITE-5211 Classes based constructor for QueryEntities




> Classes based constructor for QueryEntities
> ---
>
> Key: IGNITE-5211
> URL: https://issues.apache.org/jira/browse/IGNITE-5211
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Denis Magda
>Assignee: Taras Ledkov
>Priority: Critical
> Fix For: 2.2
>
>
> We need to add constructor {{QueryEntity(Class keyType, Class valueType)}} to 
> query entities class and deprecate {{CacheConfiguration.setIndexedTypes(…)}} 
> method.
> Otherwise, there is no easy way for people who define SQL scheme with the 
> annotations to do advanced settings like names of key and value objects, 
> table name, etc.
> See this discussion for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/SQL-setting-key-field-name-for-types-registered-via-CacheConfiguration-setIndexedTypes-td17603.html



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

[jira] [Commented] (IGNITE-5736) Add test of backward-compatibility

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur commented on IGNITE-5736:


[Link to VarintArraysSizeCompatibilityTest 
only.|https://github.com/daradurvs/ignite/blob/c1cddffc986a0f4e3a41a3074f72bb5bf115ef37/modules/core/src/test/java/org/apache/ignite/internal/binary/VarintArraysSizeCompatibilityTest.java]

> Add test of backward-compatibility
> --
>
> Key: IGNITE-5736
> URL: https://issues.apache.org/jira/browse/IGNITE-5736
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
> Fix For: 2.2
>
>
> Need to add unit-test to test compatibility with AI 2.0.



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

[jira] [Commented] (IGNITE-5211) Classes based constructor for QueryEntities

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5211:


Github user tledkov-gridgain closed the pull request at:

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


> Classes based constructor for QueryEntities
> ---
>
> Key: IGNITE-5211
> URL: https://issues.apache.org/jira/browse/IGNITE-5211
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Denis Magda
>Assignee: Taras Ledkov
>Priority: Critical
> Fix For: 2.2
>
>
> We need to add constructor {{QueryEntity(Class keyType, Class valueType)}} to 
> query entities class and deprecate {{CacheConfiguration.setIndexedTypes(…)}} 
> method.
> Otherwise, there is no easy way for people who define SQL scheme with the 
> annotations to do advanced settings like names of key and value objects, 
> table name, etc.
> See this discussion for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/SQL-setting-key-field-name-for-types-registered-via-CacheConfiguration-setIndexedTypes-td17603.html



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

[jira] [Commented] (IGNITE-5736) Add test of backward-compatibility

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5736:


GitHub user daradurvs opened a pull request:

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

IGNITE-5736 Add test of backward-compatibility



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

$ git pull https://github.com/daradurvs/ignite ignite-5736

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

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


commit 1e1e8432dc936df7c62557575a57c4a159b4bca6
Author: Vyacheslav Daradur 
Date:   2017-05-31T08:41:56Z

ignite-5097: writing arrays length in varint encoding was implemented

commit d162d3e3d9036cddb275b4a3d86b8f5de9795185
Author: daradurvs 
Date:   2017-06-01T18:35:13Z

ignite-5097: doUnsafeWriteUnsignedVarint method was added

commit bfe381b3a7498eb5bebeb25026a43d36656c6041
Author: daradurvs 
Date:   2017-06-04T21:25:48Z

ignite-5097: dotNET - writing arrays length in varint encoding was 
implemented

commit 516fcf41e4e973abf41cdd19acd2c9ea1bfb9445
Author: daradurvs 
Date:   2017-06-04T21:26:00Z

ignite-5097: dotNET - hardcoded hashcode values in the tests were changed 
according to new conditions

commit fb43cbd77e9c83ef1aeb9dced923d9ca094a8be3
Author: Vyacheslav Daradur 
Date:   2017-07-05T20:25:27Z

Merge branch 'master' into ignite-5097_2

commit 398cb205c26c65f369dc3bdc4198f6032a206e87
Author: daradurvs 
Date:   2017-07-06T18:12:09Z

ignite-5097: compatibility property to allow to keep data in old format was 
added in Java part

commit 4105cf073e0e23f44c0c271407ce5415f867a352
Author: daradurvs 
Date:   2017-07-06T18:12:55Z

ignite-5097: dotNET - compatibility property to allow to keep data in old 
format was added

commit 86082a8052ce2e5c818183a18d16eddf54d5e346
Author: Vyacheslav Daradur 
Date:   2017-07-07T14:15:14Z

ignite-5097: compatibility mode test was added

commit 6aadaa985d021d38accedeaa3ada6790eb1981a9
Author: daradurvs 
Date:   2017-07-07T17:46:56Z

ignite-5097: dotNET - compatibility mode tests were added; fix constant 
condition

commit bd24ccf6e8c2b4deb85cd3ad48635be9addaecd3
Author: Vyacheslav Daradur 
Date:   2017-07-10T15:22:01Z

ignite-5097: dotNET - fix compatibility property condition

commit 5f3e1543c8de140a533d0fbdbfca74a2ffd89a36
Author: Vyacheslav Daradur 
Date:   2017-07-10T15:32:44Z

ignite-5097: rename constant of compatibility mode

commit ac59755342093609c2c9505ccde3308ebf1f1ed4
Author: daradurvs 
Date:   2017-07-10T17:42:00Z

ignite-5097: dotNET - fix compatibility mode test

commit bc2c07a63cd28b2e99d195b1f307c900e0ca
Author: Vyacheslav Daradur 
Date:   2017-07-14T15:02:27Z

ignite-5732: added test plugin to allow join topology nodes with different 
version

commit 45dc0c662f8392ead950c722f63c91e3467683fa
Author: daradurvs 
Date:   2017-08-01T14:53:07Z

ignite-5732: functional of starting node from Maven artifact was added (wip 
commits squashed)

commit 3321b2b48481e7c672cb250bd6c92e22c659d559
Author: daradurvs 
Date:   2017-08-01T15:00:22Z

ignite-5732: added MavenUtils

commit 3a1c2df63d8c30cdf4520083afd6f73a326a906e
Author: daradurvs 
Date:   2017-08-01T16:13:15Z

ignite-5732: minor refactoring

commit c4baa2847cd34a8733cad0929302eb8ecd89beae
Author: daradurvs 
Date:   2017-08-01T17:31:59Z

ignite-5732: minor refactoring 2

commit dbb5df2e8136b2a7b159fd11565d05fa2bd9f076
Author: daradurvs 
Date:   2017-08-02T10:33:14Z

ignite-5732: plugins were moved to another package

commit 8fbf34e3f84d77d6af8b40847eaa2f9faa0075fd
Author: daradurvs 
Date:   2017-08-02T11:10:46Z

ignite-5732: fix spi-attributes error in log

commit 9c205a303dbea0154f683e9514c926f4d53b8d12
Author: daradurvs 
Date:   2017-08-02T13:42:59Z

ignite-5732: refactoring; fixes of review notes

commit 35b56df32c8a9e0a06b9f9803999d3e32035959b
Author: daradurvs 
Date:   2017-08-02T15:24:42Z

ignite-5732: MavenUtils refactoring

commit 4eb47095eb37102f276f240a642a99e6eaedc23b
Author: daradurvs 
Date:   2017-08-02T16:07:55Z

ignite-5732: refactoring according to review note (DRY principle); minor 
style fixes

commit 03b4d916b3a8f7132d06a7f561c3c64d1ee6254f
Author: 

[jira] [Commented] (IGNITE-5890) Add estimated time to rebalance completion and time to rebalance start to MXBean

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5890:


GitHub user DmitriyGovorukhin opened a pull request:

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

IGNITE-5890 Estimated time to rebalance completion



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

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

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

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


commit 41664ea92205d9517d692edfc2620ad096cb1d44
Author: Dmitriy Govorukhin 
Date:   2017-08-03T08:05:34Z

IGNITE-5890 WIP. Estimated time to rebalance completion

commit 039e2ea9dfb9e5dc6c1cbfdc2fb8cf8fdee8a444
Author: Dmitriy Govorukhin 
Date:   2017-08-03T14:18:59Z

IGNITE-5890 added test estimate rebalance finish time

commit b44a72dabab928c0ab849d413b38e35934640001
Author: Dmitriy Govorukhin 
Date:   2017-08-03T14:25:57Z

IGNITE-5890 fix java doc




> Add estimated time to rebalance completion and time to rebalance start to 
> MXBean
> 
>
> Key: IGNITE-5890
> URL: https://issues.apache.org/jira/browse/IGNITE-5890
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Dmitriy Govorukhin
> Fix For: 2.2
>
>
> We already have rebalance speed metrics on MXBean, would be nice to see time 
> to rebalance start (when delayed rebalancing is used) and estimated time to 
> rebalance completion.



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

[jira] [Created] (IGNITE-5922) Improve collisionSpi doc - ParallelJobsNumber should be less than PublicThreadPoolSize

[Evgenii Zhuravlev (JIRA)]

Evgenii Zhuravlev created IGNITE-5922:
-

 Summary: Improve collisionSpi doc - ParallelJobsNumber should be 
less than PublicThreadPoolSize
 Key: IGNITE-5922
 URL: https://issues.apache.org/jira/browse/IGNITE-5922
 Project: Ignite
  Issue Type: Improvement
  Components: documentation
Reporter: Evgenii Zhuravlev
Priority: Minor






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

[jira] [Updated] (IGNITE-5918) Adding and searching objects in index tree produces a lot of garbage

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov updated IGNITE-5918:
--
Affects Version/s: 2.1

> Adding and searching objects in index tree produces a lot of garbage
> 
>
> Key: IGNITE-5918
> URL: https://issues.apache.org/jira/browse/IGNITE-5918
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Mikhail Cherkasov
>Assignee: Igor Seliverstov
>
> Adding and searching objects in index tree produces a lot of garbage and this 
> can lead to big GC pauses.
> Tests with data streaming of object with 5 string indexes show that ignite 
> server spends about 15-25% CPU time in GC.
> The problem is that ignite deserialize objects for comparing, while for the 
> primitive type and strings comparing can be implemented for bytes.



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

[jira] [Assigned] (IGNITE-5918) Adding and searching objects in index tree produces a lot of garbage

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov reassigned IGNITE-5918:
-

Assignee: Igor Seliverstov  (was: Mikhail Cherkasov)

> Adding and searching objects in index tree produces a lot of garbage
> 
>
> Key: IGNITE-5918
> URL: https://issues.apache.org/jira/browse/IGNITE-5918
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Mikhail Cherkasov
>Assignee: Igor Seliverstov
>
> Adding and searching objects in index tree produces a lot of garbage and this 
> can lead to big GC pauses.
> Tests with data streaming of object with 5 string indexes show that ignite 
> server spends about 15-25% CPU time in GC.
> The problem is that ignite deserialize objects for comparing, while for the 
> primitive type and strings comparing can be implemented for bytes.



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

[jira] [Updated] (IGNITE-5918) Adding and searching objects in index tree produces a lot of garbage

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov updated IGNITE-5918:
--
Description: 
Adding and searching objects in index tree produces a lot of garbage and this 
can lead to big GC pauses.
Tests with data streaming of object with 5 string indexes show that ignite 
server spends about 15-25% CPU time in GC.

The problem is that ignite deserialize objects for comparing, while for the 
primitive type and strings comparing can be implemented for bytes.


  was:
Adding and searching objects in index tree produces a lot of garbage and this 
can lead to big GC pauses.
Tests with data streaming of object with 5 string indexes show that ignite 
server spends about 15-25% CPU time in GC.

The problem is that ignite desirialize objects for comparing 



> Adding and searching objects in index tree produces a lot of garbage
> 
>
> Key: IGNITE-5918
> URL: https://issues.apache.org/jira/browse/IGNITE-5918
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Mikhail Cherkasov
>Assignee: Mikhail Cherkasov
>
> Adding and searching objects in index tree produces a lot of garbage and this 
> can lead to big GC pauses.
> Tests with data streaming of object with 5 string indexes show that ignite 
> server spends about 15-25% CPU time in GC.
> The problem is that ignite deserialize objects for comparing, while for the 
> primitive type and strings comparing can be implemented for bytes.



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

[jira] [Updated] (IGNITE-5918) Adding and searching objects in index tree produces a lot of garbage

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov updated IGNITE-5918:
--
Description: 
Adding and searching objects in index tree produces a lot of garbage and this 
can lead to big GC pauses.
Tests with data streaming of object with 5 string indexes show that ignite 
server spends about 15-25% CPU time in GC.

The problem is that ignite desirialize objects for comparing 


  was:
Adding and searching objects in index tree produces a lot of garbage and this 
can lead to big GC pauses.
Tests with data streaming of object with 5 string indexes show that ignite 
server spends about 15-25% CPU time in GC.



> Adding and searching objects in index tree produces a lot of garbage
> 
>
> Key: IGNITE-5918
> URL: https://issues.apache.org/jira/browse/IGNITE-5918
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Mikhail Cherkasov
>Assignee: Mikhail Cherkasov
>
> Adding and searching objects in index tree produces a lot of garbage and this 
> can lead to big GC pauses.
> Tests with data streaming of object with 5 string indexes show that ignite 
> server spends about 15-25% CPU time in GC.
> The problem is that ignite desirialize objects for comparing 



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

[jira] [Created] (IGNITE-5921) Reduce contention for free list access

[Mikhail Cherkasov (JIRA)]

Mikhail Cherkasov created IGNITE-5921:
-

 Summary: Reduce contention for free list access
 Key: IGNITE-5921
 URL: https://issues.apache.org/jira/browse/IGNITE-5921
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.1
 Environment: Reduce contention for free list access.
Reporter: Mikhail Cherkasov
Assignee: Igor Seliverstov


Reduce contention for free list access.



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

[jira] [Comment Edited] (IGNITE-5898) .NET: Datagrid.QueryDmlExample: Incorrect result if run example with standalone Apache Ignite.NET node

[Irina Zaporozhtseva (JIRA)]

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

Irina Zaporozhtseva edited comment on IGNITE-5898 at 8/3/17 12:51 PM:
--

the same problem for EntryProcessorExample:

without or with one standalone node:
Persons working for Apache:
>>> Person [idHash=4684212, Name=James Wilson Jr., CompanyId=-1]
>>> Person [idHash=9462952, Name=Daniel Adams, CompanyId=-1]
>>> Person [idHash=23179698, Name=Cristian Moss, CompanyId=-1]

with three standalone nodes:
>> Persons working for Apache:
>>> Person [idHash=4684212, Name=James Wilson Jr., CompanyId=-1]
>>> Person [idHash=23179698, Name=Cristian Moss, CompanyId=-1]

the same for QueryDmlExample


was (Author: izaporozhtseva):
the same problem for EntryProcessorExample:

without or with one standalone node:
Persons working for Apache:
>>> Person [idHash=4684212, Name=James Wilson Jr., CompanyId=-1]
>>> Person [idHash=9462952, Name=Daniel Adams, CompanyId=-1]
>>> Person [idHash=23179698, Name=Cristian Moss, CompanyId=-1]

with three standalone nodes:
>> Persons working for Apache:
>>> Person [idHash=4684212, Name=James Wilson Jr., CompanyId=-1]
>>> Person [idHash=23179698, Name=Cristian Moss, CompanyId=-1]

> .NET: Datagrid.QueryDmlExample: Incorrect result if run example  with 
> standalone Apache Ignite.NET node
> ---
>
> Key: IGNITE-5898
> URL: https://issues.apache.org/jira/browse/IGNITE-5898
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.9, 2.1
>Reporter: Irina Zaporozhtseva
>Priority: Minor
>  Labels: .NET
>
> {{Datagrid.QueryDmlExample}}: Incorrect result if run example with standalone 
> Apache Ignite.NET node
> without standalone node:
> {code}
> >>> Inserted data
> >>> 1: John Doe, ASF, 4000
> >>> 2: Jane Roe, ASF, 5000
> >>> 3: Mary Major, Eclipse, 2000
> >>> 4: Richard Miles, Eclipse, 3000
> >>> Update salary for ASF employees
> >>> 1: John Doe, ASF, 4400
> >>> 2: Jane Roe, ASF, 5500
> >>> 3: Mary Major, Eclipse, 2000
> >>> 4: Richard Miles, Eclipse, 3000
> >>> Delete non-ASF employees
> >>> 1: John Doe, ASF, 4400
> >>> 2: Jane Roe, ASF, 5500
> {code}
> with standalone node:
> {code}
> >>> Inserted data
> >>> 1: John Doe, ASF, 4000
> >>> 3: Mary Major, Eclipse, 2000
> >>> Update salary for ASF employees
> >>> 1: John Doe, ASF, 4400
> >>> 3: Mary Major, Eclipse, 2000
> >>> Delete non-ASF employees
> >>> 1: John Doe, ASF, 4400
> {code}



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

[jira] [Updated] (IGNITE-5898) .NET: Datagrid.QueryDmlExample: Incorrect result if run example with standalone Apache Ignite.NET node

[Irina Zaporozhtseva (JIRA)]

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

Irina Zaporozhtseva updated IGNITE-5898:

Affects Version/s: 1.9

> .NET: Datagrid.QueryDmlExample: Incorrect result if run example  with 
> standalone Apache Ignite.NET node
> ---
>
> Key: IGNITE-5898
> URL: https://issues.apache.org/jira/browse/IGNITE-5898
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.9, 2.1
>Reporter: Irina Zaporozhtseva
>Priority: Minor
>  Labels: .NET
>
> {{Datagrid.QueryDmlExample}}: Incorrect result if run example with standalone 
> Apache Ignite.NET node
> without standalone node:
> {code}
> >>> Inserted data
> >>> 1: John Doe, ASF, 4000
> >>> 2: Jane Roe, ASF, 5000
> >>> 3: Mary Major, Eclipse, 2000
> >>> 4: Richard Miles, Eclipse, 3000
> >>> Update salary for ASF employees
> >>> 1: John Doe, ASF, 4400
> >>> 2: Jane Roe, ASF, 5500
> >>> 3: Mary Major, Eclipse, 2000
> >>> 4: Richard Miles, Eclipse, 3000
> >>> Delete non-ASF employees
> >>> 1: John Doe, ASF, 4400
> >>> 2: Jane Roe, ASF, 5500
> {code}
> with standalone node:
> {code}
> >>> Inserted data
> >>> 1: John Doe, ASF, 4000
> >>> 3: Mary Major, Eclipse, 2000
> >>> Update salary for ASF employees
> >>> 1: John Doe, ASF, 4400
> >>> 3: Mary Major, Eclipse, 2000
> >>> Delete non-ASF employees
> >>> 1: John Doe, ASF, 4400
> {code}



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

[jira] [Updated] (IGNITE-5920) CacheClientBinaryQueryExample return different results if we add nodes to grid

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5920:

Fix Version/s: 2.2

> CacheClientBinaryQueryExample return different results if we add nodes to grid
> --
>
> Key: IGNITE-5920
> URL: https://issues.apache.org/jira/browse/IGNITE-5920
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Aleksey Chetaev
>Assignee: Taras Ledkov
> Fix For: 2.2
>
>
> 1. Start CacheClientBinaryQueryExample without external nodes. Section ">>> 
> Employees working for GridGain" isn't empty.
> 2. Start 3 node and after that start example. section ">>> Employees working 
> for GridGain" is empty.



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

[jira] [Commented] (IGNITE-5823) Need to remove CacheAtomicUpdateTimeoutException

[Sergey Dorozhkin (JIRA)]

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

Sergey Dorozhkin commented on IGNITE-5823:
--

[~yzhdanov] , can you please review?

> Need to remove CacheAtomicUpdateTimeoutException
> 
>
> Key: IGNITE-5823
> URL: https://issues.apache.org/jira/browse/IGNITE-5823
> Project: Ignite
>  Issue Type: Task
>Reporter: Yakov Zhdanov
>Assignee: Sergey Dorozhkin
>Priority: Minor
>  Labels: newbie
> Fix For: 2.2
>
>
> And releated - CacheAtomicUpdateTimeoutCheckedException
> These exceptions are not used any more and can be removed.



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

[jira] [Commented] (IGNITE-5920) CacheClientBinaryQueryExample return different results if we add nodes to grid

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-5920:
-

Possible causes:
1) Missing co-location (if applicable)
2) Missing "distributedJoins=true"
3) PRIMARY_SYNC mode

> CacheClientBinaryQueryExample return different results if we add nodes to grid
> --
>
> Key: IGNITE-5920
> URL: https://issues.apache.org/jira/browse/IGNITE-5920
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Aleksey Chetaev
>Assignee: Taras Ledkov
>
> 1. Start CacheClientBinaryQueryExample without external nodes. Section ">>> 
> Employees working for GridGain" isn't empty.
> 2. Start 3 node and after that start example. section ">>> Employees working 
> for GridGain" is empty.



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

[jira] [Assigned] (IGNITE-5920) CacheClientBinaryQueryExample return different results if we add nodes to grid

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-5920:
---

Assignee: Taras Ledkov

> CacheClientBinaryQueryExample return different results if we add nodes to grid
> --
>
> Key: IGNITE-5920
> URL: https://issues.apache.org/jira/browse/IGNITE-5920
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Aleksey Chetaev
>Assignee: Taras Ledkov
>
> 1. Start CacheClientBinaryQueryExample without external nodes. Section ">>> 
> Employees working for GridGain" isn't empty.
> 2. Start 3 node and after that start example. section ">>> Employees working 
> for GridGain" is empty.



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

[jira] [Updated] (IGNITE-5920) CacheClientBinaryQueryExample return different results if we add nodes to grid

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5920:

Component/s: sql

> CacheClientBinaryQueryExample return different results if we add nodes to grid
> --
>
> Key: IGNITE-5920
> URL: https://issues.apache.org/jira/browse/IGNITE-5920
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Aleksey Chetaev
>
> 1. Start CacheClientBinaryQueryExample without external nodes. Section ">>> 
> Employees working for GridGain" isn't empty.
> 2. Start 3 node and after that start example. section ">>> Employees working 
> for GridGain" is empty.



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

[jira] [Updated] (IGNITE-5920) CacheClientBinaryQueryExample return different results if we add nodes to grid

[Aleksey Chetaev (JIRA)]

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

Aleksey Chetaev updated IGNITE-5920:

Summary: CacheClientBinaryQueryExample return different results if we add 
nodes to grid  (was: CacheClientBinaryQueryExample return different results if 
we add non local node)

> CacheClientBinaryQueryExample return different results if we add nodes to grid
> --
>
> Key: IGNITE-5920
> URL: https://issues.apache.org/jira/browse/IGNITE-5920
> Project: Ignite
>  Issue Type: Bug
>Reporter: Aleksey Chetaev
>
> 1. Start CacheClientBinaryQueryExample without external nodes. Section ">>> 
> Employees working for GridGain" isn't empty.
> 2. Start 3 node and after that start example. section ">>> Employees working 
> for GridGain" is empty.



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

[jira] [Created] (IGNITE-5920) CacheClientBinaryQueryExample return different results if we add non local node

[Aleksey Chetaev (JIRA)]

Aleksey Chetaev created IGNITE-5920:
---

 Summary: CacheClientBinaryQueryExample return different results if 
we add non local node
 Key: IGNITE-5920
 URL: https://issues.apache.org/jira/browse/IGNITE-5920
 Project: Ignite
  Issue Type: Bug
Reporter: Aleksey Chetaev


1. Start CacheClientBinaryQueryExample without external nodes. Section ">>> 
Employees working for GridGain" isn't empty.
2. Start 3 node and after that start example. section ">>> Employees working 
for GridGain" is empty.



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

[jira] [Updated] (IGNITE-5918) Adding and searching objects in index tree produces a lot of garbage

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov updated IGNITE-5918:
--
Description: 
Adding and searching objects in index tree produces a lot of garbage and this 
can lead to big GC pauses.
Tests with data streaming of object with 5 string indexes show that ignite 
server spends about 15-25% CPU time in GC.


  was:
Adding and searching objects in index tree produces a lot of garbage and this 
can lead to big GC pauses.
Tests with data streaming of object with 5 string indexes shows that ignite 
server spends about 15-25% cpu time in GC.



> Adding and searching objects in index tree produces a lot of garbage
> 
>
> Key: IGNITE-5918
> URL: https://issues.apache.org/jira/browse/IGNITE-5918
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Mikhail Cherkasov
>Assignee: Mikhail Cherkasov
>
> Adding and searching objects in index tree produces a lot of garbage and this 
> can lead to big GC pauses.
> Tests with data streaming of object with 5 string indexes show that ignite 
> server spends about 15-25% CPU time in GC.



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

[jira] [Created] (IGNITE-5919) .NET: EntryProcessorExample closes immediately after execution

[Irina Zaporozhtseva (JIRA)]

Irina Zaporozhtseva created IGNITE-5919:
---

 Summary: .NET: EntryProcessorExample closes immediately after 
execution
 Key: IGNITE-5919
 URL: https://issues.apache.org/jira/browse/IGNITE-5919
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 1.9
Reporter: Irina Zaporozhtseva
Priority: Minor


EntryProcessorExample closes immediately after execution. Please, add:

Console.WriteLine();
Console.WriteLine(">>> Example finished, press any key to exit ...");
Console.ReadKey();



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

[jira] [Updated] (IGNITE-5918) Adding and searching objects in index tree produces a lot of garbage

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov updated IGNITE-5918:
--
Description: 
Adding and searching objects in index tree produces a lot of garbage and this 
can lead to big GC pauses.
Tests with data streaming of object with 5 string indexes shows that ignite 
server spends about 15-25% cpu time in GC.


  was:Adding and searching objects in index tree produce a lot of garbage 


> Adding and searching objects in index tree produces a lot of garbage
> 
>
> Key: IGNITE-5918
> URL: https://issues.apache.org/jira/browse/IGNITE-5918
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Mikhail Cherkasov
>Assignee: Mikhail Cherkasov
>
> Adding and searching objects in index tree produces a lot of garbage and this 
> can lead to big GC pauses.
> Tests with data streaming of object with 5 string indexes shows that ignite 
> server spends about 15-25% cpu time in GC.



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

[jira] [Updated] (IGNITE-5301) JVM crashes on H2TreeIndex destroy

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5301:

Component/s: (was: sql)

> JVM crashes on H2TreeIndex destroy
> --
>
> Key: IGNITE-5301
> URL: https://issues.apache.org/jira/browse/IGNITE-5301
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
> Attachments: hs_err_pid9664.log
>
>
> There is a bug in destroy method because of which 
> {noformat}cctx.offheap().dropRootPageForIndex(idxName){noformat} method 
> actually does nothing. It happens because idx names on create RootPage and 
> destroy it are different (unlike creation a root page, a segment suffix isn't 
> added to tree name on destroy, so that it can't delete the page from 
> metastore by different key).
> After fixing this behavior I faced JVM crash. 
> I'm quite not familiar with the code, but I suppose something is wrong in 
> MetaStoreInnerIO logic.
> Crash report is attached.
> How to reproduce:
> just create and destroy a cache with indexed types and enabled PDS feature 
> after the fix I provided above is applied.



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

[jira] [Comment Edited] (IGNITE-5898) .NET: Datagrid.QueryDmlExample: Incorrect result if run example with standalone Apache Ignite.NET node

[Irina Zaporozhtseva (JIRA)]

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

Irina Zaporozhtseva edited comment on IGNITE-5898 at 8/3/17 12:05 PM:
--

the same problem for EntryProcessorExample:

without or with one standalone node:
Persons working for Apache:
>>> Person [idHash=4684212, Name=James Wilson Jr., CompanyId=-1]
>>> Person [idHash=9462952, Name=Daniel Adams, CompanyId=-1]
>>> Person [idHash=23179698, Name=Cristian Moss, CompanyId=-1]

with three standalone nodes:
>> Persons working for Apache:
>>> Person [idHash=4684212, Name=James Wilson Jr., CompanyId=-1]
>>> Person [idHash=23179698, Name=Cristian Moss, CompanyId=-1]


was (Author: izaporozhtseva):
the same problem for EntryProcessorExample:
without or with one standalone node:
Persons working for Apache:
>>> Person [idHash=4684212, Name=James Wilson Jr., CompanyId=-1]
>>> Person [idHash=9462952, Name=Daniel Adams, CompanyId=-1]
>>> Person [idHash=23179698, Name=Cristian Moss, CompanyId=-1]

with three standalone nodes:
>> Persons working for Apache:
>>> Person [idHash=4684212, Name=James Wilson Jr., CompanyId=-1]
>>> Person [idHash=23179698, Name=Cristian Moss, CompanyId=-1]

> .NET: Datagrid.QueryDmlExample: Incorrect result if run example  with 
> standalone Apache Ignite.NET node
> ---
>
> Key: IGNITE-5898
> URL: https://issues.apache.org/jira/browse/IGNITE-5898
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Irina Zaporozhtseva
>Priority: Minor
>  Labels: .NET
>
> {{Datagrid.QueryDmlExample}}: Incorrect result if run example with standalone 
> Apache Ignite.NET node
> without standalone node:
> {code}
> >>> Inserted data
> >>> 1: John Doe, ASF, 4000
> >>> 2: Jane Roe, ASF, 5000
> >>> 3: Mary Major, Eclipse, 2000
> >>> 4: Richard Miles, Eclipse, 3000
> >>> Update salary for ASF employees
> >>> 1: John Doe, ASF, 4400
> >>> 2: Jane Roe, ASF, 5500
> >>> 3: Mary Major, Eclipse, 2000
> >>> 4: Richard Miles, Eclipse, 3000
> >>> Delete non-ASF employees
> >>> 1: John Doe, ASF, 4400
> >>> 2: Jane Roe, ASF, 5500
> {code}
> with standalone node:
> {code}
> >>> Inserted data
> >>> 1: John Doe, ASF, 4000
> >>> 3: Mary Major, Eclipse, 2000
> >>> Update salary for ASF employees
> >>> 1: John Doe, ASF, 4400
> >>> 3: Mary Major, Eclipse, 2000
> >>> Delete non-ASF employees
> >>> 1: John Doe, ASF, 4400
> {code}



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

[jira] [Commented] (IGNITE-5898) .NET: Datagrid.QueryDmlExample: Incorrect result if run example with standalone Apache Ignite.NET node

[Irina Zaporozhtseva (JIRA)]

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

Irina Zaporozhtseva commented on IGNITE-5898:
-

the same problem for EntryProcessorExample:
without or with one standalone node:
Persons working for Apache:
>>> Person [idHash=4684212, Name=James Wilson Jr., CompanyId=-1]
>>> Person [idHash=9462952, Name=Daniel Adams, CompanyId=-1]
>>> Person [idHash=23179698, Name=Cristian Moss, CompanyId=-1]

with three standalone nodes:
>> Persons working for Apache:
>>> Person [idHash=4684212, Name=James Wilson Jr., CompanyId=-1]
>>> Person [idHash=23179698, Name=Cristian Moss, CompanyId=-1]

> .NET: Datagrid.QueryDmlExample: Incorrect result if run example  with 
> standalone Apache Ignite.NET node
> ---
>
> Key: IGNITE-5898
> URL: https://issues.apache.org/jira/browse/IGNITE-5898
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Irina Zaporozhtseva
>Priority: Minor
>  Labels: .NET
>
> {{Datagrid.QueryDmlExample}}: Incorrect result if run example with standalone 
> Apache Ignite.NET node
> without standalone node:
> {code}
> >>> Inserted data
> >>> 1: John Doe, ASF, 4000
> >>> 2: Jane Roe, ASF, 5000
> >>> 3: Mary Major, Eclipse, 2000
> >>> 4: Richard Miles, Eclipse, 3000
> >>> Update salary for ASF employees
> >>> 1: John Doe, ASF, 4400
> >>> 2: Jane Roe, ASF, 5500
> >>> 3: Mary Major, Eclipse, 2000
> >>> 4: Richard Miles, Eclipse, 3000
> >>> Delete non-ASF employees
> >>> 1: John Doe, ASF, 4400
> >>> 2: Jane Roe, ASF, 5500
> {code}
> with standalone node:
> {code}
> >>> Inserted data
> >>> 1: John Doe, ASF, 4000
> >>> 3: Mary Major, Eclipse, 2000
> >>> Update salary for ASF employees
> >>> 1: John Doe, ASF, 4400
> >>> 3: Mary Major, Eclipse, 2000
> >>> Delete non-ASF employees
> >>> 1: John Doe, ASF, 4400
> {code}



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

[jira] [Updated] (IGNITE-5918) Adding and searching objects in index tree produce a lot of garbage

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov updated IGNITE-5918:
--
Description: Adding and searching objects in index tree produce a lot of 
garbage 

> Adding and searching objects in index tree produce a lot of garbage
> ---
>
> Key: IGNITE-5918
> URL: https://issues.apache.org/jira/browse/IGNITE-5918
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Mikhail Cherkasov
>Assignee: Mikhail Cherkasov
>
> Adding and searching objects in index tree produce a lot of garbage 



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

[jira] [Updated] (IGNITE-5918) Adding and searching objects in index tree produces a lot of garbage

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov updated IGNITE-5918:
--
Summary: Adding and searching objects in index tree produces a lot of 
garbage  (was: Adding and searching objects in index tree produce a lot of 
garbage)

> Adding and searching objects in index tree produces a lot of garbage
> 
>
> Key: IGNITE-5918
> URL: https://issues.apache.org/jira/browse/IGNITE-5918
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Mikhail Cherkasov
>Assignee: Mikhail Cherkasov
>
> Adding and searching objects in index tree produce a lot of garbage 



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

[jira] [Updated] (IGNITE-5918) Adding and searching objects in index tree produce a lot of garbage

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov updated IGNITE-5918:
--
Issue Type: Improvement  (was: Bug)

> Adding and searching objects in index tree produce a lot of garbage
> ---
>
> Key: IGNITE-5918
> URL: https://issues.apache.org/jira/browse/IGNITE-5918
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Mikhail Cherkasov
>Assignee: Mikhail Cherkasov
>




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

[jira] [Resolved] (IGNITE-5626) SQL TRIM function is not working properly

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-5626.
-

> SQL TRIM function is not working properly
> -
>
> Key: IGNITE-5626
> URL: https://issues.apache.org/jira/browse/IGNITE-5626
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
> Attachments: SqlTrimTest.java
>
>
> {{TRIM}} function trims only first char instead of the whole provided string. 
> Trailing chars are not trimmed at all.
> Reproducer attached.



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

[jira] [Closed] (IGNITE-5626) SQL TRIM function is not working properly

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-5626.
---

> SQL TRIM function is not working properly
> -
>
> Key: IGNITE-5626
> URL: https://issues.apache.org/jira/browse/IGNITE-5626
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
> Attachments: SqlTrimTest.java
>
>
> {{TRIM}} function trims only first char instead of the whole provided string. 
> Trailing chars are not trimmed at all.
> Reproducer attached.



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

[jira] [Commented] (IGNITE-5626) SQL TRIM function is not working properly

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-5626:
-

Sorry, looks like everything is fine - {{TRIM}} works in a way it should work.

> SQL TRIM function is not working properly
> -
>
> Key: IGNITE-5626
> URL: https://issues.apache.org/jira/browse/IGNITE-5626
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
> Attachments: SqlTrimTest.java
>
>
> {{TRIM}} function trims only first char instead of the whole provided string. 
> Trailing chars are not trimmed at all.
> Reproducer attached.



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

[jira] [Closed] (IGNITE-5624) SQL: LTRIM/RTRIM not working with multiple character

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-5624.
---

> SQL: LTRIM/RTRIM not working with multiple character
> 
>
> Key: IGNITE-5624
> URL: https://issues.apache.org/jira/browse/IGNITE-5624
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
>
>  LTRIM/RTRIM is working only for one char and not for a word (Multiple 
> Character). For instance, the example below doesn't work for Ignite:
> {code}
> SELECT product_name, LTRIM(product_name, 'Monitor ') "Short Name"
>FROM products
>WHERE product_name LIKE 'Monitor%';
> {code}



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

[jira] [Commented] (IGNITE-5626) SQL TRIM function is not working properly

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-5626:
-

Re-opening. {{TRIM}} is widely used function. We need to find a way how to make 
it work correctly.

> SQL TRIM function is not working properly
> -
>
> Key: IGNITE-5626
> URL: https://issues.apache.org/jira/browse/IGNITE-5626
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
> Attachments: SqlTrimTest.java
>
>
> {{TRIM}} function trims only first char instead of the whole provided string. 
> Trailing chars are not trimmed at all.
> Reproducer attached.



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

[jira] [Resolved] (IGNITE-5624) SQL: LTRIM/RTRIM not working with multiple character

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-5624.
-

> SQL: LTRIM/RTRIM not working with multiple character
> 
>
> Key: IGNITE-5624
> URL: https://issues.apache.org/jira/browse/IGNITE-5624
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
>
>  LTRIM/RTRIM is working only for one char and not for a word (Multiple 
> Character). For instance, the example below doesn't work for Ignite:
> {code}
> SELECT product_name, LTRIM(product_name, 'Monitor ') "Short Name"
>FROM products
>WHERE product_name LIKE 'Monitor%';
> {code}



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

[jira] [Comment Edited] (IGNITE-5794) BinaryMetadata is lost if all server nodes have been restarted

[Sergey Chugunov (JIRA)]

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

Sergey Chugunov edited comment on IGNITE-5794 at 8/3/17 11:41 AM:
--

Correct fix for this issue is to clean up all metadata on client when it 
reconnects to the cluster. 

Sending metadata from client to server is dangerous as client node may 
disconnect from one cluster and connect to a completely different. Binary 
metadata cache in new cluster will be polluted by reconnected client.

The issue affects versions older than 2.0 but in 2.0+ it is more visible 
because of NPE.

However workaround to fix it is simple and requires only restarting client node 
on event of reconnect.


was (Author: sergey-chugunov):
Correct fix for this issue is to clean up all metadata on client when it 
reconnects to the cluster. 
Sending metadata from client to server is dangerous as client node may 
disconnect from one cluster and connect to a completely different. Binary 
metadata cache in new cluster will be polluted by reconnected client.

The issue affects versions older than 2.0 but in 2.0+ it is more visible 
because of NPE.

However workaround to fix it is simple and requires only restarting client node 
on event of reconnect.

> BinaryMetadata is lost if all server nodes have been restarted
> --
>
> Key: IGNITE-5794
> URL: https://issues.apache.org/jira/browse/IGNITE-5794
> Project: Ignite
>  Issue Type: Bug
>  Components: binary, general
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>
> Steps to reproduce are described here: 
> http://apache-ignite-users.70518.x6.nabble.com/Problem-with-Messages-after-client-reconnect-td15127.html#none
> This problem occurs because client has metadata in it's local metadata cache 
> and decides that server node should have it too. But server lost it after 
> restart.
> Possible fixes:
> - Make client nodes re-send all contents of local metadata cache after 
> reconnect.
> - If node doesn't have metadata to process incoming message, it should 
> request it from sender node.



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

[jira] [Commented] (IGNITE-5794) BinaryMetadata is lost if all server nodes have been restarted

[Sergey Chugunov (JIRA)]

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

Sergey Chugunov commented on IGNITE-5794:
-

Correct fix for this issue is to clean up all metadata on client when it 
reconnects to the cluster. 
Sending metadata from client to server is dangerous as client node may 
disconnect from one cluster and connect to a completely different. Binary 
metadata cache in new cluster will be polluted by reconnected client.

The issue affects versions older than 2.0 but in 2.0+ it is more visible 
because of NPE.

However workaround to fix it is simple and requires only restarting client node 
on event of reconnect.

> BinaryMetadata is lost if all server nodes have been restarted
> --
>
> Key: IGNITE-5794
> URL: https://issues.apache.org/jira/browse/IGNITE-5794
> Project: Ignite
>  Issue Type: Bug
>  Components: binary, general
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>
> Steps to reproduce are described here: 
> http://apache-ignite-users.70518.x6.nabble.com/Problem-with-Messages-after-client-reconnect-td15127.html#none
> This problem occurs because client has metadata in it's local metadata cache 
> and decides that server node should have it too. But server lost it after 
> restart.
> Possible fixes:
> - Make client nodes re-send all contents of local metadata cache after 
> reconnect.
> - If node doesn't have metadata to process incoming message, it should 
> request it from sender node.



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

[jira] [Created] (IGNITE-5918) Adding and searching objects in index tree produce a lot of garbage

[Mikhail Cherkasov (JIRA)]

Mikhail Cherkasov created IGNITE-5918:
-

 Summary: Adding and searching objects in index tree produce a lot 
of garbage
 Key: IGNITE-5918
 URL: https://issues.apache.org/jira/browse/IGNITE-5918
 Project: Ignite
  Issue Type: Bug
Reporter: Mikhail Cherkasov
Assignee: Mikhail Cherkasov






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

[jira] [Updated] (IGNITE-5917) Fields have no error-triangle in case of incorrect value

[Pavel Konstantinov (JIRA)]

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

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

> Fields have no error-triangle in case of incorrect value
> 
>
> Key: IGNITE-5917
> URL: https://issues.apache.org/jira/browse/IGNITE-5917
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
> Fix For: 2.2
>
> Attachments: screenshot-1.png
>
>




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

[jira] [Commented] (IGNITE-5897) Ignite Cache Full API Multi JVM: 7 test failed in master

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-5897:


[~NIzhikov], could you notify when TC is completed and share link to run-all?

> Ignite Cache Full API Multi JVM: 7 test failed in master
> 
>
> Key: IGNITE-5897
> URL: https://issues.apache.org/jira/browse/IGNITE-5897
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Dmitriy Pavlov
>Assignee: Nikolay Izhikov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Failure on TC: 
> http://ci.ignite.apache.org/viewLog.html?buildId=749671=buildResultsDiv=Ignite20Tests_IgniteCacheFullApiMultiJvm#testNameId-6305397409161667157
> org.apache.ignite.internal.processors.cache.multijvm (7)
> - 
> GridCachePartitionedNearDisabledMultiJvmFullApiSelfTest.testTransformResourceInjection
>   
> - 
> GridCachePartitionedNearDisabledMultiJvmP2PDisabledFullApiSelfTest.testTransformResourceInjection
>
> - 
> GridCachePartitionedNearDisabledOnheapMultiJvmFullApiSelfTest.testTransformResourceInjection
> 
> - GridCacheReplicatedMultiJvmFullApiSelfTest.testTransformResourceInjection   
> - 
> GridCacheReplicatedMultiJvmP2PDisabledFullApiSelfTest.testTransformResourceInjection
> 
> - 
> GridCacheReplicatedNearOnlyMultiJvmFullApiSelfTest.testTransformResourceInjection
>
> - 
> GridCacheReplicatedOnheapMultiJvmFullApiSelfTest.testTransformResourceInjection
>  
> Stable reproducible locally
> First failure changes:
> http://ci.ignite.apache.org/viewLog.html?buildId=727280=buildChangesDiv=Ignite20Tests_IgniteCacheFullApiMultiJvm
> {noformat}
> IGNITE-5753: CPP Memory leak fixed.   Igor Sapego 
> IGNITE-5444: Collections.singletonList is not properly serialized by binary 
> marshaller. This closes #2217.andrey.mashenkov 
> ignite-5722 Cache entries stay in onheap after scan query execution for 
> OFFHEAP_TIRED cache with expiry policyAndrey Gura 
> ignite-5489 Fixed possible connection leaks when loadPreviousValue set to 
> truetikhonovnicolay 
> IGNITE-4831: Add an option to disable MBeans. This closes #2265.  
> andrey.mashenkov   
> {noformat}
> Stacktrace: 
> {noformat}
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea] class 
> org.apache.ignite.IgniteCheckedException: java.lang.NullPointerException
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadFromStore(GridCacheStoreManagerAdapter.java:327)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.load(GridCacheStoreManagerAdapter.java:282)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.readThrough(GridCacheMapEntry.java:445)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerGet0(GridCacheMapEntry.java:699)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerGet(GridCacheMapEntry.java:461)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.onEntriesLocked(GridDhtTxPrepareFuture.java:389)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare0(GridDhtTxPrepareFuture.java:1213)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.mapIfLocked(GridDhtTxPrepareFuture.java:668)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare(GridDhtTxPrepareFuture.java:1034)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.prepareAsync(GridDhtTxLocal.java:410)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareNearTx(IgniteTxHandler.java:459)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest(IgniteTxHandler.java:121)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> 

[jira] [Assigned] (IGNITE-5917) Fields have no error-triangle in case of incorrect value

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-5917:
--

Assignee: Vasiliy Sisko

> Fields have no error-triangle in case of incorrect value
> 
>
> Key: IGNITE-5917
> URL: https://issues.apache.org/jira/browse/IGNITE-5917
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
> Fix For: 2.2
>
> Attachments: screenshot-1.png
>
>
> !screenshot-1.png!



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

[jira] [Updated] (IGNITE-5917) Fields have no error-triangle in case of incorrect value

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-5917:
---
Description: !screenshot-1.png!

> Fields have no error-triangle in case of incorrect value
> 
>
> Key: IGNITE-5917
> URL: https://issues.apache.org/jira/browse/IGNITE-5917
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
> Fix For: 2.2
>
> Attachments: screenshot-1.png
>
>
> !screenshot-1.png!



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

[jira] [Updated] (IGNITE-5917) Fields have no error-triangle in case of incorrect value

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-5917:
---
Description: !screenshot-2.png!

> Fields have no error-triangle in case of incorrect value
> 
>
> Key: IGNITE-5917
> URL: https://issues.apache.org/jira/browse/IGNITE-5917
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
> Fix For: 2.2
>
>
> !screenshot-2.png!



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

[jira] [Updated] (IGNITE-5917) Fields have no error-triangle in case of incorrect value

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-5917:
---
Attachment: screenshot-2.png

> Fields have no error-triangle in case of incorrect value
> 
>
> Key: IGNITE-5917
> URL: https://issues.apache.org/jira/browse/IGNITE-5917
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
> Fix For: 2.2
>
>




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

[jira] [Updated] (IGNITE-5917) Fields have no error-triangle in case of incorrect value

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-5917:
---
Description: (was: !screenshot-2.png!)

> Fields have no error-triangle in case of incorrect value
> 
>
> Key: IGNITE-5917
> URL: https://issues.apache.org/jira/browse/IGNITE-5917
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
> Fix For: 2.2
>
>




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

[jira] [Updated] (IGNITE-5917) Fields have no error-triangle in case of incorrect value

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-5917:
---
Attachment: (was: screenshot-2.png)

> Fields have no error-triangle in case of incorrect value
> 
>
> Key: IGNITE-5917
> URL: https://issues.apache.org/jira/browse/IGNITE-5917
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
> Fix For: 2.2
>
>




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

[jira] [Created] (IGNITE-5917) Fields have no error-triangle in case of incorrect value

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-5917:
--

 Summary: Fields have no error-triangle in case of incorrect value
 Key: IGNITE-5917
 URL: https://issues.apache.org/jira/browse/IGNITE-5917
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Pavel Konstantinov
 Fix For: 2.2






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

[jira] [Updated] (IGNITE-5917) Fields have no error-triangle in case of incorrect value

[Pavel Konstantinov (JIRA)]

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

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

> Fields have no error-triangle in case of incorrect value
> 
>
> Key: IGNITE-5917
> URL: https://issues.apache.org/jira/browse/IGNITE-5917
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
> Fix For: 2.2
>
> Attachments: screenshot-1.png
>
>




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

[jira] [Created] (IGNITE-5916) Web console: incorrect default value for Cache-Queries & Indexing-SQL index max inline size = -1

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-5916:
--

 Summary: Web console: incorrect default value for Cache-Queries & 
Indexing-SQL index max inline size = -1
 Key: IGNITE-5916
 URL: https://issues.apache.org/jira/browse/IGNITE-5916
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov


If I set -1 as real value then field become incorrect (red border)



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

[jira] [Assigned] (IGNITE-5145) Support multiple service deployment in API

[Alexandr Fedotov (JIRA)]

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

Alexandr Fedotov reassigned IGNITE-5145:


Assignee: Denis Mekhanikov

> Support multiple service deployment in API
> --
>
> Key: IGNITE-5145
> URL: https://issues.apache.org/jira/browse/IGNITE-5145
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Dmitry Karachentsev
>Assignee: Denis Mekhanikov
>
> IgniteServices should support possibility of deploying batch of services at 
> once to speed up deployment.



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

[jira] [Updated] (IGNITE-5544) Ignite Cache: floating failure in testBackupRestore

[Dmitriy Pavlov (JIRA)]

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

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

> Ignite Cache: floating failure in testBackupRestore
> ---
>
> Key: IGNITE-5544
> URL: https://issues.apache.org/jira/browse/IGNITE-5544
> Project: Ignite
>  Issue Type: Test
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>  Labels: MakeTeamcityGreenAgain, test-fail
>
> http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-3580536643752440720=testDetails
> Success rate on TC - 83%
> http://ci.ignite.apache.org/viewLog.html?buildId=674133=buildResultsDiv=Ignite20Tests_IgniteCache#testNameId-3580536643752440720
> GridCacheReplicatedLocalStoreSelfTest.testBackupRestorePrimary 
> testBackupRestorePrimary
> Has floating failure
> Can be reproduced locally with run until failure, 7-10 runs required:
> {noformat}
> junit.framework.AssertionFailedError
>   at junit.framework.Assert.fail(Assert.java:55)
>   at junit.framework.Assert.assertTrue(Assert.java:22)
>   at junit.framework.Assert.assertTrue(Assert.java:31)
>   at junit.framework.TestCase.assertTrue(TestCase.java:201)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractLocalStoreSelfTest.testBackupRestore(GridCacheAbstractLocalStoreSelfTest.java:319)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractLocalStoreSelfTest.testBackupRestorePrimary(GridCacheAbstractLocalStoreSelfTest.java:285)
> {noformat}



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

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

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-:
---
Description: 

http://ci.ignite.apache.org/viewLog.html?buildId=675694=buildResultsDiv=Ignite20Tests_IgnitePds1#

Stacktrace indicates failure was in ignite code
{noformat}
[12:37:10][org.apache.ignite:ignite-core] 
[12:37:10][org.apache.ignite:ignite-core] Thread [name="main", id=1, 
state=RUNNABLE, blockCnt=254, waitCnt=281]
[12:37:10][org.apache.ignite:ignite-core] at 
sun.management.ThreadImpl.dumpThreads0(Native Method)
[12:37:10][org.apache.ignite:ignite-core] at 
sun.management.ThreadImpl.dumpAllThreads(ThreadImpl.java:446)
[12:37:10][org.apache.ignite:ignite-core] at 
o.a.i.i.util.IgniteUtils.dumpThreads(IgniteUtils.java:1272)
[12:37:10][org.apache.ignite:ignite-core] at 
o.a.i.testframework.junits.GridAbstractTest.runTest(GridAbstractTest.java:1937)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestCase.runBare(TestCase.java:141)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestResult$1.protect(TestResult.java:122)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestResult.runProtected(TestResult.java:142)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestResult.run(TestResult.java:125)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestCase.run(TestCase.java:129)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestSuite.runTest(TestSuite.java:255)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestSuite.run(TestSuite.java:250)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestSuite.runTest(TestSuite.java:255)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestSuite.run(TestSuite.java:250)
[12:37:10][org.apache.ignite:ignite-core] at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
{noformat}

  was:
http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-3580536643752440720=testDetails

http://ci.ignite.apache.org/viewLog.html?buildId=675694=buildResultsDiv=Ignite20Tests_IgnitePds1#

Stacktrace indicates failure was in ignite code
{noformat}
[12:37:10][org.apache.ignite:ignite-core] 
[12:37:10][org.apache.ignite:ignite-core] Thread [name="main", id=1, 
state=RUNNABLE, blockCnt=254, waitCnt=281]
[12:37:10][org.apache.ignite:ignite-core] at 
sun.management.ThreadImpl.dumpThreads0(Native Method)
[12:37:10][org.apache.ignite:ignite-core] at 
sun.management.ThreadImpl.dumpAllThreads(ThreadImpl.java:446)
[12:37:10][org.apache.ignite:ignite-core] at 
o.a.i.i.util.IgniteUtils.dumpThreads(IgniteUtils.java:1272)
[12:37:10][org.apache.ignite:ignite-core] at 
o.a.i.testframework.junits.GridAbstractTest.runTest(GridAbstractTest.java:1937)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestCase.runBare(TestCase.java:141)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestResult$1.protect(TestResult.java:122)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestResult.runProtected(TestResult.java:142)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestResult.run(TestResult.java:125)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestCase.run(TestCase.java:129)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestSuite.runTest(TestSuite.java:255)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestSuite.run(TestSuite.java:250)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestSuite.runTest(TestSuite.java:255)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestSuite.run(TestSuite.java:250)
[12:37:10][org.apache.ignite:ignite-core] at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
{noformat}


> Ignite PDS 1: JVM crash on teamcity (Rare)
> --
>
> Key: IGNITE-
> URL: https://issues.apache.org/jira/browse/IGNITE-
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>  Labels: MakeTeamcityGreenAgain, test-fail
> Attachments: crash_report, thread_dump
>
>
> http://ci.ignite.apache.org/viewLog.html?buildId=675694=buildResultsDiv=Ignite20Tests_IgnitePds1#
> Stacktrace indicates failure was in ignite code
> {noformat}
> [12:37:10][org.apache.ignite:ignite-core] 
> [12:37:10][org.apache.ignite:ignite-core] Thread [name="main", id=1, 
> state=RUNNABLE, blockCnt=254, waitCnt=281]
> [12:37:10][org.apache.ignite:ignite-core] at 
> sun.management.ThreadImpl.dumpThreads0(Native Method)
> 

[jira] [Updated] (IGNITE-5544) Ignite Cache: floating failure in testBackupRestore

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5544:
---
Description: 
http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-3580536643752440720=testDetails


http://ci.ignite.apache.org/viewLog.html?buildId=674133=buildResultsDiv=Ignite20Tests_IgniteCache#testNameId-3580536643752440720

GridCacheReplicatedLocalStoreSelfTest.testBackupRestorePrimary 
testBackupRestorePrimary
Has floating failure
Can be reproduced locally with run until failure, 7-10 runs required:
{noformat}
junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:55)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertTrue(Assert.java:31)
at junit.framework.TestCase.assertTrue(TestCase.java:201)
at 
org.apache.ignite.internal.processors.cache.GridCacheAbstractLocalStoreSelfTest.testBackupRestore(GridCacheAbstractLocalStoreSelfTest.java:319)
at 
org.apache.ignite.internal.processors.cache.GridCacheAbstractLocalStoreSelfTest.testBackupRestorePrimary(GridCacheAbstractLocalStoreSelfTest.java:285)
{noformat}


  was:
http://ci.ignite.apache.org/viewLog.html?buildId=674133=buildResultsDiv=Ignite20Tests_IgniteCache#testNameId-3580536643752440720

GridCacheReplicatedLocalStoreSelfTest.testBackupRestorePrimary 
testBackupRestorePrimary
Has floating failure
Can be reproduced locally with run until failure, 7-10 runs required:
{noformat}
junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:55)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertTrue(Assert.java:31)
at junit.framework.TestCase.assertTrue(TestCase.java:201)
at 
org.apache.ignite.internal.processors.cache.GridCacheAbstractLocalStoreSelfTest.testBackupRestore(GridCacheAbstractLocalStoreSelfTest.java:319)
at 
org.apache.ignite.internal.processors.cache.GridCacheAbstractLocalStoreSelfTest.testBackupRestorePrimary(GridCacheAbstractLocalStoreSelfTest.java:285)
{noformat}



> Ignite Cache: floating failure in testBackupRestore
> ---
>
> Key: IGNITE-5544
> URL: https://issues.apache.org/jira/browse/IGNITE-5544
> Project: Ignite
>  Issue Type: Test
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>  Labels: MakeTeamcityGreenAgain, test-fail
>
> http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-3580536643752440720=testDetails
> http://ci.ignite.apache.org/viewLog.html?buildId=674133=buildResultsDiv=Ignite20Tests_IgniteCache#testNameId-3580536643752440720
> GridCacheReplicatedLocalStoreSelfTest.testBackupRestorePrimary 
> testBackupRestorePrimary
> Has floating failure
> Can be reproduced locally with run until failure, 7-10 runs required:
> {noformat}
> junit.framework.AssertionFailedError
>   at junit.framework.Assert.fail(Assert.java:55)
>   at junit.framework.Assert.assertTrue(Assert.java:22)
>   at junit.framework.Assert.assertTrue(Assert.java:31)
>   at junit.framework.TestCase.assertTrue(TestCase.java:201)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractLocalStoreSelfTest.testBackupRestore(GridCacheAbstractLocalStoreSelfTest.java:319)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractLocalStoreSelfTest.testBackupRestorePrimary(GridCacheAbstractLocalStoreSelfTest.java:285)
> {noformat}



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

[jira] [Updated] (IGNITE-5544) Ignite Cache: floating failure in testBackupRestore

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5544:
---
Description: 
http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-3580536643752440720=testDetails

Success rate on TC - 83%

http://ci.ignite.apache.org/viewLog.html?buildId=674133=buildResultsDiv=Ignite20Tests_IgniteCache#testNameId-3580536643752440720

GridCacheReplicatedLocalStoreSelfTest.testBackupRestorePrimary 
testBackupRestorePrimary
Has floating failure
Can be reproduced locally with run until failure, 7-10 runs required:
{noformat}
junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:55)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertTrue(Assert.java:31)
at junit.framework.TestCase.assertTrue(TestCase.java:201)
at 
org.apache.ignite.internal.processors.cache.GridCacheAbstractLocalStoreSelfTest.testBackupRestore(GridCacheAbstractLocalStoreSelfTest.java:319)
at 
org.apache.ignite.internal.processors.cache.GridCacheAbstractLocalStoreSelfTest.testBackupRestorePrimary(GridCacheAbstractLocalStoreSelfTest.java:285)
{noformat}


  was:
http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-3580536643752440720=testDetails


http://ci.ignite.apache.org/viewLog.html?buildId=674133=buildResultsDiv=Ignite20Tests_IgniteCache#testNameId-3580536643752440720

GridCacheReplicatedLocalStoreSelfTest.testBackupRestorePrimary 
testBackupRestorePrimary
Has floating failure
Can be reproduced locally with run until failure, 7-10 runs required:
{noformat}
junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:55)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertTrue(Assert.java:31)
at junit.framework.TestCase.assertTrue(TestCase.java:201)
at 
org.apache.ignite.internal.processors.cache.GridCacheAbstractLocalStoreSelfTest.testBackupRestore(GridCacheAbstractLocalStoreSelfTest.java:319)
at 
org.apache.ignite.internal.processors.cache.GridCacheAbstractLocalStoreSelfTest.testBackupRestorePrimary(GridCacheAbstractLocalStoreSelfTest.java:285)
{noformat}



> Ignite Cache: floating failure in testBackupRestore
> ---
>
> Key: IGNITE-5544
> URL: https://issues.apache.org/jira/browse/IGNITE-5544
> Project: Ignite
>  Issue Type: Test
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>  Labels: MakeTeamcityGreenAgain, test-fail
>
> http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-3580536643752440720=testDetails
> Success rate on TC - 83%
> http://ci.ignite.apache.org/viewLog.html?buildId=674133=buildResultsDiv=Ignite20Tests_IgniteCache#testNameId-3580536643752440720
> GridCacheReplicatedLocalStoreSelfTest.testBackupRestorePrimary 
> testBackupRestorePrimary
> Has floating failure
> Can be reproduced locally with run until failure, 7-10 runs required:
> {noformat}
> junit.framework.AssertionFailedError
>   at junit.framework.Assert.fail(Assert.java:55)
>   at junit.framework.Assert.assertTrue(Assert.java:22)
>   at junit.framework.Assert.assertTrue(Assert.java:31)
>   at junit.framework.TestCase.assertTrue(TestCase.java:201)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractLocalStoreSelfTest.testBackupRestore(GridCacheAbstractLocalStoreSelfTest.java:319)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractLocalStoreSelfTest.testBackupRestorePrimary(GridCacheAbstractLocalStoreSelfTest.java:285)
> {noformat}



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

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

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-:
---
Description: 
http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-3580536643752440720=testDetails

http://ci.ignite.apache.org/viewLog.html?buildId=675694=buildResultsDiv=Ignite20Tests_IgnitePds1#

Stacktrace indicates failure was in ignite code
{noformat}
[12:37:10][org.apache.ignite:ignite-core] 
[12:37:10][org.apache.ignite:ignite-core] Thread [name="main", id=1, 
state=RUNNABLE, blockCnt=254, waitCnt=281]
[12:37:10][org.apache.ignite:ignite-core] at 
sun.management.ThreadImpl.dumpThreads0(Native Method)
[12:37:10][org.apache.ignite:ignite-core] at 
sun.management.ThreadImpl.dumpAllThreads(ThreadImpl.java:446)
[12:37:10][org.apache.ignite:ignite-core] at 
o.a.i.i.util.IgniteUtils.dumpThreads(IgniteUtils.java:1272)
[12:37:10][org.apache.ignite:ignite-core] at 
o.a.i.testframework.junits.GridAbstractTest.runTest(GridAbstractTest.java:1937)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestCase.runBare(TestCase.java:141)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestResult$1.protect(TestResult.java:122)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestResult.runProtected(TestResult.java:142)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestResult.run(TestResult.java:125)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestCase.run(TestCase.java:129)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestSuite.runTest(TestSuite.java:255)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestSuite.run(TestSuite.java:250)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestSuite.runTest(TestSuite.java:255)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestSuite.run(TestSuite.java:250)
[12:37:10][org.apache.ignite:ignite-core] at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
{noformat}

  was:
http://ci.ignite.apache.org/viewLog.html?buildId=675694=buildResultsDiv=Ignite20Tests_IgnitePds1#

Stacktrace indicates failure was in ignite code
{noformat}
[12:37:10][org.apache.ignite:ignite-core] 
[12:37:10][org.apache.ignite:ignite-core] Thread [name="main", id=1, 
state=RUNNABLE, blockCnt=254, waitCnt=281]
[12:37:10][org.apache.ignite:ignite-core] at 
sun.management.ThreadImpl.dumpThreads0(Native Method)
[12:37:10][org.apache.ignite:ignite-core] at 
sun.management.ThreadImpl.dumpAllThreads(ThreadImpl.java:446)
[12:37:10][org.apache.ignite:ignite-core] at 
o.a.i.i.util.IgniteUtils.dumpThreads(IgniteUtils.java:1272)
[12:37:10][org.apache.ignite:ignite-core] at 
o.a.i.testframework.junits.GridAbstractTest.runTest(GridAbstractTest.java:1937)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestCase.runBare(TestCase.java:141)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestResult$1.protect(TestResult.java:122)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestResult.runProtected(TestResult.java:142)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestResult.run(TestResult.java:125)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestCase.run(TestCase.java:129)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestSuite.runTest(TestSuite.java:255)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestSuite.run(TestSuite.java:250)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestSuite.runTest(TestSuite.java:255)
[12:37:10][org.apache.ignite:ignite-core] at 
junit.framework.TestSuite.run(TestSuite.java:250)
[12:37:10][org.apache.ignite:ignite-core] at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
{noformat}


> Ignite PDS 1: JVM crash on teamcity (Rare)
> --
>
> Key: IGNITE-
> URL: https://issues.apache.org/jira/browse/IGNITE-
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>  Labels: MakeTeamcityGreenAgain, test-fail
> Attachments: crash_report, thread_dump
>
>
> http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-3580536643752440720=testDetails
> http://ci.ignite.apache.org/viewLog.html?buildId=675694=buildResultsDiv=Ignite20Tests_IgnitePds1#
> Stacktrace indicates failure was in ignite code
> {noformat}
> [12:37:10][org.apache.ignite:ignite-core] 
> [12:37:10][org.apache.ignite:ignite-core] Thread [name="main", id=1, 
> state=RUNNABLE, blockCnt=254, waitCnt=281]
> 

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

[Dmitriy Pavlov (JIRA)]

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

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

> Ignite PDS 1: JVM crash on teamcity (Rare)
> --
>
> Key: IGNITE-
> URL: https://issues.apache.org/jira/browse/IGNITE-
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>  Labels: MakeTeamcityGreenAgain, test-fail
> Attachments: crash_report, thread_dump
>
>
> http://ci.ignite.apache.org/viewLog.html?buildId=675694=buildResultsDiv=Ignite20Tests_IgnitePds1#
> Stacktrace indicates failure was in ignite code
> {noformat}
> [12:37:10][org.apache.ignite:ignite-core] 
> [12:37:10][org.apache.ignite:ignite-core] Thread [name="main", id=1, 
> state=RUNNABLE, blockCnt=254, waitCnt=281]
> [12:37:10][org.apache.ignite:ignite-core] at 
> sun.management.ThreadImpl.dumpThreads0(Native Method)
> [12:37:10][org.apache.ignite:ignite-core] at 
> sun.management.ThreadImpl.dumpAllThreads(ThreadImpl.java:446)
> [12:37:10][org.apache.ignite:ignite-core] at 
> o.a.i.i.util.IgniteUtils.dumpThreads(IgniteUtils.java:1272)
> [12:37:10][org.apache.ignite:ignite-core] at 
> o.a.i.testframework.junits.GridAbstractTest.runTest(GridAbstractTest.java:1937)
> [12:37:10][org.apache.ignite:ignite-core] at 
> junit.framework.TestCase.runBare(TestCase.java:141)
> [12:37:10][org.apache.ignite:ignite-core] at 
> junit.framework.TestResult$1.protect(TestResult.java:122)
> [12:37:10][org.apache.ignite:ignite-core] at 
> junit.framework.TestResult.runProtected(TestResult.java:142)
> [12:37:10][org.apache.ignite:ignite-core] at 
> junit.framework.TestResult.run(TestResult.java:125)
> [12:37:10][org.apache.ignite:ignite-core] at 
> junit.framework.TestCase.run(TestCase.java:129)
> [12:37:10][org.apache.ignite:ignite-core] at 
> junit.framework.TestSuite.runTest(TestSuite.java:255)
> [12:37:10][org.apache.ignite:ignite-core] at 
> junit.framework.TestSuite.run(TestSuite.java:250)
> [12:37:10][org.apache.ignite:ignite-core] at 
> junit.framework.TestSuite.runTest(TestSuite.java:255)
> [12:37:10][org.apache.ignite:ignite-core] at 
> junit.framework.TestSuite.run(TestSuite.java:250)
> [12:37:10][org.apache.ignite:ignite-core] at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> {noformat}



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

[jira] [Updated] (IGNITE-5897) Ignite Cache Full API Multi JVM: 7 test failed in master

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5897:
---
Affects Version/s: 2.2

> Ignite Cache Full API Multi JVM: 7 test failed in master
> 
>
> Key: IGNITE-5897
> URL: https://issues.apache.org/jira/browse/IGNITE-5897
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Dmitriy Pavlov
>Assignee: Nikolay Izhikov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Failure on TC: 
> http://ci.ignite.apache.org/viewLog.html?buildId=749671=buildResultsDiv=Ignite20Tests_IgniteCacheFullApiMultiJvm#testNameId-6305397409161667157
> org.apache.ignite.internal.processors.cache.multijvm (7)
> - 
> GridCachePartitionedNearDisabledMultiJvmFullApiSelfTest.testTransformResourceInjection
>   
> - 
> GridCachePartitionedNearDisabledMultiJvmP2PDisabledFullApiSelfTest.testTransformResourceInjection
>
> - 
> GridCachePartitionedNearDisabledOnheapMultiJvmFullApiSelfTest.testTransformResourceInjection
> 
> - GridCacheReplicatedMultiJvmFullApiSelfTest.testTransformResourceInjection   
> - 
> GridCacheReplicatedMultiJvmP2PDisabledFullApiSelfTest.testTransformResourceInjection
> 
> - 
> GridCacheReplicatedNearOnlyMultiJvmFullApiSelfTest.testTransformResourceInjection
>
> - 
> GridCacheReplicatedOnheapMultiJvmFullApiSelfTest.testTransformResourceInjection
>  
> Stable reproducible locally
> First failure changes:
> http://ci.ignite.apache.org/viewLog.html?buildId=727280=buildChangesDiv=Ignite20Tests_IgniteCacheFullApiMultiJvm
> {noformat}
> IGNITE-5753: CPP Memory leak fixed.   Igor Sapego 
> IGNITE-5444: Collections.singletonList is not properly serialized by binary 
> marshaller. This closes #2217.andrey.mashenkov 
> ignite-5722 Cache entries stay in onheap after scan query execution for 
> OFFHEAP_TIRED cache with expiry policyAndrey Gura 
> ignite-5489 Fixed possible connection leaks when loadPreviousValue set to 
> truetikhonovnicolay 
> IGNITE-4831: Add an option to disable MBeans. This closes #2265.  
> andrey.mashenkov   
> {noformat}
> Stacktrace: 
> {noformat}
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea] class 
> org.apache.ignite.IgniteCheckedException: java.lang.NullPointerException
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadFromStore(GridCacheStoreManagerAdapter.java:327)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.load(GridCacheStoreManagerAdapter.java:282)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.readThrough(GridCacheMapEntry.java:445)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerGet0(GridCacheMapEntry.java:699)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerGet(GridCacheMapEntry.java:461)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.onEntriesLocked(GridDhtTxPrepareFuture.java:389)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare0(GridDhtTxPrepareFuture.java:1213)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.mapIfLocked(GridDhtTxPrepareFuture.java:668)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare(GridDhtTxPrepareFuture.java:1034)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.prepareAsync(GridDhtTxLocal.java:410)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareNearTx(IgniteTxHandler.java:459)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest(IgniteTxHandler.java:121)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$000(IgniteTxHandler.java:95)
> [2017-08-01 

[jira] [Updated] (IGNITE-5914) Web console: improve importing model from DB

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-5914:
---
Summary: Web console: improve importing model from DB  (was: Web console: 
incorrect cache mode in case if cache was created during importing  model from 
DB)

> Web console: improve importing model from DB
> 
>
> Key: IGNITE-5914
> URL: https://issues.apache.org/jira/browse/IGNITE-5914
> Project: Ignite
>  Issue Type: Wish
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 2.2
>
>
> I set mode = Replicated, but after import cache has Partitioned mode



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

[jira] [Updated] (IGNITE-5842) ODBC: Make sure ODBC driver works correctly with RazorSQL.

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-5842:

Fix Version/s: 2.2

> ODBC: Make sure ODBC driver works correctly with RazorSQL.
> --
>
> Key: IGNITE-5842
> URL: https://issues.apache.org/jira/browse/IGNITE-5842
> Project: Ignite
>  Issue Type: Improvement
>  Components: odbc
>Affects Versions: 2.0
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: odbc
> Fix For: 2.2
>
>
> Users often try to use ODBC driver to connect to Ignite with RazorSQL. 
> However, it can't be used with our driver, as it tries to configure driver to 
> act according to unsupported ODBC version. Here is the log:
> {noformat}
> razorsql12d8-1374 ENTER SQLAllocEnv 
>   HENV *  0x2FBEECB0
> razorsql12d8-1374 EXIT  SQLAllocEnv  with return code 0 
> (SQL_SUCCESS)
>   HENV *  0x2FBEECB0 ( 0x003DE650)
> razorsql12d8-1374 ENTER SQLAllocConnect 
>   HENV0x003DE650
>   HDBC *  0x2FBEEC10
> razorsql12d8-1374 EXIT  SQLAllocConnect  with return code 0 
> (SQL_SUCCESS)
>   HENV0x003DE650
>   HDBC *  0x2FBEEC10 ( 0x003DE6D0)
> razorsql12d8-1374 ENTER SQLSetConnectOption 
>   HDBC0x003DE6D0
>   SQLINTEGER 103 
>   SQLPOINTER35
> razorsql12d8-1374 EXIT  SQLSetConnectOption  with return code 0 
> (SQL_SUCCESS)
>   HDBC0x003DE6D0
>   SQLINTEGER 103 
>   SQLPOINTER35
> razorsql12d8-1374 ENTER SQLDriverConnectW 
>   HDBC0x003DE6D0
>   HWND0x
>   WCHAR * 0x6F861F7C [  -3] "**\ 0"
>   SWORD   -3 
>   WCHAR * 0x6F861F7C 
>   SWORD   -3 
>   SWORD * 0x
>   UWORD0 
> razorsql12d8-1374 EXIT  SQLDriverConnectW  with return code -1 
> (SQL_ERROR)
>   HDBC0x003DE6D0
>   HWND0x
>   WCHAR * 0x6F861F7C [  -3] "**\ 0"
>   SWORD   -3 
>   WCHAR * 0x6F861F7C 
>   SWORD   -3 
>   SWORD * 0x
>   UWORD0 
>   DIAG [S1000] ODBC version is not supported. (0) 
>   DIAG [08001] Failed to establish connection with the host. (0) 
> razorsql12d8-1374 ENTER SQLErrorW 
>   HENV0x
>   HDBC0x003DE6D0
>   HSTMT   0x
>   WCHAR * 0x2FBEEAF4
>   SDWORD *0x2FBEEB3C
>   WCHAR * 0x2FBEE6F4 
>   SWORD  300 
>   SWORD * 0x2FBEEB38
> razorsql12d8-1374 EXIT  SQLErrorW  with return code 0 
> (SQL_SUCCESS)
>   HENV0x
>   HDBC0x003DE6D0
>   HSTMT   0x
>   WCHAR * 0x2FBEEAF4 [   5] "S1000"
>   SDWORD *0x2FBEEB3C (0)
>   WCHAR * 0x2FBEE6F4 [  30] "ODBC version is not 
> supported."
>   SWORD  300 
>   SWORD * 0x2FBEEB38 (30)
> razorsql12d8-1374 ENTER SQLErrorW 
>   HENV0x
>   HDBC0x003DE6D0
>   HSTMT   0x
>   WCHAR * 0x2FBEEAF4
>   SDWORD *0x2FBEEB3C
>   WCHAR * 0x2FBEE6F4 
>   SWORD  300 
>   SWORD * 0x2FBEEB38
> razorsql12d8-1374 EXIT  SQLErrorW  with return code 0 
> (SQL_SUCCESS)
>   HENV0x
>   HDBC0x003DE6D0
>   HSTMT   0x
>   WCHAR * 0x2FBEEAF4 [   5] "08001"
>   SDWORD *0x2FBEEB3C (0)
>   WCHAR * 0x2FBEE6F4 [  45] "Failed to establish 
> connection with the host."
>   SWORD  300 
>   SWORD * 0x2FBEEB38 

[jira] [Created] (IGNITE-5915) Add more clear WAL mode documentation and print a warning when NONE mode is used

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5915:


 Summary: Add more clear WAL mode documentation and print a warning 
when NONE mode is used
 Key: IGNITE-5915
 URL: https://issues.apache.org/jira/browse/IGNITE-5915
 Project: Ignite
  Issue Type: Improvement
  Components: persistence
Affects Versions: 2.1
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
 Fix For: 2.2


Describe which guarantees each WAL mode gives and print a warning when NONE is 
used.



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

[jira] [Updated] (IGNITE-5914) Web console: incorrect cache mode in case if cache was created during importing model from DB

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-5914:
---
Issue Type: Wish  (was: Bug)

> Web console: incorrect cache mode in case if cache was created during 
> importing  model from DB
> --
>
> Key: IGNITE-5914
> URL: https://issues.apache.org/jira/browse/IGNITE-5914
> Project: Ignite
>  Issue Type: Wish
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 2.2
>
>
> I set mode = Replicated, but after import cache has Partitioned mode



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

[jira] [Comment Edited] (IGNITE-5914) Web console: incorrect cache mode in case if cache was created during importing model from DB

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov edited comment on IGNITE-5914 at 8/3/17 9:19 AM:


I  understood what is the reason of this error - I didn't click on 'Apply' 
button - this is inconveniently.
I suggest to do Apply button inactive initially and make it active only if user 
changed one of the field. Also please add warring message that Apply was not 
clicked.


was (Author: pkonstantinov):
I  understood what is the reason of this error - I didn't click on 'Apply' 
button - this is inconveniently.
I suggest to do Apply button inactive and make it active if user changed one of 
the field.

> Web console: incorrect cache mode in case if cache was created during 
> importing  model from DB
> --
>
> Key: IGNITE-5914
> URL: https://issues.apache.org/jira/browse/IGNITE-5914
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
> Fix For: 2.2
>
>
> I set mode = Replicated, but after import cache has Partitioned mode



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

[jira] [Updated] (IGNITE-5914) Web console: incorrect cache mode in case if cache was created during importing model from DB

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-5914:
---
Priority: Minor  (was: Major)

> Web console: incorrect cache mode in case if cache was created during 
> importing  model from DB
> --
>
> Key: IGNITE-5914
> URL: https://issues.apache.org/jira/browse/IGNITE-5914
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 2.2
>
>
> I set mode = Replicated, but after import cache has Partitioned mode



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

[jira] [Commented] (IGNITE-5914) Web console: incorrect cache mode in case if cache was created during importing model from DB

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-5914:


I  understood what is the reason of this error - I didn't click on 'Apply' 
button - this is inconveniently.
I suggest to do Apply button inactive and make it active if user changed one of 
the field.

> Web console: incorrect cache mode in case if cache was created during 
> importing  model from DB
> --
>
> Key: IGNITE-5914
> URL: https://issues.apache.org/jira/browse/IGNITE-5914
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
> Fix For: 2.2
>
>
> I set mode = Replicated, but after import cache has Partitioned mode



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

[jira] [Assigned] (IGNITE-5914) Web console: incorrect cache mode in case if cache was created during importing model from DB

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-5914:


Assignee: Alexey Kuznetsov

> Web console: incorrect cache mode in case if cache was created during 
> importing  model from DB
> --
>
> Key: IGNITE-5914
> URL: https://issues.apache.org/jira/browse/IGNITE-5914
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
> Fix For: 2.2
>
>
> I set mode = Replicated, but after import cache has Partitioned mode



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

[jira] [Created] (IGNITE-5914) Web console: incorrect cache mode in case if cache was created during importing model from DB

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-5914:
--

 Summary: Web console: incorrect cache mode in case if cache was 
created during importing  model from DB
 Key: IGNITE-5914
 URL: https://issues.apache.org/jira/browse/IGNITE-5914
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Pavel Konstantinov
 Fix For: 2.2


I set mode = Replicated, but after import cache has Partitioned mode



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

[jira] [Commented] (IGNITE-5897) Ignite Cache Full API Multi JVM: 7 test failed in master

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-5897:
-

[~dpavlov] I fix this bug. Who can review my changes?
TC run in progress.

> Ignite Cache Full API Multi JVM: 7 test failed in master
> 
>
> Key: IGNITE-5897
> URL: https://issues.apache.org/jira/browse/IGNITE-5897
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Nikolay Izhikov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Failure on TC: 
> http://ci.ignite.apache.org/viewLog.html?buildId=749671=buildResultsDiv=Ignite20Tests_IgniteCacheFullApiMultiJvm#testNameId-6305397409161667157
> org.apache.ignite.internal.processors.cache.multijvm (7)
> - 
> GridCachePartitionedNearDisabledMultiJvmFullApiSelfTest.testTransformResourceInjection
>   
> - 
> GridCachePartitionedNearDisabledMultiJvmP2PDisabledFullApiSelfTest.testTransformResourceInjection
>
> - 
> GridCachePartitionedNearDisabledOnheapMultiJvmFullApiSelfTest.testTransformResourceInjection
> 
> - GridCacheReplicatedMultiJvmFullApiSelfTest.testTransformResourceInjection   
> - 
> GridCacheReplicatedMultiJvmP2PDisabledFullApiSelfTest.testTransformResourceInjection
> 
> - 
> GridCacheReplicatedNearOnlyMultiJvmFullApiSelfTest.testTransformResourceInjection
>
> - 
> GridCacheReplicatedOnheapMultiJvmFullApiSelfTest.testTransformResourceInjection
>  
> Stable reproducible locally
> First failure changes:
> http://ci.ignite.apache.org/viewLog.html?buildId=727280=buildChangesDiv=Ignite20Tests_IgniteCacheFullApiMultiJvm
> {noformat}
> IGNITE-5753: CPP Memory leak fixed.   Igor Sapego 
> IGNITE-5444: Collections.singletonList is not properly serialized by binary 
> marshaller. This closes #2217.andrey.mashenkov 
> ignite-5722 Cache entries stay in onheap after scan query execution for 
> OFFHEAP_TIRED cache with expiry policyAndrey Gura 
> ignite-5489 Fixed possible connection leaks when loadPreviousValue set to 
> truetikhonovnicolay 
> IGNITE-4831: Add an option to disable MBeans. This closes #2265.  
> andrey.mashenkov   
> {noformat}
> Stacktrace: 
> {noformat}
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea] class 
> org.apache.ignite.IgniteCheckedException: java.lang.NullPointerException
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadFromStore(GridCacheStoreManagerAdapter.java:327)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.load(GridCacheStoreManagerAdapter.java:282)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.readThrough(GridCacheMapEntry.java:445)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerGet0(GridCacheMapEntry.java:699)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerGet(GridCacheMapEntry.java:461)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.onEntriesLocked(GridDhtTxPrepareFuture.java:389)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare0(GridDhtTxPrepareFuture.java:1213)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.mapIfLocked(GridDhtTxPrepareFuture.java:668)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare(GridDhtTxPrepareFuture.java:1034)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.prepareAsync(GridDhtTxLocal.java:410)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareNearTx(IgniteTxHandler.java:459)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest(IgniteTxHandler.java:121)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> 

[jira] [Commented] (IGNITE-5912) [Redis] EXPIRE/PEXPIRE on keys

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5912:


GitHub user shroman opened a pull request:

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

IGNITE-5912: Redis EXPIRE/PEXPIRE commands.



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

$ git pull https://github.com/shroman/ignite IGNITE-5912

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

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


commit 696c1613d41c741a66241da6214559f2f5dd1494
Author: shroman 
Date:   2017-08-03T07:59:50Z

IGNITE-5912: Redis EXPIRE/PEXPIRE commands.

commit 0c86dc18d55749df6e1d2282a2edd222c0330833
Author: shroman 
Date:   2017-08-03T08:08:18Z

IGNITE-5912: Redis EXPIRE/PEXPIRE commands. Replaced lambdas with anonymous 
classes for Java 7.




> [Redis] EXPIRE/PEXPIRE on keys
> --
>
> Key: IGNITE-5912
> URL: https://issues.apache.org/jira/browse/IGNITE-5912
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> https://redis.io/commands/expire
> https://redis.io/commands/pexpire



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

[jira] [Created] (IGNITE-5913) Web console: code (spring\java) is not generated for field 'Long query timeout:' on cluster level in Miscellaneous group

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-5913:
--

 Summary: Web console: code (spring\java) is not generated for 
field 'Long query timeout:' on cluster level in Miscellaneous group
 Key: IGNITE-5913
 URL: https://issues.apache.org/jira/browse/IGNITE-5913
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Pavel Konstantinov
Priority: Minor
 Fix For: 2.2


It exists in Summary but not generated in Miscellaneous group 



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

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

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur reassigned IGNITE-2894:
--

Assignee: Vyacheslav Daradur  (was: Amelchev Nikita)

> 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: Vyacheslav Daradur
>Priority: Critical
>  Labels: community, customer
> Fix For: 2.2
>
>
> 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] [Assigned] (IGNITE-2894) Binary object inside of Externalizable still serialized with OptimizedMarshaller

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur reassigned IGNITE-2894:
--

Assignee: Amelchev Nikita  (was: Vyacheslav Daradur)

> 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
> Fix For: 2.2
>
>
> 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] [Created] (IGNITE-5912) [Redis] EXPIRE/PEXPIRE on keys

[Roman Shtykh (JIRA)]

Roman Shtykh created IGNITE-5912:


 Summary: [Redis] EXPIRE/PEXPIRE on keys
 Key: IGNITE-5912
 URL: https://issues.apache.org/jira/browse/IGNITE-5912
 Project: Ignite
  Issue Type: New Feature
Reporter: Roman Shtykh
Assignee: Roman Shtykh


https://redis.io/commands/expire
https://redis.io/commands/pexpire



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

[jira] [Created] (IGNITE-5911) .NET: EntityFramework cache eager update

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5911:
--

 Summary: .NET: EntityFramework cache eager update
 Key: IGNITE-5911
 URL: https://issues.apache.org/jira/browse/IGNITE-5911
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn


Ignite EntityFramework 2nd level cache invalidates cache entries when one of 
the related entity sets has been updated.

We can add an option to re-run affected queries and populate invalidated 
entries eagerly so that user queries hit the cache right away.

Command text is already stored as part of the cache key, so 
{{DbCache.InvalidateSets}} could retrieve affected keys and run queries.

User list thread:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-NET-and-Entityframework-refresh-cached-queries-instead-of-invalidating-it-td15916.html



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

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

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur updated IGNITE-5910:
---
Description: 
{code:title=Exception at call}
java.lang.ClassCastException: 
org.apache.ignite.testframework.junits.multijvm.IgniteProcessProxy cannot be 
cast to org.apache.ignite.internal.IgniteKernal
{code}

{code:title=Reproducer snippet}
/** {@inheritDoc} */
@Override protected boolean isMultiJvm() {
return true;
}

/**
 * @throws Exception If failed.
 */
public void testGrid() throws Exception {
try {
startGrid(0);

startGrid(1);
}
finally {
stopGrid(1);

stopGrid(0);
}
}
{code}

  was:
{code:title=Exception at call}
java.lang.ClassCastException: 
org.apache.ignite.testframework.junits.multijvm.IgniteProcessProxy cannot be 
cast to org.apache.ignite.internal.IgniteKernal
{code}

{code:title=Reproducer snippet}
/** {@inheritDoc} */
@Override protected boolean isMultiJvm() {
return true;
}

/**
 * @throws Exception If failed.
 */
public void testGrid() throws Exception {
try {
startGrid(0);

startGrid(1);
}
finally {
stopGrid(1);

stopGrid(0);
}
}
{code}


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



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

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

[Vyacheslav Daradur (JIRA)]

Vyacheslav Daradur created IGNITE-5910:
--

 Summary: Method stopGrid(name) doesn't work in multiJvm mode
 Key: IGNITE-5910
 URL: https://issues.apache.org/jira/browse/IGNITE-5910
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Vyacheslav Daradur
Assignee: Vyacheslav Daradur
 Fix For: 2.2


{code:title=Exception at call}
java.lang.ClassCastException: 
org.apache.ignite.testframework.junits.multijvm.IgniteProcessProxy cannot be 
cast to org.apache.ignite.internal.IgniteKernal
{code}

{code:title=Reproducer snippet}
/** {@inheritDoc} */
@Override protected boolean isMultiJvm() {
return true;
}

/**
 * @throws Exception If failed.
 */
public void testGrid() throws Exception {
try {
startGrid(0);

startGrid(1);
}
finally {
stopGrid(1);

stopGrid(0);
}
}
{code}



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

[jira] [Updated] (IGNITE-5909) Web console: Implement editable list

[Dmitriy Shabalin (JIRA)]

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

Dmitriy Shabalin updated IGNITE-5909:
-
Attachment: screenshot-1.png

> Web console: Implement editable list
> 
>
> Key: IGNITE-5909
> URL: https://issues.apache.org/jira/browse/IGNITE-5909
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Dmitriy Shabalin
> Fix For: 2.2
>
> Attachments: screenshot-1.png
>
>




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