[
https://issues.apache.org/jira/browse/UIMA-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646825#comment-13646825
]
Lou DeGenaro commented on UIMA-2854:
------------------------------------
1. Add optional .debug to each class definition that is effective only when
policy is FAIR_SHARE and submitted Job is process_debug or all_in_one. The
value indicates the name of the substitute class to be used. Example:
scheduling.class.background.policy = FAIR_SHARE
scheduling.class.background.share_weight = 1
scheduling.class.background.priority = 10
scheduling.class.background.cap = 0
scheduling.class.background.debug = debug
#
# used for debug and all-in-one
#
scheduling.class.debug.policy = FIXED_SHARE
scheduling.class.debug.share_weight = 1
scheduling.class.debug.priority = 9
scheduling.class.debug.cap = 0
scheduling.class.debug.debug = irrelevant
2. Allow for a global default, in cases where a FAIR_SHARE class does not
specify a specific debugging class. Example:
#
# class to use when debug or all-in-one is specified
# and .debug is absent from fair_share class
#
scheduling.default.name.debug = debug
3. Instrument JobSubmit to make class substitution if/when specified in .class
definitions file.
4. Display Debug classes on WS System Classes page, where brackets [debug]
indicate that the default debugging class will be used.
> DUCC command line interface (CLI) should choose an appropriate "fixed" class
> for submission when all-in-one or debug flag is specified
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: UIMA-2854
> URL: https://issues.apache.org/jira/browse/UIMA-2854
> Project: UIMA
> Issue Type: Improvement
> Reporter: Lou DeGenaro
> Assignee: Lou DeGenaro
> Priority: Minor
>
> There should be an "automatic" mapping from a preempt-type class to a
> corresponding fixed-type class so that all-in-one and debug jobs are not
> interrupted by the scheduler.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
