Mesos/Marathon is not update docker image.

I have Mesos cluster consists of 9 Ubuntu 14.04 machines on cloud environment. ZooKeeper and Mesos-Master is running on 3 machines and Mesos-Slave is running on 6 machines. Also, Marathon is running on master node. Docker registry is private resistry. I am trying to deploy this container via Ma

Marathon is not update docker image.

I have Mesos cluster consists of 9 Ubuntu 14.04 machines on cloud environment. ZooKeeper and Mesos-Master is running on 3 machines and Mesos-Slave is running on 6 machines. Also, Marathon is running on master node. Docker registry is private resistry. I am trying to deploy this container via Ma

Marathon is not update docker image.

I have Mesos cluster consists of 9 Ubuntu 14.04 machines on cloud environment. ZooKeeper and Mesos-Master is running on 3 machines and Mesos-Slave is running on 6 machines. Also, Marathon is running on master node. Docker registry is private resistry. I am trying to deploy this container via Ma

Marathon is not update docker image.

I have Mesos cluster consists of 9 Ubuntu 14.04 machines on cloud environment. ZooKeeper and Mesos-Master is running on 3 machines and Mesos-Slave is running on 6 machines. Also, Marathon is running on master node. Docker registry is private resistry. I am trying to deploy this container via Ma

MesosCon Seattle 2015 Keynote Speakers Announced

The countdown until #MesosCon has begun: 7 weeks until MesosCon! MesosCon is an annual conference organized by the Apache Mesos community, bringing together users and developers to share and learn about the project and its growing ecosystem. Register now[1] and join us in Seattle this August! Her

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

+1 As an API writer (and consumer), this behavior makes sense, and most clients (notably, Apache HttpClient) would be able to handle this transparently (I think - it's been a few years since I messed with it :) I completely agree that returning a 200 OK with empty (or, worse, stale) data would be

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

Oh, I got it. I would discuss document this with @adam. Thank you for your great advice. On Thu, Jul 2, 2015 at 12:33 AM, James DeFelice wrote: > Sure, that makes sense. I guess I was wondering if we should document a > recommended retry-limit threshold for people writing clients - along with a

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

Sure, that makes sense. I guess I was wondering if we should document a recommended retry-limit threshold for people writing clients - along with a recommended approach for backing off before retrying again. On Wed, Jul 1, 2015 at 12:29 PM, haosdent wrote: > Hi, @James Thank you very much for yo

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

Hi, @James Thank you very much for your good question. My current patch could not avoid this problem. I think you could handle this in client side, give it up or return error when redirect times overflow your define limit. On Thu, Jul 2, 2015 at 12:23 AM, James DeFelice wrote: > In a cluster tha

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

In a cluster that's having network problems and the selected leader is "flapping" is there an upper limit on how many subsequent redirects a client may expect to receive before it should give up for some period of time? For example: client requests /tasks.json from master1 master1 sends redirect t

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

Hi, @Tomas Senart. Currently, my patch is to redirect the request to correct url. For example: $ curl -i http://master1:5050/master/tasks.json HTTP/1.1 307 Temporary Redirect Date: Mon, 01 Jun 2015 06:30:08 GMT Location: http://master2:5050/master/tasks.json Content-Length: 0 Assume master1 is no

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

I'll volunteer to shepherd this, unless somebody else really wants to. I think returning any HTTP error code (other than 200 OK) would be preferable for those endpoints that would return empty data otherwise, but redirect is the most actionable one for getting to the real data. On Wed, Jul 1, 2015

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

Hi Haosdent, Do you have a shepherd for this change? On 1 Jul 2015 8:06 am, "Adam Bordelon" wrote: > The original ticket MESOS-1865 > argues the point that > requesting state data (e.g. tasks.json) from a non-leading master should > not return 2