You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Jessica J (JIRA)" <ji...@apache.org> on 2012/05/31 16:34:25 UTC
[jira] [Updated] (MESOS-202) Deploy scripts start two instances of
each process
[ https://issues.apache.org/jira/browse/MESOS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jessica J updated MESOS-202:
----------------------------
Description: When I run any of the deploy scripts (e.g., mesos-start-cluster, mesos-master, mesos-slave), two instances of each process are launched. I've run ps on each node in my cluster to verify; master nodes run two instances of mesos-master and slave nodes run two instances of mesos-slave. (was: When I run any of the deploy scripts (e.g., mesos-start-cluster, mesos-master, mesos-slave), two instances of each process are launched. I've run ps on each node in my cluster to verify; master nodes run two instances of mesos-master and slave nodes run two instances of mesos-slave. This appears to affect frameworks as well. When I run, for example, the MPI framework, it launches one more instance of the framework than the number of processes I specify with -n. That is to say, instead of -n3 meaning 1 process on each of three nodes, I see each of three nodes running the same process 4 times.)
Edited because the framework issue was specific to the MPI framework, not to the deploy scripts.
> Deploy scripts start two instances of each process
> --------------------------------------------------
>
> Key: MESOS-202
> URL: https://issues.apache.org/jira/browse/MESOS-202
> Project: Mesos
> Issue Type: Bug
> Components: framework, master, slave
> Reporter: Jessica J
>
> When I run any of the deploy scripts (e.g., mesos-start-cluster, mesos-master, mesos-slave), two instances of each process are launched. I've run ps on each node in my cluster to verify; master nodes run two instances of mesos-master and slave nodes run two instances of mesos-slave.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira