manifoldcf-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shashank Raj <>
Subject Re: ManifoldCF two server setup
Date Tue, 13 Mar 2018 06:22:20 GMT
Hi Karl,
            In the documentation for "Simplified multiprocess model using
file based synchronisation", it is indicated that the war files should be
taken from "web" folder of multiprocess-file-example. But there is no such
folder or file. Can we get some inputs on where do we need to take war
files from in this case?

Regarding database , in the steps you have asked us to run start-database
and initialize-database script files but we have deployed it using pgsql
and database is getting created and initialized automatically with single
process file example for now.
Now we are switching to multiprocess model. Do we still need to run those

And should we run start-agent in one server and start-agent2 in another

On 20-Feb-2018 9:21 PM, "Karl Wright" <> wrote:

> Hi Shashank,
> You can have multiple servers running against the same database, BUT if
> you do so, they must be individually configured to have their own IDs, and
> they must share locks and by extension, must use the same zookeeper.
> See multiprocess-zk-example in the binary distribution.
> Thanks,
> Karl
> On Tue, Feb 20, 2018 at 6:58 AM, Shashank Raj <>
> wrote:
>> Hi Karl,
>>             I have setup ManifoldCF using Tomcat on two servers with a
>> load balancer in front of them. Both instances of ManifoldCf connect to the
>> same database. The scenario is to have a backup server running all the
>> time. Is this setup correct or does ManifoldCF supports only a single
>> server setup.
>> Also, I am getting an error  : Duplicate key value violates unique
>> constraint "repohistory_pkey". Detail: Key(id)=(1519119640499) already
>> exists.
>> This error pops up upon running jobs with different repositories.
>> Our ManifoldCf job setup is as follows : File System>Tika Content
>> Extractor>Solr Output Connection.
>> Thanks and regards.

View raw message