Burn Lewis created UIMA-5340:
Summary: Provide an example of a service registry for custom
services
Key: UIMA-5340
URL: https://issues.apache.org/jira/browse/UIMA-5340
Project: UIMA
Issue Type:
[
https://issues.apache.org/jira/browse/UIMA-5330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis updated UIMA-5330:
-
Fix Version/s: (was: future-DUCC)
2.2.1-Ducc
> Custom pinger may fail if classpath
[
https://issues.apache.org/jira/browse/UIMA-5330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis resolved UIMA-5330.
--
Resolution: Fixed
Put sm & common & cli jars at head of custom pinger's classpath
> Custom pinger may
Burn Lewis created UIMA-5330:
Summary: Custom pinger may fail if classpath has old DUCC jars
Key: UIMA-5330
URL: https://issues.apache.org/jira/browse/UIMA-5330
Project: UIMA
Issue Type: Bug
Burn Lewis created UIMA-5329:
Summary: 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:
Burn Lewis created UIMA-5328:
Summary: DUCC should set DUCC_UMASK for all submitted work (if not
already set)
Key: UIMA-5328
URL: https://issues.apache.org/jira/browse/UIMA-5328
Project: UIMA
Burn Lewis created UIMA-5313:
Summary: 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
[
https://issues.apache.org/jira/browse/UIMA-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis reassigned UIMA-5058:
Assignee: Marshall Schor (was: Burn Lewis)
Ready for 3.0
> Scaled out pipelines can falsely
[
https://issues.apache.org/jira/browse/UIMA-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15858048#comment-15858048
]
Burn Lewis commented on UIMA-5274:
--
Fixed problem of not clearing context. Changed all cases to save &
[
https://issues.apache.org/jira/browse/UIMA-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis reassigned UIMA-5274:
Assignee: Marshall Schor (was: Burn Lewis)
Code in trunk, ready to be moved to 3.0
> Support
[
https://issues.apache.org/jira/browse/UIMA-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15850440#comment-15850440
]
Burn Lewis commented on UIMA-5274:
--
Since the envVarRef element is actually allowed in many more places
[
https://issues.apache.org/jira/browse/UIMA-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15850440#comment-15850440
]
Burn Lewis edited comment on UIMA-5274 at 2/2/17 8:31 PM:
--
Since the envVarRef
[
https://issues.apache.org/jira/browse/UIMA-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on UIMA-5274 started by Burn Lewis.
> Support descriptor customization by allowing external setting variables in
> some
[
https://issues.apache.org/jira/browse/UIMA-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis updated UIMA-5274:
-
Description:
Currently the element supports customization via system properties
in 4 ways (see below).
[
https://issues.apache.org/jira/browse/UIMA-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis resolved UIMA-5282.
--
Resolution: Fixed
start_sim now adds the virtual IP address to the cmd line so the duplicate
daemon
Burn Lewis created UIMA-5282:
Summary: DUCC simulator fails to start multiple virtual agents on
a node
Key: UIMA-5282
URL: https://issues.apache.org/jira/browse/UIMA-5282
Project: UIMA
Issue
[
https://issues.apache.org/jira/browse/UIMA-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis closed UIMA-5227.
Resolution: Fixed
Code was in RC2 but its Jira was wrongly marked
> Customized user logging fails in DUCC
[
https://issues.apache.org/jira/browse/UIMA-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis updated UIMA-5227:
-
Fix Version/s: (was: future-DUCC)
2.2.0-Ducc
> Customized user logging fails in
[
https://issues.apache.org/jira/browse/UIMA-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis resolved UIMA-5277.
--
Resolution: Fixed
> start/stop_ducc scripts should check for unwanted args
>
[
https://issues.apache.org/jira/browse/UIMA-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis updated UIMA-5277:
-
Fix Version/s: (was: future-DUCC)
2.2.0-Ducc
> start/stop_ducc scripts should check
Burn Lewis created UIMA-5274:
Summary: Support descriptor customization by allowing external
setting variables in some fields
Key: UIMA-5274
URL: https://issues.apache.org/jira/browse/UIMA-5274
Project:
[
https://issues.apache.org/jira/browse/UIMA-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis closed UIMA-5208.
Reference doc updated. Added Junit tests as part of UIMA-5273
> Also search the classpath and datapath when
[
https://issues.apache.org/jira/browse/UIMA-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis resolved UIMA-5273.
--
Resolution: Fixed
Lookup now fails if circular references are found. Added simple Junit test.
> Check
[
https://issues.apache.org/jira/browse/UIMA-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis updated UIMA-5273:
-
Fix Version/s: (was: 3.0.0)
3.0.0SDK-alpha
> Check for circular definitions in
Burn Lewis created UIMA-5273:
Summary: Check for circular definitions in external override
settings
Key: UIMA-5273
URL: https://issues.apache.org/jira/browse/UIMA-5273
Project: UIMA
Issue Type:
Burn Lewis created UIMA-5268:
Summary: 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
[
https://issues.apache.org/jira/browse/UIMA-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis closed UIMA-5244.
> SM sometimes keeps starting failing instances forever
> -
[
https://issues.apache.org/jira/browse/UIMA-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis resolved UIMA-5244.
--
Resolution: Fixed
Backed out check for disabled as when restarting a service after a full bounce
the SM
[
https://issues.apache.org/jira/browse/UIMA-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis reopened UIMA-5244:
--
For complex reasons this fix exposes a problem in restarting services when DUCC
is bounced. Some
Burn Lewis created UIMA-5263:
Summary: Improve DUCC's handling of deprecated properties
Key: UIMA-5263
URL: https://issues.apache.org/jira/browse/UIMA-5263
Project: UIMA
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/UIMA-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis closed UIMA-5244.
> SM sometimes keeps starting failing instances forever
> -
[
https://issues.apache.org/jira/browse/UIMA-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis resolved UIMA-5244.
--
Resolution: Fixed
Changing the registered instances to 1 does not change the original target
instance
[
https://issues.apache.org/jira/browse/UIMA-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis updated UIMA-5244:
-
Fix Version/s: (was: future-DUCC)
2.2.0-Ducc
Added check of disabled to the check
Burn Lewis created UIMA-5246:
Summary: Serialize re-registration of DUCC services to reduce
chance of duplicate services
Key: UIMA-5246
URL: https://issues.apache.org/jira/browse/UIMA-5246
Project: UIMA
[
https://issues.apache.org/jira/browse/UIMA-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816189#comment-15816189
]
Burn Lewis commented on UIMA-5221:
--
We could also use an additive logger that captures just warning and
[
https://issues.apache.org/jira/browse/UIMA-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15806062#comment-15806062
]
Burn Lewis commented on UIMA-5244:
--
Changing the number of instances to 1 didn't stop it. That changed
Burn Lewis created UIMA-5244:
Summary: SM sometimes keeps starting failing instances forever
Key: UIMA-5244
URL: https://issues.apache.org/jira/browse/UIMA-5244
Project: UIMA
Issue Type: Bug
[
https://issues.apache.org/jira/browse/UIMA-5059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis closed UIMA-5059.
> DUCC WS should compile jsps into $DUCC_HOME/tmp/ducc/jsp
>
[
https://issues.apache.org/jira/browse/UIMA-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis closed UIMA-5086.
> DUCC should consider slightly larger machines when reserving a whole machine
>
[
https://issues.apache.org/jira/browse/UIMA-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis closed UIMA-5150.
Attempts to start a duplicate daemon (with ducc.py) now fail.
> Duplicate agents (or daemons) MUST be avoided
>
[
https://issues.apache.org/jira/browse/UIMA-5170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis closed UIMA-5170.
> When pages have "no data" indicate if because not logged in or data missing
>
[
https://issues.apache.org/jira/browse/UIMA-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis closed UIMA-5182.
> ducc-mon should hide/show other large values when displaying Job, AP, or
> Service specifications
>
[
https://issues.apache.org/jira/browse/UIMA-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis closed UIMA-5145.
> DUCC attempts to run even if the DB doesn't start
> -
>
>
[
https://issues.apache.org/jira/browse/UIMA-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis updated UIMA-5150:
-
Fix Version/s: (was: future-DUCC)
2.2.0-Ducc
> Duplicate agents (or daemons) MUST
[
https://issues.apache.org/jira/browse/UIMA-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis updated UIMA-5221:
-
Description:
Original description was a partial duplicate of 5150.
If don't ssh to localhost then could
[
https://issues.apache.org/jira/browse/UIMA-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15798597#comment-15798597
]
Burn Lewis commented on UIMA-5150:
--
When checking for an already-running agent the code (unnecessarily)
[
https://issues.apache.org/jira/browse/UIMA-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15798590#comment-15798590
]
Burn Lewis commented on UIMA-5150:
--
Consensus is #3 ... agent should use ps to verify that it is the only
[
https://issues.apache.org/jira/browse/UIMA-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15768906#comment-15768906
]
Burn Lewis commented on UIMA-5227:
--
The problem was not the ToLog class - apparently the java logging
[
https://issues.apache.org/jira/browse/UIMA-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on UIMA-5227 started by Burn Lewis.
> Customized user logging fails in DUCC Job Driver
>
[
https://issues.apache.org/jira/browse/UIMA-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis reassigned UIMA-5227:
Assignee: Burn Lewis
> Customized user logging fails in DUCC Job Driver
>
[
https://issues.apache.org/jira/browse/UIMA-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis resolved UIMA-5182.
--
Resolution: Fixed
Format classpath. jvm-args & environment entries & add hide/show button if
large.
>
[
https://issues.apache.org/jira/browse/UIMA-5170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis resolved UIMA-5170.
--
Resolution: Fixed
Indicate if data missing or perhaps unreadable if not logged in
> When pages have "no
[
https://issues.apache.org/jira/browse/UIMA-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis updated UIMA-5209:
-
Fix Version/s: (was: 2.2.0-Ducc)
future-DUCC
Needs investigation
> Some external
[
https://issues.apache.org/jira/browse/UIMA-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis updated UIMA-5227:
-
Fix Version/s: (was: 2.2.0-Ducc)
future-DUCC
> Customized user logging fails in
Burn Lewis created UIMA-5227:
Summary: Customized user logging fails in DUCC Job Driver
Key: UIMA-5227
URL: https://issues.apache.org/jira/browse/UIMA-5227
Project: UIMA
Issue Type: Bug
[
https://issues.apache.org/jira/browse/UIMA-5183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis resolved UIMA-5183.
--
Resolution: Fixed
Use a node-specific configuration file if it exists, e.g. use
[
https://issues.apache.org/jira/browse/UIMA-5183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis closed UIMA-5183.
> Support "fenced-off" worker nodes with read-only access to DUCC_HOME
>
[
https://issues.apache.org/jira/browse/UIMA-5190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis updated UIMA-5190:
-
Fix Version/s: (was: 2.2.0-Ducc)
future-DUCC
> DUCC's RM logs too much
>
Burn Lewis created UIMA-5221:
Summary: DUCC start script should not start duplicate agents
Key: UIMA-5221
URL: https://issues.apache.org/jira/browse/UIMA-5221
Project: UIMA
Issue Type: Bug
[
https://issues.apache.org/jira/browse/UIMA-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis reopened UIMA-5208:
--
Must update docs
> Also search the classpath and datapath when loading an extenal overrides file
>
[
https://issues.apache.org/jira/browse/UIMA-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis updated UIMA-5208:
-
Fix Version/s: 3.0.0SDKexp
> Also search the classpath and datapath when loading an extenal overrides file
Burn Lewis created UIMA-5214:
Summary: 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
[
https://issues.apache.org/jira/browse/UIMA-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis resolved UIMA-5208.
--
Resolution: Fixed
Use the RelativePathResolver to load from the datapath or classpath if the
settings
[
https://issues.apache.org/jira/browse/UIMA-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis closed UIMA-5208.
> Also search the classpath and datapath when loading an extenal overrides file
>
[
https://issues.apache.org/jira/browse/UIMA-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis updated UIMA-5177:
-
Summary: NPEs occur if Saxon is in the classpath (was: NPEs occur if
Saxon9 is in the classpath)
> NPEs
[
https://issues.apache.org/jira/browse/UIMA-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15738871#comment-15738871
]
Burn Lewis commented on UIMA-5177:
--
No, quite similar to my results on Linux ... I saw the first (which is
[
https://issues.apache.org/jira/browse/UIMA-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis closed UIMA-5177.
> NPEs occur if Saxon9 is in the classpath
>
>
> Key:
[
https://issues.apache.org/jira/browse/UIMA-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis closed UIMA-4856.
Also provided an unsecure configuration for ducc-sim as it uses the DUCC broker
as an application broker.
>
[
https://issues.apache.org/jira/browse/UIMA-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis resolved UIMA-4856.
--
Resolution: Fixed
Assignee: Burn Lewis
Modified broker configuration
> DUCC broker should be
[
https://issues.apache.org/jira/browse/UIMA-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis updated UIMA-4856:
-
Fix Version/s: (was: future-DUCC)
2.2.0-Ducc
> DUCC broker should be restricted to
Burn Lewis created UIMA-5199:
Summary: UIMA-AS should check for a core UIMA version no older
than it
Key: UIMA-5199
URL: https://issues.apache.org/jira/browse/UIMA-5199
Project: UIMA
Issue
[
https://issues.apache.org/jira/browse/UIMA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis closed UIMA-5117.
> UIMA-AS: dd2spring should log at INFO
> -
>
> Key:
[
https://issues.apache.org/jira/browse/UIMA-5126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis closed UIMA-5126.
> UIMA-AS thows an NPE if saxon9he.jar is in the classpath
>
Burn Lewis created UIMA-5190:
Summary: 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
Burn Lewis created UIMA-5183:
Summary: Support "fenced-off" worker nodes with read-only access
to DUCC_HOME
Key: UIMA-5183
URL: https://issues.apache.org/jira/browse/UIMA-5183
Project: UIMA
Burn Lewis created UIMA-5182:
Summary: ducc-mon should hide/show other large values when
displaying Job, AP, or Service specifications
Key: UIMA-5182
URL: https://issues.apache.org/jira/browse/UIMA-5182
[
https://issues.apache.org/jira/browse/UIMA-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15654175#comment-15654175
]
Burn Lewis commented on UIMA-5177:
--
Spec says that the the startElement arguments localName and qName can
[
https://issues.apache.org/jira/browse/UIMA-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on UIMA-5177 started by Burn Lewis.
> NPEs occur if Saxon9 is in the classpath
>
>
>
Burn Lewis created UIMA-5177:
Summary: NPEs occur if Saxon9 is in the classpath
Key: UIMA-5177
URL: https://issues.apache.org/jira/browse/UIMA-5177
Project: UIMA
Issue Type: Bug
[
https://issues.apache.org/jira/browse/UIMA-5170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis updated UIMA-5170:
-
Summary: When pages have "no data" indicate if because not logged in or
data missing (was: Improve
Burn Lewis created UIMA-5170:
Summary: Improve handling of Experiments and other pages when not
logged in
Key: UIMA-5170
URL: https://issues.apache.org/jira/browse/UIMA-5170
Project: UIMA
Issue
Burn Lewis created UIMA-5152:
Summary: DUCC may let a JP grab some WIs if pre-empted just as
initilization completes
Key: UIMA-5152
URL: https://issues.apache.org/jira/browse/UIMA-5152
Project: UIMA
Burn Lewis created UIMA-5150:
Summary: Duplicate agents (or daemons) MUST be avoided
Key: UIMA-5150
URL: https://issues.apache.org/jira/browse/UIMA-5150
Project: UIMA
Issue Type: Bug
Burn Lewis created UIMA-5146:
Summary: Multiple pipelines need to share just the resources in a
ResourceManager
Key: UIMA-5146
URL: https://issues.apache.org/jira/browse/UIMA-5146
Project: UIMA
[
https://issues.apache.org/jira/browse/UIMA-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis closed UIMA-4837.
> When a nodepool is empty a job will just say WaitingForResources
>
[
https://issues.apache.org/jira/browse/UIMA-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis updated UIMA-5075:
-
Fix Version/s: (was: future-DUCC)
2.2.0-Ducc
> DUCC should check that it runs with
[
https://issues.apache.org/jira/browse/UIMA-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis closed UIMA-5075.
> DUCC should check that it runs with the uid of the installer
>
[
https://issues.apache.org/jira/browse/UIMA-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis closed UIMA-5080.
> DUCC uses UIMA-AS's dd2spring.xsl file which generates an obsolete dtd
>
[
https://issues.apache.org/jira/browse/UIMA-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis updated UIMA-5080:
-
Fix Version/s: (was: future-DUCC)
2.2.0-Ducc
> DUCC uses UIMA-AS's dd2spring.xsl
[
https://issues.apache.org/jira/browse/UIMA-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis updated UIMA-5124:
-
Summary: DUCC-MON doesn't display the Reason for WaitingForResources for
jobs (was: DUCC-MON doesn'y
[
https://issues.apache.org/jira/browse/UIMA-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis reopened UIMA-5124:
--
> DUCC-MON doesn'y display the Reason for WaitingForResources for jobs
>
[
https://issues.apache.org/jira/browse/UIMA-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis closed UIMA-5124.
Resolution: Fixed
> DUCC-MON doesn't display the Reason for WaitingForResources for jobs
>
[
https://issues.apache.org/jira/browse/UIMA-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis updated UIMA-5124:
-
Fix Version/s: (was: future-DUCC)
2.2.0-Ducc
> DUCC-MON doesn'y display the Reason
[
https://issues.apache.org/jira/browse/UIMA-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis reopened UIMA-5124:
--
> DUCC-MON doesn'y display the Reason for WaitingForResources for jobs
>
[
https://issues.apache.org/jira/browse/UIMA-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis closed UIMA-5124.
Resolution: Fixed
> DUCC-MON doesn'y display the Reason for WaitingForResources for jobs
>
[
https://issues.apache.org/jira/browse/UIMA-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis resolved UIMA-5145.
--
Resolution: Fixed
If start_ducc fails to connect to the DB don't start other daemons. DB may be
Burn Lewis created UIMA-5145:
Summary: DUCC attempts to run even if the DB doesn't start
Key: UIMA-5145
URL: https://issues.apache.org/jira/browse/UIMA-5145
Project: UIMA
Issue Type: Bug
[
https://issues.apache.org/jira/browse/UIMA-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis updated UIMA-5086:
-
Fix Version/s: (was: future-DUCC)
2.2.0-Ducc
> DUCC should consider slightly larger
[
https://issues.apache.org/jira/browse/UIMA-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis resolved UIMA-5086.
--
Resolution: Fixed
After rounding up a reserve request consider machines up to
ducc.rm.reserve_overage
[
https://issues.apache.org/jira/browse/UIMA-5126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1812#comment-1812
]
Burn Lewis edited comment on UIMA-5126 at 10/7/16 6:12 PM:
---
Problem starts with:
201 - 300 of 918 matches
Mail list logo