[
https://issues.apache.org/jira/browse/SLIDER-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066100#comment-14066100
]
Sumit Mohanty commented on SLIDER-239:
--------------------------------------
A number of services such as memcached, data stores have a single component
type with all components being peers. In this case, all instances of a
component may need to advertise some data about themselves. Currently, Slider
only supports advertising data based on applied config. With applied config, if
some field (e.g. port) is different for each instance then the data needs to be
advertised separately for each component instance.
Proposal:
Components can explicitly define what they want to publish. These information
should be scoped to the life time of the component instance. After the
component instance is STARTED, it can publish any data - from applied
configuration, host name, etc. Slider app master should automatically purge the
data if the component instance is no longer active.
> Component instances should be able to advertise associated ports
> ----------------------------------------------------------------
>
> Key: SLIDER-239
> URL: https://issues.apache.org/jira/browse/SLIDER-239
> Project: Slider
> Issue Type: Wish
> Reporter: Rui Zhang
> Assignee: Sumit Mohanty
> Labels: port
>
> Some applications such as Databases(especially for databases that all nodes
> are of the same role and can all be connected) need to know the port number
> they are listening, so that DBAs and clients can manage the databases better.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
