If that *fails*, let's try running the standard load tests on your
machine. To do that, download the sources, and do the following:
ant make-core-deps
ant load-hs
That should take many hours, but if it fails you'll know there's something
fundamentally wrong with your environment.
Karl
On
In addition my all job are waiting as "End notification" status now.
Cihad Güzel
Cihad Guzel , 13 Tem 2019 Cmt, 22:27 tarihinde şunu
yazdı:
> Hi Karl,
>
> No, this is different new setup. But I use same version for mfc and
> database. I am tring new setup for my every testing. I didn't see any
Hi Karl,
No, this is different new setup. But I use same version for mfc and
database. I am tring new setup for my every testing. I didn't see any
repeated or non-repeated error logs like before.
Then, I have build the jdbc connector from trunk branch and changed the
jdbc-connector.jar with new
You previously reported errors of the kind that ManifoldCF throws when it
finds that the database seemingly lost transactional integrity.
My question is whether you are still using the same database setup where
you previously got those errors?
The ArrayIndexOutOfBounds exception applied to JDBC
Hi Karl,
If you are talking about is
https://issues.apache.org/jira/browse/CONNECTORS-1613, my setup doesn't
include this change because I use mfc 2.12. Are you suggesting I use a
trunk version?
Cihad Güzel
Karl Wright , 13 Tem 2019 Cmt, 17:27 tarihinde şunu
yazdı:
> Is this the same setup
Is this the same setup where you were getting errors because of
inconsistent database states?
That could lead to this problem, you know.
Karl
On Sat, Jul 13, 2019 at 10:14 AM Cihad Guzel wrote:
> Hi Karl,
>
> I also have a job waiting for 12 days as an "Aborting" status.
>
> Status: Aborting
Hi Karl,
I also have a job waiting for 12 days as an "Aborting" status.
Status: Aborting
Start time: 7/1/19 4:01:46 PM
Documents: 10003
Active: 10003
Processed: 10002
Cihad Guzel
Cihad Guzel , 13 Tem 2019 Cmt, 16:53 tarihinde şunu
yazdı:
> Hi Karl,
>
> I tried quick-start single process
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
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
Hi Karl,
Nothing. I don't have any error log.
8 Tem 2019 Pzt 03:18 tarihinde Karl Wright ş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 wrote:
>
>> Hi Karl,
>>
>> I mistakenly wrote "Stopping"
Hi Cihad,
What does your manifoldcf log have in it? Any errors?
Karl
On Sun, Jul 7, 2019 at 3:52 PM Cihad Guzel 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
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 , 7 Tem 2019 Paz, 22:42 tarihinde şunu yazdı:
> Hi Karl,
>
> I have a few
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
13 matches
Mail list logo
