[MESOS-183] Included MPI Framework Fails to Start

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.9.0
• Fix Version/s: 0.10.0
• Component/s: documentation, framework
• Labels: documentation mpi setup

Environment

Scientific Linux Cluster

• Assignee: Harvey Feng
• Reporter: Jessica J
• Created: 12/Apr/12 16:09
• Updated: 22/May/13 01:24
• Resolved: 22/May/13 01:24

Description

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 setup.py build and python setup.py 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 "./nmpiexec.py", line 2, in <module>
import mesos
File "/usr/lib64/python2.6/site-packages/mesos-0.9.0-py2.6-linux-x86_64.egg/mesos.py", line 22, in <module>
import _mesos
File "/usr/lib64/python2.6/site-packages/mesos-0.9.0-py2.6-linux-x86_64.egg/mesos_pb2.py", line 1286, in <module>
DESCRIPTOR.message_types_by_name['FrameworkID'] = _FRAMEWORKID
AttributeError: 'FileDescriptor' object has no attribute 'message_types_by_name'

I've examined setup.py and determined that the version of protobuf it includes (2.4.1) does, indeed, contain a FileDescriptor class in descriptor.py 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?