[
https://issues.apache.org/jira/browse/AURORA-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237371#comment-15237371
]
John Sirois commented on AURORA-1534:
-------------------------------------
The official schema for server sets:
https://github.com/apache/aurora/blob/master/commons/src/main/thrift/org/apache/aurora/common/thrift/endpoint.thrift#L89
https://github.com/twitter/commons/blob/master/src/thrift/com/twitter/thrift/endpoint.thrift#L114
In both cases shard is in fact marked optional, so tolerance seems to be the
correct client behavior anyhow.
[~paulcavallaro] - I'm going to mark this as won't fix, but feel free to
re-open if you have more input on this.
> Announce Aurora with the Same JSON as Aurora Jobs
> -------------------------------------------------
>
> Key: AURORA-1534
> URL: https://issues.apache.org/jira/browse/AURORA-1534
> Project: Aurora
> Issue Type: Task
> Affects Versions: 0.9.0
> Reporter: Paul Cavallaro
> Assignee: John Sirois
> Priority: Minor
>
> Currently Aurora announce itself under /aurora/services in ZooKeeper, but the
> JSON it writes is not the same as the normal Aurora Jobs being announced.
> Namely it does not include a 'shard' key:value.
> Having it be the same, is useful for reusing code that watches Aurora Jobs to
> be able to use to watch the Aurora Leader (for accessing the HTTP API, Thrift
> API, etc.).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
