uima-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lou DeGenaro <lou.degen...@gmail.com>
Subject Re: CanceledByDriver status in DUCC
Date Fri, 06 Jun 2014 12:33:40 GMT
There should be no job queue "leak" on the broker.  The Orchestrator should
be cleaning these up.  It's a bug otherwise.

Search <ducc_home>/logs/or.log* files for ERROR or WARN messages especially
relative to the MqReaper.

Lou.



On Fri, Jun 6, 2014 at 5:41 AM, reshu.agarwal <reshu.agarwal@orkash.com>
wrote:

> On 06/05/2014 06:30 PM, Lou DeGenaro wrote:
>
>> How long does it take to process your longest work item through your
>>
> Hi Lou,
>
> It was 3 Minutes that time. We increased this to 10 minutes now for
> testing as you told me to increase it. I have also restarted DUCC. Till
> now, I didn't face the similar problem. But, If I face this again I will
> update you in this same mail trail. But if you see any other reason for
> this then please let me know.
>
> I have one more question as I have read in DUCC document, Orchestrator
> automatically deletes the job's queue from the Broker when job is over. But
> when I monitor the broker service using jconsole, I saw all the jobs queues
> are still there with in the broker.
>
> Will this can create a problem after a time in DUCC?
>
> Is this what Orchestrator ensure in DUCC?
>
> Thanks in advance.
>
> --
> Reshu Agarwal
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message