[
https://issues.apache.org/jira/browse/CONNECTORS-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774474#comment-13774474
]
Karl Wright commented on CONNECTORS-13:
---------------------------------------
I doubt I'll be able to look at CONNECTORS-780 for the 1.4 release cycle, but
with help I think it is conceivable that we can get CONNECTORS-13 done. At the
very least I am pretty sure I can get to the refactoring of the ILockManager
interface to include configuration, and the proper redirection of configuration
properties throughout the rest of MCF.
This depends on getting good answers to previously asked but unanswered
questions though - namely:
(a) How do we SET properties in Zookeeper? When does this happen, and by what
process?
(b) Is the zookeeper property paradigm hierarchical? I.e. is there a good
mapping from XML to stuff you'd keep in zookeeper?
Prompt answers would allow me to do the right thing at the interface level in
MCF... And as soon as I get them, I'll create a branch to work on this code
for 1.4.
> We should move to eliminate process synchronization via shared file system,
> and use a process/service instead
> -------------------------------------------------------------------------------------------------------------
>
> Key: CONNECTORS-13
> URL: https://issues.apache.org/jira/browse/CONNECTORS-13
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Framework core
> Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2
> Reporter: Karl Wright
> Fix For: ManifoldCF next
>
>
> The current implementation relies on the file system to synchronize activity
> between various LCF processes. This has several downsides: first, it is
> possible to get the file system into a state that is corrupted (by killing
> processes); second, this limits the future ability to spread crawler workload
> over multiple machines.
> It should be reasonably straightforward, and probably more resilient, to
> introduce a "synchronization process", which all other LCF processes talk to
> in order to manage locks, shared data, and other synchronization activities.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
