Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ModuleInstances should be executed as processes, not threads #4

Open
pbloem opened this issue Jun 20, 2014 · 0 comments
Open

ModuleInstances should be executed as processes, not threads #4

pbloem opened this issue Jun 20, 2014 · 0 comments

Comments

@pbloem
Copy link
Member

pbloem commented Jun 20, 2014

Also in the LocalExecutionProfile.

This would help us to create an environment where every module (in whatever domain) can just write to the current working directory, current in/out etc. and ducktape will catch it, and put it in the right place.

With any other solution (like threads) the modules must be written with techniques that are specific to ducktape, which is what we're trying to avoid.

The only problem is that this might increase the overhead, but probably not by that much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant