mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jessica J (Commented) (JIRA)" <>
Subject [jira] [Commented] (MESOS-183) Included MPI Framework Fails to Start
Date Thu, 12 Apr 2012 17:41:20 GMT


Jessica J commented on MESOS-183:

Here's a bonafide bug--looks like the MesosSchedulerDriver signature changed but the calling
code did not. Is there an easy way I can patch this on my own machine?

[jessica@golgatha mpi]$ ./nmpiexec -n 10 mesos://master@ hostname
Connecting to mesos master mesos://master@
MPD_PID is golgatha.[...].net_40165
Traceback (most recent call last):
  File "./", line 171, in <module>
    mesos.MesosSchedulerDriver(sched, args[0]).run()
TypeError: function takes exactly 3 arguments (2 given)

> Included MPI Framework Fails to Start
> -------------------------------------
>                 Key: MESOS-183
>                 URL:
>             Project: Mesos
>          Issue Type: Bug
>          Components: documentation, framework
>         Environment: Scientific Linux Cluster
>            Reporter: Jessica J
>            Assignee: Harvey Feng 
>              Labels: documentation, mpi, setup
> There are really two facets to this issue. The first is that no good documentation exists
for setting up and using the included MPI framework. The second, and more important issue,
is that the framework will not run. The second issue is possibly related to the first in that
I may not be setting it up properly. 
> To test the MPI framework, by trial and error I determined I needed to run python
build and python install in the MESOS-HOME/src/python directory. Now when I try to
run nmpiexec -h, I get an AttributeError, below: 
> Traceback (most recent call last):
>   File "./", line 2, in <module>
>     import mesos
>   File "/usr/lib64/python2.6/site-packages/mesos-0.9.0-py2.6-linux-x86_64.egg/",
line 22, in <module>
>     import _mesos
>   File "/usr/lib64/python2.6/site-packages/mesos-0.9.0-py2.6-linux-x86_64.egg/",
line 1286, in <module>
>     DESCRIPTOR.message_types_by_name['FrameworkID'] = _FRAMEWORKID
> AttributeError: 'FileDescriptor' object has no attribute 'message_types_by_name'
> I've examined and determined that the version of protobuf it includes (2.4.1)
does, indeed, contain a FileDescriptor class in that sets self.message_types_by_name,
so I'm not sure what the issue is. Is this a bug? Or is there a step I'm missing? Do I need
to also build/install protobuf?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message