[jira] [Updated] (UIMA-6445) CPE not calling destroy if there was an exception
[ https://issues.apache.org/jira/browse/UIMA-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6445: - Fix Version/s: 3.4.0SDK (was: 3.3.2SDK) > CPE not calling destroy if there was an exception > - > > Key: UIMA-6445 > URL: https://issues.apache.org/jira/browse/UIMA-6445 > Project: UIMA > Issue Type: Bug > Components: Collection Processing >Affects Versions: 3.3.0SDK >Reporter: Richard Eckart de Castilho >Priority: Major > Fix For: 3.4.0SDK > > > There are indications that the CPE is not calling destroy if there was an > exception. > Need a test case for this. > Need to think if calling destroy is ok or whether it might disrupt some > functionality of CPEs (checkpoints?). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-6482) Request for Visual Studio Code or IDEA Extension
[ https://issues.apache.org/jira/browse/UIMA-6482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6482. -- Resolution: Feedback Received > Request for Visual Studio Code or IDEA Extension > - > > Key: UIMA-6482 > URL: https://issues.apache.org/jira/browse/UIMA-6482 > Project: UIMA > Issue Type: New Feature > Components: addons, Ruta >Reporter: Yue Yang >Priority: Trivial > > Eclipse is slow and losing popularity, and I request visual studio code or > IDEA extension so that I can debug my Ruta script there. I found [one IDEA > extension|https://plugins.jetbrains.com/plugin/12212-uima-ruta-language-support] > but it is not compatible with the latest release of IntelliJ IDE now. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-6178) Daemons fail to start on Mac OSX
[ https://issues.apache.org/jira/browse/UIMA-6178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6178. -- Resolution: Abandoned DUCC has been retired. > Daemons fail to start on Mac OSX > > > Key: UIMA-6178 > URL: https://issues.apache.org/jira/browse/UIMA-6178 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Assignee: Burn L. Lewis >Priority: Minor > > Setup of JAVA_HOME is wrong for latest OS/X (Catalina) > Test for ssh-to-self may falsely succeed (on any platform) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3816) DUCC SM should support ping-only UIMA-AS services
[ https://issues.apache.org/jira/browse/UIMA-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3816. -- Resolution: Abandoned DUCC has been retired. > DUCC SM should support ping-only UIMA-AS services > - > > Key: UIMA-3816 > URL: https://issues.apache.org/jira/browse/UIMA-3816 > Project: UIMA > Issue Type: New Feature > Components: DUCC >Affects Versions: 1.0.0-Ducc >Reporter: Jim Challenger >Assignee: Jim Challenger >Priority: Major > Fix For: future-DUCC > > > Currently DUCC supports only CUSTOM services as ping-only. While it is > possible to define a ping-only services that monitors a UIMA-AS service, this > is not explicit. > The new function is to allow a UIMA-AS service with no DD to be defined. > DUCC will treat this as ping-only, using the UIMA-AS ping/monitor logic > explicitly rather than the CUSTOM ping logic. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5010) Errors triggered when a JP is preempted can falsely produce an Error sttus
[ https://issues.apache.org/jira/browse/UIMA-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5010. -- Resolution: Abandoned DUCC has been retired. > Errors triggered when a JP is preempted can falsely produce an Error sttus > -- > > Key: UIMA-5010 > URL: https://issues.apache.org/jira/browse/UIMA-5010 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > When a JP is preempted just as it starts running, the shutdown may trigger a > UIMA-AS error (Uima EE Client Not In Running State) ... ducc-mon should > report it as preempted (Forced?) ... not as Error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4044) DUCC Job Driver (JD) having OOM should cause job to terminate immediately
[ https://issues.apache.org/jira/browse/UIMA-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4044. -- Resolution: Abandoned DUCC has been retired. > DUCC Job Driver (JD) having OOM should cause job to terminate immediately > - > > Key: UIMA-4044 > URL: https://issues.apache.org/jira/browse/UIMA-4044 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > 06 Oct 2014 17:58:28,157 16969 ERROR user.err workItemError 2007263482 > seqNo:7307 wiId:1010 PID:4473:52 > 06 Oct 2014 17:58:29,444 16969 ERROR user.err workItemError 2007263482 > java.lang.OutOfMemoryError: Java heap space > at sun.net.www.ParseUtil.encodePath(ParseUtil.java:117) > at sun.misc.URLClassPath$FileLoader.getResource(URLClassPath.java:1287) > at sun.misc.URLClassPath$FileLoader.findResource(URLClassPath.java:1276) > at sun.misc.URLClassPath.findResource(URLClassPath.java:298) > at java.net.URLClassLoader$1.run(URLClassLoader.java:901) > at java.net.URLClassLoader$1.run(URLClassLoader.java:899) > at > java.security.AccessController.doPrivileged(AccessController.java:252) > at java.net.URLClassLoader.findResource(URLClassLoader.java:898) > at java.lang.ClassLoader.getResource(ClassLoader.java:485) > at java.net.URLClassLoader.getResourceAsStream(URLClassLoader.java:356) > at org.apache.xerces.parsers.SecuritySupport$6.run(Unknown Source) > at > java.security.AccessController.doPrivileged(AccessController.java:229) > at > org.apache.xerces.parsers.SecuritySupport.getResourceAsStream(Unknown Source) > at > org.apache.xerces.parsers.ObjectFactory.findJarServiceProvider(Unknown Source) > at org.apache.xerces.parsers.ObjectFactory.createObject(Unknown Source) > at org.apache.xerces.parsers.ObjectFactory.createObject(Unknown Source) > at org.apache.xerces.parsers.DOMParser.(Unknown Source) > at org.apache.xerces.parsers.DOMParser.(Unknown Source) > at org.apache.xerces.jaxp.DocumentBuilderImpl.(Unknown Source) > at > org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(Unknown > Source) > at > com.thoughtworks.xstream.io.xml.DomDriver.createReader(DomDriver.java:75) > at > com.thoughtworks.xstream.io.xml.DomDriver.createReader(DomDriver.java:66) > at com.thoughtworks.xstream.XStream.fromXML(XStream.java:853) > at com.thoughtworks.xstream.XStream.fromXML(XStream.java:845) > at > org.apache.uima.aae.UimaSerializer.deserializePerformanceMetrics(UimaSerializer.java:299) > at > org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl.completeProcessingReply(BaseUIMAAsynchronousEngineCommon_impl.java:1705) > at > org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl.deserializeAndCompleteProcessingReply(BaseUIMAAsynchronousEngineCommon_impl.java:2274) > at > org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl.sendAndReceiveCAS(BaseUIMAAsynchronousEngineCommon_impl.java:2240) > at > org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl.sendAndReceiveCAS(BaseUIMAAsynchronousEngineCommon_impl.java:2049) > at org.apache.uima.ducc.jd.client.WorkItem.run(WorkItem.java:145) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:482) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:345) > at java.util.concurrent.FutureTask.run(FutureTask.java:177) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:626) > at java.lang.Thread.run(Thread.java:780) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4584) ducc-mon should warn logged-out users why files can't be read
[ https://issues.apache.org/jira/browse/UIMA-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4584. -- Resolution: Abandoned DUCC has been retired. > ducc-mon should warn logged-out users why files can't be read > - > > Key: UIMA-4584 > URL: https://issues.apache.org/jira/browse/UIMA-4584 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Affects Versions: 2.0.0-Ducc >Reporter: Burn L. Lewis >Priority: Minor > > Currently just says "No data found" --- could add "Try logging in" if not > already logged in -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3073) DUCC webserver (WS) shows job not completed, yet jd.out.log show all work items ended?
[ https://issues.apache.org/jira/browse/UIMA-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3073. -- Resolution: Abandoned DUCC has been retired. > DUCC webserver (WS) shows job not completed, yet jd.out.log show all work > items ended? > -- > > Key: UIMA-3073 > URL: https://issues.apache.org/jira/browse/UIMA-3073 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > It seems that all work items for job 60037 completed, by examination of > jd.out.log. Yet WS shows otherwise. > Perhaps more logging is needed in OR to determine if correct JD publications > are arriving. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4766) DUCC Job Driver (JD) and Job Process (JP) support for keyless investment reset function
[ https://issues.apache.org/jira/browse/UIMA-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4766. -- Resolution: Abandoned DUCC has been retired. > DUCC Job Driver (JD) and Job Process (JP) support for keyless investment > reset function > --- > > Key: UIMA-4766 > URL: https://issues.apache.org/jira/browse/UIMA-4766 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Jaroslaw Cwiklik >Priority: Major > Fix For: future-DUCC > > > Deprecate keyed investment reset, which uses user supplied work item name as > key. Replace with keyless investment reset function, based on JP thread > and/or JD assigned sequence number. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3118) DUCC job driver (JD) should detect "missing" exception and fail work items on any JP that has croaked
[ https://issues.apache.org/jira/browse/UIMA-3118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3118. -- Resolution: Abandoned DUCC has been retired. > DUCC job driver (JD) should detect "missing" exception and fail work items on > any JP that has croaked > - > > Key: UIMA-3118 > URL: https://issues.apache.org/jira/browse/UIMA-3118 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > Job 63470. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5491) A WI in a DUCC job fails with a NPE but JPs are restarted forever
[ https://issues.apache.org/jira/browse/UIMA-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5491. -- Resolution: Abandoned DUCC has been retired. > A WI in a DUCC job fails with a NPE but JPs are restarted forever > - > > Key: UIMA-5491 > URL: https://issues.apache.org/jira/browse/UIMA-5491 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > The JD throws java.io.NotSerializableException when the error is returned. > See job 361532 on the floor, 427 on terstducc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4959) JobDriver is sometimes a reserved class, sometimes set in ducc.properties
[ https://issues.apache.org/jira/browse/UIMA-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4959. -- Resolution: Abandoned DUCC has been retired. > JobDriver is sometimes a reserved class, sometimes set in ducc.properties > - > > Key: UIMA-4959 > URL: https://issues.apache.org/jira/browse/UIMA-4959 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > DuccSchedulingClasses treats JobDriver as a reserved class name, but the OR > uses the value in ducc.jd.host.name (which is not documented) ... also the > docs don't indicate that JobDriver is a reserved class-name. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4939) First creation of a DB in ducc_post_install can fail if Cassandra is already running
[ https://issues.apache.org/jira/browse/UIMA-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4939. -- Resolution: Abandoned DUCC has been retired. > First creation of a DB in ducc_post_install can fail if Cassandra is already > running > > > Key: UIMA-4939 > URL: https://issues.apache.org/jira/browse/UIMA-4939 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Major > Fix For: future-DUCC > > > The console spits out many messages of the form: > connect Authorization fails with both the default userid/password and the new > userid/password. > connect Retrying, as first-time database may take a few moments to > initialize. > connect Initial DB connection failed with AuthorizationException. Retrying > database connection with your supplied userid and password. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-2764) DUCC Services need monitoring support, similar to Jobs + Managed Reservations
[ https://issues.apache.org/jira/browse/UIMA-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-2764. -- Resolution: Abandoned DUCC has been retired. > DUCC Services need monitoring support, similar to Jobs + Managed Reservations > - > > Key: UIMA-2764 > URL: https://issues.apache.org/jira/browse/UIMA-2764 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4688) DUCC should self-detect and provide an alert when unable to write its log files
[ https://issues.apache.org/jira/browse/UIMA-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4688. -- Resolution: Abandoned DUCC has been retired. > DUCC should self-detect and provide an alert when unable to write its log > files > --- > > Key: UIMA-4688 > URL: https://issues.apache.org/jira/browse/UIMA-4688 > Project: UIMA > Issue Type: New Feature > Components: DUCC >Reporter: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > In the case where DUCC's log files are written to a filesystem with a quota, > when the quota is exceeded DUCC will be prevented from writing its logs. > Usually the inability to write to the file system would result in an > Exception with reason "quota exceeded". However, log4j v1 suppresses > exceptions and continues as if all is well. > Some possible alternatives: > 1. use log4j v2 > 2. use native Java logging > 3. use an alternative filesystem not writeable detection mechanism -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3488) Add support for injecting a new process into an existing container
[ https://issues.apache.org/jira/browse/UIMA-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3488. -- Resolution: Abandoned DUCC has been retired. > Add support for injecting a new process into an existing container > -- > > Key: UIMA-3488 > URL: https://issues.apache.org/jira/browse/UIMA-3488 > Project: UIMA > Issue Type: New Feature > Components: DUCC >Reporter: Eddie Epstein >Assignee: Jaroslaw Cwiklik >Priority: Major > Fix For: future-DUCC > > > ducc_submit should allow users to inject a new process into an existing > container that they own. Given that no new allocation need be done, this > operation should be fast, typically a few seconds at most. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-6100) viaducc does not handle attach_console correctly
[ https://issues.apache.org/jira/browse/UIMA-6100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6100. -- Resolution: Abandoned DUCC has been retired. > viaducc does not handle attach_console correctly > > > Key: UIMA-6100 > URL: https://issues.apache.org/jira/browse/UIMA-6100 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Eddie Epstein >Assignee: Eddie Epstein >Priority: Major > Fix For: 3.0.1-DUCC > > > by default viaducc enable both attach_console and cancel_on_interrupt. An > option was added to suppress cancel_on_interrupt with the intent to let the > remote process continue running after the local submit process was > terminated. This was misguided because in many cases the remote process will > terminate when it's stdout/stderr pipes were broken. > The new change makes attach_console an option, which in addition sets > cancel_on_interrupt. The result is that by default viaducc will only monitor > the DUCC state of the remote process and the remote process will not be > terminated if the local submitter is stopped. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5134) DUCC should verify that the version of ducc_ling is compatible
[ https://issues.apache.org/jira/browse/UIMA-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5134. -- Resolution: Abandoned DUCC has been retired. > DUCC should verify that the version of ducc_ling is compatible > -- > > Key: UIMA-5134 > URL: https://issues.apache.org/jira/browse/UIMA-5134 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > There was a change in 2.1.0 that separated the stdout & stderr streams for > APs ... this change requires a 2.1.0 ducc_ling -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5214) Add option to restrict vertical scaling of DUCC service instances
[ https://issues.apache.org/jira/browse/UIMA-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5214. -- Resolution: Abandoned DUCC has been retired. > Add option to restrict vertical scaling of DUCC service instances > - > > Key: UIMA-5214 > URL: https://issues.apache.org/jira/browse/UIMA-5214 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > Could also add an option to request horizontal or vertical scaling -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5190) DUCC's RM logs too much
[ https://issues.apache.org/jira/browse/UIMA-5190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5190. -- Resolution: Abandoned DUCC has been retired. > DUCC's RM logs too much > --- > > Key: UIMA-5190 > URL: https://issues.apache.org/jira/browse/UIMA-5190 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Assignee: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > Reduce level to "info" and change some messages to debug. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5549) DUCC may fail to stop a service if there is an instance id is invalid
[ https://issues.apache.org/jira/browse/UIMA-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5549. -- Resolution: Abandoned DUCC has been retired. > DUCC may fail to stop a service if there is an instance id is invalid > - > > Key: UIMA-5549 > URL: https://issues.apache.org/jira/browse/UIMA-5549 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > The DB entry for service 9776 has implementor 365461.0 which was killed > during a shutdown but not recorded by the SM. So now when it tries to cancel > it the request is ignored (service not found in even log) but perhaps because > the OR doesn't publish that this so-called "job" has terminated it is never > removed from the list of implementors. Perhaps the SM should validate the OR > publications against its lists of implementors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3699) ducc.py script does not work for broker with localhost
[
https://issues.apache.org/jira/browse/UIMA-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-3699.
--
Resolution: Abandoned
DUCC has been retired.
> ducc.py script does not work for broker with localhost
> --
>
> Key: UIMA-3699
> URL: https://issues.apache.org/jira/browse/UIMA-3699
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
>Affects Versions: future-DUCC
> Environment: uima-ducc-vm, see Jira Infra 7194
>Reporter: Lou DeGenaro
>Assignee: Jaroslaw Cwiklik
>Priority: Major
>
> We had to hack ducc.py to handle blocked ports. In particular:
> os.environ['ACTIVEMQ_OPTS'] = '-Djava.rmi.server.hostname=localhost
> -DDUCC_AMQ_PORT=' + broker_port + \
> and
> jvm_opts.append('-Djava.rmi.server.hostname=localhost')
> From Infra 7194:
> Also, the AMQ broker's RMI needed to be configured (via -D) to use localhost
> instead of defaulting to the host's IP address.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (UIMA-6032) DUCC shutdown has become slow
[ https://issues.apache.org/jira/browse/UIMA-6032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6032. -- Resolution: Abandoned DUCC has been retired. > DUCC shutdown has become slow > - > > Key: UIMA-6032 > URL: https://issues.apache.org/jira/browse/UIMA-6032 > Project: UIMA > Issue Type: Bug > Components: DUCC >Affects Versions: 3.0.0-Ducc >Reporter: Eddie Epstein >Priority: Minor > Fix For: future-DUCC > > > DUCC 3.0.0 shutdown is considerably slower and more verbose than previous > versions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3329) DUCC webserver (WS) graphs
[ https://issues.apache.org/jira/browse/UIMA-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3329. -- Resolution: Abandoned DUCC has been retired. > DUCC webserver (WS) graphs > -- > > Key: UIMA-3329 > URL: https://issues.apache.org/jira/browse/UIMA-3329 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3064) Updates to services in ducc-mon should apply immediately
[ https://issues.apache.org/jira/browse/UIMA-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3064. -- Resolution: Abandoned DUCC has been retired. > Updates to services in ducc-mon should apply immediately > > > Key: UIMA-3064 > URL: https://issues.apache.org/jira/browse/UIMA-3064 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > Currently a service owner can change the autostart & instances fields in the > registry, but they are not "activated" until the service is restarted. Just > like the start & stop buttons these changes should be applied when made. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4337) Isolate DUCC Agent so that it is not dependent on common and transport
[ https://issues.apache.org/jira/browse/UIMA-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4337. -- Resolution: Abandoned DUCC has been retired. > Isolate DUCC Agent so that it is not dependent on common and transport > -- > > Key: UIMA-4337 > URL: https://issues.apache.org/jira/browse/UIMA-4337 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Jaroslaw Cwiklik >Assignee: Jaroslaw Cwiklik >Priority: Major > Fix For: future-DUCC > > > Changes to common and transport require Agent restart. Since the restart > means killing all running jobs (JDs, JPs and Services) such action can be > expensive. > The proposal is to find a way to remove Agent dependency on common and > transport jars. Agent code should be isolated and self contained. This > requires major refactoring with impact on other Ducc daemons. > Currently an Agent publishes its inventory of processes using common classes > included in transport jar. It also publishes metrics using classes from > common jar. Those publications are consumed by RM, OR, and WS. The Agent uses > common code to bootstrap and configure itself just like all of the Ducc > daemons. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4570) If a log directory exists DUCC renames it and sweeps away the job spec
[ https://issues.apache.org/jira/browse/UIMA-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4570. -- Resolution: Abandoned DUCC has been retired. > If a log directory exists DUCC renames it and sweeps away the job spec > -- > > Key: UIMA-4570 > URL: https://issues.apache.org/jira/browse/UIMA-4570 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > The result is that ducc-mon cannot find the job specification. > Since this renaming of the log directory is only useful in the unusual case > of reinstalling DUCC without preserving the orchestrator sequence number, we > should remove the logsweeper ... or somehow make it run before any other > component opens the log directory. Without it, if job numbers are reused, > the log directory would have stale out-of-date log files ... easily avoided > if the directory is removed before restarting DUCC. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3083) DUCC webserver (WS) consumes excessive memory and CPU under java 1.7
[ https://issues.apache.org/jira/browse/UIMA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3083. -- Resolution: Abandoned DUCC has been retired. > DUCC webserver (WS) consumes excessive memory and CPU under java 1.7 > > > Key: UIMA-3083 > URL: https://issues.apache.org/jira/browse/UIMA-3083 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > Bypass is to specify useLegacyMergeSort in ducc.properties, for example: > ducc.ws.jvm.args = -Xmx12G -XX:-OmitStackTraceInFastThrow > -Djava.util.Arrays.useLegacyMergeSort=true -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3522) DUCC orchestrtor (OR) StateManager should not prune too soon
[ https://issues.apache.org/jira/browse/UIMA-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3522. -- Resolution: Abandoned DUCC has been retired. > DUCC orchestrtor (OR) StateManager should not prune too soon > > > Key: UIMA-3522 > URL: https://issues.apache.org/jira/browse/UIMA-3522 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > StateManager prunes after 1 minute. To be "friendly" to subscribers, it > should not prune a map entry until it has been published at least once as > "Completed". > This is low priority, since map absence should be seen as Completed by > subscribers anyway. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-6198) ducc_watcher should employ SSL certificate validation
[ https://issues.apache.org/jira/browse/UIMA-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6198. -- Resolution: Abandoned DUCC has been retired. > ducc_watcher should employ SSL certificate validation > - > > Key: UIMA-6198 > URL: https://issues.apache.org/jira/browse/UIMA-6198 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > See Sumary. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3448) DUCC orchestrator (OR) and job driver (JD) should not retry forever work items that appear on failing JPs
[ https://issues.apache.org/jira/browse/UIMA-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3448. -- Resolution: Abandoned DUCC has been retired. > DUCC orchestrator (OR) and job driver (JD) should not retry forever work > items that appear on failing JPs > - > > Key: UIMA-3448 > URL: https://issues.apache.org/jira/browse/UIMA-3448 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > One or more work items may cause a Job Process (JP) to crash. The work items > should be tracked and given-up on after some number of JP crashes. And/or > there should be some limit to the number of JP crashes for the Job before it > is auto-terminated for cause. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4790) DUCC Job Driver (JD) and Job Process (JP) support for encrypted communication
[ https://issues.apache.org/jira/browse/UIMA-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4790. -- Resolution: Abandoned DUCC has been retired. > DUCC Job Driver (JD) and Job Process (JP) support for encrypted communication > - > > Key: UIMA-4790 > URL: https://issues.apache.org/jira/browse/UIMA-4790 > Project: UIMA > Issue Type: New Feature > Components: DUCC >Reporter: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > DUCC's work item communications between Job Driver (JD) and Job Process (JP) > should be configurable to employ encryption, similar that for for Web Server > (WS) login requests over https. > Justification: private information within the user supplied work item (e.g. > personal health, financial...) may be transmitted for processing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3942) Agents hang on shutdown if broker shutsdown too quickly
[ https://issues.apache.org/jira/browse/UIMA-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3942. -- Resolution: Abandoned DUCC has been retired. > Agents hang on shutdown if broker shutsdown too quickly > --- > > Key: UIMA-3942 > URL: https://issues.apache.org/jira/browse/UIMA-3942 > Project: UIMA > Issue Type: Bug > Components: DUCC >Affects Versions: 1.0.0-Ducc >Reporter: Burn L. Lewis >Assignee: Jaroslaw Cwiklik >Priority: Minor > Fix For: future-DUCC > > > As a first step increase the stop_ducc wait time from 30 to 60 secs -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3847) DUCC Web Server (WS) needs to simplify Scheduler & Agent { States + Reasons + Exit Codes } on Processes tab of Job Details page
[
https://issues.apache.org/jira/browse/UIMA-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-3847.
--
Resolution: Abandoned
DUCC has been retired.
> DUCC Web Server (WS) needs to simplify Scheduler & Agent { States + Reasons +
> Exit Codes } on Processes tab of Job Details page
> ---
>
> Key: UIMA-3847
> URL: https://issues.apache.org/jira/browse/UIMA-3847
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
>Reporter: Lou DeGenaro
>Assignee: Lou DeGenaro
>Priority: Minor
> Fix For: future-DUCC
>
>
> One unified state perhaps? Or leave as is but flag unexpected results in
> red? And/or have admin and user views?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (UIMA-4434) DUCC Orchestrator (OR) job:node blacklisting
[ https://issues.apache.org/jira/browse/UIMA-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4434. -- Resolution: Abandoned DUCC has been retired. > DUCC Orchestrator (OR) job:node blacklisting > > > Key: UIMA-4434 > URL: https://issues.apache.org/jira/browse/UIMA-4434 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > A submitted Job may have shares allocated on some nodes where the JP works > and some nodes where the JP fails. > With respect to initialization, the OR should have a limit to the number of > initialization failures on a node before that node is banished for the Job. > The OR should communicate the blacklisted nodes for each Job to the RM who > should then not allocate and shares on said nodes for said corresponding Jobs. > An example failure situation is as follows: > 1. Node X does not have Filesystem F mounted > 2. Job 1 is submitted and is allocated to Node X > 3. Job 1's JP on Node X fails initialization (missing files!) > 4. RM allocates next JP for Job 1 to same Node X, ad infinitum until max init > failures is reached > 5. Job 1 is prevented from expanding because of a single "bad" Node > If Node X had been blacklisted, then the RM would have allocated Node Y to > Job 1 and expansion could have occurred. > Other types of JP failure scenarios: process croak and work item > failure/timeout will not be considered for blacklisting, presently. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3551) DUCC orchestrtor (OR) should take over responsibility for auto-cancel monitoring and enforcement
[ https://issues.apache.org/jira/browse/UIMA-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3551. -- Resolution: Abandoned DUCC has been retired. > DUCC orchestrtor (OR) should take over responsibility for auto-cancel > monitoring and enforcement > > > Key: UIMA-3551 > URL: https://issues.apache.org/jira/browse/UIMA-3551 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > This functionality is presently provided by the WS, due in part to early > development concerns relative to OR stability and performance which are no > longer. > This will free the WS from any requisite duties for running DUCC. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-2902) DUCC webserver (WS) should display enough of primitive name (Performance Name) to make it unique
[ https://issues.apache.org/jira/browse/UIMA-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-2902. -- Resolution: Abandoned DUCC has been retired. > DUCC webserver (WS) should display enough of primitive name (Performance > Name) to make it unique > > > Key: UIMA-2902 > URL: https://issues.apache.org/jira/browse/UIMA-2902 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > Sometime duplicates appear under Performance Name due to "mindless" > truncation of leading path. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4197) Using non-blocking "Future" instead of blocking "Future.get" to improve performance?
[
https://issues.apache.org/jira/browse/UIMA-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-4197.
--
Resolution: Abandoned
DUCC has been retired.
> Using non-blocking "Future" instead of blocking "Future.get" to improve
> performance?
>
>
> Key: UIMA-4197
> URL: https://issues.apache.org/jira/browse/UIMA-4197
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
>Reporter: Yu Lin
>Priority: Minor
> Fix For: future-DUCC
>
>
> Hi, I'm doing research on asynchronous programming. I found at some places,
> the code in uima-ducc ("trunk" branch) invokes "Future.get()", while it is a
> blocking call.
> For example, in "startAgents" method of "DuccAdmin" class (line 296), you
> invoke "result.get()", where "result" is a Future, so the code blocks.
> Why not use Guava ListenableFuture or Java8 CompletableFuture and avoid
> "Future.get()"? These two new constructs provide callbacks to listen to the
> Future's result:
> http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/util/concurrent/ListenableFuture.html
> https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html
> For example, in "DuccAdmin" class, you may put the code after "result.get()"
> (such as lines 301-307) into "CompletableFuture.thenRunAsync" method.
> Then make "startAgents" method return this CompletableFuture, and in the
> callers (such as "DuccAdmin.process()" or "DuccAdmin.main" method) you can
> put more continuations into "CompletableFuture.thenRunAsync". And you can
> also invoke "Future.get" somewhere in the callers (for example in
> "DuccAdmin.process()" method), instead of immediately.
> Do you think such kind of change is correct and can improve the code?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (UIMA-3864) DUCC Web Server (WS) hide/show on services page may result in misleading display...
[ https://issues.apache.org/jira/browse/UIMA-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3864. -- Resolution: Abandoned DUCC has been retired. > DUCC Web Server (WS) hide/show on services page may result in misleading > display... > --- > > Key: UIMA-3864 > URL: https://issues.apache.org/jira/browse/UIMA-3864 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > The hide/show buttons on the Serivce Details page expand and contract all at > once. That is, the hide/show button for svc.classpath and the one for > svc.service_ping_classpath each cause both to hide or show in unison. > The user must then scroll to the right location on the page. > In one case, the user clicks on show for svc.service_ping_classpath. Both > and svc.service_ping_classpath are expanded, but the updated display starts > at the top where svc.classpath is displayed. The user expects to see > svc.service_ping_classpath and does not realize that scrolling down is > necessary, and is fooled into thinking the data in view is the data desired. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4940) Resurrect ducc_perf_stats
[ https://issues.apache.org/jira/browse/UIMA-4940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4940. -- Resolution: Abandoned DUCC has been retired. > Resurrect ducc_perf_stats > - > > Key: UIMA-4940 > URL: https://issues.apache.org/jira/browse/UIMA-4940 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > See UIMA-4509. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4489) CLI commands that don't use the log directory will fail if it cannot be created
[ https://issues.apache.org/jira/browse/UIMA-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4489. -- Resolution: Abandoned DUCC has been retired. > CLI commands that don't use the log directory will fail if it cannot be > created > --- > > Key: UIMA-4489 > URL: https://issues.apache.org/jira/browse/UIMA-4489 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Assignee: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > All CLI commands try to create the log directory and check that it exists, > even if they don't use it. Produces a surprising error if the default > ~/ducc/logs is a symbolic link to a deleted dir. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3065) DUCC webserver (WS) shows blank for new Service
[ https://issues.apache.org/jira/browse/UIMA-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3065. -- Resolution: Abandoned DUCC has been retired. > DUCC webserver (WS) shows blank for new Service > --- > > Key: UIMA-3065 > URL: https://issues.apache.org/jira/browse/UIMA-3065 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > 10 Jul 2013 09:58:07,612 INFO WS.DuccHandler - handle N/A > java.lang.NullPointerException > At: > > org.apache.uima.ducc.ws.server.DuccHandler.handleDuccServletServiceSummaryData(DuccHandler.java:1907) > > org.apache.uima.ducc.ws.server.DuccHandler.handleDuccRequest(DuccHandler.java:3470) > > org.apache.uima.ducc.ws.server.DuccHandler.handle(DuccHandler.java:3620) > > org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:47) > > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:110) > org.eclipse.jetty.server.Server.handle(Server.java:346) > ... -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3697) DUCC common services
[ https://issues.apache.org/jira/browse/UIMA-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3697. -- Resolution: Abandoned DUCC has been retired. > DUCC common services > > > Key: UIMA-3697 > URL: https://issues.apache.org/jira/browse/UIMA-3697 > Project: UIMA > Issue Type: Bug > Components: DUCC >Affects Versions: 1.0.0-Ducc >Reporter: Lou DeGenaro >Assignee: Jaroslaw Cwiklik >Priority: Minor > Fix For: future-DUCC > > > If information that is needed for route building is missing from > ducc.properties, no clue is given in the daemon logs. > Below is shown a stack trace obtained by adding try/catch code to WS > component only. > In this case, the problem was that the following was missing from > ducc.properties: > ducc.db.state.update.endpoint=ducc.db.state > The same problem could occur for other daemons relative their routes. > = > 26 Mar 2014 18:22:04,827 1 INFO WS.WebServerConfiguration - webServer > N/A routes added > 26 Mar 2014 18:22:04,907 1 INFO WS.WebServerComponent - start N/A > .Starting Admin Channel on endpoint:activemq:topic:ducc.admin.channel > 26 Mar 2014 18:22:05,005 1 INFO WS.WebServerComponent - startAdminChannel > N/A Admin Channel Activated on endpoint:activemq:topic:ducc.admin.channel > 26 Mar 2014 18:22:05,005 1 INFO WS.WebServerComponent - start N/A > .Starting Camel Context > 26 Mar 2014 18:22:07,722 1 ERROR WS.WebServerComponent - null N/A > org.apache.camel.FailedToCreateRouteException: Failed to create route route6: > Route[[From[no uri or ref supplied!]] -> [process[org.apache... because of > Either 'uri' or 'ref' must be specified on: > org.apache.camel.impl.DefaultRouteContext@52ea8917 > at > org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:176) > at > org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:722) > at > org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:1779) > at > org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:1572) > at > org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:1437) > at > org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:60) > at > org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:1405) > at > org.apache.uima.ducc.common.component.AbstractDuccComponent.start(AbstractDuccComponent.java:283) > at > org.apache.uima.ducc.ws.WebServerComponent.start(WebServerComponent.java:74) > at > org.apache.uima.ducc.common.component.AbstractDuccComponent.start(AbstractDuccComponent.java:263) > at > org.apache.uima.ducc.common.main.DuccService.boot(DuccService.java:141) > at > org.apache.uima.ducc.common.main.DuccService.main(DuccService.java:212) > Caused by: java.lang.IllegalArgumentException: Either 'uri' or 'ref' must be > specified on: org.apache.camel.impl.DefaultRouteContext@52ea8917 > at > org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:129) > at > org.apache.camel.model.FromDefinition.resolveEndpoint(FromDefinition.java:72) > at > org.apache.camel.impl.DefaultRouteContext.getEndpoint(DefaultRouteContext.java:89) > at > org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:851) > at > org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:171) > ... 11 more -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5473) Remove JCas classes from the user jar for UIMA V2/V3 compatibility
[ https://issues.apache.org/jira/browse/UIMA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5473. -- Resolution: Abandoned DUCC has been retired. > Remove JCas classes from the user jar for UIMA V2/V3 compatibility > -- > > Key: UIMA-5473 > URL: https://issues.apache.org/jira/browse/UIMA-5473 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Major > Fix For: future-DUCC > > > UIMA V2 & V3 JCas classes are incompatible and since the uima-ducc-user jar > is added to the user's class path we must either support 2 versions of that > jar or remove any use of JCas. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5283) SM sometimes keeps starting failing instances forever (see UIMA-5244)
[ https://issues.apache.org/jira/browse/UIMA-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5283. -- Resolution: Abandoned DUCC has been retired. > SM sometimes keeps starting failing instances forever (see UIMA-5244) > - > > Key: UIMA-5283 > URL: https://issues.apache.org/jira/browse/UIMA-5283 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > Another attempt at fixing the problem reported in 5244. Must also fix the > false reporting of failing instances when DUCC is restarted and the OR > initially claims that the instances running at shutdown are still running. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3532) DUCC doesn't fully follow UIMA resource-loading conventions
[ https://issues.apache.org/jira/browse/UIMA-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3532. -- Resolution: Abandoned DUCC has been retired. > DUCC doesn't fully follow UIMA resource-loading conventions > --- > > Key: UIMA-3532 > URL: https://issues.apache.org/jira/browse/UIMA-3532 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > DUCC doesn't use the UIMA resolveRelativePath method correctly when loading > descriptors. It should be set up with the user's classpath and JVM args. > Currently DUCC services must be given a file DD as classpath/data-path > loading doesn't work. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3126) DUCC webserver (WS) improvements for handing "down" node with respect to work items thereto dispatched
[ https://issues.apache.org/jira/browse/UIMA-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3126. -- Resolution: Abandoned DUCC has been retired. > DUCC webserver (WS) improvements for handing "down" node with respect to work > items thereto dispatched > -- > > Key: UIMA-3126 > URL: https://issues.apache.org/jira/browse/UIMA-3126 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > 1. On Work Items tab, show down nodes for active work items in RED > 2. Indicate such "troubled" work items on Jobs page > 3. Offer user one button "clean-up" for doomed work items -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5099) DUCC Service Manager (SM) pinger message not clear when incorrect JMX has been port specified
[ https://issues.apache.org/jira/browse/UIMA-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5099. -- Resolution: Abandoned DUCC has been retired. > DUCC Service Manager (SM) pinger message not clear when incorrect JMX has > been port specified > - > > Key: UIMA-5099 > URL: https://issues.apache.org/jira/browse/UIMA-5099 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Jaroslaw Cwiklik >Priority: Minor > Fix For: future-DUCC > > > Service was configured with: > service_ping_arguments broker-jmx-port=1100 > After starting service, message in registry was: > = > meta.service-statistics JMX Failure[Failed to retrieve RMIServer stub: > javax.naming.ServiceUnavailableException [Root exception is > java.rmi.ConnectException: Connection refused to host: broker1; nested > exception is: java.net.ConnectException: Connection refused]]] > MetaNode[192.168.2.120] MetaPid[13647:76 > = > Problem was that port should have been 1099. > More clarity is desirable, such as: unable to connect to broker1 on port 1100. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3960) DUCC Orchestrator (OR) records wrong exit code == 0 to a Managed Reservation canceled by user
[ https://issues.apache.org/jira/browse/UIMA-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3960. -- Resolution: Abandoned DUCC has been retired. > DUCC Orchestrator (OR) records wrong exit code == 0 to a Managed Reservation > canceled by user > - > > Key: UIMA-3960 > URL: https://issues.apache.org/jira/browse/UIMA-3960 > Project: UIMA > Issue Type: Bug > Components: DUCC > Environment: Reported by Burn. >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > Correct exit code should be 15. Probably a race condition in the OR. > Note: see logs in /degenaro/tmp/186050 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4629) DUCC Job Driver (JD) should provide individual work item performance breakdowns submit --flag
[ https://issues.apache.org/jira/browse/UIMA-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4629. -- Resolution: Abandoned DUCC has been retired. > DUCC Job Driver (JD) should provide individual work item performance > breakdowns submit --flag > - > > Key: UIMA-4629 > URL: https://issues.apache.org/jira/browse/UIMA-4629 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > See UIMA-4586. > Replace environment variable with ducc_submit flag and add to doc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5268) When DUCC is restarted the OR publishes defunct work that are treated as failures by the SM
[ https://issues.apache.org/jira/browse/UIMA-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5268. -- Resolution: Abandoned DUCC has been retired. > When DUCC is restarted the OR publishes defunct work that are treated as > failures by the SM > --- > > Key: UIMA-5268 > URL: https://issues.apache.org/jira/browse/UIMA-5268 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Major > Fix For: future-DUCC > > > The work that was active at shutdown is presented as Running after the > restart but is soon changed to Completed. This sometimes makes the SM > disable a service. Perhaps the completion-type or rationale could be > something like "Framework Error" or "node restart" so these are not treated > as user errors. > SM.ServiceHandler - 6107 handleModifiedServices !! Processing modified > instance 297751 state Running > SM.ServiceHandler - 6107 handleModifiedServices !! Processing modified > instance 297751 state Completed completion-type Warning rationale process > failure(s) occurred > After restarting all instances the registry had the following: > submit-errorService stopped by exessive failures. Initialization > failures[0], Runtime failures[0] > but soon after this was remove and ducc-mon said Available. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5582) Launch external pingers with the user-supplied --jvm instead of DUCC's
[ https://issues.apache.org/jira/browse/UIMA-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5582. -- Resolution: Abandoned DUCC has been retired. > Launch external pingers with the user-supplied --jvm instead of DUCC's > -- > > Key: UIMA-5582 > URL: https://issues.apache.org/jira/browse/UIMA-5582 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Burn L. Lewis >Assignee: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > Currently if JAVA_HOME is not in the environment DUCC uses the same JVM as > DUCC to launch external pingers. Instead use the jvm supplied by the user > which is likely to be the same as the service. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3498) DUCC webserver (WS) improved use of /bin/cat
[
https://issues.apache.org/jira/browse/UIMA-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-3498.
--
Resolution: Abandoned
DUCC has been retired.
> DUCC webserver (WS) improved use of /bin/cat
>
>
> Key: UIMA-3498
> URL: https://issues.apache.org/jira/browse/UIMA-3498
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
>Reporter: Lou DeGenaro
>Assignee: Lou DeGenaro
>Priority: Minor
> Fix For: future-DUCC
>
>
> In AlienFile.java, follow the recipe provided by Burn below:
> // Run process and log all output
> ProcessBuilder pb = new ProcessBuilder(args);
> pb.redirectErrorStream(true);
> Process p = pb.start();
> BufferedReader in = new BufferedReader(new
> InputStreamReader(p.getInputStream()));
> String line = in.readLine();
> while (line != null) {
> if (outStream == null) {
> logger.log(Level.INFO, "[" + id + "] " + line);
> } else {
> outStream.println(line);
> }
> line = in.readLine();
> }
> in.close();
> if (outStream != null) {
> outStream.close();
> }
> rc = p.waitFor();
> if (rc != 0 && outStream != null) {
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (UIMA-3009) DUCC webserver (WS) needs to employ executable jars
[ https://issues.apache.org/jira/browse/UIMA-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3009. -- Resolution: Abandoned DUCC has been retired. > DUCC webserver (WS) needs to employ executable jars > --- > > Key: UIMA-3009 > URL: https://issues.apache.org/jira/browse/UIMA-3009 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > slf4j messages are annoying! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5012) No error notification for services specifying an unwritable logfile directory
[ https://issues.apache.org/jira/browse/UIMA-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5012. -- Resolution: Abandoned DUCC has been retired. > No error notification for services specifying an unwritable logfile directory > - > > Key: UIMA-5012 > URL: https://issues.apache.org/jira/browse/UIMA-5012 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Eddie Epstein >Priority: Major > Fix For: future-DUCC > > > For other DUCC work submissions the cli checks for this problem and does a > fast fail. The same needs to be done for service instance submissions done by > the Service Manager, with the error persisted in the service meta information > and shown on the service page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5615) DUCC's WaitingForDriver should not include the JD initialization phase
[ https://issues.apache.org/jira/browse/UIMA-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5615. -- Resolution: Abandoned DUCC has been retired. > DUCC's WaitingForDriver should not include the JD initialization phase > -- > > Key: UIMA-5615 > URL: https://issues.apache.org/jira/browse/UIMA-5615 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > It would be better to add another state, Initializing Job Driver, to help > distinguish between waiting for the resource and waiting for the CR to > initialize -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4469) DUCC SM: Reference stop fails after some hot-restarts
[ https://issues.apache.org/jira/browse/UIMA-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4469. -- Resolution: Abandoned DUCC has been retired. > DUCC SM: Reference stop fails after some hot-restarts > - > > Key: UIMA-4469 > URL: https://issues.apache.org/jira/browse/UIMA-4469 > Project: UIMA > Issue Type: Bug > Components: DUCC >Affects Versions: 1.0.0-Ducc, 1.1.0-Ducc, 2.0.0-Ducc >Reporter: Jim Challenger >Assignee: Jim Challenger >Priority: Minor > Fix For: future-DUCC > > > If SM is taken down for a while and jobs referencing existing services exit > so the services no longer are referenced, then SM is restarted, the fact that > a reference-started service is no longer referenced is not acted upon. > To fix, on hot restart, SM needs to insure all reference-started services are > still referenced and begin the lingering stop if not. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3981) DUCC Orchestrator (OR) makes wrong time stamp for Croaked JPs?
[ https://issues.apache.org/jira/browse/UIMA-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3981. -- Resolution: Abandoned DUCC has been retired. > DUCC Orchestrator (OR) makes wrong time stamp for Croaked JPs? > -- > > Key: UIMA-3981 > URL: https://issues.apache.org/jira/browse/UIMA-3981 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > It has been reported that when a Job Process (JP) Croaks and later the Job > goes to Completed state, the ending time stamp for the JP is changed from the > actual time it finished (as observed via Web Server) to a time close in > proximity to the Job Completion time. > The OR should not (if it does) modify the time of an already completed JP > during Job Completed clean-up time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4756) check_ducc reports success for a remote worker that cannot be reached
[ https://issues.apache.org/jira/browse/UIMA-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4756. -- Resolution: Abandoned DUCC has been retired. > check_ducc reports success for a remote worker that cannot be reached > - > > Key: UIMA-4756 > URL: https://issues.apache.org/jira/browse/UIMA-4756 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Eddie Epstein >Priority: Minor > Fix For: future-DUCC > > > check_ducc shows no errors for machines that are not reachable on the network. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-2641) DUCC orchestrator (OR) should mark unused, stubbornly alive Job Processes (JPs) as "Stopped" when all work items are accounted for...
[ https://issues.apache.org/jira/browse/UIMA-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-2641. -- Resolution: Abandoned DUCC has been retired. > DUCC orchestrator (OR) should mark unused, stubbornly alive Job Processes > (JPs) as "Stopped" when all work items are accounted for... > - > > Key: UIMA-2641 > URL: https://issues.apache.org/jira/browse/UIMA-2641 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > Recently, a job was submitted but got stuck in state "Completing". All work > items had completed. During the run a Job Process (JP) was launched and got > stuck in Initializing state because the machine on which it (once) existed > crashed and (therefore) the DUCC Agent responsible was unable to report or > take action. This stuck JP was keeping the job from advancing to the > "Completed" state. > The user issued the DUCC cancel command using flag --dpid to cancel the bogus > JP and the job completed normally. > This situation could be detected by the orchestrator (OR) and handled w/o > human (user) intervention. > Additionally, the WS could be helpful in a) identifying those cases that > cannot be automatically handled and b) offering guidance towards freeing up > work items held in limbo. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3592) DUCC WebServer (WS) some pages missing data for logged-in user
[ https://issues.apache.org/jira/browse/UIMA-3592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3592. -- Resolution: Abandoned DUCC has been retired. > DUCC WebServer (WS) some pages missing data for logged-in user > --- > > Key: UIMA-3592 > URL: https://issues.apache.org/jira/browse/UIMA-3592 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > - downloaded RC10 binary tarball to standalone 8GB thinkpad running RHEL 6.4 > - followed directions from INSTALL file for single-user install and > verification > - followed directions for multi-user install with webserver login and > verified with 1.job submitted from non-ducc user. Found webserver problem > displaying "Files" in the job details page. More on this below (*). > - followed directions from duccbook.html, chapter 9 to install opennlp and > run text processing sample > - ran CAS input processing sample from chapter 10 > - setup java_viaducc as per chapter 3.13 and ran hello world type program. > Process ran fine, but webserver again could not display "Files" or > "Specification" from reservation details page. See (**). > (*) Directory permissions for non-ducc user are configured to not allow > read access by user "ducc". In this situation the webserver will not be > able to display job details from user log files, unless authenticated to > the webserver as the user with read permission. After logging into the > webserver, all job details were accessible except for "Files" tab. > (**) Similar problem as with Job details. Log file OK, but nothing shown in > "Files" or "Specification" tabs. > All these details are available to users as human readable files in their > filesystem. Another workaround available, if it is OK for cluster users to > see each others logfiles, is simply to give user "ducc" read access to the > user log directories and files there. Therefor I do not consider this a > blocker for first release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5313) Can get concurrent modification when closing the threads attached to a DUCC AP
[ https://issues.apache.org/jira/browse/UIMA-5313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5313. -- Resolution: Abandoned DUCC has been retired. > Can get concurrent modification when closing the threads attached to a DUCC AP > -- > > Key: UIMA-5313 > URL: https://issues.apache.org/jira/browse/UIMA-5313 > Project: UIMA > Issue Type: Bug >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > id:32044 state:Completed > id:32044 rationale:code=0 > id:32044 rc:0 > java.util.ConcurrentModificationException > at java.util.HashMap$HashIterator.nextEntry(HashMap.java:934) > at java.util.HashMap$ValueIterator.next(HashMap.java:962) > at > org.apache.uima.ducc.cli.ConsoleListener.shutdown(ConsoleListener.java:89) > at org.apache.uima.ducc.cli.CliBase.monitorExits(CliBase.java:677) > at org.apache.uima.ducc.cli.MonitorListener.run(MonitorListener.java:92) > at java.lang.Thread.run(Thread.java:809) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3048) DUCC components, for example Job Driver (JD), should publish data (e.g. JSON) not objects across the network
[ https://issues.apache.org/jira/browse/UIMA-3048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3048. -- Resolution: Abandoned DUCC has been retired. > DUCC components, for example Job Driver (JD), should publish data (e.g. JSON) > not objects across the network > > > Key: UIMA-3048 > URL: https://issues.apache.org/jira/browse/UIMA-3048 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > By passing JSON data (for example) instead of Java objects between daemons, > the theory is that backward compatibility is more easily achieved as DUCC > development moves forward. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3976) DUCC Web Server (WS) Job and Service JMX accessability
[ https://issues.apache.org/jira/browse/UIMA-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3976. -- Resolution: Abandoned DUCC has been retired. > DUCC Web Server (WS) Job and Service JMX accessability > -- > > Key: UIMA-3976 > URL: https://issues.apache.org/jira/browse/UIMA-3976 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > When (UIMA) Jobs or Services become hung, problem determination often > comprises finding a relevant hung process and looking at its stack via JMX. > This procedure should be made "one-click" via the Web Server, to the extent > possible. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4763) DUCC Web Server (WS) remove from ducc.js function ducc_transform_all_cookies()
[ https://issues.apache.org/jira/browse/UIMA-4763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4763. -- Resolution: Abandoned DUCC has been retired. > DUCC Web Server (WS) remove from ducc.js function ducc_transform_all_cookies() > -- > > Key: UIMA-4763 > URL: https://issues.apache.org/jira/browse/UIMA-4763 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > Remove deprecated function, used in 2.1 to transform cookies prefix from > ducc: to DUCC. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4285) DUCC JP container for a service should not need UIMA
[ https://issues.apache.org/jira/browse/UIMA-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4285. -- Resolution: Abandoned DUCC has been retired. > DUCC JP container for a service should not need UIMA > > > Key: UIMA-4285 > URL: https://issues.apache.org/jira/browse/UIMA-4285 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > When starting a DUCC service the JP is using a UIMA class but the intent was > to isolate all UIMA use to the user container. > java.lang.ClassNotFoundException: > org.apache.uima.analysis_engine.AnalysisEngineManagement -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-6023) change String.replaceAll() to replace() if the replaced one is plain string.
[
https://issues.apache.org/jira/browse/UIMA-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-6023.
--
Resolution: Abandoned
DUCC has been retired.
> change String.replaceAll() to replace() if the replaced one is plain string.
>
>
> Key: UIMA-6023
> URL: https://issues.apache.org/jira/browse/UIMA-6023
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
>Reporter: bd2019us
>Priority: Major
> Labels: pull-request-available
> Attachments: 1.patch
>
>
> Location:
> uima-ducc-user/src/main/java/org/apache/uima/ducc/user/common/UimaUtils.java
> The replaced string ("/") is a plain string, which need not to be compiled a
> head of time. Therefore, use the replaceAll() API may damage the performance
> since replaceAll() will compile the given string. The replace() method is
> recommended to improve performance.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (UIMA-6034) ducc_ling version not correctly checked if no shared FS
[ https://issues.apache.org/jira/browse/UIMA-6034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6034. -- Resolution: Abandoned DUCC has been retired. > ducc_ling version not correctly checked if no shared FS > --- > > Key: UIMA-6034 > URL: https://issues.apache.org/jira/browse/UIMA-6034 > Project: UIMA > Issue Type: Bug > Components: DUCC >Affects Versions: 3.0.0-Ducc >Reporter: Eddie Epstein >Priority: Minor > Fix For: 3.0.1-DUCC > > > The ducc_ling version from the head node is written into a file in > $DUCC_RUNTIME/state. This value is checked when starting each agent on a > worker node. When $DUCC_RUNTIME is not on a shared filesystem the check is > broken. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4876) ducc-mon shows WI process times while active that are larger than when completed
[ https://issues.apache.org/jira/browse/UIMA-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4876. -- Resolution: Abandoned DUCC has been retired. > ducc-mon shows WI process times while active that are larger than when > completed > > > Key: UIMA-4876 > URL: https://issues.apache.org/jira/browse/UIMA-4876 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > Possibly because the ws uses the current time as an estimate of the end time. > Perhaps the OR could provide a publication timestamp that indicates when the > job state was captured. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3966) DUCC Web Server (WS) Daemons page show conflicting information
[ https://issues.apache.org/jira/browse/UIMA-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3966. -- Resolution: Abandoned DUCC has been retired. > DUCC Web Server (WS) Daemons page show conflicting information > -- > > Key: UIMA-3966 > URL: https://issues.apache.org/jira/browse/UIMA-3966 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > Agents show entries with conflicting information similar to: > Status: up > Heartbeat (last) 2159 > Heartbeat (max) 63 > 1. Why is last > max? > 2. What value for last time triggers change from up to down? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3436) DUCC job is wrongly auto-canceled
[ https://issues.apache.org/jira/browse/UIMA-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3436. -- Resolution: Abandoned DUCC has been retired. > DUCC job is wrongly auto-canceled > - > > Key: UIMA-3436 > URL: https://issues.apache.org/jira/browse/UIMA-3436 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > Job 105387 was wrongly auto-canceled when cancel_on_interrupt is specified. > There may be a hole such that when the Monitor performs ping to WS to both > acknowledge submitter is still alive and to get the current Job state, the > latter may not yet exist at WS due to latency of OR publication causing > Monitor to ...? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5782) Improve ducc_update handling of elevated ducc_ling
[ https://issues.apache.org/jira/browse/UIMA-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5782. -- Resolution: Abandoned DUCC has been retired. > Improve ducc_update handling of elevated ducc_ling > -- > > Key: UIMA-5782 > URL: https://issues.apache.org/jira/browse/UIMA-5782 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Assignee: Burn L. Lewis >Priority: Major > Fix For: future-DUCC > > > Build ducc_ling in place after removing existing one. Check in start_ducc > that it is elevated (unless non-elevated explicitly indicated) > Fix ducc_update when PWD is not in the environment > check_ducc should merge in the site properties > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4435) DUCC Orchestrator (OR) job:process publication size reduction
[ https://issues.apache.org/jira/browse/UIMA-4435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4435. -- Resolution: Abandoned DUCC has been retired. > DUCC Orchestrator (OR) job:process publication size reduction > - > > Key: UIMA-4435 > URL: https://issues.apache.org/jira/browse/UIMA-4435 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > OR should publish only active JPs. Those JPs that have run their course > should be removed. The goal is to reduce OR publication size. > The WS will need to use other means to represent the full Job Details view > under the Processes tab. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3944) DUCC should not hide error messages from Camel & Spring
[ https://issues.apache.org/jira/browse/UIMA-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3944. -- Resolution: Abandoned DUCC has been retired. > DUCC should not hide error messages from Camel & Spring > --- > > Key: UIMA-3944 > URL: https://issues.apache.org/jira/browse/UIMA-3944 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Assignee: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > Warning & error messages from Camel and Spring should be logged. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5221) DUCC start script should not discard stdout from daemons
[ https://issues.apache.org/jira/browse/UIMA-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5221. -- Resolution: Abandoned DUCC has been retired. > DUCC start script should not discard stdout from daemons > > > Key: UIMA-5221 > URL: https://issues.apache.org/jira/browse/UIMA-5221 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > Original description was a partial duplicate of 5150. > If don't ssh to localhost then could capture stdout. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4531) DUCC Web Server (WS) Jobs/Services don't display RM reason for WaitingForResources
[ https://issues.apache.org/jira/browse/UIMA-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4531. -- Resolution: Abandoned DUCC has been retired. > DUCC Web Server (WS) Jobs/Services don't display RM reason for > WaitingForResources > -- > > Key: UIMA-4531 > URL: https://issues.apache.org/jira/browse/UIMA-4531 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Jim Challenger >Priority: Minor > Fix For: future-DUCC > > > StateManager line 937 insert: > duccWork.setRmReason(rmReason); -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4338) Ducc job process sometimes does not exit cleanly
[ https://issues.apache.org/jira/browse/UIMA-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4338. -- Resolution: Abandoned DUCC has been retired. > Ducc job process sometimes does not exit cleanly > > > Key: UIMA-4338 > URL: https://issues.apache.org/jira/browse/UIMA-4338 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Jaroslaw Cwiklik >Assignee: Jaroslaw Cwiklik >Priority: Minor > Fix For: future-DUCC > > > It looks like sometimes a JP process does not terminate after it is told to > stop by an agent. All process threads seem to exit but some daemon thread is > still running preventing the jvm from exiting. The hypothesis is that one > minute may not be enough for the jvm to complete all shutdown tasks. An agent > allows 1 minute for the process to go away due to pre-emption after which a > process is killed via kill -9. > The scenario where this problem was observed involved 10 process threads. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3056) DUCC Orchestrator (OR) does not indicate why environment variable string is unacceptable
[ https://issues.apache.org/jira/browse/UIMA-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3056. -- Resolution: Abandoned DUCC has been retired. > DUCC Orchestrator (OR) does not indicate why environment variable string is > unacceptable > > > Key: UIMA-3056 > URL: https://issues.apache.org/jira/browse/UIMA-3056 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5581) When a CLI request fails because ducc is down, say so
[ https://issues.apache.org/jira/browse/UIMA-5581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5581. -- Resolution: Abandoned DUCC has been retired. > When a CLI request fails because ducc is down, say so > - > > Key: UIMA-5581 > URL: https://issues.apache.org/jira/browse/UIMA-5581 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > Currently a long stack trace ends with "Connection refused" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3033) run time value may be wrong...until EOJ
[ https://issues.apache.org/jira/browse/UIMA-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3033. -- Resolution: Abandoned DUCC has been retired. > run time value may be wrong...until EOJ > --- > > Key: UIMA-3033 > URL: https://issues.apache.org/jira/browse/UIMA-3033 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > From Burn; > I see in your json file that timeRunStart is much less that timeInitEnd ... > is actually ~= timeInitStart ... so this is why ducc-mon shows a jump in run > time -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-6103) start_ducc should always check ssh access
[ https://issues.apache.org/jira/browse/UIMA-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6103. -- Resolution: Abandoned DUCC has been retired. > start_ducc should always check ssh access > - > > Key: UIMA-6103 > URL: https://issues.apache.org/jira/browse/UIMA-6103 > Project: UIMA > Issue Type: Bug > Components: DUCC >Affects Versions: 3.0.0-Ducc >Reporter: Burn L. Lewis >Priority: Minor > > Only one of the 2 ways to start agents makes the check ... change so both use > the same code -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4873) ducc-mon job performance tab shows very large Total times
[ https://issues.apache.org/jira/browse/UIMA-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4873. -- Resolution: Abandoned DUCC has been retired. > ducc-mon job performance tab shows very large Total times > - > > Key: UIMA-4873 > URL: https://issues.apache.org/jira/browse/UIMA-4873 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > test-ducc job 294723 ran for 56 mins but Performance -> Total says > 2:23:57:33.6 ... nearly 3 days! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4836) When a nodepool is empty a job will just say WaitingForResources
[ https://issues.apache.org/jira/browse/UIMA-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4836. -- Resolution: Abandoned DUCC has been retired. > When a nodepool is empty a job will just say WaitingForResources > > > Key: UIMA-4836 > URL: https://issues.apache.org/jira/browse/UIMA-4836 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > RM log says waiting for preemptions ... should say no resources available and > ducc-mon should display it ... perhaps as a hover, or as the Reason, just > like waiting for services -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5329) While a custom service is initing ducc-mon and the SM claim the pinger is not working
[ https://issues.apache.org/jira/browse/UIMA-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5329. -- Resolution: Abandoned DUCC has been retired. > While a custom service is initing ducc-mon and the SM claim the pinger is not > working > - > > Key: UIMA-5329 > URL: https://issues.apache.org/jira/browse/UIMA-5329 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > When a custom service is initializing its pinger usually reports not alive > and not healthy ... but ducc-mon says "pinger not reporting" while it does > display the pinger's info msg. Also the SM log says "pinger data stale" ... > seems confusing! Note that we could use the first "alive" pinger report to > indicate that initialization is complete. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4999) Remove need for simulated DUCC runs to set ducc.runmode=Test
[ https://issues.apache.org/jira/browse/UIMA-4999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4999. -- Resolution: Abandoned DUCC has been retired. > Remove need for simulated DUCC runs to set ducc.runmode=Test > > > Key: UIMA-4999 > URL: https://issues.apache.org/jira/browse/UIMA-4999 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > Would also be safer by ensuring that test-mode is set ONLY for simulated runs -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5654) ducc_ling should verify that it's "ducc" id is correct
[ https://issues.apache.org/jira/browse/UIMA-5654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5654. -- Resolution: Abandoned DUCC has been retired. > ducc_ling should verify that it's "ducc" id is correct > -- > > Key: UIMA-5654 > URL: https://issues.apache.org/jira/browse/UIMA-5654 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Assignee: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > It should check that the compiled ducc-id is correct -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4174) DUCC Monitor (CLI) should display host (and PID) for Managed Reservations
[ https://issues.apache.org/jira/browse/UIMA-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4174. -- Resolution: Abandoned DUCC has been retired. > DUCC Monitor (CLI) should display host (and PID) for Managed Reservations > - > > Key: UIMA-4174 > URL: https://issues.apache.org/jira/browse/UIMA-4174 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > It would be useful to view in the monitor output where the Managed > Reservation has been deployed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5779) DUCC should tolerate DB errors
[ https://issues.apache.org/jira/browse/UIMA-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5779. -- Resolution: Abandoned DUCC has been retired. > DUCC should tolerate DB errors > -- > > Key: UIMA-5779 > URL: https://issues.apache.org/jira/browse/UIMA-5779 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Assignee: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > If the DB fails the daemons merely log the problem and carry on in a bad > state. > The SM will not persist any registry changes and will confuse the WS > The RM thread handling node updates is blocked by synchronized methods in the > scheduler and cause nodes to be falsely purged of their work > The OR fails writing the checkpoint -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-2733) DUCC Orchestrator (OR) should share authentication/role functions with other DUCC components
[ https://issues.apache.org/jira/browse/UIMA-2733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-2733. -- Resolution: Abandoned DUCC has been retired. > DUCC Orchestrator (OR) should share authentication/role functions with other > DUCC components > > > Key: UIMA-2733 > URL: https://issues.apache.org/jira/browse/UIMA-2733 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5263) Improve DUCC's handling of deprecated properties
[ https://issues.apache.org/jira/browse/UIMA-5263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5263. -- Resolution: Abandoned DUCC has been retired. > Improve DUCC's handling of deprecated properties > > > Key: UIMA-5263 > URL: https://issues.apache.org/jira/browse/UIMA-5263 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > If a property is deprecated or renamed start_ducc should complain if the old > value is found in the site properties. Rather than making the code handle > old & new names we should insist that every entry in the site file also > exists in the default file ... properties should not be commented out in the > default file ... an empty value should be assigned instead of omitting the > property. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3359) DUCC webserver scroll view (via Datatables) shows duplicate rows
[ https://issues.apache.org/jira/browse/UIMA-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3359. -- Resolution: Abandoned DUCC has been retired. > DUCC webserver scroll view (via Datatables) shows duplicate rows > > > Key: UIMA-3359 > URL: https://issues.apache.org/jira/browse/UIMA-3359 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > Probably due to Datatable not being cleared prior to fetch of replacement > data. > Possible work-arounds for end user: > 1. Use "Classic" mode for Table Style in Preferences > 2. Hit enter to redisplay page -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-6139) "all_in_one local" needs to add workitem jar to classpath
[ https://issues.apache.org/jira/browse/UIMA-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6139. -- Resolution: Abandoned DUCC has been retired. > "all_in_one local" needs to add workitem jar to classpath > - > > Key: UIMA-6139 > URL: https://issues.apache.org/jira/browse/UIMA-6139 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Eddie Epstein >Priority: Major > Fix For: future-DUCC > > > In order to support core uima v2 and v3, there are two versions of the > workitem jar containing jcas classes. For normal DUCC jobs the appropriate > jar based on user specified uimaj-core is added to the job classpath. This > was overlooked for "all_in_one local" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4854) DUCC Job Driver (JD) fast fail: immediately fetch first work item to exercise getNext()
[ https://issues.apache.org/jira/browse/UIMA-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4854. -- Resolution: Abandoned DUCC has been retired. > DUCC Job Driver (JD) fast fail: immediately fetch first work item to exercise > getNext() > --- > > Key: UIMA-4854 > URL: https://issues.apache.org/jira/browse/UIMA-4854 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > > Presently, the first work item is not fetched from the Collection Reader (CR) > until the first Job Process (JP) successfully initializes and requests same. > For the case where the CR is "bad" (e.g. during development) it would be good > to fail fast, rather than waiting, potentially, for quite a long time for the > first JP to initialize before learning that getNext() is foobar. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4906) UIMA DUCC: Need override for default saxon and dd2spring.xsl
[ https://issues.apache.org/jira/browse/UIMA-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4906. -- Resolution: Abandoned DUCC has been retired. > UIMA DUCC: Need override for default saxon and dd2spring.xsl > > > Key: UIMA-4906 > URL: https://issues.apache.org/jira/browse/UIMA-4906 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Jaroslaw Cwiklik >Assignee: Jaroslaw Cwiklik >Priority: Major > > UIMA-AS based services use DUCC's dd2spring.xsl and saxon8.jar. To improve > separation of Ducc and user code enable override mechanism to allow users to > specify their own dd2spring and saxon. It seems there is a way to override > dd2spring via -D. Add a new one for saxon. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4778) DUCC Web Server (WS) should provide a maximum-field-display-length user preference
[ https://issues.apache.org/jira/browse/UIMA-4778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4778. -- Resolution: Abandoned DUCC has been retired. > DUCC Web Server (WS) should provide a maximum-field-display-length user > preference > --- > > Key: UIMA-4778 > URL: https://issues.apache.org/jira/browse/UIMA-4778 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > > Some fields in the tables displayed by the Web Server could potentially be > very large. The Web Server should provide a user preference to control the > maximum length displayed, and when truncated the full display would be > viewable on hover. A reasonable default truncation value, say 64, will be > employed if no cookie preference is found. A visual indicator that > truncation has occurred is also desirable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4811) DUCC Job Driver (JD) consumes large memory near EOJ?
[ https://issues.apache.org/jira/browse/UIMA-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4811. -- Resolution: Abandoned DUCC has been retired. > DUCC Job Driver (JD) consumes large memory near EOJ? > > > Key: UIMA-4811 > URL: https://issues.apache.org/jira/browse/UIMA-4811 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > > while true; do echo -n `date`" "; echo -n $(cat > /cgroup/ducc/5749.5749.0/memory.usage_in_bytes)" "; echo -n $(cat > /cgroup/ducc/5749.5749.0/memory.max_usage_in_bytes); echo; sleep 60; done > Mon Feb 29 20:42:55 EST 2016 490405888 493027328 > Mon Feb 29 20:43:55 EST 2016 553910272 703987712 > Mon Feb 29 20:44:55 EST 2016 532152320 703987712 > Mon Feb 29 20:45:55 EST 2016 539492352 703987712 > Mon Feb 29 20:46:55 EST 2016 537722880 703987712 > Mon Feb 29 20:47:55 EST 2016 571932672 703987712 > Mon Feb 29 20:48:55 EST 2016 552796160 703987712 > Mon Feb 29 20:49:55 EST 2016 561709056 703987712 > Mon Feb 29 20:50:55 EST 2016 cat: > /cgroup/ducc/5749.5749.0/memory.usage_in_bytes: No such file or directory > cat: /cgroup/ducc/5749.5749.0/memory.max_usage_in_bytes: No such file or > directory > Note the big jump in max_memory from ~493MB to ~703MB in a one minute period. > Luckily the cgroup had been pushed up to 734003200 (700MB) and so it just > made it. > The previous job went much slower, running for 105 minutes. The max memory > use was fairly flat until the end and then had a bump too: > Mon Feb 29 20:21:21 EST 2016 482934784 494206976 > Mon Feb 29 20:22:21 EST 2016 485687296 494206976 > Mon Feb 29 20:23:21 EST 2016 506396672 538968064 > Mon Feb 29 20:24:21 EST 2016 490864640 538968064 > Mon Feb 29 20:25:21 EST 2016 522190848 538968064 > Mon Feb 29 20:26:21 EST 2016 539033600 545062912 > Mon Feb 29 20:27:21 EST 2016 558301184 559087616 > Mon Feb 29 20:28:21 EST 2016 545325056 562429952 > Mon Feb 29 20:29:21 EST 2016 566296576 567672832 > Mon Feb 29 20:30:21 EST 2016 572653568 572653568 > Mon Feb 29 20:31:21 EST 2016 555024384 592904192 > Mon Feb 29 20:32:21 EST 2016 562888704 592904192 > Mon Feb 29 20:33:21 EST 2016 564133888 592904192 > Mon Feb 29 20:34:21 EST 2016 568131584 592904192 > I think there is something going on in the JD that is using a [relatively] > large amount of memory near the end of jobs. Should be fairly easy to > simulate. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4894) UIMA-DUCC: JP should Include Reason for InitializationFailure
[ https://issues.apache.org/jira/browse/UIMA-4894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4894. -- Resolution: Abandoned DUCC has been retired. > UIMA-DUCC: JP should Include Reason for InitializationFailure > - > > Key: UIMA-4894 > URL: https://issues.apache.org/jira/browse/UIMA-4894 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Jaroslaw Cwiklik >Assignee: Jaroslaw Cwiklik >Priority: Major > > On initialization failure the JP notifies its agent of the failure but it is > not including a stack trace containing reason. When communicating failure add > the state trace to the outgoing message -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5100) DUCC script admin/start_ducc allows multiple singleton components to be started
[ https://issues.apache.org/jira/browse/UIMA-5100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5100. -- Resolution: Abandoned DUCC has been retired. > DUCC script admin/start_ducc allows multiple singleton components to be > started > --- > > Key: UIMA-5100 > URL: https://issues.apache.org/jira/browse/UIMA-5100 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Priority: Major > > start_ducc allows the following syntax: -c component@nodeX > It is possible to issue start_ducc first with -c rm@nodeA and then with -c > rm@nodeB which will result in 2 rm's running on the cluster! > One suggested solution is to allow the component@nodeX syntax only for Agents. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5223) DUCC failover support (dynamic - agent)
[ https://issues.apache.org/jira/browse/UIMA-5223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5223. -- Resolution: Abandoned DUCC has been retired. > DUCC failover support (dynamic - agent) > --- > > Key: UIMA-5223 > URL: https://issues.apache.org/jira/browse/UIMA-5223 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Jaroslaw Cwiklik >Priority: Major > > Agent should detect that failover node list has changed in ducc.properties > and should reconnect to broker accordingly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5036) UIMA-DUCC: fix Agent RejectedExecutionException
[ https://issues.apache.org/jira/browse/UIMA-5036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5036. -- Resolution: Abandoned DUCC has been retired. > UIMA-DUCC: fix Agent RejectedExecutionException > --- > > Key: UIMA-5036 > URL: https://issues.apache.org/jira/browse/UIMA-5036 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Jaroslaw Cwiklik >Assignee: Jaroslaw Cwiklik >Priority: Major > > Fix a race condition which leads to RejectedExecutionException in > LinuxProcessMetricsProcessor.process() method. The method fails with this > stack trace: > java.util.concurrent.RejectedExecutionException: Task > java.util.concurrent.FutureTask@4c38895 rejected from > java.util.concurrent.ThreadPoolExecutor@41c10669[Terminated, pool \ > size = 0, active threads = 0, queued tasks = 0, completed tasks = 2052] > at > java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047) > at > java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823) > at > java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1369) > at > java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134) > at > org.apache.uima.ducc.agent.processors.LinuxProcessMetricsProcessor.process(LinuxProcessMetricsProcessor.java:291) > at > org.apache.camel.processor.DelegateSyncProcessor.process(DelegateSyncProcessor.java:63) > at > org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:460) > at > org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:190) > at > org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:190) > at > org.apache.camel.component.timer.TimerConsumer.sendTimerExchange(TimerConsumer.java:165) > at > org.apache.camel.component.timer.TimerConsumer$1.run(TimerConsumer.java:73) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > In the above, the thread pool state shows as Terminated when a submit API was > called. This means that the thread pool was stopped when the code was trying > to use the pool. > > Each process spawned by an Agent has a Camel driven timer which triggers > metrics collection. The metrics are collected in multiple threads provided by > the thread pool. > The fix is to synchronize code in close() and process() on a common lock. In > stop() the code sets a boolean indicating that the metrics collection should > not take place. In the process(), the code checks the boolean to determine if > it should proceed. > The Camel driven timer is eventually stopped in a code handling process > termination. -- This message was sent by Atlassian Jira (v8.20.10#820010)
