uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eddie Epstein (JIRA)" <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-3682) DUCC WebServer (WS) Services Page reorganization
Date Mon, 28 Apr 2014 22:21:15 GMT

    [ https://issues.apache.org/jira/browse/UIMA-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983669#comment-13983669
] 

Eddie Epstein commented on UIMA-3682:
-------------------------------------

1. 
   Since Type is now always registered, good plan to remove the column
   Folding Pinger [pinger state] and health into State sounds good

2. 
   What is Reason supposed to contain?
   For State
      (a) thru (d) look good.
      (e) no longer necessary becase of new 'Last Use' column
      'Error' is also an existing State which needs to be retained

Also, with the latest changes allowing pingers to dynamically manage number of service instances,
the meaning of Instances column becomes "Number of instances when service is started, and
lower limit that pinger can reduce to."

> DUCC WebServer (WS) Services Page reorganization
> ------------------------------------------------
>
>                 Key: UIMA-3682
>                 URL: https://issues.apache.org/jira/browse/UIMA-3682
>             Project: UIMA
>          Issue Type: Improvement
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>             Fix For: 2.0.0-Ducc
>
>
> Rationalization: 
> Currently the Services Page displayed by the WebServer is transparent, showing "raw"
data that is not as clear in meaning as it could be.
> Proposed:
> 1. Remove columns: Type, State, Pinger, Health as currently implemented
> 2. Add Columns: State, Reason
> (a) Unknown, Pinger down
> (b) Down, Pinger reporting		
> (c) Poor, Pinger reporting 
> (d) Good, Pinger reporting
> (e) Idle, ddd:hh:mm:ss since last use
> Notes:
> 1. For (c) and (d) hover over state shows pinger provided status string, as before
> 2. For (e) decision to display Idle over Good or Poor is based on time of last use as
reported by pinger and a ducc.service.idle.time.threshold <time-in-millis> specified
in ducc.properties (or registry for that service?) with default value of 24 hours.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message