You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2017/10/24 08:23:00 UTC
[jira] [Resolved] (IGNITE-6719) Get rid of noop segment lock-unlock
in PageMemoryImpl
[ https://issues.apache.org/jira/browse/IGNITE-6719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Goncharuk resolved IGNITE-6719.
--------------------------------------
Resolution: Fixed
Merged to master
> Get rid of noop segment lock-unlock in PageMemoryImpl
> -----------------------------------------------------
>
> Key: IGNITE-6719
> URL: https://issues.apache.org/jira/browse/IGNITE-6719
> Project: Ignite
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
> Affects Versions: 2.3
> Reporter: Alexey Goncharuk
> Assignee: Alexey Goncharuk
> Fix For: 2.4
>
>
> We have the following pattern in PageMemoryImpl#stop():
> {code}
> volatile boolean closed;
> ...
> closed = true;
> writeLock.lock();
> writeLock.unlock();
> {code}
> An empty lock/unlock pair can be eliminated, so the code must be changed and the flag should be moved to the segment class.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)