Another thing: it's quite important to guarantee a working setup here,
otherwise you're just wasting everyone's time. So, please base your
installation on the multiprocess-zk-example. Start off by running the
example as is, on a small test crawl. Once you know how it works, then
move next to
Zookeeper does not require a locking directory. It is a process that
synchronizes other processes, and they connect to it by port.
Karl
On Sat, Dec 1, 2018 at 2:55 PM krishna agrawal wrote:
> Thanks for the information.
> if we use Zookeeper how can we make sure all our ManifoldCF processes
Thanks for the information.
if we use Zookeeper how can we make sure all our ManifoldCF processes use
same locking directory does it can be done at the configuration level while
installing.
thanks,
Krishna A
On Sat, Dec 1, 2018 at 1:39 PM Karl Wright wrote:
> That error is the result of the
That error is the result of the database not managing transactions
properly. It can occur if the locking system is not set up properly, or if
you are using multiple agents processes and each process does not have its
own ID. We have also seen it reported before just because MySQL seems to
have
Thanks Karl,
I will take a look at it
But there is the error keep on tossing at manifold log
ERROR 2018-12-01T11:13:26,297 (Job reset thread) - Exception tossed:
Unexpected job status encountered: 33
org.apache.manifoldcf.core.interfaces.ManifoldCFException: Unexpected job
status encountered:
