uima-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Burn Lewis <burnle...@gmail.com>
Subject Re: problem in calling DUCC Service with ducc_submit
Date Fri, 01 Aug 2014 12:30:15 GMT
DUCC is just managing UIMA-AS jobs and services.  It is up to the
descriptor for the job to specify what annotators and services to use.  The
simplest way to use a service in a job is to reference it via a JMS service
descriptor.  The flow of execution in the job and the data it processes is
up to you .... DUCC is only responsible for running the job  (providing as
many resources as available and necessary to complete the work rapidly) and
also for starting and stopping any required services.


On Thu, Jul 31, 2014 at 8:45 AM, reshu.agarwal <reshu.agarwal@orkash.com>
wrote:

>
> Dear Burn,
>
> Thanks for the information. But problem is as Eddie Said before, we can
> not use the DUCC Service using ducc_submit, we can just check availability
> of service by using service_dependency in job.
>
> There is only a way that I have to create a Analysis Engine which is using
> ducc service using UIMA AS client.
>
> If there is another way to use DUCC Service in Job so I can use DUCC
> Service as my AE or DD, then please tell me.
>
>
>
> On 07/31/2014 06:05 PM, Burn Lewis wrote:
>
>> You can register a DUCC service with --autostart set to true and the
>> service will start when it is registered and stay running.  If your job
>> has
>> a dependency on that service DUCC will verify that it is running before
>> starting your job.
>> If instead you register the service without autostart then DUCC will start
>> the service (if it is not already running) before starting your job.  When
>> the last job that references that service ends DUCC will stop the service
>> after an idle delay defined by the service's --linger value.  If you make
>> linger very large the service can be made to stay running, even if it is
>> idle, for many hours between jobs.
>>
>> ~Burn
>>
>>
>> On Thu, Jul 31, 2014 at 2:41 AM, reshu.agarwal <reshu.agarwal@orkash.com>
>> wrote:
>>
>>  Hi,
>>>
>>> Today, I got understand the reason of why DUCC Job is not using DUCC
>>> Service. But All I want that my initialization Part of a Process_DD
>>> should
>>> occur once. I don't need to wait every time for initialization. So, I
>>> want
>>> to use DUCC Service in my DUCC JOB.
>>>
>>> Is there any way to configure in DUCC that Process_DD initialized once
>>> and
>>> Job will start again and again?
>>>
>>> On 04/01/2014 05:21 PM, Eddie Epstein wrote:
>>>
>>>  Declaring a service dependency does not affect application code paths.
>>>> The
>>>> job still needs to connect to the service in the normal way.
>>>>
>>>> DUCC uses services dependency for several reasons: to automatically
>>>> start
>>>> services when needed by a job; to not give resources to a job or service
>>>> for which a dependent service is not running; and to post a warning on
>>>> running jobs when a dependent service goes "bad".
>>>>
>>>> Eddie
>>>>
>>>>
>>>> On Tue, Apr 1, 2014 at 1:27 AM, reshu.agarwal <reshu.agarwal@orkash.com
>>>> >
>>>> wrote:
>>>>
>>>>   Hi,
>>>>
>>>>> I am again in a problem. I have successfully deployed DUCC UIMA AS
>>>>> Service
>>>>> using ducc_service. The service status is available with good health.
>>>>> If
>>>>> I
>>>>> try to use my this service using parameter service_dependency to my Job
>>>>> in
>>>>> ducc_submit then it is not showing any error but executes only the DB
>>>>> Collection Reader not this service.
>>>>>
>>>>> --
>>>>> Thanks,
>>>>> Reshu Agarwal
>>>>>
>>>>>
>>>>>
>>>>>  --
>>> Thanks,
>>> Reshu Agarwal
>>>
>>>
>>>
>
> --
> Thanks,
> Reshu Agarwal
>
>

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