You can just change the setup provided you point to the same database.
Thanks,
Karl
On Mon, Dec 3, 2018 at 9:57 AM krishna agrawal wrote:
> thanks Karl,
>
> I have deployed in my local as simple example and in Dev and QA with the
> recomendation of Dev Ops team we deployed as multiprocess
thanks Karl,
I have deployed in my local as simple example and in Dev and QA with the
recomendation of Dev Ops team we deployed as multiprocess file example we
had brief discussion about considering multiprocess-zk-example and at that
time we were unsure of multiprocess-zk-example.
But i will
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:
Hi Krishna,
First of all I suggest that you *not* use multiprocess-file-example, and
instead use multiprocess-zk-example.
Your symptoms suggest many possibilities. But if you move to Zookeeper we
will be able to eliminate dangling file locks as a complication. So please
do that first.
Karl
Yeah in our local set up we did Simple example but in server we did
multiprocess-file-example are you suggesting us to upgrade from 2.10 to
2.11 ?
and we are using MY Sql database ,
So most of time i saw nothing is running and still it say job is running
and you have to wait for it to complete.
It also may be useful to start with the simple example, which is not
multiprocess, and get familiar with using ManifoldCF that way, before you
try to go to a more complicated setup.
Thanks,
Karl
On Fri, Nov 30, 2018 at 9:46 AM Karl Wright wrote:
> "simplified multi-process"? There is no such
"simplified multi-process"? There is no such example.
These are the examples available. Which one are you using?
11/15/2018 03:40 AM example
11/15/2018 03:40 AM example-proprietary
11/15/2018 03:40 AM multiprocess-file-example
11/15/2018 03:40 AM
We have deployed the Manifold using
- Simplified multi-process model
We did try clean up of lock Sh but that also did not work.
I dont have forget all document button in output connector.
[image: image.png]
On Thu, Nov 29, 2018 at 6:52 PM Karl Wright wrote:
> Hi Krishna,
>
> Please give
Hi Krishna,
Please give us some background as to how you've deployed ManifoldCF. Are
you using one of the examples? If so, which one?
The detailed answer to your question is: the job must delete all documents
it indexed before it can be deleted. That is the typical way jobs work.
Thus, if you
Hi We are facing issue of action button is not available
[image: image.png]
I have stop the agent process but still i am not able to remove the job it
say it
there should be some way to forcefully restart and stop the running process
?
Job 1542835910915 is busy; you must wait and/or shut it
14 matches
Mail list logo
