[
https://issues.apache.org/jira/browse/IGNITE-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15002123#comment-15002123
]
Ivan Veselovsky commented on IGNITE-183:
----------------------------------------
The problem is that the busyLock exists both in IgfsImpl and IgfsMetamanager,
so in many cases bothe the busy locks are acquired, what is redundant.
The suggestion is to consider possibility to have only one busy lock, and have
it locked only once.
> Delete busyLock from IgfsMetaManager
> ------------------------------------
>
> Key: IGNITE-183
> URL: https://issues.apache.org/jira/browse/IGNITE-183
> Project: Ignite
> Issue Type: Task
> Components: hadoop
> Affects Versions: sprint-1
> Reporter: Alexey Kuznetsov
> Assignee: Ivan Veselovsky
> Fix For: 1.6
>
>
> It seems that busy lock is not needed and owner busy lock could be used when
> needed.
> Ask Yakov or Alex G. for details if needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
