[
https://issues.apache.org/jira/browse/CONNECTORS-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright resolved CONNECTORS-867.
------------------------------------
Resolution: Fixed
r1560841 commits the zookeeper implementation fixes from the branch.
> Lock prioritization should favor UI locks over crawler locks
> ------------------------------------------------------------
>
> Key: CONNECTORS-867
> URL: https://issues.apache.org/jira/browse/CONNECTORS-867
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Framework core
> Affects Versions: ManifoldCF 1.4.1
> Reporter: Karl Wright
> Assignee: Karl Wright
> Fix For: ManifoldCF 1.6
>
>
> When crawling is active, it is often difficult to lock the resources needed
> to do anything useful in the UI. This can be because of contention with the
> crawling threads, which usually win in a lock contention situation because
> there are so many more of them.
> This is not an easy ticket to solve for a number of reasons, one of which is
> that the ONLY known strategy for resolving locking requiring multiple locks
> is to acquire the locks in a certain order, and release them and retry
> if/when they can't all be acquired. However, the UI itself doesn't actually
> seem to make use of the multiple-locks-at-one-time situation very often, so I
> believe that a simple system of lock prioritization on single locks would
> likely help enormously. While still not easy to implement, this would solve
> a long-standing annoying failure case in ManifoldCF.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
