Re: Unable to follow Sandbox links from Mesos UI.
It is a request from your browser session, not from the master that is going to the slaves - so in order to view the sandbox you need to ensure that the machine your browser is on can resolve and route to the masters _and_ the slaves. The master doesn't proxy the sandbox requests through itself (yet) - they are made directly from your browser instance to the slaves. Make sure you can resolve the slaves from the machine you're browsing the UI on. Cheers, ryan On 22 January 2015 at 15:42, Dan Dong dongda...@gmail.com wrote: Thank you all, the master and slaves can resolve each others' hostname and ssh login without password, firewalls have been switched off on all the machines too. So I'm confused what will block such a pull of info of slaves from UI? Cheers, Dan 2015-01-21 16:35 GMT-06:00 Cody Maloney c...@mesosphere.io: Also see https://issues.apache.org/jira/browse/MESOS-2129 if you want to track progress on changing this. Unfortunately it is on hold for me at the moment to fix. Cody On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas r.n.tho...@gmail.com wrote: Hey Dan, The UI will attempt to pull that info directly from the slave so you need to make sure the host is resolvable and routeable from your browser. Cheers, Ryan From my phone On Wednesday, 21 January 2015, Dan Dong dongda...@gmail.com wrote: Hi, All, When I try to access sandbox on mesos UI, I see the following info( The same error appears on every slave sandbox.): Failed to connect to slave '20150115-144719-3205108908-5050-4552-S0' on 'centos-2.local:5051'. Potential reasons: The slave's hostname, 'centos-2.local', is not accessible from your network The slave's port, '5051', is not accessible from your network I checked that: slave centos-2.local can be login from any machine in the cluster without password by ssh centos-2.local ; port 5051 on slave centos-2.local could be connected from master by telnet centos-2.local 5051 The stdout and stderr are there on each slave's /tmp/mesos/..., but seems mesos UI just could not access it. (and Both master and slaves are on the same network IP ranges). Should I open any port on slaves? Any hint what's the problem here? Cheers, Dan
Re: Unable to follow Sandbox links from Mesos UI.
Thank you all, the master and slaves can resolve each others' hostname and ssh login without password, firewalls have been switched off on all the machines too. So I'm confused what will block such a pull of info of slaves from UI? Cheers, Dan 2015-01-21 16:35 GMT-06:00 Cody Maloney c...@mesosphere.io: Also see https://issues.apache.org/jira/browse/MESOS-2129 if you want to track progress on changing this. Unfortunately it is on hold for me at the moment to fix. Cody On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas r.n.tho...@gmail.com wrote: Hey Dan, The UI will attempt to pull that info directly from the slave so you need to make sure the host is resolvable and routeable from your browser. Cheers, Ryan From my phone On Wednesday, 21 January 2015, Dan Dong dongda...@gmail.com wrote: Hi, All, When I try to access sandbox on mesos UI, I see the following info( The same error appears on every slave sandbox.): Failed to connect to slave '20150115-144719-3205108908-5050-4552-S0' on 'centos-2.local:5051'. Potential reasons: The slave's hostname, 'centos-2.local', is not accessible from your network The slave's port, '5051', is not accessible from your network I checked that: slave centos-2.local can be login from any machine in the cluster without password by ssh centos-2.local ; port 5051 on slave centos-2.local could be connected from master by telnet centos-2.local 5051 The stdout and stderr are there on each slave's /tmp/mesos/..., but seems mesos UI just could not access it. (and Both master and slaves are on the same network IP ranges). Should I open any port on slaves? Any hint what's the problem here? Cheers, Dan
Re: Accessing stdout/stderr of a task programmattically?
First off, you can only do this per executor - not per task.
To my understanding, the webui just picks up the executor directory from
the slave state.json, but the container id should also be available there.
Here is a snippet from a run of a echo 'foobar' baz.txt job:
The slave state endpoint:
{
...
completed_frameworks: [
{
...
completed_executors: [
{
...
*container*: 26491475-9515-464d-bcd0-c72790489a85,
*directory*:
/tmp/mesos/0/slaves/20150122-175457-16777343-5050-18106-S0/frameworks/20150122-182305-16777343-5050-18833-/executors/bar/runs/26491475-9515-464d-bcd0-c72790489a85,
id: bar,
name: Command Executor (Task: bar) (Command: sh -c 'echo
'foobar...'),
...
}
],
executors: [],
...
}
],
...
frameworks: [],
...
}
From that point on, you can browse (path 'just' URL encoded):
$ curl http://
host:5050/files/browse.json?path=%2Ftmp%2Fmesos%2F0%2Fslaves%2F20150122-175457-16777343-5050-18106-S0%2Fframeworks%2F20150122-182305-16777343-5050-18833-%2Fexecutors%2Fbar%2Fruns%2F26491475-9515-464d-bcd0-c72790489a85
[
{
gid: wheel,
mode: -rw-r--r--,
mtime: 1421979805,
nlink: 1,
path:
/tmp/mesos/0/slaves/20150122-175457-16777343-5050-18106-S0/frameworks/20150122-182305-16777343-5050-18833-/executors/bar/runs/26491475-9515-464d-bcd0-c72790489a85/baz.txt,
size: 7,
uid: nnielsen
}
]
Or grab the file:
$ curl
http://localhost:5050/files/read.json?path=%2Ftmp%2Fmesos%2F0%2Fslaves%2F20150122-175457-16777343-5050-18106-S0%2Fframeworks%2F20150122-182305-16777343-5050-18833-%2Fexecutors%2Fbar%2Fruns%2F26491475-9515-464d-bcd0-c72790489a85%2Fbaz.txt\offset=0
{
data: foobar\n,
offset: 0
}
Hope this helps.
Niklas
On 21 January 2015 at 13:53, David Greenberg dsg123456...@gmail.com wrote:
It seems that if I take the URL that the Download button for stderr
points to and curl it, I get the file. But, if I change the container_id to
latest instead of the UUID, then I get a 404. Is there another way to
resolve what the container_id is, since it seems critical to get files
programmatically.
On Wed, Jan 21, 2015 at 3:17 PM, Ian Downes idow...@twitter.com wrote:
No, the container id is generated by the slave when it launches the
executor for a task (see Framework::launchExecutor() in
src/slave/slave.cpp).
However, the 'latest' symlink will point to the most recent container_id
directory so you can likely just use that unless your framework is re-using
executor_ids (which would mean a new container for each run).
On Wed, Jan 21, 2015 at 11:52 AM, David Greenberg dsg123456...@gmail.com
wrote:
Is it possible to know the container_id prior when you submit the
TaskInfo? If not, how can you find it out?
On Wed, Jan 21, 2015 at 1:17 PM, Ian Downes idow...@twitter.com wrote:
The final component is the container_id. Take a look in
src/slave/paths.hpp to see the directory layout.
On Wed, Jan 21, 2015 at 8:50 AM, David Greenberg
dsg123456...@gmail.com wrote:
So, I've looked into this more, and the UUID in runs doesn't appear
appear to be the task-id, executor-id, or framework-id. do you have any
idea what it could be?
On Tue, Jan 13, 2015 at 5:21 PM, David Greenberg
dsg123456...@gmail.com wrote:
Thank you for your answers!
On Tue, Jan 13, 2015 at 5:15 PM, Tim Chen t...@mesosphere.io wrote:
You can get the slave_id, framework_id and executor_id of a task all
from state.json.
ie:
- {
- executor_id: 20141231-115728-16777343-5050-49193-S0,
- framework_id: 20141231-115728-16777343-5050-49193-,
- id: 1,
- labels: [ ],
- name: Task 1,
- resources:
{
- cpus: 6,
- disk: 0,
- mem: 13312
},
- slave_id: 20141231-115728-16777343-5050-49193-S0,
- state: TASK_KILLED,
- statuses:
[
-
{
- state: TASK_RUNNING,
- timestamp: 1420056049.88177
},
-
{
- state: TASK_KILLED,
- timestamp: 1420056124.66483
}
]
},
On Tue, Jan 13, 2015 at 1:48 PM, David Greenberg
dsg123456...@gmail.com wrote:
I was trying to figure out how to programmatically access a task's
stdout stderr, and I don't fully understand how the URL is
constructed.
It seems to be of the form http://
$slave_url:5050/read.json?$work_dir/work/slaves/$slave_id/frameworks/$framework_id/executors/$executor_id/runs/$something
What is the $something? Is there an easier way, given just the
task_id, to find where the output is?
Thanks,
David
Re: Mesos 0.22.0
Hi all, I created a JIRA to track the 0.22.0 release: https://issues.apache.org/jira/browse/MESOS-2248 Feel free to add and mark JIRA tickets (major features and minor fixes) you would like to go into this release. We will mark the tickets as blockers when we have agreed on a reasonable set of features and fixes to go in. The next step after that will be to mark all other tickets as target version 0.23.0. Cheers, Niklas On 21 January 2015 at 17:15, Adam Bordelon a...@mesosphere.io wrote: Cosmin: 0.21.1-rc2 is actually the same as 0.21.1. Both are tagged to commit 2ae1ba91e64f92ec71d327e10e6ba9e8ad5477e8 On Wed, Jan 21, 2015 at 3:52 PM, Cosmin Lehene cleh...@adobe.com wrote: Also, the release page on github shows 0.21.1-rc2 as being after the 0.21.1 release... https://github.com/apache/mesos/releases Cosmin -- *From:* Tim Chen t...@mesosphere.io *Sent:* Tuesday, January 20, 2015 1:36 PM *To:* Dave Lester *Cc:* user@mesos.apache.org *Subject:* Re: Mesos 0.22.0 Hi Dave, Sorry about the blog post, I lost track of it in the middle of other tasks. I'm going to update the website and the blog post very soon. Tim On Tue, Jan 20, 2015 at 12:37 PM, Dave Lester d...@davelester.org wrote: Thanks Niklas for kicking off this thread. +1 to you as release manager, could you please create a JIRA ticket to track the progress so we could subscribe? A minor correction to your email, Mesos 0.21.1 was voted on in late December (see http://markmail.org/message/e2iam7guxukl3r6c), however the website wasn't updated nor was blogged about like we normally do. Tim (cc'd), do you still plan to make this update? Any way others can help? I'd like to see this updated before we cut another release. +1 to Chris' suggestion of a page to plan future release managers, this would bring some longer-term clarity to who is driving feature releases and what they include. Dave On Tue, Jan 20, 2015, at 12:03 PM, Chris Aniszczyk wrote: definite +1, lets keep the release rhythm going! maybe some space on the wiki for release planning / release managers would be a step forward On Tue, Jan 20, 2015 at 1:59 PM, Joe Stein joe.st...@stealth.ly wrote: +1 so excited for the persistence primitives, awesome! /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop / On Tue, Jan 20, 2015 at 2:55 PM, John Pampuch j...@mesosphere.io wrote: +1! -John On Tue, Jan 20, 2015 at 11:52 AM, Niklas Nielsen nik...@mesosphere.io wrote: Hi all, We have been releasing major versions of Mesos roughly every second month (current average is ~66 days) and we are now 2 months after the 0.21.0 release, so I would like to propose that we start planning for 0.22.0 Not only in terms of timing, but also because we have some exciting features which are getting ready, including persistence primitives, modules and SSL support (I probably forgot a ton - please chime in). Since we are stakeholders in SSL and Modules, I would like to volunteer as release manager. Like in previous releases, I'd be happy to collaborate with co-release managers to make 0.22.0 a successful release. Niklas -- Cheers, Chris Aniszczyk | Open Source | Twitter, Inc. @cra | +1 512 961 6719
Re: can mesos-dns + mesos + docker emulate kubernetes' style of service discovery?
we use the HAProxy configurator script bundled with marathon to bind applications to ports : https://github.com/mesosphere/marathon/blob/master/bin/ haproxy-marathon-bridge Given the foregoing, can mesos-dns + mesos (possibly, mesosphere’s marathon) + docker be configured to emulate Kubernetes’ style of service discovery, i.e., no responsibility for DNS resolution in an application consuming other services via TCP? Thanks Craig. I will try that approach, which I see documented here: mesosphere.com/docs/getting-started/service-discovery. In light of your response, and direction to an approach that predates mesos-dns, it will need to consider what, if any, part mesos-dns has for my goal. Directly, it was progrium.com/blog/2014/09/10/automatic-docker-service-announcement-with-registrator and philzim.com/2014/11/12/service-discovery-orchestration-with-mesos-and-consul that set my expectation that consul could now be replaced with mesos-dns in mesos/marathon clusters. G
Re: cluster wide init
Schedulers can only use resources on slaves that are unused by and unallocated to other schedulers. Therefore, schedulers cannot achieve this unless you reserve slots on every slave for the scheduler. Seems kind of a forced fit. An init like support would be more fundamental to Mesos cluster itself, if available. On Thu, Jan 22, 2015 at 10:08 AM, Ryan Thomas r.n.tho...@gmail.com wrote: This seems more like the responsibility of the scheduler that is running, like marathon or aurora. I haven't tried it but I would imagine if you had 10 slaves and started a job with 11 tasks with host exclusivity when you spin up an 11th slave marathon would start it there. On Thursday, 22 January 2015, Sharma Podila spod...@netflix.com wrote: Just a thought looking forward... Might be useful to define an init kind of feature in Mesos slaves. Configuration can be defined in Mesos master that lists services that must be run on all slaves. When slaves register, they get the list of services to run all the time. Updates to the configuration can be dynamically reflected on all slaves and therefore this ensures that all slaves run the required services. Sophistication can be put in place to have different set of services for different types of slaves (by resource types/quantity, etc.). Such a feature bodes well with Mesos being the DataCenter OS/Kernel. On Thu, Jan 22, 2015 at 9:43 AM, CCAAT cc...@tampabay.rr.com wrote: On 01/21/2015 11:10 PM, Shuai Lin wrote: OK, I'll take a look at the debian package. thanks, James You can always write the init wrapper scripts for marathon. There is an official debian package, which you can find in mesos's apt repo. On Thu, Jan 22, 2015 at 4:20 AM, CCAAT cc...@tampabay.rr.com mailto:cc...@tampabay.rr.com wrote: Hello all, I was reading about Marathon: Marathon scheduler processes were started outside of Mesos using init, upstart, or a similar tool [1] This means So my related questions are Does Marathon work with mesos + Openrc as the init system? Are there any other frameworks that work with Mesos + Openrc? James [1] http://mesosphere.github.io/__marathon/ http://mesosphere.github.io/marathon/
Re: Unable to follow Sandbox links from Mesos UI.
Thanks Ryan, yes, from the machine where the browser is on slave hostnames could not be resolved, so that's why failure, but it can reach them by IP address( I don't think sys admin would like to add those VMs entries to /etc/hosts on the server). I tried to change masters and slaves of mesos to IP addresses instead of hostname but UI still points to hostnames of slaves. Is threre a way to let mesos only use IP address of master and slaves? Cheers, Dan 2015-01-22 9:48 GMT-06:00 Ryan Thomas r.n.tho...@gmail.com: It is a request from your browser session, not from the master that is going to the slaves - so in order to view the sandbox you need to ensure that the machine your browser is on can resolve and route to the masters _and_ the slaves. The master doesn't proxy the sandbox requests through itself (yet) - they are made directly from your browser instance to the slaves. Make sure you can resolve the slaves from the machine you're browsing the UI on. Cheers, ryan On 22 January 2015 at 15:42, Dan Dong dongda...@gmail.com wrote: Thank you all, the master and slaves can resolve each others' hostname and ssh login without password, firewalls have been switched off on all the machines too. So I'm confused what will block such a pull of info of slaves from UI? Cheers, Dan 2015-01-21 16:35 GMT-06:00 Cody Maloney c...@mesosphere.io: Also see https://issues.apache.org/jira/browse/MESOS-2129 if you want to track progress on changing this. Unfortunately it is on hold for me at the moment to fix. Cody On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas r.n.tho...@gmail.com wrote: Hey Dan, The UI will attempt to pull that info directly from the slave so you need to make sure the host is resolvable and routeable from your browser. Cheers, Ryan From my phone On Wednesday, 21 January 2015, Dan Dong dongda...@gmail.com wrote: Hi, All, When I try to access sandbox on mesos UI, I see the following info( The same error appears on every slave sandbox.): Failed to connect to slave '20150115-144719-3205108908-5050-4552-S0' on 'centos-2.local:5051'. Potential reasons: The slave's hostname, 'centos-2.local', is not accessible from your network The slave's port, '5051', is not accessible from your network I checked that: slave centos-2.local can be login from any machine in the cluster without password by ssh centos-2.local ; port 5051 on slave centos-2.local could be connected from master by telnet centos-2.local 5051 The stdout and stderr are there on each slave's /tmp/mesos/..., but seems mesos UI just could not access it. (and Both master and slaves are on the same network IP ranges). Should I open any port on slaves? Any hint what's the problem here? Cheers, Dan
Re: Unable to follow Sandbox links from Mesos UI.
Try the --hostname parameters for master/slave. If you want to be extra explicit about the IP (e.g. publish the public IP instead of the private one in a cloud environment), you can also set the --ip parameter on master/slave. On Thu, Jan 22, 2015 at 8:43 AM, Dan Dong dongda...@gmail.com wrote: Thanks Ryan, yes, from the machine where the browser is on slave hostnames could not be resolved, so that's why failure, but it can reach them by IP address( I don't think sys admin would like to add those VMs entries to /etc/hosts on the server). I tried to change masters and slaves of mesos to IP addresses instead of hostname but UI still points to hostnames of slaves. Is threre a way to let mesos only use IP address of master and slaves? Cheers, Dan 2015-01-22 9:48 GMT-06:00 Ryan Thomas r.n.tho...@gmail.com: It is a request from your browser session, not from the master that is going to the slaves - so in order to view the sandbox you need to ensure that the machine your browser is on can resolve and route to the masters _and_ the slaves. The master doesn't proxy the sandbox requests through itself (yet) - they are made directly from your browser instance to the slaves. Make sure you can resolve the slaves from the machine you're browsing the UI on. Cheers, ryan On 22 January 2015 at 15:42, Dan Dong dongda...@gmail.com wrote: Thank you all, the master and slaves can resolve each others' hostname and ssh login without password, firewalls have been switched off on all the machines too. So I'm confused what will block such a pull of info of slaves from UI? Cheers, Dan 2015-01-21 16:35 GMT-06:00 Cody Maloney c...@mesosphere.io: Also see https://issues.apache.org/jira/browse/MESOS-2129 if you want to track progress on changing this. Unfortunately it is on hold for me at the moment to fix. Cody On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas r.n.tho...@gmail.com wrote: Hey Dan, The UI will attempt to pull that info directly from the slave so you need to make sure the host is resolvable and routeable from your browser. Cheers, Ryan From my phone On Wednesday, 21 January 2015, Dan Dong dongda...@gmail.com wrote: Hi, All, When I try to access sandbox on mesos UI, I see the following info( The same error appears on every slave sandbox.): Failed to connect to slave '20150115-144719-3205108908-5050-4552-S0' on 'centos-2.local:5051'. Potential reasons: The slave's hostname, 'centos-2.local', is not accessible from your network The slave's port, '5051', is not accessible from your network I checked that: slave centos-2.local can be login from any machine in the cluster without password by ssh centos-2.local ; port 5051 on slave centos-2.local could be connected from master by telnet centos-2.local 5051 The stdout and stderr are there on each slave's /tmp/mesos/..., but seems mesos UI just could not access it. (and Both master and slaves are on the same network IP ranges). Should I open any port on slaves? Any hint what's the problem here? Cheers, Dan
Re: cluster wide init
On 01/21/2015 11:10 PM, Shuai Lin wrote: OK, I'll take a look at the debian package. thanks, James You can always write the init wrapper scripts for marathon. There is an official debian package, which you can find in mesos's apt repo. On Thu, Jan 22, 2015 at 4:20 AM, CCAAT cc...@tampabay.rr.com mailto:cc...@tampabay.rr.com wrote: Hello all, I was reading about Marathon: Marathon scheduler processes were started outside of Mesos using init, upstart, or a similar tool [1] This means So my related questions are Does Marathon work with mesos + Openrc as the init system? Are there any other frameworks that work with Mesos + Openrc? James [1] http://mesosphere.github.io/__marathon/ http://mesosphere.github.io/marathon/
can mesos-dns + mesos + docker emulate kubernetes' style of service discovery?
Hi, My goal has been to develop multi-container docker applications locally and expect their seamless introduction to production environments (wow.) I have done a POC for my goal with fig and Kubernetes, and I enjoy that I can depend on standard service ip/port environment variables to be present. (Similarly, I see that efforts resembling Jeff Lindsay’s approaches with docker + consul also rely on standard ip/port environment variables.) Given the foregoing, can mesos-dns + mesos (possibly, mesosphere’s marathon) + docker be configured to emulate Kubernetes’ style of service discovery, i.e., no responsibility for DNS resolution in an application consuming other services via TCP? Thanks, Gallagher
Re: cluster wide init
Just a thought looking forward... Might be useful to define an init kind of feature in Mesos slaves. Configuration can be defined in Mesos master that lists services that must be run on all slaves. When slaves register, they get the list of services to run all the time. Updates to the configuration can be dynamically reflected on all slaves and therefore this ensures that all slaves run the required services. Sophistication can be put in place to have different set of services for different types of slaves (by resource types/quantity, etc.). Such a feature bodes well with Mesos being the DataCenter OS/Kernel. On Thu, Jan 22, 2015 at 9:43 AM, CCAAT cc...@tampabay.rr.com wrote: On 01/21/2015 11:10 PM, Shuai Lin wrote: OK, I'll take a look at the debian package. thanks, James You can always write the init wrapper scripts for marathon. There is an official debian package, which you can find in mesos's apt repo. On Thu, Jan 22, 2015 at 4:20 AM, CCAAT cc...@tampabay.rr.com mailto:cc...@tampabay.rr.com wrote: Hello all, I was reading about Marathon: Marathon scheduler processes were started outside of Mesos using init, upstart, or a similar tool [1] This means So my related questions are Does Marathon work with mesos + Openrc as the init system? Are there any other frameworks that work with Mesos + Openrc? James [1] http://mesosphere.github.io/__marathon/ http://mesosphere.github.io/marathon/
Re: Unable to follow Sandbox links from Mesos UI.
Yes, --hostname solves the problem. Now I can see all files there like stdout, stderr etc, but when I click on e.g stdout, it pops a new blank window(pailer.html) without the content of the file(9KB size). Although it provides a Download link beside, it would be much more convenient if one can view the stdout and stderr directly. Is this normal or there is still problem on my envs? Thanks! Cheers, Dan 2015-01-22 11:33 GMT-06:00 Adam Bordelon a...@mesosphere.io: Try the --hostname parameters for master/slave. If you want to be extra explicit about the IP (e.g. publish the public IP instead of the private one in a cloud environment), you can also set the --ip parameter on master/slave. On Thu, Jan 22, 2015 at 8:43 AM, Dan Dong dongda...@gmail.com wrote: Thanks Ryan, yes, from the machine where the browser is on slave hostnames could not be resolved, so that's why failure, but it can reach them by IP address( I don't think sys admin would like to add those VMs entries to /etc/hosts on the server). I tried to change masters and slaves of mesos to IP addresses instead of hostname but UI still points to hostnames of slaves. Is threre a way to let mesos only use IP address of master and slaves? Cheers, Dan 2015-01-22 9:48 GMT-06:00 Ryan Thomas r.n.tho...@gmail.com: It is a request from your browser session, not from the master that is going to the slaves - so in order to view the sandbox you need to ensure that the machine your browser is on can resolve and route to the masters _and_ the slaves. The master doesn't proxy the sandbox requests through itself (yet) - they are made directly from your browser instance to the slaves. Make sure you can resolve the slaves from the machine you're browsing the UI on. Cheers, ryan On 22 January 2015 at 15:42, Dan Dong dongda...@gmail.com wrote: Thank you all, the master and slaves can resolve each others' hostname and ssh login without password, firewalls have been switched off on all the machines too. So I'm confused what will block such a pull of info of slaves from UI? Cheers, Dan 2015-01-21 16:35 GMT-06:00 Cody Maloney c...@mesosphere.io: Also see https://issues.apache.org/jira/browse/MESOS-2129 if you want to track progress on changing this. Unfortunately it is on hold for me at the moment to fix. Cody On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas r.n.tho...@gmail.com wrote: Hey Dan, The UI will attempt to pull that info directly from the slave so you need to make sure the host is resolvable and routeable from your browser. Cheers, Ryan From my phone On Wednesday, 21 January 2015, Dan Dong dongda...@gmail.com wrote: Hi, All, When I try to access sandbox on mesos UI, I see the following info( The same error appears on every slave sandbox.): Failed to connect to slave '20150115-144719-3205108908-5050-4552-S0' on 'centos-2.local:5051'. Potential reasons: The slave's hostname, 'centos-2.local', is not accessible from your network The slave's port, '5051', is not accessible from your network I checked that: slave centos-2.local can be login from any machine in the cluster without password by ssh centos-2.local ; port 5051 on slave centos-2.local could be connected from master by telnet centos-2.local 5051 The stdout and stderr are there on each slave's /tmp/mesos/..., but seems mesos UI just could not access it. (and Both master and slaves are on the same network IP ranges). Should I open any port on slaves? Any hint what's the problem here? Cheers, Dan
Re: cluster wide init
If this was going to be used to allocate tasks outside of the schedulers resource management, and for every slave, why not just use the OS provided init system instead? On 22 January 2015 at 19:40, Sharma Podila spod...@netflix.com wrote: Schedulers can only use resources on slaves that are unused by and unallocated to other schedulers. Therefore, schedulers cannot achieve this unless you reserve slots on every slave for the scheduler. Seems kind of a forced fit. An init like support would be more fundamental to Mesos cluster itself, if available. On Thu, Jan 22, 2015 at 10:08 AM, Ryan Thomas r.n.tho...@gmail.com wrote: This seems more like the responsibility of the scheduler that is running, like marathon or aurora. I haven't tried it but I would imagine if you had 10 slaves and started a job with 11 tasks with host exclusivity when you spin up an 11th slave marathon would start it there. On Thursday, 22 January 2015, Sharma Podila spod...@netflix.com wrote: Just a thought looking forward... Might be useful to define an init kind of feature in Mesos slaves. Configuration can be defined in Mesos master that lists services that must be run on all slaves. When slaves register, they get the list of services to run all the time. Updates to the configuration can be dynamically reflected on all slaves and therefore this ensures that all slaves run the required services. Sophistication can be put in place to have different set of services for different types of slaves (by resource types/quantity, etc.). Such a feature bodes well with Mesos being the DataCenter OS/Kernel. On Thu, Jan 22, 2015 at 9:43 AM, CCAAT cc...@tampabay.rr.com wrote: On 01/21/2015 11:10 PM, Shuai Lin wrote: OK, I'll take a look at the debian package. thanks, James You can always write the init wrapper scripts for marathon. There is an official debian package, which you can find in mesos's apt repo. On Thu, Jan 22, 2015 at 4:20 AM, CCAAT cc...@tampabay.rr.com mailto:cc...@tampabay.rr.com wrote: Hello all, I was reading about Marathon: Marathon scheduler processes were started outside of Mesos using init, upstart, or a similar tool [1] This means So my related questions are Does Marathon work with mesos + Openrc as the init system? Are there any other frameworks that work with Mesos + Openrc? James [1] http://mesosphere.github.io/__marathon/ http://mesosphere.github.io/marathon/
