[
https://issues.apache.org/jira/browse/IGNITE-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16409824#comment-16409824
]
ASF GitHub Bot commented on IGNITE-8019:
----------------------------------------
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/3685
IGNITE-8019 : Optimized checkpointReadLock acquisition during rebalancing.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8019
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3685.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 #3685
----
commit 5fd8230f860eb925d63957ac86f45f8cf8de85b5
Author: Ilya Lantukh <ilantukh@...>
Date: 2018-03-22T16:30:08Z
ignite-8019 : Optimized checkpointReadLock acquisition during rebalancing.
----
> During rebalancing checkpoint read lock is acquired for each entry (twice).
> ---------------------------------------------------------------------------
>
> Key: IGNITE-8019
> URL: https://issues.apache.org/jira/browse/IGNITE-8019
> Project: Ignite
> Issue Type: Bug
> Reporter: Ilya Lantukh
> Assignee: Ilya Lantukh
> Priority: Major
>
> In GridDhtPartitionDemander.preloadEntry(...) checkpointReadLock is acquired
> twice, which is definitely a mistake. But even acquiring it once per entry
> causes unnecessary contention - it should be taken once for SupplyMessage.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
