If you want to see which slaves are in the SCHEDULED state, please take a look at the /maintenance endpoint.
On Mon, Dec 15, 2014 at 3:39 PM, Alexius Ludeman <l...@lexinator.com> wrote: > > thanks for quick response. > > I'm trying to determine which slaves are in "SCHEDULED" mode which only > appears on /slaves. > > Noted on separate zookeepers. > > thanks > > On Mon, Dec 15, 2014 at 3:19 PM, Zameer Manji <zma...@twopensource.com> > wrote: > > > > The output of /slaves is not in a machine readable format. I believe > there > > is a ticket somewhere that tracks changing it into a JSON endpoint. I'm > not > > sure if there is another endpoint which can easily give you every slave > > that Aurora uses. Have you looked into what the Mesos master can give you > > here? > > > > For using the ServerSet announcer I believe the best practice is to have > > Aurora+Mesos zk cluster and the service discovery zk cluster be separate. > > However, if your cluster is relatively small it might be easier to just > put > > everything on one zk cluster. > > > > On Mon, Dec 15, 2014 at 1:07 PM, Alexius Ludeman <l...@lexinator.com> > > wrote: > > > > > > hiya, > > > > > > is it possible to have scheduler (http://localhost:8081/slaves) render > > in > > > something non-html(?format=json)? or alternately, is there a way to > get a > > > list of slave names from /apibeta? > > > > > > I'm looking to start using ServerSet Annoucer. what is the recommended > > > practice for which zookeepers to use? should I use the same ones for > > > aurora+mesos? or a separate set for this service? > > > > > > thanks in advance. > > > > > > > > > -- > > Zameer Manji > > > -- Zameer Manji
