You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "John Sirois (JIRA)" <ji...@apache.org> on 2016/04/12 17:27:25 UTC

[jira] [Resolved] (AURORA-1534) Announce Aurora with the Same JSON as Aurora Jobs

     [ https://issues.apache.org/jira/browse/AURORA-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Sirois resolved AURORA-1534.
---------------------------------
    Resolution: Won't Fix

The JSON used by the scheduler today is the same JSON it uses to announce clients, the shard field is optional in the server-set schema; so clients should handle a missing shard field gracefully.

> 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)