You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2014/05/21 11:10:37 UTC

[jira] [Commented] (SLIDER-97) When an app does publishing of configs/URLs should be configurable

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

Steve Loughran commented on SLIDER-97:
--------------------------------------

SLIDER-35 is doing the work for providers to add more service types; the tests for this are the hbase provider registering its hbase-site.xml, *under a different service name*. 

that is, instead of {{org.apache.slider/$name}}, its also registering {{org.apache.hbase/$name}} with the set of published documents being {{hbase-site.xml}}

this is done in the provider's {{serviceStart()}} method -not at the time the original slider service is registered

> When an app does publishing of configs/URLs should be configurable
> ------------------------------------------------------------------
>
>                 Key: SLIDER-97
>                 URL: https://issues.apache.org/jira/browse/SLIDER-97
>             Project: Slider
>          Issue Type: Bug
>          Components: agent-provider
>    Affects Versions: Slider 0.30
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: Slider 0.30
>
>
> Currently, when the MASTER component comes up it publishes the applied config and any URLs that the application wishes to publish. Slider should make it configurable as to when the application should publish its configuration as its not necessary that when the MASTER is up all artifacts for publication are known. For example, some application may have a monitoring endpoint hosted outside the master which relies on the master to be up first.
> This limitation could still be documented for Slider-0.30 but its a good capability to have.



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