[
https://issues.apache.org/jira/browse/TWILL-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200091#comment-14200091
]
Steve Loughran commented on TWILL-107:
--------------------------------------
# we use one node per service, with each endpoint listed in the
internal/exported lists (idea taken from Helix)
# this gives us a view of a service as a whole, being able to go from one of
its exported services to an adjacent one
# individual components can also register themselves (JMX ports, etc)
# Not using ephemeral nodes as it is (a) brittle against connection loss and
(b) won't work over our planned REST API. We have some tie-in to yarn
container, attempt and app lifespans, with the YARN RM triggering cleanup
operations.
# you can stick extra k:v pairs into the JSON, they just get ignored.
Recommendation is to prefix them, to get attributes like {{twill:auth}} and
{{twill:owner}}
> Support payloads for Discoverables
> ----------------------------------
>
> Key: TWILL-107
> URL: https://issues.apache.org/jira/browse/TWILL-107
> Project: Apache Twill
> Issue Type: Improvement
> Components: discovery
> Reporter: Parth Gandhi
> Fix For: 0.5.0-incubating
>
>
> Discoverables store only a name and an InetSocketAddress. It would help
> extensibility to allow an arbitrary payload of bytes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
