[jira] [Commented] (IGNITE-4907) Excessive service instances can be started with dynamic deployment.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4907:


Github user AMashenkov closed the pull request at:

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


> Excessive service instances can be started with dynamic deployment.
> ---
>
> Key: IGNITE-4907
> URL: https://issues.apache.org/jira/browse/IGNITE-4907
> Project: Ignite
>  Issue Type: Bug
>  Components: managed services
>Affects Versions: 1.9
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>  Labels: user-experience
> Fix For: 2.0
>
> Attachments: ServiceDeploymentBug.java
>
>
> More than needed service instances can be started when service deployed 
> dynamicly. 
> For next service configuration all 3 instances will be started even if 
> cluster has 2 ignites nodes only:
>   cfg.setMaxPerNodeCount(1);
>   cfg.setTotalCount(3);
> See for details: 
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-may-start-more-service-instances-per-node-than-maxPerNodeCount-in-case-of-manual-redeploy-td11661.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-4993) Distributed join on partitioned caches with segmented indices broken in master.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-4993:


 Summary: Distributed join on partitioned caches with segmented 
indices broken in master.
 Key: IGNITE-4993
 URL: https://issues.apache.org/jira/browse/IGNITE-4993
 Project: Ignite
  Issue Type: Bug
  Components: SQL
Reporter: Andrew Mashenkov
 Fix For: 2.0


Next test fails in master sporadicaly:
org.apache.ignite.internal.processors.query.IgniteSqlSegmentedIndexSelfTest.testMultiNodeIndexSegmentation

Test looks fine on commit before IGNITE-3477 merged to master.
Seems, there is a race.

[20:14:51,340][ERROR][query-#162%query.IgniteSqlSegmentedIndexMultiNodeSelfTest0%][GridMapQueryExecutor]
 Failed to execute local query.
class org.apache.ignite.cache.query.QueryCancelledException: The query was 
cancelled while executing.
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest0(GridMapQueryExecutor.java:610)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.access$400(GridMapQueryExecutor.java:99)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor$5.call(GridMapQueryExecutor.java:433)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor$5.call(GridMapQueryExecutor.java:431)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6601)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:914)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4992) Fix Segmented SQL Index self tests.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov commented on IGNITE-4992:
--

I've fixed flacky tests.

Test testMultiNodeIndexSegmentation failed on TC on multi-node grid in master.
I've check test works fine on commit 7e106cd right before IGNITE-3477 was 
merged.

Look like there is a bug in master.


> Fix Segmented SQL Index self tests.
> ---
>
> Key: IGNITE-4992
> URL: https://issues.apache.org/jira/browse/IGNITE-4992
> Project: Ignite
>  Issue Type: Test
>  Components: SQL
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>  Labels: flaky
> Fix For: 2.0
>
>
> Flacky tests:
> org.apache.ignite.internal.processors.query.IgniteSqlSegmentedIndexSelfTest.testMultiNodeIndexSegmentation
> org.apache.ignite.internal.processors.query.IgniteSqlSegmentedIndexSelfTest.testSingleNodeIndexSegmentationWithSwapEnabled



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4927) Write behind - add an option to skip write coalescing

[Alexander Belyak (JIRA)]

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

Alexander Belyak commented on IGNITE-4927:
--

Rewrite solution again to increase and smooth out write speed. Waiting for TC 
tests.

> Write behind - add an option to skip write coalescing
> -
>
> Key: IGNITE-4927
> URL: https://issues.apache.org/jira/browse/IGNITE-4927
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 1.9
>Reporter: Yakov Zhdanov
>Assignee: Yakov Zhdanov
> Fix For: 2.0
>
>
> Currently, the write-behind store is backed by a map, therefore when several 
> updates come to the same key, they are coalesced. 
> We need to introduce optional mode and back write-behind with a queue and 
> pass each  to a database.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-1561) Cross cache tx tests with near cache fail with asserts

[Semen Boikov (JIRA)]

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

Semen Boikov commented on IGNITE-1561:
--

So far Identified these issues:
- we should not allow onePhase commit if tx has cache with near cache (since we 
do not know in advance if there are near caches to update)
- GridNearPessimisticTxPrepareFuture maps requests using  
key, so it can send multiple concurrent near prepare requests on the same node 
which breaks internal logic. Actually it seems there is no need to create 
separate near prepare requests for near cache entries  (the same mapping issue 
exists for others near prepare futures)

> Cross cache tx tests with near cache fail with asserts
> --
>
> Key: IGNITE-1561
> URL: https://issues.apache.org/jira/browse/IGNITE-1561
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: 2.1
>
>
> I added in master cross cache txs test from ignite-80 branch 
> (IgniteCrossCacheTxNearEnabledSelfTest), it fails with various asserts, e.g.:
> {noformat}
> java.lang.AssertionError
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxMapping.initLast(GridDhtTxMapping.java:86)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepare(GridNearOptimisticTxPrepareFuture.java:544)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepare0(GridNearOptimisticTxPrepareFuture.java:452)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepareOnTopology(GridNearOptimisticTxPrepareFuture.java:341)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepare(GridNearOptimisticTxPrepareFuture.java:279)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.prepareAsync(GridNearTxLocal.java:758)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.commitAsync(GridNearTxLocal.java:769)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheSharedContext.commitTxAsync(GridCacheSharedContext.java:642)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.TransactionProxyImpl.commit(TransactionProxyImpl.java:256)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteCrossCacheTxSelfTest.checkTxsSingleOp(IgniteCrossCacheTxSelfTest.java:170)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteCrossCacheTxSelfTest.testOptimisticRepeatableRead(IgniteCrossCacheTxSelfTest.java:136)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
> {noformat}
> Test pass is near cache is disabled (added separate test for this mode: 
> IgniteCrossCacheTxSelfTest).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-4501) Improvement of connection in a cluster of new node

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov edited comment on IGNITE-4501 at 4/14/17 3:58 PM:


Alexander, you are right. Before your change new node has always been placed 
right before the coordinator. 

Did you manage to fix this? I think clearing discovery data on the node right 
before coordinator node may work.

I see one more point here. If new node is placed in the middle of the ring then 
(with current approach) it finishes its start before the rest of the ring 
(after new node to coordinator) have fired NODE_ADDED_EVT for it. Probably, we 
will need to reapproach joining process.


was (Author: yzhdanov):
Alexander, you are right. Before your change new node has always been placed 
right before the coordinator. 

Did you manage to fix this? I think clearing discovery data on the node right 
before coordinator node.

I see one more point here. If new node is placed in the middle of the ring then 
(with current approach) it finishes its start before the rest of the ring 
(after new node to coordinator) have fired NODE_ADDED_EVT for it. Probably, we 
will need to reapproach joining process.

> Improvement of connection in a cluster of new node
> --
>
> Key: IGNITE-4501
> URL: https://issues.apache.org/jira/browse/IGNITE-4501
> Project: Ignite
>  Issue Type: Improvement
>  Components: messaging
>Affects Versions: 1.8
>Reporter: Vyacheslav Daradur
>Assignee: Alexander Menshikov
> Fix For: 2.0
>
>
> h3. Main description:
> Cluster nodes connect a ring.
> For example: we have 6 nodes: A, B, C, D, E, F. 
> They can connect a ring in any possible way: A-B-C-D-E-F-A, or A-F-B-E-C-D-A, 
> etc.
> If some node leaves topology, adjacent nodes must reconnect. 
> If nodes A, B, C are in same physical place, nodes D, E, F are in other 
> place, and places lost connect each other, we will have many ways of 
> reconnections.
> At best case, if we had a ring: A-B-CxD-E-FxA ('x' means disconnect) -- then 
> we have only one reconnect (C
> will be connected to A or F will be connected to D -- depends on what part of 
> the cluster was alive.
> Also, if we had a not ring: AxFxBxExCxDxA -- then we have a lot of 
> reconnections (A to B, B to C, C to A -- in general n/2 reconnections, where 
> n -- number of nodes). 
> h3. Approach:
> It is necessary to develop approach of node insertion to the correct place 
> for creation of the correct ring-topology.
> h3. Solutions:
> Main idea is a sorting according to latency.
> * group nodes in arcs on an ARC_ID. (manualy?)
> * implement NodeComparator (nodes on the same host : nodes on the same subnet 
> : other nodes). We will use it when we connect a new node.
> * [dev list 
> thread|http://mail-archives.apache.org/mod_mbox/ignite-dev/201612.mbox/%3CCAN+WSNyWYXSXEBpGErVt72zTgi2pTQzUWLv8JY=ke83-5-r...@mail.gmail.com%3E]
> Update Dec, 29 Yakov Zhdanov:
> # introduce CLUSTER_REGION_ID node attribute. This can be done by adding 
> public static final constant to TcpDiscoverySpi.
> # Alter 
> org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNodesRing#nextNode(java.util.Collection)
>  to order basing on per node attribute value
> # Node comparison should be stable and consistent. E.g. if CLUSTER_REGION_IDs 
> are equal then we should compare nodes' IDs. This way we have consistent 
> order on all nodes in topology.
> # Also nextNode() has to group nodes on same host and in same subnet. This 
> can be postponed and implemented after we have other points done.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4501) Improvement of connection in a cluster of new node

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov commented on IGNITE-4501:
---

Alexander, you are right. Before your change new node has always been placed 
right before the coordinator. 

Did you manage to fix this? I think clearing discovery data on the node right 
before coordinator node.

I see one more point here. If new node is placed in the middle of the ring then 
(with current approach) it finishes its start before the rest of the ring 
(after new node to coordinator) have fired NODE_ADDED_EVT for it. Probably, we 
will need to reapproach joining process.

> Improvement of connection in a cluster of new node
> --
>
> Key: IGNITE-4501
> URL: https://issues.apache.org/jira/browse/IGNITE-4501
> Project: Ignite
>  Issue Type: Improvement
>  Components: messaging
>Affects Versions: 1.8
>Reporter: Vyacheslav Daradur
>Assignee: Alexander Menshikov
> Fix For: 2.0
>
>
> h3. Main description:
> Cluster nodes connect a ring.
> For example: we have 6 nodes: A, B, C, D, E, F. 
> They can connect a ring in any possible way: A-B-C-D-E-F-A, or A-F-B-E-C-D-A, 
> etc.
> If some node leaves topology, adjacent nodes must reconnect. 
> If nodes A, B, C are in same physical place, nodes D, E, F are in other 
> place, and places lost connect each other, we will have many ways of 
> reconnections.
> At best case, if we had a ring: A-B-CxD-E-FxA ('x' means disconnect) -- then 
> we have only one reconnect (C
> will be connected to A or F will be connected to D -- depends on what part of 
> the cluster was alive.
> Also, if we had a not ring: AxFxBxExCxDxA -- then we have a lot of 
> reconnections (A to B, B to C, C to A -- in general n/2 reconnections, where 
> n -- number of nodes). 
> h3. Approach:
> It is necessary to develop approach of node insertion to the correct place 
> for creation of the correct ring-topology.
> h3. Solutions:
> Main idea is a sorting according to latency.
> * group nodes in arcs on an ARC_ID. (manualy?)
> * implement NodeComparator (nodes on the same host : nodes on the same subnet 
> : other nodes). We will use it when we connect a new node.
> * [dev list 
> thread|http://mail-archives.apache.org/mod_mbox/ignite-dev/201612.mbox/%3CCAN+WSNyWYXSXEBpGErVt72zTgi2pTQzUWLv8JY=ke83-5-r...@mail.gmail.com%3E]
> Update Dec, 29 Yakov Zhdanov:
> # introduce CLUSTER_REGION_ID node attribute. This can be done by adding 
> public static final constant to TcpDiscoverySpi.
> # Alter 
> org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNodesRing#nextNode(java.util.Collection)
>  to order basing on per node attribute value
> # Node comparison should be stable and consistent. E.g. if CLUSTER_REGION_IDs 
> are equal then we should compare nodes' IDs. This way we have consistent 
> order on all nodes in topology.
> # Also nextNode() has to group nodes on same host and in same subnet. This 
> can be postponed and implemented after we have other points done.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4992) Fix Segmented SQL Index self tests.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4992:


GitHub user AMashenkov opened a pull request:

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

IGNITE-4992: Fix Segmented SQL Index self tests.



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

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

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

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


commit 78f995f0a512d60102c671f99600af1d469988e0
Author: Andrey V. Mashenkov 
Date:   2017-04-14T15:54:56Z

IGNITE-4992: Fix Segmented SQL Index self tests.

commit 8b38e7942db4f659f8b82f3e226608db3698d62c
Author: Andrey V. Mashenkov 
Date:   2017-04-14T15:56:56Z

Minor




> Fix Segmented SQL Index self tests.
> ---
>
> Key: IGNITE-4992
> URL: https://issues.apache.org/jira/browse/IGNITE-4992
> Project: Ignite
>  Issue Type: Test
>  Components: SQL
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>  Labels: flaky
> Fix For: 2.0
>
>
> Flacky tests:
> org.apache.ignite.internal.processors.query.IgniteSqlSegmentedIndexSelfTest.testMultiNodeIndexSegmentation
> org.apache.ignite.internal.processors.query.IgniteSqlSegmentedIndexSelfTest.testSingleNodeIndexSegmentationWithSwapEnabled



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4572) Machine Learning: Develop distributed algebra support for dense and sparse data sets.

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-4572:
-
Fix Version/s: 2.0

> Machine Learning: Develop distributed algebra support for dense and sparse 
> data sets.
> -
>
> Key: IGNITE-4572
> URL: https://issues.apache.org/jira/browse/IGNITE-4572
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Nikita Ivanov
>Assignee: Nikita Ivanov
>  Labels: gsoc2017
> Fix For: 2.0
>
>
> Apache Ignite community has recently kicked off development of its new 
> component - Apache Ignite Machine Learning Grid. The component will empower 
> researchers, scientists, engineers and companies to train, deploy and execute 
> machine learning models in a distributed fashion gaining significant 
> performance benefits and making real the ability to apply machine learning 
> for Big Data use cases in real-time or near real-time scenarios.
> This is the base functionality for adding support for future ML capabilities. 
> Subtasks will be created and linked to this ticket later on.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (IGNITE-4572) Machine Learning: Develop distributed algebra support for dense and sparse data sets.

[Anton Vinogradov (JIRA)]

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

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

> Machine Learning: Develop distributed algebra support for dense and sparse 
> data sets.
> -
>
> Key: IGNITE-4572
> URL: https://issues.apache.org/jira/browse/IGNITE-4572
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Nikita Ivanov
>Assignee: Nikita Ivanov
>  Labels: gsoc2017
>
> Apache Ignite community has recently kicked off development of its new 
> component - Apache Ignite Machine Learning Grid. The component will empower 
> researchers, scientists, engineers and companies to train, deploy and execute 
> machine learning models in a distributed fashion gaining significant 
> performance benefits and making real the ability to apply machine learning 
> for Big Data use cases in real-time or near real-time scenarios.
> This is the base functionality for adding support for future ML capabilities. 
> Subtasks will be created and linked to this ticket later on.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-3536) IGFS: Implement async methods for all base file system operations.

[Alexei Kaigorodov (JIRA)]

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

Alexei Kaigorodov reassigned IGNITE-3536:
-

Assignee: Alexei Kaigorodov

> IGFS: Implement async methods for all base file system operations.
> --
>
> Key: IGNITE-3536
> URL: https://issues.apache.org/jira/browse/IGNITE-3536
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Alexei Kaigorodov
> Fix For: 2.1
>
>
> 1) Remove {{IgniteAsyncSupport}} interface
> 2) Implement async counterparts for all FS operations.
> Justification: some structure file system operations might be very 
> time-consuming, so having async counterparts sounds like a good idea.
> The questions is what thread pool will host these tasks.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4992) Fix Segmented SQL Index self tests.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-4992:
-
Description: 
Flacky tests:
org.apache.ignite.internal.processors.query.IgniteSqlSegmentedIndexSelfTest.testMultiNodeIndexSegmentation
org.apache.ignite.internal.processors.query.IgniteSqlSegmentedIndexSelfTest.testSingleNodeIndexSegmentationWithSwapEnabled

> Fix Segmented SQL Index self tests.
> ---
>
> Key: IGNITE-4992
> URL: https://issues.apache.org/jira/browse/IGNITE-4992
> Project: Ignite
>  Issue Type: Test
>  Components: SQL
>Reporter: Andrew Mashenkov
>  Labels: flaky
> Fix For: 2.0
>
>
> Flacky tests:
> org.apache.ignite.internal.processors.query.IgniteSqlSegmentedIndexSelfTest.testMultiNodeIndexSegmentation
> org.apache.ignite.internal.processors.query.IgniteSqlSegmentedIndexSelfTest.testSingleNodeIndexSegmentationWithSwapEnabled



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4992) Fix Segmented SQL Index self tests.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov reassigned IGNITE-4992:


Assignee: Andrew Mashenkov

> Fix Segmented SQL Index self tests.
> ---
>
> Key: IGNITE-4992
> URL: https://issues.apache.org/jira/browse/IGNITE-4992
> Project: Ignite
>  Issue Type: Test
>  Components: SQL
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>  Labels: flaky
> Fix For: 2.0
>
>
> Flacky tests:
> org.apache.ignite.internal.processors.query.IgniteSqlSegmentedIndexSelfTest.testMultiNodeIndexSegmentation
> org.apache.ignite.internal.processors.query.IgniteSqlSegmentedIndexSelfTest.testSingleNodeIndexSegmentationWithSwapEnabled



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4992) Fix Segmented SQL Index self tests.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-4992:
-
Labels: flaky  (was: )

> Fix Segmented SQL Index self tests.
> ---
>
> Key: IGNITE-4992
> URL: https://issues.apache.org/jira/browse/IGNITE-4992
> Project: Ignite
>  Issue Type: Test
>  Components: SQL
>Reporter: Andrew Mashenkov
>  Labels: flaky
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4982) GridCacheAbstractRemoveFailureTest fail

[Konstantin Dudkov (JIRA)]

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

Konstantin Dudkov commented on IGNITE-4982:
---

Semen,

I added two methods to GridDhtAtomicAbstractUpdateRequest: int obsoleteSize() & 
KeyCacheObject obsoleteKey(int idx) witn new structure in request and did small 
refactoring in GridNearAtomicCache#processDhtAtomicUpdateRequest.

Please review.
Thanks.

> GridCacheAbstractRemoveFailureTest fail
> ---
>
> Key: IGNITE-4982
> URL: https://issues.apache.org/jira/browse/IGNITE-4982
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Konstantin Dudkov
>Assignee: Konstantin Dudkov
> Fix For: 2.0
>
>
> GridCacheAbstractRemoveFailureTest (and some child tests) fails. Reproducer:
> {code:java}
> import java.util.Collection;
> import java.util.HashSet;
> import java.util.Map;
> import java.util.concurrent.Callable;
> import java.util.concurrent.CyclicBarrier;
> import java.util.concurrent.ThreadLocalRandom;
> import java.util.concurrent.TimeUnit;
> import java.util.concurrent.TimeoutException;
> import java.util.concurrent.atomic.AtomicBoolean;
> import java.util.concurrent.atomic.AtomicLong;
> import java.util.concurrent.atomic.AtomicReference;
> import javax.cache.CacheException;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteCache;
> import org.apache.ignite.IgniteException;
> import org.apache.ignite.IgniteTransactions;
> import org.apache.ignite.cache.CacheAtomicWriteOrderMode;
> import org.apache.ignite.cache.CacheAtomicityMode;
> import org.apache.ignite.cache.CacheMode;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.configuration.NearCacheConfiguration;
> import org.apache.ignite.internal.IgniteInternalFuture;
> import org.apache.ignite.internal.cluster.ClusterTopologyCheckedException;
> import org.apache.ignite.internal.util.lang.GridTuple;
> import org.apache.ignite.internal.util.typedef.F;
> import org.apache.ignite.internal.util.typedef.T2;
> import org.apache.ignite.internal.util.typedef.X;
> import org.apache.ignite.internal.util.typedef.internal.U;
> import org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi;
> import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.TcpDiscoveryIpFinder;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
> import org.apache.ignite.testframework.GridTestUtils;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> import org.apache.ignite.transactions.Transaction;
> import org.apache.ignite.transactions.TransactionConcurrency;
> import org.apache.ignite.transactions.TransactionIsolation;
> import org.jsr166.ConcurrentHashMap8;
> import static 
> org.apache.ignite.IgniteSystemProperties.IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE;
> import static org.apache.ignite.cache.CacheMode.PARTITIONED;
> import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;
> import static 
> org.apache.ignite.transactions.TransactionConcurrency.OPTIMISTIC;
> import static 
> org.apache.ignite.transactions.TransactionConcurrency.PESSIMISTIC;
> import static 
> org.apache.ignite.transactions.TransactionIsolation.REPEATABLE_READ;
> import static 
> org.apache.ignite.transactions.TransactionIsolation.SERIALIZABLE;
> /**
>  * Tests that removes are not lost when topology changes.
>  */
> public abstract class GridCacheAbstractRemoveFailureTest extends 
> GridCommonAbstractTest {
> /** IP finder. */
> private static final TcpDiscoveryIpFinder IP_FINDER = new 
> TcpDiscoveryVmIpFinder(true);
> /** */
> private static final int GRID_CNT = 3;
> /** Keys count. */
> private static final int KEYS_CNT = 10_000;
> /** Test duration. */
> private static final long DUR = 90 * 1000L;
> /** Cache data assert frequency. */
> private static final long ASSERT_FREQ = 10_000;
> /** Kill delay. */
> private static final T2 KILL_DELAY = new T2<>(2000, 
> 5000);
> /** Start delay. */
> private static final T2 START_DELAY = new T2<>(2000, 
> 5000);
> /** */
> private static String sizePropVal;
> /** {@inheritDoc} */
> @Override protected IgniteConfiguration getConfiguration(String 
> igniteInstanceName) throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
> 
> ((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER).setForceServerMode(true);
> if (testClientNode() && 
> getTestIgniteInstanceName(0).equals(igniteInstanceName))
> cfg.setClientMode(true);
> 
> 

[jira] [Comment Edited] (IGNITE-3920) Hadoop: remove PayloadAware interface.

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-3920 at 4/14/17 2:56 PM:
---

Merged with master.
TC 
[result|http://195.239.208.174/project.html?projectId=IgniteTests_IgniteTests=pull%2F1107%2Fhead]
 are OK with me.


was (Author: tledkov-gridgain):
Merged with master.
Waits for TC 
[result|http://195.239.208.174/project.html?projectId=IgniteTests_IgniteTests=pull%2F1107%2Fhead]

> Hadoop: remove PayloadAware interface.
> --
>
> Key: IGNITE-3920
> URL: https://issues.apache.org/jira/browse/IGNITE-3920
> Project: Ignite
>  Issue Type: Task
>  Components: hadoop
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
> Attachments: default-config.xml
>
>
> When IGNITE-3376 is ready, we will be able to execute {{PROXY}} operations 
> directly from {{IgfsImpl}}. It means that we no longer need 
> {{HadoopPayloadAware}} interface, and we no longer need to pass {{IgfsPaths}} 
> to the client. 
> Let's remove them all together.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-4991) Do not print out system properties when IGNITE_TO_STRING_INCLUDE_SENSITIVE is set

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-4991:
---

 Summary: Do not print out system properties when 
IGNITE_TO_STRING_INCLUDE_SENSITIVE is set
 Key: IGNITE-4991
 URL: https://issues.apache.org/jira/browse/IGNITE-4991
 Project: Ignite
  Issue Type: Improvement
  Components: general
Affects Versions: 1.9
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
 Fix For: 2.1


{{IgniteKernal#ackSystemProperties}} and {{IgniteKernal#ackVmArguments}} print 
out system properties that can contain sensitive data. This print outs should 
be disabled when {{IGNITE_TO_STRING_INCLUDE_SENSITIVE}} system property is set 
to {{true}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4182) Improve error output when query parsing failed.

[Alexei Kaigorodov (JIRA)]

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

Alexei Kaigorodov reassigned IGNITE-4182:
-

Assignee: Alexei Kaigorodov

> Improve error output when query parsing failed.
> ---
>
> Key: IGNITE-4182
> URL: https://issues.apache.org/jira/browse/IGNITE-4182
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Alexei Kaigorodov
>Priority: Minor
> Fix For: 2.1
>
>
> There is no enough information in the exception when SLQ query can not be 
> parsed. In most cases we get something like this:
> {noformat}
> Failed to execute SQL query [reqId=2, req=OdbcQueryExecuteRequest 
> [cacheName=cache, sqlQry=SELECT a FROM B, args=[]]]
> javax.cache.CacheException: class org.apache.ignite.IgniteException: Failed 
> to parse query: SELECT a FROM B
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:740)
> at 
> org.apache.ignite.internal.processors.odbc.OdbcRequestHandler.executeQuery(OdbcRequestHandler.java:193)
> at 
> org.apache.ignite.internal.processors.odbc.OdbcRequestHandler.handle(OdbcRequestHandler.java:104)
> at 
> org.apache.ignite.internal.processors.odbc.OdbcNioListener.onMessage(OdbcNioListener.java:124)
> at 
> org.apache.ignite.internal.processors.odbc.OdbcNioListener.onMessage(OdbcNioListener.java:33)
> at 
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:270)
> at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
> at 
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:95)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at 
> org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteException: Failed to parse query: 
> SELECT a FROM B
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:749)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:728)
> ... 12 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to parse 
> query: SELECT a FROM B
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1695)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:742)
> ... 13 more
> Caused by: class 
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to 
> parse query: SELECT a FROM B
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep0(IgniteH2Indexing.java:1887)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1793)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$2.applyx(GridQueryProcessor.java:744)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$2.applyx(GridQueryProcessor.java:742)
> at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1672)
> ... 14 more
> {noformat}
> In this particular case, for example, we do not have table "B", nor we have 
> column "a", but you can't get it from the exception.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3920) Hadoop: remove PayloadAware interface.

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-3920:
--

Merged with master.
Waits for TC 
[result|http://195.239.208.174/project.html?projectId=IgniteTests_IgniteTests=pull%2F1107%2Fhead]

> Hadoop: remove PayloadAware interface.
> --
>
> Key: IGNITE-3920
> URL: https://issues.apache.org/jira/browse/IGNITE-3920
> Project: Ignite
>  Issue Type: Task
>  Components: hadoop
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
> Attachments: default-config.xml
>
>
> When IGNITE-3376 is ready, we will be able to execute {{PROXY}} operations 
> directly from {{IgfsImpl}}. It means that we no longer need 
> {{HadoopPayloadAware}} interface, and we no longer need to pass {{IgfsPaths}} 
> to the client. 
> Let's remove them all together.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4182) Improve error output when query parsing failed.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4182:


GitHub user rfqu opened a pull request:

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

IGNITE-4182: fixed

detailed diagnostics from H2 driver retained as wrapper exception's message.

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

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

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

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


commit a2b20dbff9a9d70b551e1ad47b079d777378ec4d
Author: rfqu 
Date:   2017-04-14T14:00:48Z

fix for ticket IGNITE-4182 (Improve error output when query parsing failed).

commit db1757d7fc2441de0584a1d96b5f0c9b359364cf
Author: rfqu 
Date:   2017-04-14T14:01:02Z

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




> Improve error output when query parsing failed.
> ---
>
> Key: IGNITE-4182
> URL: https://issues.apache.org/jira/browse/IGNITE-4182
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Priority: Minor
> Fix For: 2.1
>
>
> There is no enough information in the exception when SLQ query can not be 
> parsed. In most cases we get something like this:
> {noformat}
> Failed to execute SQL query [reqId=2, req=OdbcQueryExecuteRequest 
> [cacheName=cache, sqlQry=SELECT a FROM B, args=[]]]
> javax.cache.CacheException: class org.apache.ignite.IgniteException: Failed 
> to parse query: SELECT a FROM B
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:740)
> at 
> org.apache.ignite.internal.processors.odbc.OdbcRequestHandler.executeQuery(OdbcRequestHandler.java:193)
> at 
> org.apache.ignite.internal.processors.odbc.OdbcRequestHandler.handle(OdbcRequestHandler.java:104)
> at 
> org.apache.ignite.internal.processors.odbc.OdbcNioListener.onMessage(OdbcNioListener.java:124)
> at 
> org.apache.ignite.internal.processors.odbc.OdbcNioListener.onMessage(OdbcNioListener.java:33)
> at 
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:270)
> at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
> at 
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:95)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at 
> org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteException: Failed to parse query: 
> SELECT a FROM B
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:749)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:728)
> ... 12 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to parse 
> query: SELECT a FROM B
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1695)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:742)
> ... 13 more
> Caused by: class 
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to 
> parse query: SELECT a FROM B
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep0(IgniteH2Indexing.java:1887)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1793)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$2.applyx(GridQueryProcessor.java:744)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$2.applyx(GridQueryProcessor.java:742)
> at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1672)
> ... 14 more
> {noformat}
> In this particular case, for example, we do not have table "B", nor 

[jira] [Commented] (IGNITE-3523) IGFS: Remove "initialize default path modes" feature.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-3523:
-

[~tledkov-gridgain], need to re-evaluate after IGNITE-3920 is ready. As we 
already implemented correct {{PROXY}} mode, and secondary file system is never 
instantiated on client side, probably there is not more performance impact.

> IGFS: Remove "initialize default path modes" feature.
> -
>
> Key: IGNITE-3523
> URL: https://issues.apache.org/jira/browse/IGNITE-3523
> Project: Ignite
>  Issue Type: Sub-task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> Currently IGFS can create several paths by default, which will forcefully 
> work in different modes. This will never require in practice, but caused some 
> problems, e.g. performance degradation in our Hadoop FileSystem implementaions
> Let's just remove that feature along with relevant property in 
> {{FileSystemConfiguration}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-4565) Support CREATE INDEX DDL statements

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov edited comment on IGNITE-4565 at 4/14/17 1:41 PM:
--

Outstanding issues:
1) Fix client reconnect schema consistency issue
2) Fix DROP INDEX data consistency issue (+ add more concurrent data tests).
3) Additional test for local cache, replicated cache, near+dht and near caches.


was (Author: vozerov):
Outstanding issues:
1) Fix client reconnect schema consistency issue
2) Fix DROP INDEX data consistency issue (+ add more concurrent data tests).

> Support CREATE INDEX DDL statements
> ---
>
> Key: IGNITE-4565
> URL: https://issues.apache.org/jira/browse/IGNITE-4565
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache, SQL
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
>  Labels: important
> Fix For: 2.0
>
>
> We need to implement support for dynamic {{CREATE INDEX}} and {{DROP INDEX}} 
> invocations.
> Design document: 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=67640367
> Base branch: {{ignite-4565}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-3469) Get rid of deprecated APIs and entities

[Taras Ledkov (JIRA)]

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

Taras Ledkov reassigned IGNITE-3469:


Assignee: Alexey Kuznetsov  (was: Taras Ledkov)

> Get rid of deprecated APIs and entities
> ---
>
> Key: IGNITE-3469
> URL: https://issues.apache.org/jira/browse/IGNITE-3469
> Project: Ignite
>  Issue Type: Task
>Reporter: Alexey Goncharuk
>Assignee: Alexey Kuznetsov
>  Labels: important
> Fix For: 2.0
>
>
> There are more than 220 deprecated elements in Ignite code kept for the sake 
> of backward compatibility. We need to cleanup the code for Ignite 2.0 release.
> 2.0 migration guide has to be updated if needed: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3939:

Labels: important  (was: )

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



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4990) Remove deprecated properties from FileSystemConfiguration

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-4990:
-

[~kuaw26], could you please fix Visor part accordingly?

> Remove deprecated properties from FileSystemConfiguration
> -
>
> Key: IGNITE-4990
> URL: https://issues.apache.org/jira/browse/IGNITE-4990
> Project: Ignite
>  Issue Type: Sub-task
>  Components: IGFS
>Reporter: Vladimir Ozerov
>Assignee: Alexey Kuznetsov
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4990) Remove deprecated properties from FileSystemConfiguration

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-4990:
---

Assignee: Alexey Kuznetsov  (was: Vladimir Ozerov)

> Remove deprecated properties from FileSystemConfiguration
> -
>
> Key: IGNITE-4990
> URL: https://issues.apache.org/jira/browse/IGNITE-4990
> Project: Ignite
>  Issue Type: Sub-task
>  Components: IGFS
>Reporter: Vladimir Ozerov
>Assignee: Alexey Kuznetsov
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-4990) Remove deprecated properties from FileSystemConfiguration

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4990:
---

 Summary: Remove deprecated properties from FileSystemConfiguration
 Key: IGNITE-4990
 URL: https://issues.apache.org/jira/browse/IGNITE-4990
 Project: Ignite
  Issue Type: Sub-task
  Components: IGFS
Reporter: Vladimir Ozerov
 Fix For: 2.0






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4990) Remove deprecated properties from FileSystemConfiguration

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-4990:
---

Assignee: Vladimir Ozerov

> Remove deprecated properties from FileSystemConfiguration
> -
>
> Key: IGNITE-4990
> URL: https://issues.apache.org/jira/browse/IGNITE-4990
> Project: Ignite
>  Issue Type: Sub-task
>  Components: IGFS
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4942) Remove old JdbcQueryTask

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4942:


Github user devozerov closed the pull request at:

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


> Remove old JdbcQueryTask
> 
>
> Key: IGNITE-4942
> URL: https://issues.apache.org/jira/browse/IGNITE-4942
> Project: Ignite
>  Issue Type: Task
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>Priority: Minor
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4849) Review and refactoring the versioned classes

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-4849:
--

Duplicated by  IGNITE-4941 & IGNITE-4942

> Review and refactoring the versioned classes
> 
>
> Key: IGNITE-4849
> URL: https://issues.apache.org/jira/browse/IGNITE-4849
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> There are some classes without and with {{V2}} suffix. Usually they are used 
> to backward compatibility.
> These classes must be reviewed and refactored if it is necessary. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4989) Assertion error in BPlusTree#finishTail

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk updated IGNITE-4989:
-
Fix Version/s: 2.0

> Assertion error in BPlusTree#finishTail
> ---
>
> Key: IGNITE-4989
> URL: https://issues.apache.org/jira/browse/IGNITE-4989
> Project: Ignite
>  Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Sergi Vladykin
> Fix For: 2.0
>
>
> This assertion occasionally appears in CacheRandomOperationsMultithreadedTest
> {code}
> [15:03:13]W:   [org.apache.ignite:ignite-indexing] 
> [12:03:13,541][ERROR][sys-stripe-9-#3935%cache.CacheRandomOperationsMultithreadedTest2%][GridNearTxLocal]
>  Commit failed.
> [15:03:13]W:   [org.apache.ignite:ignite-indexing] class 
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException: 
> Commit produced a runtime exception (all transaction entries will be 
> invalidated): 
> GridDhtTxRemote[id=6fc395c6b51-062d9824--0001--015b6c5889ed, 
> concurrency=OPTIMISTIC, isolation=READ_COMMITTED, state=COMMITTING, 
> invalidate=false, rollbackOnly=false, 
> nodeId=04efe5ed-8050-4529-ba7c-395e3900, duration=10]
> [15:03:13]W:   [org.apache.ignite:ignite-indexing]at 
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxRemoteAdapter.commitIfLocked(GridDistributedTxRemoteAdapter.java:719)
> [15:03:13]W:   [org.apache.ignite:ignite-indexing]at 
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxRemoteAdapter.commitRemoteTx(GridDistributedTxRemoteAdapter.java:789)
> [15:03:13]W:   [org.apache.ignite:ignite-indexing]at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:1222)
> [15:03:13]W:   [org.apache.ignite:ignite-indexing]at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processDhtTxFinishRequest(IgniteTxHandler.java:1130)
> [15:03:13]W:   [org.apache.ignite:ignite-indexing]at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$600(IgniteTxHandler.java:95)
> [15:03:13]W:   [org.apache.ignite:ignite-indexing]at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$7.apply(IgniteTxHandler.java:180)
> [15:03:13]W:   [org.apache.ignite:ignite-indexing]at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$7.apply(IgniteTxHandler.java:178)
> [15:03:13]W:   [org.apache.ignite:ignite-indexing]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:863)
> [15:03:13]W:   [org.apache.ignite:ignite-indexing]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:386)
> [15:03:13]W:   [org.apache.ignite:ignite-indexing]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:308)
> [15:03:13]W:   [org.apache.ignite:ignite-indexing]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:100)
> [15:03:13]W:   [org.apache.ignite:ignite-indexing]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:253)
> [15:03:13]W:   [org.apache.ignite:ignite-indexing]at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1238)
> [15:03:13]W:   [org.apache.ignite:ignite-indexing]at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:866)
> [15:03:13]W:   [org.apache.ignite:ignite-indexing]at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$2100(GridIoManager.java:111)
> [15:03:13]W:   [org.apache.ignite:ignite-indexing]at 
> org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:798)
> [15:03:13]W:   [org.apache.ignite:ignite-indexing]at 
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:483)
> [15:03:13]W:   [org.apache.ignite:ignite-indexing]at 
> java.lang.Thread.run(Thread.java:745)
> [15:03:13]W:   [org.apache.ignite:ignite-indexing] Caused by: 
> java.lang.AssertionError: Assertion error on search row: Row@19cdbda1[ key: 
> org.apache.ignite.internal.processors.cache.CacheRandomOperationsMultithreadedTest$TestKey@2e5,
>  val: 
> org.apache.ignite.internal.processors.cache.CacheRandomOperationsMultithreadedTest$TestData@125ca243
>  ][ 131925325, 131925325 ]
> [15:03:13]W:   [org.apache.ignite:ignite-indexing]at 
> 

[jira] [Created] (IGNITE-4989) Assertion error in BPlusTree#finishTail

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-4989:


 Summary: Assertion error in BPlusTree#finishTail
 Key: IGNITE-4989
 URL: https://issues.apache.org/jira/browse/IGNITE-4989
 Project: Ignite
  Issue Type: Bug
Reporter: Alexey Goncharuk
Assignee: Sergi Vladykin


This assertion occasionally appears in CacheRandomOperationsMultithreadedTest

{code}
[15:03:13]W: [org.apache.ignite:ignite-indexing] 
[12:03:13,541][ERROR][sys-stripe-9-#3935%cache.CacheRandomOperationsMultithreadedTest2%][GridNearTxLocal]
 Commit failed.
[15:03:13]W: [org.apache.ignite:ignite-indexing] class 
org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException: 
Commit produced a runtime exception (all transaction entries will be 
invalidated): 
GridDhtTxRemote[id=6fc395c6b51-062d9824--0001--015b6c5889ed, 
concurrency=OPTIMISTIC, isolation=READ_COMMITTED, state=COMMITTING, 
invalidate=false, rollbackOnly=false, 
nodeId=04efe5ed-8050-4529-ba7c-395e3900, duration=10]
[15:03:13]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxRemoteAdapter.commitIfLocked(GridDistributedTxRemoteAdapter.java:719)
[15:03:13]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxRemoteAdapter.commitRemoteTx(GridDistributedTxRemoteAdapter.java:789)
[15:03:13]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:1222)
[15:03:13]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processDhtTxFinishRequest(IgniteTxHandler.java:1130)
[15:03:13]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$600(IgniteTxHandler.java:95)
[15:03:13]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$7.apply(IgniteTxHandler.java:180)
[15:03:13]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$7.apply(IgniteTxHandler.java:178)
[15:03:13]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:863)
[15:03:13]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:386)
[15:03:13]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:308)
[15:03:13]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:100)
[15:03:13]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:253)
[15:03:13]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1238)
[15:03:13]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:866)
[15:03:13]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$2100(GridIoManager.java:111)
[15:03:13]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:798)
[15:03:13]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:483)
[15:03:13]W: [org.apache.ignite:ignite-indexing]at 
java.lang.Thread.run(Thread.java:745)
[15:03:13]W: [org.apache.ignite:ignite-indexing] Caused by: 
java.lang.AssertionError: Assertion error on search row: Row@19cdbda1[ key: 
org.apache.ignite.internal.processors.cache.CacheRandomOperationsMultithreadedTest$TestKey@2e5,
 val: 
org.apache.ignite.internal.processors.cache.CacheRandomOperationsMultithreadedTest$TestData@125ca243
 ][ 131925325, 131925325 ]
[15:03:13]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.doRemove(BPlusTree.java:1773)
[15:03:13]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.removex(BPlusTree.java:1570)
[15:03:13]W: 

[jira] [Issue Comment Deleted] (IGNITE-4699) Introduce custom configurable executors.

[Taras Ledkov (JIRA)]

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

Taras Ledkov updated IGNITE-4699:
-
Comment: was deleted

(was: Tests 
[results|http://195.239.208.174/project.html?projectId=IgniteTests=projectOverview_IgniteTests=pull%2F1718%2Fhead])

> Introduce custom configurable executors.
> 
>
> Key: IGNITE-4699
> URL: https://issues.apache.org/jira/browse/IGNITE-4699
> Project: Ignite
>  Issue Type: Task
>  Components: compute
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>  Labels: important
> Fix For: 2.0
>
>
> We need to provide a way to configure custom thread pools for user compute 
> tasks. 
> Proposed API:
> 1) Config
> {code}
> class ExecutorConfiguration {
> String name;
> int size;
> }
> {code}
> 2) Choosing executor for compute task:
> {code}
> IgniteCompute compute = Ignite.compute().withExecutor("my_exec");
> {code}
> 3) Accessing raw executor (could be required for proper execution of future 
> listeners):
> {code}
> ThreadPoolExecutor exec = ignite.compute().localExecutor("my_exec");
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4915) Remove deprecated methods and properties at the public API

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4915:


Github user asfgit closed the pull request at:

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


> Remove deprecated methods and properties at the public API
> --
>
> Key: IGNITE-4915
> URL: https://issues.apache.org/jira/browse/IGNITE-4915
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> Methods to remove:
> - {{IgniteCluster.mapKeysToNodes}};
> - {{IgniteCache.randomEntry}};
> - {{FileSystemConfiguration}} properties;
> - {{IgfsPath}} methods.
> - deprecated properties of the {{TcpCommunicationSpi}};
> - {{GridTupleV}};
> - {{AffinityNideHashResolver}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-3689) .NET: Remove IgniteProxy

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-3689 at 4/14/17 12:41 PM:
--

IgniteProxy removed, running tests 
(http://ci.ignite.apache.org/project.html?projectId=IgniteTests_IgniteTests=pull%2F1797%2Fhead)
 to see if we actually ever needed it.

I'm not sure about use cases: why would user want to serialize injected fields? 
Why would user even want to serialize the class which is eligible for injection?

We currently inject resources in the following cases:
* cache filters and listeners
* compute actions and jobs
* message and event listeners
* plugin context

It is very unlikely that these entities are going to be serialized by the user 
manually.
We should just skip {{Ignite}} fields during serialization.


was (Author: ptupitsyn):
IgniteProxy removed, running tests to see if we actually ever needed it.

I'm not sure about use cases: why would user want to serialize injected fields? 
Why would user even want to serialize the class which is eligible for injection?

We currently inject resources in the following cases:
* cache filters and listeners
* compute actions and jobs
* message and event listeners
* plugin context

It is very unlikely that these entities are going to be serialized by the user 
manually.
We should just skip {{Ignite}} fields during serialization.

> .NET: Remove IgniteProxy
> 
>
> Key: IGNITE-3689
> URL: https://issues.apache.org/jira/browse/IGNITE-3689
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, breaking
> Fix For: 2.0
>
>
> IgniteProxy exists to handle serialization of injected IIgnite fields in user 
> classes.
> As a result, we write a type id and a null flag in place of injected fields.
> Instead we should just skip injected fields altogether.
> There are two cases:
> * Binarizable. In this case we can use a special no-op serializer or add a 
> check to BinaryWriter.
> * Serializable. Override ISerializable in Ignite and don't write anything.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3689) .NET: Remove IgniteProxy

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-3689:


IgniteProxy removed, running tests to see if we actually ever needed it.

I'm not sure about use cases: why would user want to serialize injected fields? 
Why would user even want to serialize the class which is eligible for injection?

We currently inject resources in the following cases:
* cache filters and listeners
* compute actions and jobs
* message and event listeners
* plugin context

It is very unlikely that these entities are going to be serialized by the user 
manually.
We should just skip {{Ignite}} fields during serialization.

> .NET: Remove IgniteProxy
> 
>
> Key: IGNITE-3689
> URL: https://issues.apache.org/jira/browse/IGNITE-3689
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, breaking
> Fix For: 2.0
>
>
> IgniteProxy exists to handle serialization of injected IIgnite fields in user 
> classes.
> As a result, we write a type id and a null flag in place of injected fields.
> Instead we should just skip injected fields altogether.
> There are two cases:
> * Binarizable. In this case we can use a special no-op serializer or add a 
> check to BinaryWriter.
> * Serializable. Override ISerializable in Ignite and don't write anything.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-4988) Web Console: Cleanup and refactor VisorXxx tasks and DTO for ignite-2.0

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-4988:


 Summary: Web Console: Cleanup and refactor VisorXxx tasks and DTO 
for ignite-2.0
 Key: IGNITE-4988
 URL: https://issues.apache.org/jira/browse/IGNITE-4988
 Project: Ignite
  Issue Type: Task
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3689) .NET: Remove IgniteProxy

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3689:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-3689 .NET: Remove IgniteProxy



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

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

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

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


commit e2b156f6399f36d326bd1a820bc3853466884e8f
Author: Pavel Tupitsyn 
Date:   2017-04-14T12:23:44Z

Remove IgniteProxy

commit 32b62ad7c141a1fbb4f262ef801b7f23b86d4606
Author: Pavel Tupitsyn 
Date:   2017-04-14T12:32:40Z

Add debug output




> .NET: Remove IgniteProxy
> 
>
> Key: IGNITE-3689
> URL: https://issues.apache.org/jira/browse/IGNITE-3689
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, breaking
> Fix For: 2.0
>
>
> IgniteProxy exists to handle serialization of injected IIgnite fields in user 
> classes.
> As a result, we write a type id and a null flag in place of injected fields.
> Instead we should just skip injected fields altogether.
> There are two cases:
> * Binarizable. In this case we can use a special no-op serializer or add a 
> check to BinaryWriter.
> * Serializable. Override ISerializable in Ignite and don't write anything.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4694) Add tests to check there are no memory leaks in PageMemory

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov commented on IGNITE-4694:
--

The required number of pages was increased because of changes in H2TreeIndex. 
The index became segmented, so what it requires a bit more space now (A tree 
per segment)

Fixed the tests

> Add tests to check there are no memory leaks in PageMemory
> --
>
> Key: IGNITE-4694
> URL: https://issues.apache.org/jira/browse/IGNITE-4694
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Igor Seliverstov
> Fix For: 2.1
>
>
> Need add several tests running for 5-10 munites verifying there are no memory 
> leaks in new data structures based of PageMemory:
> - test various page size
> - test various objects size
> - test put/get/remove operations
> - test create cache/destroy cache operations
> - test cases when indexes enabled/disabled
> - test case when cache expiry policy is used
> New tests should be added in new test suite.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4694) Add tests to check there are no memory leaks in PageMemory

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4694:


GitHub user gvvinblade opened a pull request:

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

IGNITE-4694



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

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

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

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


commit 1abb53178e933596f3e005cb6d50c3af5858df72
Author: Igor Seliverstov 
Date:   2017-04-14T12:22:53Z

[IGNITE-4694] Add tests to check there are no memory leaks in PageMemory




> Add tests to check there are no memory leaks in PageMemory
> --
>
> Key: IGNITE-4694
> URL: https://issues.apache.org/jira/browse/IGNITE-4694
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Igor Seliverstov
> Fix For: 2.1
>
>
> Need add several tests running for 5-10 munites verifying there are no memory 
> leaks in new data structures based of PageMemory:
> - test various page size
> - test various objects size
> - test put/get/remove operations
> - test create cache/destroy cache operations
> - test cases when indexes enabled/disabled
> - test case when cache expiry policy is used
> New tests should be added in new test suite.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3548) .NET: Rename ILifecycleBean

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-3548:


Migration guide updated

> .NET: Rename ILifecycleBean
> ---
>
> Key: IGNITE-3548
> URL: https://issues.apache.org/jira/browse/IGNITE-3548
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .net, breaking-api
> Fix For: 2.0
>
>
> Bean is a Java term. 
> Either rename this interface to something like ILifecycle, or rework the 
> lifecycle notifications to C# event handlers.
> 2.0 migration guide has to be updated if needed: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4980) .NET: NuGet packages do not work with PackageReference in VS2017

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4980:


Nothing to fix now:
{{Package references are currently supported for only .NET Core and .NET 
Standard projects in Visual Studio 2017}}
https://docs.microsoft.com/en-us/nuget/consume-packages/package-references-in-project-files

Ignite.NET is not supported in .NET Core and .NET Standard. Postponing to look 
into this later.

> .NET: NuGet packages do not work with PackageReference in VS2017
> 
>
> Key: IGNITE-4980
> URL: https://issues.apache.org/jira/browse/IGNITE-4980
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> VS2017 & NuGet 4.0 come with a new way of referencing packages: instead of 
> {{packages.config}}, there is a {{PackageReference}} section in {{csproj}} 
> file: 
> http://blog.nuget.org/20170316/NuGet-now-fully-integrated-into-MSBuild.html
> This feature does not support {{install.ps1}} script which we use to insert 
> build event for copying JARs to output directory.
> This is not a blocker, since build event can be set up manually.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4980) .NET: NuGet packages do not work with PackageReference in VS2017

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-4980:
---
Fix Version/s: (was: 2.0)
   2.1

> .NET: NuGet packages do not work with PackageReference in VS2017
> 
>
> Key: IGNITE-4980
> URL: https://issues.apache.org/jira/browse/IGNITE-4980
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> VS2017 & NuGet 4.0 come with a new way of referencing packages: instead of 
> {{packages.config}}, there is a {{PackageReference}} section in {{csproj}} 
> file: 
> http://blog.nuget.org/20170316/NuGet-now-fully-integrated-into-MSBuild.html
> This feature does not support {{install.ps1}} script which we use to insert 
> build event for copying JARs to output directory.
> This is not a blocker, since build event can be set up manually.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4980) .NET: NuGet packages do not work with PackageReference in VS2017

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-4980:
--

Assignee: (was: Pavel Tupitsyn)

> .NET: NuGet packages do not work with PackageReference in VS2017
> 
>
> Key: IGNITE-4980
> URL: https://issues.apache.org/jira/browse/IGNITE-4980
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> VS2017 & NuGet 4.0 come with a new way of referencing packages: instead of 
> {{packages.config}}, there is a {{PackageReference}} section in {{csproj}} 
> file: 
> http://blog.nuget.org/20170316/NuGet-now-fully-integrated-into-MSBuild.html
> This feature does not support {{install.ps1}} script which we use to insert 
> build event for copying JARs to output directory.
> This is not a blocker, since build event can be set up manually.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-3689) .NET: Remove IgniteProxy

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-3689:
--

Assignee: Pavel Tupitsyn

> .NET: Remove IgniteProxy
> 
>
> Key: IGNITE-3689
> URL: https://issues.apache.org/jira/browse/IGNITE-3689
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, breaking
> Fix For: 2.0
>
>
> IgniteProxy exists to handle serialization of injected IIgnite fields in user 
> classes.
> As a result, we write a type id and a null flag in place of injected fields.
> Instead we should just skip injected fields altogether.
> There are two cases:
> * Binarizable. In this case we can use a special no-op serializer or add a 
> check to BinaryWriter.
> * Serializable. Override ISerializable in Ignite and don't write anything.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3548) .NET: Rename ILifecycleBean

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3548:


Github user asfgit closed the pull request at:

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


> .NET: Rename ILifecycleBean
> ---
>
> Key: IGNITE-3548
> URL: https://issues.apache.org/jira/browse/IGNITE-3548
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .net, breaking-api
> Fix For: 2.0
>
>
> Bean is a Java term. 
> Either rename this interface to something like ILifecycle, or rework the 
> lifecycle notifications to C# event handlers.
> 2.0 migration guide has to be updated if needed: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3548) .NET: Rename ILifecycleBean

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-3548:


Merged to master

> .NET: Rename ILifecycleBean
> ---
>
> Key: IGNITE-3548
> URL: https://issues.apache.org/jira/browse/IGNITE-3548
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .net, breaking-api
> Fix For: 2.0
>
>
> Bean is a Java term. 
> Either rename this interface to something like ILifecycle, or rework the 
> lifecycle notifications to C# event handlers.
> 2.0 migration guide has to be updated if needed: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4699) Introduce custom configurable executors.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-4699:
---

Assignee: Taras Ledkov  (was: Vladimir Ozerov)

> Introduce custom configurable executors.
> 
>
> Key: IGNITE-4699
> URL: https://issues.apache.org/jira/browse/IGNITE-4699
> Project: Ignite
>  Issue Type: Task
>  Components: compute
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>  Labels: important
> Fix For: 2.0
>
>
> We need to provide a way to configure custom thread pools for user compute 
> tasks. 
> Proposed API:
> 1) Config
> {code}
> class ExecutorConfiguration {
> String name;
> int size;
> }
> {code}
> 2) Choosing executor for compute task:
> {code}
> IgniteCompute compute = Ignite.compute().withExecutor("my_exec");
> {code}
> 3) Accessing raw executor (could be required for proper execution of future 
> listeners):
> {code}
> ThreadPoolExecutor exec = ignite.compute().localExecutor("my_exec");
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4699) Introduce custom configurable executors.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-4699:
---

Assignee: Taras Ledkov  (was: Alexander Menshikov)

> Introduce custom configurable executors.
> 
>
> Key: IGNITE-4699
> URL: https://issues.apache.org/jira/browse/IGNITE-4699
> Project: Ignite
>  Issue Type: Task
>  Components: compute
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>  Labels: important
> Fix For: 2.0
>
>
> We need to provide a way to configure custom thread pools for user compute 
> tasks. 
> Proposed API:
> 1) Config
> {code}
> class ExecutorConfiguration {
> String name;
> int size;
> }
> {code}
> 2) Choosing executor for compute task:
> {code}
> IgniteCompute compute = Ignite.compute().withExecutor("my_exec");
> {code}
> 3) Accessing raw executor (could be required for proper execution of future 
> listeners):
> {code}
> ThreadPoolExecutor exec = ignite.compute().localExecutor("my_exec");
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4699) Introduce custom configurable executors.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-4699:
---

Assignee: Vladimir Ozerov  (was: Taras Ledkov)

> Introduce custom configurable executors.
> 
>
> Key: IGNITE-4699
> URL: https://issues.apache.org/jira/browse/IGNITE-4699
> Project: Ignite
>  Issue Type: Task
>  Components: compute
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>  Labels: important
> Fix For: 2.0
>
>
> We need to provide a way to configure custom thread pools for user compute 
> tasks. 
> Proposed API:
> 1) Config
> {code}
> class ExecutorConfiguration {
> String name;
> int size;
> }
> {code}
> 2) Choosing executor for compute task:
> {code}
> IgniteCompute compute = Ignite.compute().withExecutor("my_exec");
> {code}
> 3) Accessing raw executor (could be required for proper execution of future 
> listeners):
> {code}
> ThreadPoolExecutor exec = ignite.compute().localExecutor("my_exec");
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (IGNITE-4983) .NET: Cache plugins do not work

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-4983.

Resolution: Fixed

> .NET: Cache plugins do not work
> ---
>
> Key: IGNITE-4983
> URL: https://issues.apache.org/jira/browse/IGNITE-4983
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 2.0
>
>
> IGNITE-3477 brought breaking changes to cache plugin infrastructure. Now 
> cache plugins can not exist independently of grid plugins: 
> {{PluginProvider.createCacheProvider}} creates cache provider, instead of 
> {{CachePluginConfiguration.createProvider}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4983) .NET: Cache plugins do not work

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4983:


Fixed in master

> .NET: Cache plugins do not work
> ---
>
> Key: IGNITE-4983
> URL: https://issues.apache.org/jira/browse/IGNITE-4983
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 2.0
>
>
> IGNITE-3477 brought breaking changes to cache plugin infrastructure. Now 
> cache plugins can not exist independently of grid plugins: 
> {{PluginProvider.createCacheProvider}} creates cache provider, instead of 
> {{CachePluginConfiguration.createProvider}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4871) Web console: Implement possibility to configure Kubernetes IP finder

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-4871:


Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

Merged to master. Please test.

> Web console: Implement possibility to configure Kubernetes IP finder
> 
>
> Key: IGNITE-4871
> URL: https://issues.apache.org/jira/browse/IGNITE-4871
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (IGNITE-4886) VisorServiceTask should properly handle ClassNotFound exceptions.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov closed IGNITE-4886.


Merged to master.

> VisorServiceTask should properly handle ClassNotFound exceptions.
> -
>
> Key: IGNITE-4886
> URL: https://issues.apache.org/jira/browse/IGNITE-4886
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.9
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
> Fix For: 2.0
>
>
> {code}
> org.apache.ignite.IgniteException: Failed to find service class: 
> at 
> org.apache.ignite.internal.processors.service.ServiceDescriptorImpl.serviceClass(ServiceDescriptorImpl.java:68)
> at 
> org.apache.ignite.internal.visor.service.VisorServiceDescriptor.(VisorServiceDescriptor.java:71)
> at 
> org.apache.ignite.internal.visor.service.VisorServiceTask$VisorServiceJob.run(VisorServiceTask.java:65)
> at 
> org.apache.ignite.internal.visor.service.VisorServiceTask$VisorServiceJob.run(VisorServiceTask.java:44)
> at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
> at 
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:560)
> at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6564)
> at 
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:554)
> at 
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:483)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at 
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1114)
> at 
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1894)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException: 
> at 
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1702)
> at 
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1547)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at 
> org.apache.ignite.internal.processors.service.ServiceDescriptorImpl.serviceClass(ServiceDescriptorImpl.java:65)
> ... 18 common frames omitted
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4068) Web console: Extended actions in dropdown menus should contain base action.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-4068:


Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

Merged to master. Please test.

> Web console: Extended actions in dropdown menus should contain base action.
> ---
>
> Key: IGNITE-4068
> URL: https://issues.apache.org/jira/browse/IGNITE-4068
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Attachments: dropdown.png
>
>
> F.e. Dropdown for remove button should contain remove action too how on 
> execute and scan buttons. (See attach)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4068) Web console: Extended actions in dropdown menus should contain base action.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-4068:
-
Fix Version/s: 2.0

> Web console: Extended actions in dropdown menus should contain base action.
> ---
>
> Key: IGNITE-4068
> URL: https://issues.apache.org/jira/browse/IGNITE-4068
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 2.0
>
> Attachments: dropdown.png
>
>
> F.e. Dropdown for remove button should contain remove action too how on 
> execute and scan buttons. (See attach)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4983) .NET: Cache plugins do not work

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4983:


IGNITE-4987 created to restore .NET-based cache plugins

> .NET: Cache plugins do not work
> ---
>
> Key: IGNITE-4983
> URL: https://issues.apache.org/jira/browse/IGNITE-4983
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 2.0
>
>
> IGNITE-3477 brought breaking changes to cache plugin infrastructure. Now 
> cache plugins can not exist independently of grid plugins: 
> {{PluginProvider.createCacheProvider}} creates cache provider, instead of 
> {{CachePluginConfiguration.createProvider}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4896) OptimizedMarshaller should not failed on GridClientNodeBean serialization

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-4896:
-
Fix Version/s: (was: 2.1)
   2.0

> OptimizedMarshaller should not failed on GridClientNodeBean serialization
> -
>
> Key: IGNITE-4896
> URL: https://issues.apache.org/jira/browse/IGNITE-4896
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 1.9
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
> Fix For: 2.0
>
>
> If node attributes contain some unknown for Optimized marshaller classes (not 
> present in classnames.properties) it will failed to serialize them.
> I think it is better to skip such objects and print warning in node log and 
> GridClient log.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (IGNITE-4896) OptimizedMarshaller should not failed on GridClientNodeBean serialization

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov closed IGNITE-4896.


Merged to master.

> OptimizedMarshaller should not failed on GridClientNodeBean serialization
> -
>
> Key: IGNITE-4896
> URL: https://issues.apache.org/jira/browse/IGNITE-4896
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 1.9
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
> Fix For: 2.0
>
>
> If node attributes contain some unknown for Optimized marshaller classes (not 
> present in classnames.properties) it will failed to serialize them.
> I think it is better to skip such objects and print warning in node log and 
> GridClient log.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-4987) .NET-based cache plugins

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4987:
--

 Summary: .NET-based cache plugins
 Key: IGNITE-4987
 URL: https://issues.apache.org/jira/browse/IGNITE-4987
 Project: Ignite
  Issue Type: New Feature
  Components: platforms
Affects Versions: 2.0
Reporter: Pavel Tupitsyn


Currently cache plugins on .NET side can only delegate to Java.

.NET cache plugins were implemented in IGNITE-4457 and removed in IGNITE-4983 
due to Java API changes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4938) Move OptimziedMarshaller to internal package

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4938:


Github user devozerov closed the pull request at:

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


> Move OptimziedMarshaller to internal package
> 
>
> Key: IGNITE-4938
> URL: https://issues.apache.org/jira/browse/IGNITE-4938
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>  Labels: important
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4938) Move OptimziedMarshaller to internal package

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4938:


GitHub user devozerov opened a pull request:

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

IGNITE-4938



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

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

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

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


commit ab19f23f399b1c950864c4e059527e40b9a0b17b
Author: devozerov 
Date:   2017-04-14T11:15:30Z

Moved oprimzied marshaller to private space.




> Move OptimziedMarshaller to internal package
> 
>
> Key: IGNITE-4938
> URL: https://issues.apache.org/jira/browse/IGNITE-4938
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>  Labels: important
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-4983) .NET: Cache plugins do not work

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-4983 at 4/14/17 11:11 AM:
--

We should probably remove {{ICachePluginProvider}} and related infrastructure 
and leave only Java-based plugins in place ({{ICachePluginConfiguration}} with 
non-null {{CachePluginConfigurationClosureFactoryId}}), since current 
infrastructure on .NET side does not play along with new Java aprt at all.


was (Author: ptupitsyn):
We should probably remove {{ICachePluginProvider}} and related infrastructure 
and leave only Java-based plugins in place ({{ICachePluginConfiguration}} with 
non-null {{CachePluginConfigurationClosureFactoryId}}).

> .NET: Cache plugins do not work
> ---
>
> Key: IGNITE-4983
> URL: https://issues.apache.org/jira/browse/IGNITE-4983
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 2.0
>
>
> IGNITE-3477 brought breaking changes to cache plugin infrastructure. Now 
> cache plugins can not exist independently of grid plugins: 
> {{PluginProvider.createCacheProvider}} creates cache provider, instead of 
> {{CachePluginConfiguration.createProvider}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-4986) .NET possible affinity resource leak

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-4986:


 Summary: .NET possible affinity resource leak
 Key: IGNITE-4986
 URL: https://issues.apache.org/jira/browse/IGNITE-4986
 Project: Ignite
  Issue Type: Bug
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk


Test fails with 
{code}
TearDown method failed. HandleRegistry is not empty in grid '' (expected 5, 
actual 6):
 '[1025, 
Apache.Ignite.Core.Tests.Cache.Affinity.AffinityFunctionTest+RendezvousAffinityFunctionEx]
[1026, 
Apache.Ignite.Core.Tests.Cache.Affinity.AffinityFunctionTest+SimpleAffinityFunction]
[1027, 
Apache.Ignite.Core.Tests.Cache.Affinity.AffinityFunctionTest+SimpleAffinityFunction]
[1028, 
Apache.Ignite.Core.Tests.Cache.Affinity.AffinityFunctionTest+FailInGetPartitionAffinityFunction]
[1029, 
Apache.Ignite.Core.Tests.Cache.Affinity.AffinityFunctionTest+RendezvousAffinityFunctionEx]'
   at NUnit.Framework.Assert.Fail(String message, Object[] args)
   at Apache.Ignite.Core.Tests.TestUtils.AssertHandleRegistryHasItems(IIgnite 
grid, Int32 expectedCount, Int32 timeout) in 
c:\BuildAgent\work\a9543228d3ee824c\modules\platforms\dotnet\Apache.Ignite.Core.Tests\TestUtils.cs:line
 292
   at 
Apache.Ignite.Core.Tests.Cache.Affinity.AffinityFunctionTest.FixtureTearDown() 
in 
c:\BuildAgent\work\a9543228d3ee824c\modules\platforms\dotnet\Apache.Ignite.Core.Tests\Cache\Affinity\AffinityFunctionTest.cs:line
 95
{code}
which might indicate that affinity resource is not released in Ignite



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4983) .NET: Cache plugins do not work

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4983:


We should probably remove {{ICachePluginProvider}} and related infrastructure 
and leave only Java-based plugins in place ({{ICachePluginConfiguration}} with 
non-null {{CachePluginConfigurationClosureFactoryId}}).

> .NET: Cache plugins do not work
> ---
>
> Key: IGNITE-4983
> URL: https://issues.apache.org/jira/browse/IGNITE-4983
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 2.0
>
>
> IGNITE-3477 brought breaking changes to cache plugin infrastructure. Now 
> cache plugins can not exist independently of grid plugins: 
> {{PluginProvider.createCacheProvider}} creates cache provider, instead of 
> {{CachePluginConfiguration.createProvider}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4871) Web console: Implement possibility to configure Kubernetes IP finder

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-4871:


Assignee: Alexey Kuznetsov  (was: Vasiliy Sisko)

> Web console: Implement possibility to configure Kubernetes IP finder
> 
>
> Key: IGNITE-4871
> URL: https://issues.apache.org/jira/browse/IGNITE-4871
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4615) Ignite should be compilable under JDK 9

[Evgenii Zhuravlev (JIRA)]

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

Evgenii Zhuravlev updated IGNITE-4615:
--
Fix Version/s: (was: 2.0)
   2.1

> Ignite should be compilable under JDK 9
> ---
>
> Key: IGNITE-4615
> URL: https://issues.apache.org/jira/browse/IGNITE-4615
> Project: Ignite
>  Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Evgenii Zhuravlev
> Fix For: 2.1
>
> Attachments: ignite.jar.dot
>
>
> The original discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Should-we-take-care-of-Java-9-in-Ignite-2-0-scope-td14018.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4615) Ignite should be compilable under JDK 9

[Evgenii Zhuravlev (JIRA)]

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

Evgenii Zhuravlev commented on IGNITE-4615:
---

Application ClassLoader in java 9 not  UrlClassLoader anymore. We have a code 
that casts application classloader to (UrlClassLoader) in HadoopClassLoader and 
BinaryContext, so it's not clear how to refactor this code.

> Ignite should be compilable under JDK 9
> ---
>
> Key: IGNITE-4615
> URL: https://issues.apache.org/jira/browse/IGNITE-4615
> Project: Ignite
>  Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Evgenii Zhuravlev
> Fix For: 2.0
>
> Attachments: ignite.jar.dot
>
>
> The original discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Should-we-take-care-of-Java-9-in-Ignite-2-0-scope-td14018.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4615) Ignite should be compilable under JDK 9

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-4615:
--

Possible, some beta version works?

> Ignite should be compilable under JDK 9
> ---
>
> Key: IGNITE-4615
> URL: https://issues.apache.org/jira/browse/IGNITE-4615
> Project: Ignite
>  Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Evgenii Zhuravlev
> Fix For: 2.0
>
> Attachments: ignite.jar.dot
>
>
> The original discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Should-we-take-care-of-Java-9-in-Ignite-2-0-scope-td14018.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4861) Export rebalance metrics and state as MBeans

[Ivan Rakov (JIRA)]

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

Ivan Rakov reassigned IGNITE-4861:
--

Assignee: Alexey Goncharuk  (was: Ivan Rakov)

> Export rebalance metrics and state as MBeans
> 
>
> Key: IGNITE-4861
> URL: https://issues.apache.org/jira/browse/IGNITE-4861
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
> Fix For: 2.0
>
>
> It would be nice to have rebalance metrics on an MBean:
> 1) Number of partitions to be rebalanced
> 2) Estimated number of keys to be rebalanced
> 3) Average rebalancing rate
> Any other metrics that might be useful



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-4861) Export rebalance metrics and state as MBeans

[Ivan Rakov (JIRA)]

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

Ivan Rakov edited comment on IGNITE-4861 at 4/14/17 10:41 AM:
--

The following metrics have been added to CacheMetrics:
{code}
/**
 * @return Total number of partitions on current node.
 */
public int getTotalPartitionsCount();

/**
 * @return Number of currently rebalancing partitions on current node.
 */
public int getRebalancingPartitionsCount();

/**
 * @return Estimated number of keys to be rebalanced on current node.
 */
public long getKeysToRebalanceLeft();

/**
 * @return Estimated rebalancing speed in keys.
 */
public long getRebalancingKeysRate();

/**
 * @return Estimated rebalancing speed in bytes.
 */
public long getRebalancingBytesRate();
{code}
Default timeframe for rate metrics is 1 minute, can be overriden with 
IgniteSystemProperties#IGNITE_REBALANCE_STATISTICS_TIME_INTERVAL.


was (Author: ivan.glukos):
The following metrics added to CacheMetrics:
{code}
/**
 * @return Total number of partitions on current node.
 */
public int getTotalPartitionsCount();

/**
 * @return Number of currently rebalancing partitions on current node.
 */
public int getRebalancingPartitionsCount();

/**
 * @return Estimated number of keys to be rebalanced on current node.
 */
public long getKeysToRebalanceLeft();

/**
 * @return Estimated rebalancing speed in keys.
 */
public long getRebalancingKeysRate();

/**
 * @return Estimated rebalancing speed in bytes.
 */
public long getRebalancingBytesRate();
{code}
Default timeframe for rate metrics is 1 minute, can be overriden with 
IgniteSystemProperties#IGNITE_REBALANCE_STATISTICS_TIME_INTERVAL.

> Export rebalance metrics and state as MBeans
> 
>
> Key: IGNITE-4861
> URL: https://issues.apache.org/jira/browse/IGNITE-4861
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Ivan Rakov
> Fix For: 2.0
>
>
> It would be nice to have rebalance metrics on an MBean:
> 1) Number of partitions to be rebalanced
> 2) Estimated number of keys to be rebalanced
> 3) Average rebalancing rate
> Any other metrics that might be useful



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-532) Implement IgniteAkkaStreamer to stream data from Akka actors.

[Maksim Kozlov (JIRA)]

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

Maksim Kozlov commented on IGNITE-532:
--

Hi guys,
I have some questions about the issue:
1. Akka-stream workflow implementation few stages:
{noformat}
akka-stream source -> akka-stream flow -> akka-stream sink (ignite-stream)
{noformat}
Will it be enough to implement the creation of a Sink object in ignite-stream 
for workflow akka-stream?
2. Support for the akka-actor is relevant?

> Implement IgniteAkkaStreamer to stream data from Akka actors.
> -
>
> Key: IGNITE-532
> URL: https://issues.apache.org/jira/browse/IGNITE-532
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Maksim Kozlov
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [Akka|http://akka.io/] for more information. Given that Akka is a Scala 
> frameworks, this streamer should be available in Scala.
> We should create {{IgniteAkkaStreamer}} which will consume messages from Akka 
> Actors and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert data from Akka to Ignite using an optional pluggable converter. If 
> not provided, then we should have some default mechanism.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4615) Ignite should be compilable under JDK 9

[Evgenii Zhuravlev (JIRA)]

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

Evgenii Zhuravlev commented on IGNITE-4615:
---

Also, maven-surefire-plugin doesn't works with java 9, so, it's not possible to 
run tests from maven.

> Ignite should be compilable under JDK 9
> ---
>
> Key: IGNITE-4615
> URL: https://issues.apache.org/jira/browse/IGNITE-4615
> Project: Ignite
>  Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Evgenii Zhuravlev
> Fix For: 2.0
>
> Attachments: ignite.jar.dot
>
>
> The original discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Should-we-take-care-of-Java-9-in-Ignite-2-0-scope-td14018.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4861) Export rebalance metrics and state as MBeans

[Ivan Rakov (JIRA)]

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

Ivan Rakov commented on IGNITE-4861:


The following metrics added to CacheMetrics:
{code}
/**
 * @return Total number of partitions on current node.
 */
public int getTotalPartitionsCount();

/**
 * @return Number of currently rebalancing partitions on current node.
 */
public int getRebalancingPartitionsCount();

/**
 * @return Estimated number of keys to be rebalanced on current node.
 */
public long getKeysToRebalanceLeft();

/**
 * @return Estimated rebalancing speed in keys.
 */
public long getRebalancingKeysRate();

/**
 * @return Estimated rebalancing speed in bytes.
 */
public long getRebalancingBytesRate();
{code}
Default timeframe for rate metrics is 1 minute, can be overriden with 
IgniteSystemProperties#IGNITE_REBALANCE_STATISTICS_TIME_INTERVAL.

> Export rebalance metrics and state as MBeans
> 
>
> Key: IGNITE-4861
> URL: https://issues.apache.org/jira/browse/IGNITE-4861
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Ivan Rakov
> Fix For: 2.0
>
>
> It would be nice to have rebalance metrics on an MBean:
> 1) Number of partitions to be rebalanced
> 2) Estimated number of keys to be rebalanced
> 3) Average rebalancing rate
> Any other metrics that might be useful



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4068) Web console: Extended actions in dropdown menus should contain base action.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-4068:


Assignee: Alexey Kuznetsov  (was: Andrey Novikov)

> Web console: Extended actions in dropdown menus should contain base action.
> ---
>
> Key: IGNITE-4068
> URL: https://issues.apache.org/jira/browse/IGNITE-4068
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
> Attachments: dropdown.png
>
>
> F.e. Dropdown for remove button should contain remove action too how on 
> execute and scan buttons. (See attach)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-2278) Rework all tooltips - add bullets where multilines text

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-2278:
--

Assignee: Andrey Novikov  (was: Pavel Konstantinov)

> Rework all tooltips - add bullets where multilines text
> ---
>
> Key: IGNITE-2278
> URL: https://issues.apache.org/jira/browse/IGNITE-2278
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Andrey Novikov
>
> We need to add bullets in tooltips where it make sense for better usability.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-2278) Rework all tooltips - add bullets where multilines text

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-2278:


Tested.

> Rework all tooltips - add bullets where multilines text
> ---
>
> Key: IGNITE-2278
> URL: https://issues.apache.org/jira/browse/IGNITE-2278
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
>
> We need to add bullets in tooltips where it make sense for better usability.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4985) Atomic cache operations acquire backpressure semaphore on retries

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-4985:
--

This leads to failover2 suite hanging.

> Atomic cache operations acquire backpressure semaphore on retries
> -
>
> Key: IGNITE-4985
> URL: https://issues.apache.org/jira/browse/IGNITE-4985
> Project: Ignite
>  Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-4985) Atomic cache operations acquire backpressure semaphore on retries

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-4985:


 Summary: Atomic cache operations acquire backpressure semaphore on 
retries
 Key: IGNITE-4985
 URL: https://issues.apache.org/jira/browse/IGNITE-4985
 Project: Ignite
  Issue Type: Bug
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
 Fix For: 2.0






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4551) Reconsider cache key/value peer class loading

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk updated IGNITE-4551:
-
Issue Type: Bug  (was: Sub-task)
Parent: (was: IGNITE-3477)

> Reconsider cache key/value peer class loading
> -
>
> Key: IGNITE-4551
> URL: https://issues.apache.org/jira/browse/IGNITE-4551
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Nikolay Tikhonov
> Fix For: 2.0
>
>
> In new cache implementation after entry is written in offheap information 
> about key/value classloaders in lost (before classloader ids were stored in 
> swap/offheap see GridCacheMapEntry.swap in 'master').
> Need decide how it should work with new architecture (maybe single type per 
> cache can simplify implementation).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (IGNITE-3477) Rework offheap storage

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk resolved IGNITE-3477.
--
Resolution: Fixed

Merged to master

> Rework offheap storage
> --
>
> Key: IGNITE-3477
> URL: https://issues.apache.org/jira/browse/IGNITE-3477
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>  Labels: important
> Fix For: 2.0
>
>
> Current (Ignite 1.x) implementation of cache storage relies on a tiered 
> approach where cache entry can be located in one of the three storage areas: 
> on-heap, off-heap memory and swap. It leads to the following disadvantages:
>  * Entry constantly moves from one storage area to another which leads to a 
> complex code (for example, swap/unswap listeners for queries and rebalancing)
>  * It is not possible to set per-cache memory limit
>  * Off-heap indexes require on-heap row cache. If this cache is small, 
> performance becomes very poor
>  * Continuous put/remove operations with OFFHEAP_TIERED mode lead to 
> uncontrollable memory fragmentation
> We can reapproach the cache storage and base it on a concept of page memory. 
> We will allocate several memory pools of pages of fixed size and assign each 
> cache to one of the memory pools. All storage data structures should operate 
> on memory pages, the main storage will be always off-heap with an optional 
> on-heap cache.
> This gives us the following benefits:
>  * Flexible and precise per-cache memory limit
>  * Transparent swap: we can allocate page memory over a memory-mapped file 
> and OS will take care of swapping
>  * Getting rid of on-heap cache for off-heap SQL indexes
>  * Ability to take a cluster-wide data snapshot
> I suggest the following API for memory policy configuration:
> {code}
> class MemoryPolicy {
> boolean default; // Require at least one memory policy to be default.
> private String name;
> private long size;
> private String tmpFsPath; // If memory-mapped file should be used.
> }
> class CacheConfiguration {
> 
> private String memoryPolicyName;
> 
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4068) Web console: Extended actions in dropdown menus should contain base action.

[Dmitriy Shabalin (JIRA)]

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

Dmitriy Shabalin reassigned IGNITE-4068:


Assignee: Andrey Novikov  (was: Dmitriy Shabalin)

added common primitive to output buttons group, pls review it

> Web console: Extended actions in dropdown menus should contain base action.
> ---
>
> Key: IGNITE-4068
> URL: https://issues.apache.org/jira/browse/IGNITE-4068
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>Assignee: Andrey Novikov
> Attachments: dropdown.png
>
>
> F.e. Dropdown for remove button should contain remove action too how on 
> execute and scan buttons. (See attach)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-3592) Provide some kind of pluggable compression SPI support

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur updated IGNITE-3592:
---
Fix Version/s: (was: 2.0)
   2.1

> Provide some kind of pluggable compression SPI support
> --
>
> Key: IGNITE-3592
> URL: https://issues.apache.org/jira/browse/IGNITE-3592
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Alexey Kuznetsov
>Assignee: Vyacheslav Daradur
> Fix For: 2.1
>
>
> It may be useful in some cases to compress data stored in cache.
> And in order to give access to compressed data from SQL engine this support 
> should be implemented in ignite-core level.
> See discussion on dev-list: 
> http://apache-ignite-developers.2346864.n4.nabble.com/Data-compression-in-Ignite-2-0-td10099.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-3920) Hadoop: remove PayloadAware interface.

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov edited comment on IGNITE-3920 at 4/14/17 9:52 AM:
-

Successfully tested. Please merge into target branch.


was (Author: pkonstantinov):
Successfully tested.

> Hadoop: remove PayloadAware interface.
> --
>
> Key: IGNITE-3920
> URL: https://issues.apache.org/jira/browse/IGNITE-3920
> Project: Ignite
>  Issue Type: Task
>  Components: hadoop
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Pavel Konstantinov
> Fix For: 2.0
>
> Attachments: default-config.xml
>
>
> When IGNITE-3376 is ready, we will be able to execute {{PROXY}} operations 
> directly from {{IgfsImpl}}. It means that we no longer need 
> {{HadoopPayloadAware}} interface, and we no longer need to pass {{IgfsPaths}} 
> to the client. 
> Let's remove them all together.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-4182) Improve error output when query parsing failed.

[Alexei Kaigorodov (JIRA)]

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

Alexei Kaigorodov edited comment on IGNITE-4182 at 4/14/17 9:51 AM:


I was wrong sayng the poor diagnostics goes from the H2 jdbc driver.
Actually, if we look deeper into "caused by" chain, we can see original H2 
message Table "B" not found:

Exception in thread "main" javax.cache.CacheException: class 
org.apache.ignite.IgniteException: Failed to parse query: select A from B
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:806)
at 
org.apache.ignite.examples.datagrid.CacheQueryExample.sqlQueryWithError(CacheQueryExample.java:318)
at 
org.apache.ignite.examples.datagrid.CacheQueryExample.main(CacheQueryExample.java:112)
Caused by: class org.apache.ignite.IgniteException: Failed to parse query: 
select A from B
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:414)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:794)
... 2 more
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to parse 
query: select A from B
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:832)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:407)
... 3 more
Caused by: class 
org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse 
query: select A from B
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1447)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$2.applyx(GridQueryProcessor.java:409)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$2.applyx(GridQueryProcessor.java:407)
at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:809)
... 4 more
Caused by: org.h2.jdbc.JdbcSQLException: Таблица "B" не найдена
Table "B" not found; SQL statement:
select A from B [42102-191]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at org.h2.command.Parser.readTableOrView(Parser.java:5349)
at org.h2.command.Parser.readTableFilter(Parser.java:1245)
at org.h2.command.Parser.parseSelectSimpleFromPart(Parser.java:1884)
at org.h2.command.Parser.parseSelectSimple(Parser.java:2032)
at org.h2.command.Parser.parseSelectSub(Parser.java:1878)
at org.h2.command.Parser.parseSelectUnion(Parser.java:1699)
at org.h2.command.Parser.parseSelect(Parser.java:1687)
at org.h2.command.Parser.parsePrepared(Parser.java:443)
at org.h2.command.Parser.parse(Parser.java:315)
at org.h2.command.Parser.parse(Parser.java:287)
at org.h2.command.Parser.prepareCommand(Parser.java:252)
at org.h2.engine.Session.prepareLocal(Session.java:560)
at org.h2.engine.Session.prepareCommand(Session.java:501)
at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1188)
at 
org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:73)
at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:276)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:446)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1431)
... 8 more

Process finished with exit code 1



was (Author: rfq):
the poor diagnostics goes from the H2 jdbc driver.

> Improve error output when query parsing failed.
> ---
>
> Key: IGNITE-4182
> URL: https://issues.apache.org/jira/browse/IGNITE-4182
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Priority: Minor
> Fix For: 2.1
>
>
> There is no enough information in the exception when SLQ query can not be 
> parsed. In most cases we get something like this:
> {noformat}
> Failed to execute SQL query [reqId=2, req=OdbcQueryExecuteRequest 
> [cacheName=cache, sqlQry=SELECT a FROM B, args=[]]]
> javax.cache.CacheException: class org.apache.ignite.IgniteException: Failed 
> to parse query: SELECT a FROM B
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:740)
>  

[jira] [Assigned] (IGNITE-3920) Hadoop: remove PayloadAware interface.

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-3920:
--

Assignee: Taras Ledkov  (was: Pavel Konstantinov)

> Hadoop: remove PayloadAware interface.
> --
>
> Key: IGNITE-3920
> URL: https://issues.apache.org/jira/browse/IGNITE-3920
> Project: Ignite
>  Issue Type: Task
>  Components: hadoop
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
> Attachments: default-config.xml
>
>
> When IGNITE-3376 is ready, we will be able to execute {{PROXY}} operations 
> directly from {{IgfsImpl}}. It means that we no longer need 
> {{HadoopPayloadAware}} interface, and we no longer need to pass {{IgfsPaths}} 
> to the client. 
> Let's remove them all together.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3920) Hadoop: remove PayloadAware interface.

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-3920:


Successfully tested.

> Hadoop: remove PayloadAware interface.
> --
>
> Key: IGNITE-3920
> URL: https://issues.apache.org/jira/browse/IGNITE-3920
> Project: Ignite
>  Issue Type: Task
>  Components: hadoop
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Pavel Konstantinov
> Fix For: 2.0
>
> Attachments: default-config.xml
>
>
> When IGNITE-3376 is ready, we will be able to execute {{PROXY}} operations 
> directly from {{IgfsImpl}}. It means that we no longer need 
> {{HadoopPayloadAware}} interface, and we no longer need to pass {{IgfsPaths}} 
> to the client. 
> Let's remove them all together.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-4984) AssertionError GridNearAtomicSingleUpdateFuture.onAllReceived on node left

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-4984:


 Summary: AssertionError 
GridNearAtomicSingleUpdateFuture.onAllReceived on node left
 Key: IGNITE-4984
 URL: https://issues.apache.org/jira/browse/IGNITE-4984
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Semen Boikov
Assignee: Semen Boikov
Priority: Critical
 Fix For: 2.1


Observed this assertion:
{noformat}
[17:36:35]W: [org.apache.ignite:ignite-core] 
[14:36:35,825][ERROR][disco-event-worker-#15603%atomic.IgniteCachePutRetryAtomicPrimaryWriteOrderSelfTest0%][GridEventStorageManager]
 Unexpected exception in listener notification for event: DiscoveryEvent 
[evtNode=TcpDiscoveryNode [id=aad85fba-82f7-4e2e-9e88-002251f3, 
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47502], discPort=47502, order=22, 
intOrder=13, lastExchangeTime=1492094195733, loc=false, 
ver=2.0.0#19700101-sha1:, isClient=false], topVer=23, nodeId8=23f2fe27, 
msg=Node left: TcpDiscoveryNode [id=aad85fba-82f7-4e2e-9e88-002251f3, 
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47502], discPort=47502, order=22, 
intOrder=13, lastExchangeTime=1492094195733, loc=false, 
ver=2.0.0#19700101-sha1:, isClient=false], type=NODE_LEFT, 
tstamp=1492094195813]
[17:36:35]W: [org.apache.ignite:ignite-core] 
java.lang.AssertionError
[17:36:35]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onAllReceived(GridNearAtomicSingleUpdateFuture.java:336)
[17:36:35]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onNodeLeft(GridNearAtomicSingleUpdateFuture.java:176)
[17:36:35]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCacheMvccManager$4.onEvent(GridCacheMvccManager.java:266)
[17:36:35]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager$LocalListenerWrapper.onEvent(GridEventStorageManager.java:1311)
[17:36:35]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:892)
[17:36:35]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record0(GridEventStorageManager.java:340)
[17:36:35]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:307)
[17:36:35]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:2277)
[17:36:35]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:2474)
[17:36:35]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:2306)
[17:36:35]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
[17:36:35]W: [org.apache.ignite:ignite-core]at 
java.lang.Thread.run(Thread.java:745)
[17:36:35]W: [org.apache.ignite:ignite-core] 
[14:36:35,826][ERROR][disco-event-worker-#15603%atomic.IgniteCachePutRetryAtomicPrimaryWriteOrderSelfTest0%][GridDiscoveryManager]
 Unexpected exception in discovery worker thread (ignored).
[17:36:35]W: [org.apache.ignite:ignite-core] 
java.lang.AssertionError
[17:36:35]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onAllReceived(GridNearAtomicSingleUpdateFuture.java:336)
[17:36:35]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onNodeLeft(GridNearAtomicSingleUpdateFuture.java:176)
[17:36:35]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCacheMvccManager$4.onEvent(GridCacheMvccManager.java:266)
[17:36:35]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager$LocalListenerWrapper.onEvent(GridEventStorageManager.java:1311)
[17:36:35]W: [org.apache.ignite:ignite-core]at 

[jira] [Comment Edited] (IGNITE-4565) Support CREATE INDEX DDL statements

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov edited comment on IGNITE-4565 at 4/14/17 9:29 AM:
--

Outstanding issues:
1) Fix client reconnect schema consistency issue
2) Fix DROP INDEX data consistency issue (+ add more concurrent data tests).


was (Author: vozerov):
Outstanding issues:
1) Merge with 3477
2) Fix client reconnect schema consistency issue
3) Fix DROP INDEX data consistency issue (+ add more concurrent data tests).

> Support CREATE INDEX DDL statements
> ---
>
> Key: IGNITE-4565
> URL: https://issues.apache.org/jira/browse/IGNITE-4565
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache, SQL
>Reporter: Alexander Paschenko
>Assignee: Vladimir Ozerov
>  Labels: important
> Fix For: 2.0
>
>
> We need to implement support for dynamic {{CREATE INDEX}} and {{DROP INDEX}} 
> invocations.
> Design document: 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=67640367
> Base branch: {{ignite-4565}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4950) Do not allow AffinityKeyMapped annotation on methods

[Konstantin Dudkov (JIRA)]

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

Konstantin Dudkov commented on IGNITE-4950:
---

[TC tests 
run|http://ci.ignite.apache.org/project.html?projectId=IgniteTests=projectOverview_IgniteTests=pull%2F1781%2Fhead]

I think I didn't add new failures.

> Do not allow AffinityKeyMapped annotation on methods
> 
>
> Key: IGNITE-4950
> URL: https://issues.apache.org/jira/browse/IGNITE-4950
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Konstantin Dudkov
>  Labels: important
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4052) Add ability to set up users for MESOS

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov commented on IGNITE-4052:
--

[~javaller]
It meens that lets remove #setEnv mathod and will create mock in test which 
will override {{getUser}} and {{getRole}} methods. Also how do you think might 
be need to add validation for role? Which valid set of values for this property?

> Add ability to set up users for MESOS
> -
>
> Key: IGNITE-4052
> URL: https://issues.apache.org/jira/browse/IGNITE-4052
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.7
>Reporter: Nikolay Tikhonov
>Assignee: Vadim Opolski
>Priority: Trivial
>
> In current implementation Ignite Mesos Framework connects to MESOS cluster 
> via current user. Need to add ability to configure this parameters via system 
> env properties. Also need to add properties for mesos role.
> See org/apache/ignite/mesos/IgniteFramework.java:537



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-4983) .NET: Cache plugins do not work

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4983:
--

 Summary: .NET: Cache plugins do not work
 Key: IGNITE-4983
 URL: https://issues.apache.org/jira/browse/IGNITE-4983
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 2.0
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.0


IGNITE-3477 brought breaking changes to cache plugin infrastructure. Now cache 
plugins can not exist independently of grid plugins: 
{{PluginProvider.createCacheProvider}} creates cache provider, instead of 
{{CachePluginConfiguration.createProvider}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-1561) Cross cache tx tests with near cache fail with asserts

[Semen Boikov (JIRA)]

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

Semen Boikov reassigned IGNITE-1561:


Assignee: Semen Boikov

> Cross cache tx tests with near cache fail with asserts
> --
>
> Key: IGNITE-1561
> URL: https://issues.apache.org/jira/browse/IGNITE-1561
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: 2.1
>
>
> I added in master cross cache txs test from ignite-80 branch 
> (IgniteCrossCacheTxNearEnabledSelfTest), it fails with various asserts, e.g.:
> {noformat}
> java.lang.AssertionError
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxMapping.initLast(GridDhtTxMapping.java:86)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepare(GridNearOptimisticTxPrepareFuture.java:544)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepare0(GridNearOptimisticTxPrepareFuture.java:452)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepareOnTopology(GridNearOptimisticTxPrepareFuture.java:341)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepare(GridNearOptimisticTxPrepareFuture.java:279)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.prepareAsync(GridNearTxLocal.java:758)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.commitAsync(GridNearTxLocal.java:769)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheSharedContext.commitTxAsync(GridCacheSharedContext.java:642)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.TransactionProxyImpl.commit(TransactionProxyImpl.java:256)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteCrossCacheTxSelfTest.checkTxsSingleOp(IgniteCrossCacheTxSelfTest.java:170)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteCrossCacheTxSelfTest.testOptimisticRepeatableRead(IgniteCrossCacheTxSelfTest.java:136)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
> {noformat}
> Test pass is near cache is disabled (added separate test for this mode: 
> IgniteCrossCacheTxSelfTest).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4387) Incorrect Karaf OSGI feature for ignite-rest-http

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-4387:


Resolution: Fixed
  Assignee: Sergey Kozlov  (was: Alexey Kuznetsov)

OSGI suite TC passed. Merged to master.
Please test.

> Incorrect Karaf OSGI feature for ignite-rest-http
> -
>
> Key: IGNITE-4387
> URL: https://issues.apache.org/jira/browse/IGNITE-4387
> Project: Ignite
>  Issue Type: Bug
>  Components: osgi, rest
>Affects Versions: 1.7
>Reporter: Sergej Sidorov
>Assignee: Sergey Kozlov
>Priority: Minor
> Fix For: 2.0
>
>
> In accordance with the commit f177d4312c47 (IGNITE-3277 Replaced outdated 
> json-lib 2.4 to modern Jackson 2.7.5) dependencies in module ignite-rest-http 
> have been updated. But Karaf OSGI features config has not been updated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4387) Incorrect Karaf OSGI feature for ignite-rest-http

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-4387:
-
Fix Version/s: (was: 2.1)
   2.0

> Incorrect Karaf OSGI feature for ignite-rest-http
> -
>
> Key: IGNITE-4387
> URL: https://issues.apache.org/jira/browse/IGNITE-4387
> Project: Ignite
>  Issue Type: Bug
>  Components: osgi, rest
>Affects Versions: 1.7
>Reporter: Sergej Sidorov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 2.0
>
>
> In accordance with the commit f177d4312c47 (IGNITE-3277 Replaced outdated 
> json-lib 2.4 to modern Jackson 2.7.5) dependencies in module ignite-rest-http 
> have been updated. But Karaf OSGI features config has not been updated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4572) Machine Learning: Develop distributed algebra support for dense and sparse data sets.

[JIRA]

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

Alper Çakan commented on IGNITE-4572:
-

[~dmagda]

I'm so sorry for my very late reply.

Thank you and Mr. Ivanov very much for your help!

> Machine Learning: Develop distributed algebra support for dense and sparse 
> data sets.
> -
>
> Key: IGNITE-4572
> URL: https://issues.apache.org/jira/browse/IGNITE-4572
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Nikita Ivanov
>Assignee: Nikita Ivanov
>  Labels: gsoc2017
>
> Apache Ignite community has recently kicked off development of its new 
> component - Apache Ignite Machine Learning Grid. The component will empower 
> researchers, scientists, engineers and companies to train, deploy and execute 
> machine learning models in a distributed fashion gaining significant 
> performance benefits and making real the ability to apply machine learning 
> for Big Data use cases in real-time or near real-time scenarios.
> This is the base functionality for adding support for future ML capabilities. 
> Subtasks will be created and linked to this ticket later on.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4964) Document Machine Learning Grid (Distributed Algebra Implementation)

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko commented on IGNITE-4964:


me and Nikita are going to take care of this. See also dev list: 
http://apache-ignite-developers.2346864.n4.nabble.com/Adding-ML-to-Ignite-IGNITE-4572-tp13936p16603.html

> Document Machine Learning Grid (Distributed Algebra Implementation)
> ---
>
> Key: IGNITE-4964
> URL: https://issues.apache.org/jira/browse/IGNITE-4964
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Denis Magda
>Assignee: Nikita Ivanov
> Fix For: 2.0
>
>
> In Apache Ignite 2.0 we introduce support for distributed algebra on top of 
> Ignite. This considered to be a foundation of Ignite's Machine Learning 
> framework discussed here:
> http://apache-ignite-developers.2346864.n4.nabble.com/Adding-ML-to-Ignite-IGNITE-4572-td13936.html
> Let's make an overview of the current implementation, its usage, and refer to 
> developed examples as a part of the readme.io documentation. Here is an 
> invisible page created for this purpose:
> https://dash.readme.io/project/apacheignite/v1.9/docs/distributed-algebra
> Please assign the ticket on [~dmagda] for the final review.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4982) GridCacheAbstractRemoveFailureTest fail

[Konstantin Dudkov (JIRA)]

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

Konstantin Dudkov commented on IGNITE-4982:
---

The point was as follows:

In some situations we try to add to GridDhtAtomicSingleUpdateRequest both 
writeValue and nearWriteValue. But in case of adding nearWriteValue we 
overwrite writeValue and node doesn't process DHT update. I add saparate flag 
in GridDhtAtomicSingleUpdateRequest so now node can process this situation 
right.

[PR|https://github.com/apache/ignite/pull/1792]

Please review.

> GridCacheAbstractRemoveFailureTest fail
> ---
>
> Key: IGNITE-4982
> URL: https://issues.apache.org/jira/browse/IGNITE-4982
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Konstantin Dudkov
>Assignee: Konstantin Dudkov
> Fix For: 2.0
>
>
> GridCacheAbstractRemoveFailureTest (and some child tests) fails. Reproducer:
> {code:java}
> import java.util.Collection;
> import java.util.HashSet;
> import java.util.Map;
> import java.util.concurrent.Callable;
> import java.util.concurrent.CyclicBarrier;
> import java.util.concurrent.ThreadLocalRandom;
> import java.util.concurrent.TimeUnit;
> import java.util.concurrent.TimeoutException;
> import java.util.concurrent.atomic.AtomicBoolean;
> import java.util.concurrent.atomic.AtomicLong;
> import java.util.concurrent.atomic.AtomicReference;
> import javax.cache.CacheException;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteCache;
> import org.apache.ignite.IgniteException;
> import org.apache.ignite.IgniteTransactions;
> import org.apache.ignite.cache.CacheAtomicWriteOrderMode;
> import org.apache.ignite.cache.CacheAtomicityMode;
> import org.apache.ignite.cache.CacheMode;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.configuration.NearCacheConfiguration;
> import org.apache.ignite.internal.IgniteInternalFuture;
> import org.apache.ignite.internal.cluster.ClusterTopologyCheckedException;
> import org.apache.ignite.internal.util.lang.GridTuple;
> import org.apache.ignite.internal.util.typedef.F;
> import org.apache.ignite.internal.util.typedef.T2;
> import org.apache.ignite.internal.util.typedef.X;
> import org.apache.ignite.internal.util.typedef.internal.U;
> import org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi;
> import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.TcpDiscoveryIpFinder;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
> import org.apache.ignite.testframework.GridTestUtils;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> import org.apache.ignite.transactions.Transaction;
> import org.apache.ignite.transactions.TransactionConcurrency;
> import org.apache.ignite.transactions.TransactionIsolation;
> import org.jsr166.ConcurrentHashMap8;
> import static 
> org.apache.ignite.IgniteSystemProperties.IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE;
> import static org.apache.ignite.cache.CacheMode.PARTITIONED;
> import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;
> import static 
> org.apache.ignite.transactions.TransactionConcurrency.OPTIMISTIC;
> import static 
> org.apache.ignite.transactions.TransactionConcurrency.PESSIMISTIC;
> import static 
> org.apache.ignite.transactions.TransactionIsolation.REPEATABLE_READ;
> import static 
> org.apache.ignite.transactions.TransactionIsolation.SERIALIZABLE;
> /**
>  * Tests that removes are not lost when topology changes.
>  */
> public abstract class GridCacheAbstractRemoveFailureTest extends 
> GridCommonAbstractTest {
> /** IP finder. */
> private static final TcpDiscoveryIpFinder IP_FINDER = new 
> TcpDiscoveryVmIpFinder(true);
> /** */
> private static final int GRID_CNT = 3;
> /** Keys count. */
> private static final int KEYS_CNT = 10_000;
> /** Test duration. */
> private static final long DUR = 90 * 1000L;
> /** Cache data assert frequency. */
> private static final long ASSERT_FREQ = 10_000;
> /** Kill delay. */
> private static final T2 KILL_DELAY = new T2<>(2000, 
> 5000);
> /** Start delay. */
> private static final T2 START_DELAY = new T2<>(2000, 
> 5000);
> /** */
> private static String sizePropVal;
> /** {@inheritDoc} */
> @Override protected IgniteConfiguration getConfiguration(String 
> igniteInstanceName) throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
> 
> ((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER).setForceServerMode(true);
> if 

[jira] [Updated] (IGNITE-4982) GridCacheAbstractRemoveFailureTest fail

[Konstantin Dudkov (JIRA)]

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

Konstantin Dudkov updated IGNITE-4982:
--
Description: 
GridCacheAbstractRemoveFailureTest (and some child tests) fails. Reproducer:

{code:java}
import java.util.Collection;
import java.util.HashSet;
import java.util.Map;
import java.util.concurrent.Callable;
import java.util.concurrent.CyclicBarrier;
import java.util.concurrent.ThreadLocalRandom;
import java.util.concurrent.TimeUnit;
import java.util.concurrent.TimeoutException;
import java.util.concurrent.atomic.AtomicBoolean;
import java.util.concurrent.atomic.AtomicLong;
import java.util.concurrent.atomic.AtomicReference;
import javax.cache.CacheException;
import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteCache;
import org.apache.ignite.IgniteException;
import org.apache.ignite.IgniteTransactions;
import org.apache.ignite.cache.CacheAtomicWriteOrderMode;
import org.apache.ignite.cache.CacheAtomicityMode;
import org.apache.ignite.cache.CacheMode;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.configuration.NearCacheConfiguration;
import org.apache.ignite.internal.IgniteInternalFuture;
import org.apache.ignite.internal.cluster.ClusterTopologyCheckedException;
import org.apache.ignite.internal.util.lang.GridTuple;
import org.apache.ignite.internal.util.typedef.F;
import org.apache.ignite.internal.util.typedef.T2;
import org.apache.ignite.internal.util.typedef.X;
import org.apache.ignite.internal.util.typedef.internal.U;
import org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi;
import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
import org.apache.ignite.spi.discovery.tcp.ipfinder.TcpDiscoveryIpFinder;
import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
import org.apache.ignite.testframework.GridTestUtils;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
import org.apache.ignite.transactions.Transaction;
import org.apache.ignite.transactions.TransactionConcurrency;
import org.apache.ignite.transactions.TransactionIsolation;
import org.jsr166.ConcurrentHashMap8;

import static 
org.apache.ignite.IgniteSystemProperties.IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE;
import static org.apache.ignite.cache.CacheMode.PARTITIONED;
import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;
import static org.apache.ignite.transactions.TransactionConcurrency.OPTIMISTIC;
import static org.apache.ignite.transactions.TransactionConcurrency.PESSIMISTIC;
import static 
org.apache.ignite.transactions.TransactionIsolation.REPEATABLE_READ;
import static org.apache.ignite.transactions.TransactionIsolation.SERIALIZABLE;

/**
 * Tests that removes are not lost when topology changes.
 */
public abstract class GridCacheAbstractRemoveFailureTest extends 
GridCommonAbstractTest {
/** IP finder. */
private static final TcpDiscoveryIpFinder IP_FINDER = new 
TcpDiscoveryVmIpFinder(true);

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

/** Keys count. */
private static final int KEYS_CNT = 10_000;

/** Test duration. */
private static final long DUR = 90 * 1000L;

/** Cache data assert frequency. */
private static final long ASSERT_FREQ = 10_000;

/** Kill delay. */
private static final T2 KILL_DELAY = new T2<>(2000, 5000);

/** Start delay. */
private static final T2 START_DELAY = new T2<>(2000, 
5000);

/** */
private static String sizePropVal;

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


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

if (testClientNode() && 
getTestIgniteInstanceName(0).equals(igniteInstanceName))
cfg.setClientMode(true);


((TcpCommunicationSpi)cfg.getCommunicationSpi()).setSharedMemoryPort(-1);

return cfg;
}

/** {@inheritDoc} */
@Override protected void beforeTestsStarted() throws Exception {
// Need to increase value set in GridAbstractTest
sizePropVal = 
System.getProperty(IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE);

System.setProperty(IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE, "10");

startGrids(GRID_CNT);
}

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

System.setProperty(IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE, sizePropVal 
!= null ? sizePropVal : "");

stopAllGrids();
}

/** {@inheritDoc} */
@Override protected long getTestTimeout() {
return DUR + 60_000;
}

/**
 * 

[jira] [Comment Edited] (IGNITE-3488) Prohibit null as name in all the components (cache name first of all).

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov edited comment on IGNITE-3488 at 4/14/17 7:41 AM:
---

Changes in ignite-core are ready
I hope I've fixed all places where null cache name is used in tests (about 600 
java classes), waiting for results from TC


was (Author: gvvinblade):
Cachges in ignite-core are ready
I hope I've fixed all places where null cache name is used in tests (about 600 
java classes), waiting for results from TC

> Prohibit null as name in all the components (cache name first of all).
> --
>
> Key: IGNITE-3488
> URL: https://issues.apache.org/jira/browse/IGNITE-3488
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergi Vladykin
>Assignee: Igor Seliverstov
>Priority: Critical
>  Labels: important
> Fix For: 2.0
>
>
> Need to create a list of all the affected components.
> 2.0 migration guide has to be updated: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)