Re: [Breaking Change, MESOS-1865] Redirect to the leader master when current master is not a leader

Oh, @Marco. Thank you very much for your reply, vinodkone shepherd this and it have already submitted after other kindly guys reviews. For MESOS-3841, it should be resolved now because could get the leading master by "/redirect" endpoint. Do you have any concerns about it? I would like to solve

Re: DC/OS dynamic reservation dosen't work

Sorry for make you confusing before. The offer looks match resource requirement according to your log, let me reproduce it first. On Sun, May 1, 2016 at 8:57 AM, Guangya Liu wrote: > Gaojin, > > Some questions and suggestions here: > > 1) How did you deploy the nginx with

Re: [Breaking Change, MESOS-1865] Redirect to the leader master when current master is not a leader

@haosdent - thanks for doing this, very useful indeed! On a related issue [0], I'd like to that one on: - can anyone comment if that's a good idea/bad idea; and - would anyone be willing to shepherd it? Thanks! [0] Master HTTP API support to get the leader (

Re: DC/OS dynamic reservation dosen't work

Gaojin, Some questions and suggestions here: 1) How did you deploy the nginx with new marathon URI? I did not found that I can configure the new marathon URI with nginx. 2) Can you please send out the curl output for your master node: a) curl "http://master-ip:5050/master/slaves

Re: DC/OS dynamic reservation dosen't work

dear Haosdent, > Why you send reserve request to http://10.132.46.81:5050/unreserve > , is it should be > "http://10.132.46.81:5050/reserve ”? my bad; actually i use http://10.132.46.81:5050/reserve for reservation, and

Re: DC/OS dynamic reservation dosen't work

And why you add ``` "reservation": {} ``` in the resource define? Which role you used when start Marathon? On Sun, May 1, 2016 at 2:28 AM, haosdent wrote: > Why you send reserve request to http://10.132.46.81:5050/unreserve, is it > should be

Re: DC/OS dynamic reservation dosen't work

Why you send reserve request to http://10.132.46.81:5050/unreserve, is it should be "http://10.132.46.81:5050/reserve;? On Sun, May 1, 2016 at 1:59 AM, caogaojin wrote: > Anyone has such experiences? I think it may be a dynamic reservation > issue. > In my

Re: DC/OS dynamic reservation dosen't work

Anyone has such experiences? I think it may be a dynamic reservation issue. In my situation, i turn off mesos authentication mechanism, will this be a problem? GaoJin CAO ChinaMobile(Suzhou) R Phone：18896723732 Mail：caogaojin at cmss.chinamobile.com > On May 1,

DC/OS dynamic reservation dosen't work

Hi list, I’m currently using dynamic reservation mechanism with mesosphere/DCOS 1.7, the opensourced version, and something wired just happened. I tried to setup a new marathon service from the universe repo, and i did a slight modification, setting mesos_role to `dev`. i also turned off

Re: Detecting resource issues

Hi, I will raise it over there as well, but it's also a mesos question - I'd like to detect this sort of issue, and it seems like it should be possible. I'm just looking to see if anyone has already done this and can point me in the right direction. Ultimately, we are going to be running