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

euphoria-core: multi-executor execution #44

Open
xitep opened this issue Feb 24, 2017 · 1 comment
Open

euphoria-core: multi-executor execution #44

xitep opened this issue Feb 24, 2017 · 1 comment
Labels

Comments

@xitep
Copy link
Contributor

xitep commented Feb 24, 2017

It would be desirable to run a program consisting of multiple flows on different executors. Example:

PExecutor sparkExec = new SparkExecutor(mem, cores);
PExecutor inmemExec = new InMemExecutor(mem, cores);

Flow flow1 = Flow.create("spark-flow");
Flow flow2 = Flow.create("inmem-flow");

sparkExec.registerFlow(flow1);
inmemExec.registerFlow(flow2);

// allocate YARN containers for Spark runtime and execute "flow1"
sparkExec.execute();

// allocate another YARN container for in-mem runtime
inmemExec.execute();

// kill all YARN containers
sparkExec.shutdown();
inmemExec.shutdown();

The idea is that euphoria executors be independent of the execution engine launchers and be able to allocate their own YARN containers from within which each would operate their own execution engine.

@xitep xitep added the idea label Feb 24, 2017
@je-ik
Copy link
Contributor

je-ik commented Feb 27, 2017

Do we want to incorporate a fixed dependency on YARN? I think that whether the flow runs on YARN or any other system is dependent on the settings of the executor - i.e. you can run euphoria flow on flink or spark without YARN, if you configure the executor to run in standalone mode. It would of course be desirable to be able to run multiple flows with multiple executors from single driver code.

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

No branches or pull requests

2 participants