Refactor `dacluster` to start controller and engines separately

Open
#454 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
cli, distributed-systems

Research direction

Start at the dacluster command entry point and trace how it currently starts the controller and engines, with particular attention to the restart path. Use the issue's ipcontroller and ipcluster commands as the intended model; done means dacluster can start them separately and restart kills and recreates only the engine processes.

Written by the indexing model from the issue text.

Description

enhancement

From @minrk :
"""
You can start the controller and engines separately, which makes restarting engines easier (though they will get new IDs). I typically do it this way:

ipcontroller
ipcluster engines —engines=MPI -n 8

Then I can kill/restart the engine processes.
"""

We should refactor dacluster to use this pattern, so that dacluster restart simply kills the engine processes and then fires up a new set of them.

Dominant language
Python
Stars
5
Forks
1
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from enthought/distarray

All issues in enthought/distarray

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.