[jira] [Comment Edited] (IGNITE-2948) Optimize usage of GridCacheConcurrentMap

["Ilya Lantukh (JIRA)" <ji...@apache.org>]

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

Ilya Lantukh edited comment on IGNITE-2948 at 4/9/16 12:53 AM:
---------------------------------------------------------------

Possible further optimizations:
1. GridCachePartitionTopologyImpl - get rid of RW lock, use volatile reads/writes.
2. Adjust parameters of internal CHM in new GridCacheConcurrentMapImpl.

Fixed most of simple test failures, working on the following problems now:
1. Occasional hang-ups in tests that involve constant topology changes.
2. Sometimes GridCacheAdapter tries to create local partition that shouldn't belong to current node, resulting in GridDhtInvalidPartitionException.


was (Author: ilantukh):
Possible further optimizations:
1. GridCachePartitionTopologyImpl - get rid of RW lock, use volatile reads/writes.
2. Adjust parameters of internal CHM in new GridCacheConcurrentMapImpl.

Fixed most of the tests, working on the following problems now:
1. Occasional hang-ups in tests that involve constant topology changes.
2. Sometimes GridCacheAdapter tries to create local partition that shouldn't belong to current node, resulting in GridDhtInvalidPartitionException.

> Optimize usage of GridCacheConcurrentMap
> ----------------------------------------
>
>                 Key: IGNITE-2948
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2948
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>            Reporter: Ilya Lantukh
>            Assignee: Ilya Lantukh
>
> 1. Eliminate cases where an entry is stored in multiple maps.
> 2. Change GridCacheConcurrentMap implementation to be based on internal ConcurrentMap.
> 3. Remove redundant and obsolete code related to map usage.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)