[
https://issues.apache.org/jira/browse/UIMA-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15267230#comment-15267230
]
Lou DeGenaro commented on UIMA-4829:
------------------------------------
Revised.
The pinger is "hung" whenever the interval (ducc.sm.meta.ping.stability *
ducc.sm.meta.ping.rate) is exceeded without updated pinger data. In this case,
set ping_active to false. The Web Server (WS) Services page will display
Available+Alert, with hover "Pinger is not active".
TODO:
Change state to something other than Available, perhaps NotAvailable, so as to
cause the Resource manager (RM) to not dispatch new work with dependency on
said Service.
> When a DUCC pinger hangs it is reported as Available
> ----------------------------------------------------
>
> Key: UIMA-4829
> URL: https://issues.apache.org/jira/browse/UIMA-4829
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
> Reporter: Burn Lewis
> Assignee: Lou DeGenaro
> Priority: Minor
> Fix For: 2.1.0-Ducc
>
>
> The DUCC pinger can hang and the main evidence is the stale ping statistics.
> The SM should mark it as unavailable and indicate that pinger is active but
> not responding.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
