manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Wright <daddy...@gmail.com>
Subject Re: Deployment model choice
Date Wed, 05 Dec 2018 11:17:24 GMT
Hi Jasvinder,

The multiprocess model(s) use an application server (tomcat or jetty) to
deliver the ManifoldCF UI services, and a separate family (one or more)
agents processes that do the actual crawling.  The two models are distinct
because one uses files for process synchronization (deprecated), and the
other uses Zookeeper.

Choice (4) is there for people who want to develop their own custom
deployment strategy.  This is not recommended for people not familiar at
all with ManifoldCF.

Karl


On Wed, Dec 5, 2018 at 4:49 AM jasvinder.singh@gartner.com <
jasvinder.singh@gartner.com> wrote:

> Below are the Deployment models listed in Documentation
>
> 1)Quick-start single process model
> 2)Single-process deployable war
> 3)Simplified multi-process model
>    a)Simplified multi-process model using file-based synchronization
>    b)Simplified multi-process model using ZooKeeper-based synchronization
>
> 4)Command-driven multi-process model
>
> Can you please elaborate the use case of 3 for both a & b points and 4
> model  listed above
>
> From the documentation, I could not make out in which situation to use 3
> and 4 models
> and If 3 (b) is suggested as recommended one in most places - what is
> exact puropse of model
> 4
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message