[
https://issues.apache.org/jira/browse/UIMA-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922739#comment-15922739
]
Lou DeGenaro commented on UIMA-4883:
------------------------------------
> System Events logging is to file $DUCC_HOME/logs/system-events.log, as
> configured in $DUCC_HOME/resources/log4j.xml
> System event logging is carried out by Orchestrator only
> DuccLogger class is copied to orchestrator and modified to handle alternate
> logging paramaterized methods
> SystemEventsLogger class interfaces to revised DuccLogger.class
> The following events are thus far logged via SystemEventsLogger: { Job,
> Reservation, Service } + { Submit, Cancel, End }, and Orchestrator { Boot,
> Shutdown }
> The following EventTypes are new: { BOOT, SHUTDOWN, END_OF_JOB,
> END_OF_RESERVATION, END_OF_SERVICE }
> DUCC system events log
> ----------------------
>
> Key: UIMA-4883
> URL: https://issues.apache.org/jira/browse/UIMA-4883
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
> Reporter: Lou DeGenaro
> Assignee: Lou DeGenaro
> Fix For: future-DUCC
>
>
> DUCC should keep a system-wide events log to record for example:
> 1. OR/SM/RM requests/replys
> 2. Job/AP/Service start/end
> 3. Node up/down determination
> 4. Monitor cancellations
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
