Hi Karl,

I tried quick-start single process model. After your suggestion , i have
tried multiprocess-zk-example for zookeeper-based locking. But I have the
same problem.

Status: Aborting
Start time: 7/13/19 3:42:10 PM
Documents: 10003
Active: 10003
Processed: 1021

I'm waiting for over an hour for the jdbc job to stop. I have not  any
error logs in my manifolcf log.

Cihad Güzel

Cihad Güzel


Karl Wright <[email protected]>, 8 Tem 2019 Pzt, 13:23 tarihinde şunu
yazdı:

> Are you using file-based locking?
> If so, I would suggest strongly migrating to zookeeper-based locking.
> But if you are using the file-based locking, please execute the "lock
> clean procedure" as follows:
>
> - shut down all manifoldcf processes, including the web UI
> - run the lock-clean script
> - start the processes again
>
> Thanks,
> Karl
>
>
> On Mon, Jul 8, 2019 at 5:05 AM Cihad Guzel <[email protected]> wrote:
>
>> Hi Karl,
>>
>> Nothing. I don't have any error log.
>>
>> 8 Tem 2019 Pzt 03:18 tarihinde Karl Wright <[email protected]> şunu
>> yazdı:
>>
>>> Hi Cihad,
>>>
>>> What does your manifoldcf log have in it?  Any errors?
>>>
>>> Karl
>>>
>>>
>>> On Sun, Jul 7, 2019 at 3:52 PM Cihad Guzel <[email protected]> wrote:
>>>
>>>> Hi Karl,
>>>>
>>>> I mistakenly wrote "Stopping" instead of "Aborting". My job is waiting
>>>> as "Aborting" status. I have also the same problem while restarting. I am
>>>> waiting for 2 days for one job.
>>>>
>>>> Regards,
>>>> Cihad Guzel
>>>>
>>>>
>>>> Cihad Guzel <[email protected]>, 7 Tem 2019 Paz, 22:42 tarihinde şunu
>>>> yazdı:
>>>>
>>>>> Hi Karl,
>>>>>
>>>>> I have a few jobs. I stopped all of them but only one job is waiting
>>>>> as "stopping" status.
>>>>>
>>>>> I know that some large jobs is waited long time. But, I have only 1000
>>>>> rows on database. So, all of jobs crawled small number of documents. But ,
>>>>> It doesn't make much sense to stay status of "stopping" for a long time.
>>>>> How can I identify a problem?
>>>>>
>>>>> Postgresql version: 9.4
>>>>> Manifoldcf version: 2.12
>>>>>
>>>>> Regards,
>>>>> Cihad Guzel
>>>>>
>>>>

Reply via email to