uima-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Challenger <chall...@gmail.com>
Subject Re: Infinte initialization of a process even after restarting DUCC
Date Tue, 08 Jul 2014 10:14:33 GMT
    If this is the same issue you mentioned in the Jira it's possible 
that the Agent isn't able to properly shutdown.  You can get around this 
by issuing
         check_ducc -k
         stop_ducc -a

     As a rule of thumb, I like to stop ducc by issuing check_ducc -k a 
few times after stop_ducc.  This sends kill -9 to any ducc components 
that couldn't stop for some reason.  Unfortunately it can't kill zombies 
but once you have done check_ducc -k it should not matter. As Lou 
mentioned, the 1.1.0 release will make some of this situation better but 
I've seen intense analytics leave hardware and software on hosts in 
states that only kill -9 can effectively handle.


On 7/7/14 8:23 AM, Lou DeGenaro wrote:
> DUCC depends on UIMA-AS which depends on UIMA core.  A new version UIMA-AS
> is in progress.  Voting could conclude this week, perhaps.  Once UIMA-AS is
> officially released, DUCC release candidates will follow.  So a new version
> of DUCC is possible this month.
> That said, two short term possibilities.  Firstly, the changes for the next
> version of DUCC are for the most part already in the SVN trunk so you could
> build your own interim level if the problems you are encountering are
> unbearable for a few more weeks.  I posted instructions on how to do this
> for a sim-cluster on the wiki some time ago: https://cwiki.apache
> .org/confluence/display/UIMA/DUCC#DUCC-t1.  Secondly, if you want to
> re-start your currently installed DUCC fresh be sure to use "check_ducc -k"
> to kill all running DUCC processes (if any).
> Lou.
> On Mon, Jul 7, 2014 at 5:03 AM, reshu.agarwal <reshu.agarwal@orkash.com>
> wrote:
>> Hi,
>> I have faced a problem in DUCC after continuous processing in DUCC, the
>> job initialization or ending processing go in to infinite loop. So, a new
>> job can not be started even after restarting of DUCC and job is showing end
>> of job status internally initialization waiting time is increasing.
>> I have read a issue on JIRA where you have talked about this same problem
>> . i.e. https://issues.apache.org/jira/browse/UIMA-3645. <
>> https://issues.apache.org/jira/browse/UIMA-3645>
>> When will you release UIMA DUCC 1.1.0 where you have fixed this issue? As
>> we have to restart DUCC after certain period of time.
>> <https://issues.apache.org/jira/browse/UIMA-3645>
>> --
>> Thanks,
>> Reshu Agarwal

View raw message