mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jiraposter@reviews.apache.org (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-183) Included MPI Framework Fails to Start
Date Wed, 02 May 2012 13:00:57 GMT

    [ https://issues.apache.org/jira/browse/MESOS-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266526#comment-13266526
] 

jiraposter@reviews.apache.org commented on MESOS-183:
-----------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4768/
-----------------------------------------------------------

(Updated 2012-05-02 13:00:12.162674)


Review request for mesos, Benjamin Hindman, Charles Reiss, and Jessica.


Changes
-------

-Fixed lots of style issues...
-Converted to a no-executor framework


Summary
-------

Some updates to point out:

-nmpiexec.py
  -> 'mpdallexit' should terminate all slaves' mpds in the ring. I moved 'driver.stop()'
to statusUpdate() so that it stops when all tasks have been finished, which occurs when the
executor's launched mpd processes have all exited. 
-startmpd.py
  -> Didn't remove cleanup(), and added code in shutdown() that manually kills mpd processes.
They might be useful during abnormal (cleanup) and normal (shutdown) framework/executor termination...I
think. cleanup() still terminates all mpd's in the slave, but shutdown doesn't. 
  -> killtask() stops the mpd associated with the given tid. 
  -> Task states update nicely now. They correspond to the state of a task's associated
mpd process.
-Readme
  -> Included additional info on how to setup and run MPICH2 1.2 and nmpiexec on OS X and
Ubuntu/Linux


This addresses bug MESOS-183.
    https://issues.apache.org/jira/browse/MESOS-183


Diffs (updated)
-----

  frameworks/mpi/nmpiexec.py a5db9c0 
  frameworks/mpi/README.txt cdb4553 
  frameworks/mpi/startmpd.py 8eeba5e 
  frameworks/mpi/startmpd.sh 44faa05 

Diff: https://reviews.apache.org/r/4768/diff


Testing
-------


Thanks,

Harvey


                
> Included MPI Framework Fails to Start
> -------------------------------------
>
>                 Key: MESOS-183
>                 URL: https://issues.apache.org/jira/browse/MESOS-183
>             Project: Mesos
>          Issue Type: Bug
>          Components: documentation, framework
>         Environment: Scientific Linux Cluster
>            Reporter: Jessica J
>            Assignee: Harvey Feng 
>            Priority: Blocker
>              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 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?

--
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

        

Mime
View raw message