[
https://issues.apache.org/jira/browse/AURORA-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237173#comment-15237173
]
John Sirois commented on AURORA-1534:
-------------------------------------
Nope, they also do not populate shard. The difficulty is picking one. We'd
need to force something like zk's myid in deploys that gave each scheduler in a
cluster it's own unique shard ID, say 0, 1, 2.
It seems to me it would make more sense for clients to simply be tolerant of
shard being optional.
> 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: Bill Farner
> 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)
