[jira] [Resolved] (IGNITE-8240) .NET: Use default scheduler when starting Tasks

2018-04-13 Thread Pavel Tupitsyn (JIRA) 

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

Pavel Tupitsyn resolved IGNITE-8240.

Resolution: Fixed

Merged to master: {{44c4656ce8cc304b0858a18438f57fd9daf9ecb0}}

> .NET: Use default scheduler when starting Tasks
> ---
>
> Key: IGNITE-8240
> URL: https://issues.apache.org/jira/browse/IGNITE-8240
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.5
>
>
> Default scheduler should be specified explicitly when starting new tasks to 
> avoid deadlocks: 
> http://blog.stephencleary.com/2013/10/continuewith-is-dangerous-too.html
> This applies to {{StartNew}}, {{ConyinueWith}}, etc.



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

[jira] [Updated] (IGNITE-8210) Rebalancing sometimes is not triggered when a node is added to the baseline topology

2018-04-13 Thread Sergey Chugunov (JIRA) 

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

Sergey Chugunov updated IGNITE-8210:

Fix Version/s: 2.5

> Rebalancing sometimes is not triggered when a node is added to the baseline 
> topology
> 
>
> Key: IGNITE-8210
> URL: https://issues.apache.org/jira/browse/IGNITE-8210
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Reporter: Stanislav Lukyanov
>Assignee: Sergey Chugunov
>Priority: Major
> Fix For: 2.5
>
> Attachments: RebalanceAfterNodeAddedToBaseline.java
>
>
> When a cluster already has baseline topology set and activated adding a new 
> node to the baseline should lead to rebalancing. However, in some cases the 
> new node will not receive any data when joined and added to the baseline; if 
> a cluster is later deactivated and activated again, the rebalancing happens 
> properly and partitions are assigned and transferred to the new node.



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

[jira] [Commented] (IGNITE-8210) Rebalancing sometimes is not triggered when a node is added to the baseline topology

2018-04-13 Thread Sergey Chugunov (JIRA) 

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

Sergey Chugunov commented on IGNITE-8210:
-

Fix artifacts: [PR|https://github.com/apache/ignite/pull/3814], 
[TC|https://ci.ignite.apache.org/viewQueued.html?itemId=1201192=queuedBuildOverviewTab]

> Rebalancing sometimes is not triggered when a node is added to the baseline 
> topology
> 
>
> Key: IGNITE-8210
> URL: https://issues.apache.org/jira/browse/IGNITE-8210
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Reporter: Stanislav Lukyanov
>Assignee: Sergey Chugunov
>Priority: Major
> Attachments: RebalanceAfterNodeAddedToBaseline.java
>
>
> When a cluster already has baseline topology set and activated adding a new 
> node to the baseline should lead to rebalancing. However, in some cases the 
> new node will not receive any data when joined and added to the baseline; if 
> a cluster is later deactivated and activated again, the rebalancing happens 
> properly and partitions are assigned and transferred to the new node.



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

[jira] [Assigned] (IGNITE-8210) Rebalancing sometimes is not triggered when a node is added to the baseline topology

2018-04-13 Thread Sergey Chugunov (JIRA) 

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

Sergey Chugunov reassigned IGNITE-8210:
---

Assignee: Sergey Chugunov

> Rebalancing sometimes is not triggered when a node is added to the baseline 
> topology
> 
>
> Key: IGNITE-8210
> URL: https://issues.apache.org/jira/browse/IGNITE-8210
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Reporter: Stanislav Lukyanov
>Assignee: Sergey Chugunov
>Priority: Major
> Attachments: RebalanceAfterNodeAddedToBaseline.java
>
>
> When a cluster already has baseline topology set and activated adding a new 
> node to the baseline should lead to rebalancing. However, in some cases the 
> new node will not receive any data when joined and added to the baseline; if 
> a cluster is later deactivated and activated again, the rebalancing happens 
> properly and partitions are assigned and transferred to the new node.



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

[jira] [Assigned] (IGNITE-8235) Implement execution of selected part of SQL query

2018-04-13 Thread Alexander Kalinin (JIRA) 

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

Alexander Kalinin reassigned IGNITE-8235:
-

Assignee: Pavel Konstantinov  (was: Alexander Kalinin)

Please test.
 * When user selects some rows in edito, only they should be executed
 * Refresh after executing partial query and check that partial sql expression 
should not be saved.

> Implement execution of selected part of SQL query
> -
>
> Key: IGNITE-8235
> URL: https://issues.apache.org/jira/browse/IGNITE-8235
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Pavel Konstantinov
>Priority: Minor
>
> If we had 3 SQL rows in the notebook, and selected one and clicked execute. 
> We should only execute the highlighted row. If no row is highlighted, then 
> all rows should be executed. That's a standard feature of graphical SQL tools.



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

[jira] [Commented] (IGNITE-7691) Provide info about DECIMAL column scale and precision

2018-04-13 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on IGNITE-7691:


Github user asfgit closed the pull request at:

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


> Provide info about DECIMAL column scale and precision
> -
>
> Key: IGNITE-7691
> URL: https://issues.apache.org/jira/browse/IGNITE-7691
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 2.4
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Minor
> Fix For: 2.6
>
>
> Currently, it impossible to obtain scale and precision of DECIMAL column from 
> sql table metadata.
> Ignite should provide those type of meta information.



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

[jira] [Updated] (IGNITE-7691) Provide info about DECIMAL column scale and precision

2018-04-13 Thread Nikolay Izhikov (JIRA) 

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

Nikolay Izhikov updated IGNITE-7691:

Fix Version/s: (was: 2.5)
   2.6

> Provide info about DECIMAL column scale and precision
> -
>
> Key: IGNITE-7691
> URL: https://issues.apache.org/jira/browse/IGNITE-7691
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 2.4
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Minor
> Fix For: 2.6
>
>
> Currently, it impossible to obtain scale and precision of DECIMAL column from 
> sql table metadata.
> Ignite should provide those type of meta information.



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

[jira] [Created] (IGNITE-8244) Sporadic ClusterTopologyCheckedException for the example run

2018-04-13 Thread Sergey Kozlov (JIRA) 
Sergey Kozlov created IGNITE-8244:
-

 Summary: Sporadic ClusterTopologyCheckedException for the example 
run
 Key: IGNITE-8244
 URL: https://issues.apache.org/jira/browse/IGNITE-8244
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.4
Reporter: Sergey Kozlov
 Fix For: 2.5


1. Start standalone node
2. Start example from the list:
{noformat}
org.apache.ignite.examples.binary.datagrid.store.auto.CacheBinaryAutoStoreExample
org.apache.ignite.examples.datagrid.store.CacheLoadOnlyStoreExample 
org.apache.ignite.examples.datastructures.IgniteSemaphoreExample    
org.apache.ignite.examples.java8.computegrid.ComputeCallableExample 
org.apache.ignite.examples.java8.datagrid.CacheApiExample   
org.apache.ignite.examples.datagrid.store.auto.CacheAutoStoreExample    
org.apache.ignite.examples.java8.cluster.ClusterGroupExample    
org.apache.ignite.examples.java8.computegrid.ComputeClosureExample  
org.apache.ignite.examples.java8.messaging.MessagingExample 
org.apache.ignite.examples.messaging.MessagingExample   
org.apache.ignite.scalar.examples.ScalarTaskExample 
org.apache.ignite.examples.datagrid.store.jdbc.CacheJdbcStoreExample    
org.apache.ignite.examples.java8.computegrid.ComputeAsyncExample    
org.apache.ignite.examples.java8.computegrid.ComputeRunnableExample 
org.apache.ignite.examples.java8.datagrid.CacheEntryProcessorExample    
org.apache.ignite.examples.java8.messaging.MessagingPingPongExample 
org.apache.ignite.examples.datagrid.store.spring.CacheSpringStoreExample    
org.apache.ignite.examples.java8.computegrid.ComputeBroadcastExample    
org.apache.ignite.examples.java8.datagrid.CacheAffinityExample  
org.apache.ignite.examples.java8.datastructures.IgniteExecutorServiceExample 
{noformat}
3. Sometimes example ends up with following exception:
{noformat}
class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
Failed to send message because node left grid 
[nodeId=178785f1-6df2-4395-82ba-5636b496f6cd, 
msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion 
[topVer=135009857, time=1523529863612, order=1523529860859, nodeOrder=1], 
GridCacheVersion [topVer=135009857, time=1523529863612, order=1523529860860, 
nodeOrder=1], GridCacheVersion [topVer=135009857, time=1523529863623, 
order=1523529860866, nodeOrder=1], GridCacheVersion [topVer=135009857, 
time=1523529863625, order=1523529860869, nodeOrder=1]], super=GridCacheMessage 
[msgId=-1, depInfo=null, err=null, skipPrepare=false, cacheId=0, cacheId=0]]]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1065)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6640)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:788)
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)
{noformat}



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

[jira] [Comment Edited] (IGNITE-7821) Unify and improve Apache Ignite and Web Console Dockerfiles

2018-04-13 Thread Andrey Novikov (JIRA) 

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

Andrey Novikov edited comment on IGNITE-7821 at 4/13/18 8:10 AM:
-

[~vveider], reviewed your changes in Webconsole Docker Standalone Image. Added 
comments in pull request, everything else looks good for me.


was (Author: anovikov):
[~vveider], reviewed your changes in Webconsole Docker Standalone Image. Added 
comments in pull request everything else looks good for me.

> Unify and improve Apache Ignite and Web Console Dockerfiles
> ---
>
> Key: IGNITE-7821
> URL: https://issues.apache.org/jira/browse/IGNITE-7821
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Critical
> Fix For: 2.5
>
>
> # Unify approach to docker build -- add instructions about how to build 
> specific docker images from binaries .
> # Change Apache Ignite's Dockerfile to get binaries from local build.



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

[jira] [Commented] (IGNITE-7821) Unify and improve Apache Ignite and Web Console Dockerfiles

2018-04-13 Thread Andrey Novikov (JIRA) 

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

Andrey Novikov commented on IGNITE-7821:


[~vveider], reviewed your changes in Webconsole Docker Standalone Image. Added 
comments in pull request everything else looks good for me.

> Unify and improve Apache Ignite and Web Console Dockerfiles
> ---
>
> Key: IGNITE-7821
> URL: https://issues.apache.org/jira/browse/IGNITE-7821
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Critical
> Fix For: 2.5
>
>
> # Unify approach to docker build -- add instructions about how to build 
> specific docker images from binaries .
> # Change Apache Ignite's Dockerfile to get binaries from local build.



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

[jira] [Assigned] (IGNITE-7941) Update dependencies to latest versions and migrate to caret(^) in package.json + package.json.lock

2018-04-13 Thread Pavel Konstantinov (JIRA) 

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

Pavel Konstantinov reassigned IGNITE-7941:
--

Assignee: Alexander Kalinin  (was: Pavel Konstantinov)

> Update dependencies to latest versions and migrate to caret(^) in 
> package.json + package.json.lock 
> ---
>
> Key: IGNITE-7941
> URL: https://issues.apache.org/jira/browse/IGNITE-7941
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Alexander Kalinin
>Priority: Minor
> Fix For: 2.5
>
>
> We should orgnized package.json files in way that latest stable dependencies 
> are installed
>  * move to caret versions notations.
>  * add package.json.lock to git versioning.



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

[jira] [Commented] (IGNITE-7941) Update dependencies to latest versions and migrate to caret(^) in package.json + package.json.lock

2018-04-13 Thread Pavel Konstantinov (JIRA) 

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

Pavel Konstantinov commented on IGNITE-7941:


There are a lot of errors during branch build. Please fix.

> Update dependencies to latest versions and migrate to caret(^) in 
> package.json + package.json.lock 
> ---
>
> Key: IGNITE-7941
> URL: https://issues.apache.org/jira/browse/IGNITE-7941
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.5
>
>
> We should orgnized package.json files in way that latest stable dependencies 
> are installed
>  * move to caret versions notations.
>  * add package.json.lock to git versioning.



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

[jira] [Updated] (IGNITE-8237) Ignite blocks on SecurityException in exchange-worker due to unauthorised on-heap cache configuration

2018-04-13 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-8237:

Fix Version/s: 2.5

> Ignite blocks on SecurityException in exchange-worker due to unauthorised 
> on-heap cache configuration 
> --
>
> Key: IGNITE-8237
> URL: https://issues.apache.org/jira/browse/IGNITE-8237
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Alexey Kukushkin
>Assignee: Alexey Kukushkin
>Priority: Blocker
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> Ignite blocks on SecurityException in exchange-worker due to unauthorised 
> on-heap cache configuration. Consider moving IGNITE_DISABLE_ONHEAP_CACHE 
> system property check to a more appropriate place to avoid blocking Ignite.



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

[jira] [Commented] (IGNITE-7821) Unify and improve Apache Ignite and Web Console Dockerfiles

2018-04-13 Thread Peter Ivanov (JIRA) 

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

Peter Ivanov commented on IGNITE-7821:
--

[~anovikov], please review changes to Webconsole Docker Standalone Image 
creation.
[~mshonichev], please review changes to Apache Ignite Docker Image creation.

> Unify and improve Apache Ignite and Web Console Dockerfiles
> ---
>
> Key: IGNITE-7821
> URL: https://issues.apache.org/jira/browse/IGNITE-7821
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Critical
> Fix For: 2.5
>
>
> # Unify approach to docker build -- add instructions about how to build 
> specific docker images from binaries .
> # Change Apache Ignite's Dockerfile to get binaries from local build.



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

[jira] [Assigned] (IGNITE-8162) Handle ClassNotFoundException during deserialization of persisted cache configuration

2018-04-13 Thread Denis Garus (JIRA) 

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

Denis Garus reassigned IGNITE-8162:
---

Assignee: Denis Garus

> Handle ClassNotFoundException during deserialization of persisted cache 
> configuration 
> --
>
> Key: IGNITE-8162
> URL: https://issues.apache.org/jira/browse/IGNITE-8162
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 2.4
>Reporter: Ivan Rakov
>Assignee: Denis Garus
>Priority: Major
>  Labels: newbie
> Fix For: 2.6
>
>
> Ticket is created according to dev list discussion: 
> http://apache-ignite-developers.2346864.n4.nabble.com/Fwd-Data-Loss-while-upgrading-custom-jar-from-old-jar-in-server-and-client-nodes-td28808.html
> Cache configuration is serialized by JDK marshaller and persisted in 
> cache_data.dat file. It may contain instances of classes that disappeared 
> from runtime classpath (e.g. if implementation of CacheStore has been 
> renamed). In such case, node will fail on start.
> We should handle this and show meaningful message with instruction how to 
> overcome this issue - delete cache_data.dat and restart cache.



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

[jira] [Created] (IGNITE-8243) Possible memory leak at ExchangeLatchManager during dynamic creating/removing of the local caches

2018-04-13 Thread Andrey Aleksandrov (JIRA) 
Andrey Aleksandrov created IGNITE-8243:
--

 Summary: Possible memory leak at ExchangeLatchManager during 
dynamic creating/removing of the local caches
 Key: IGNITE-8243
 URL: https://issues.apache.org/jira/browse/IGNITE-8243
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Andrey Aleksandrov
 Attachments: image.png, reproducer.java

Reproducer was attached. Memory analizer report was attached too. 

Looks like that next collection never removes its items in case of dynamic 
creating/removing of the local caches:



/** Server latches collection. */
private final ConcurrentMap, ServerLatch> 
serverLatches = new ConcurrentHashMap<>();

To see it you can modify source code a little:



private Latch createServerLatch(String id, AffinityTopologyVersion topVer, 
Collection participants) {
 final T2 latchId = new T2<>(id, topVer);

 if (serverLatches.containsKey(latchId))
 return serverLatches.get(latchId);

 ServerLatch latch = new ServerLatch(id, topVer, participants);

 serverLatches.put(latchId, latch);

 if (log.isDebugEnabled())
 log.debug("Server latch is created [latch=" + latchId + ", participantsSize=" 
+ participants.size() + "]");

 log.error("Server latch is created [size=" + serverLatches.size() +
 ", latchId = " + latchId + "]");

And add some breakpoints in places where removing can be done.

Log should be like that:

[2018-04-13 09:55:44,911][ERROR][exchange-worker-#42][ExchangeLatchManager] 
Server latch is created [size=1990, latchId = IgniteBiTuple [val1=exchange, 
val2=AffinityTopologyVersion [topVer=1, minorTopVer=1989]]]
[2018-04-13 09:55:44,911][ERROR][exchange-worker-#42][ExchangeLatchManager] 
Server latch is created [size=1991, latchId = IgniteBiTuple [val1=exchange, 
val2=AffinityTopologyVersion [topVer=1, minorTopVer=1990]]]
[2018-04-13 09:55:44,911][ERROR][exchange-worker-#42][ExchangeLatchManager] 
Server latch is created [size=1992, latchId = IgniteBiTuple [val1=exchange, 
val2=AffinityTopologyVersion [topVer=1, minorTopVer=1991]]]
[2018-04-13 09:55:44,926][ERROR][exchange-worker-#42][ExchangeLatchManager] 
Server latch is created [size=1993, latchId = IgniteBiTuple [val1=exchange, 
val2=AffinityTopologyVersion [topVer=1, minorTopVer=1992]]]
[2018-04-13 09:55:44,926][ERROR][exchange-worker-#42][ExchangeLatchManager] 
Server latch is created [size=1994, latchId = IgniteBiTuple [val1=exchange, 
val2=AffinityTopologyVersion [topVer=1, minorTopVer=1993]]]
[2018-04-13 09:55:44,926][ERROR][exchange-worker-#42][ExchangeLatchManager] 
Server latch is created [size=1995, latchId = IgniteBiTuple [val1=exchange, 
val2=AffinityTopologyVersion [topVer=1, minorTopVer=1994]]]



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

[jira] [Commented] (IGNITE-7986) GridPartitionStateMap.entrySet() optimization.

2018-04-13 Thread Aleksey Plekhanov (JIRA) 

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

Aleksey Plekhanov commented on IGNITE-7986:
---

[~VitaliyB] I have looked at your patch, it looks good for me.

> GridPartitionStateMap.entrySet() optimization.
> --
>
> Key: IGNITE-7986
> URL: https://issues.apache.org/jira/browse/IGNITE-7986
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Vitaliy Biryukov
>Assignee: Vitaliy Biryukov
>Priority: Major
> Fix For: 2.6
>
> Attachments: GridPartitionStateMapBench.java, fullResult.txt
>
>
> GridPartitionStateMap based on BitSet. And the size of a BitSet depends on 
> the maximum key element, and not on the number of elements. 
> Just using the "BitSet.nextSetBit" method, will improve the performance of 
> the iterator for big clusters or caches with a large number of partitions.



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

<    1   2