[jboss-jira] [JBoss JIRA] (WFLY-547) Track "uncleanly unregistered" hosts on the master HC; expose via management API

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978189#comment-12978189 ] 

Brian Stansberry edited comment on WFLY-547 at 6/20/14 10:44 AM:
-----------------------------------------------------------------

EAP NOTE: The code in pull request 5681 cannot be backported to EAP 6 as it makes a minor change to the ResourceProvider interface, and to the AbstractModelResource class, which is visible to subsystems. So it is not acceptable for use prior to the next major EAP release.

Not that I expect this to be backported; this note is just precautionary. 


was (Author: brian.stansberry):
EAP NOTE: The code in pull request 5681 cannot be backported to EAP 6 as it makes a minor change to the ResourceProvider interface, which is visible to subsystems via the AbstractModelResource class. So it is not acceptable for use prior to the next major EAP release.

Not that I expect this to be backported; this note is just precautionary. 

> Track "uncleanly unregistered" hosts on the master HC; expose via management API
> --------------------------------------------------------------------------------
>
>                 Key: WFLY-547
>                 URL: https://issues.jboss.org/browse/WFLY-547
>             Project: WildFly
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Domain Management
>            Reporter: Brian Stansberry
>            Assignee: Emanuel Muckenhuber
>             Fix For: 9.0.0.CR1
>
>
> When the master HC detects that a slave HC is no longer available but hasn't properly unregistered, the slave should still be visible in the management API but with some sort of status indicator.
> The slave should probably not remaining in the regular management tree, since that will encourage clients to invoke operations that will just fail, but it's existence and "unknown" status should be reflected in some manner accessible to management clients who wish to obtain a more complete view of the domain topology.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)