You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Markus Weimer (JIRA)" <ji...@apache.org> on 2015/04/15 22:34:00 UTC
[jira] [Created] (REEF-250) Support global and local Configurations
Markus Weimer created REEF-250:
----------------------------------
Summary: Support global and local Configurations
Key: REEF-250
URL: https://issues.apache.org/jira/browse/REEF-250
Project: REEF
Issue Type: Improvement
Components: REEF
Affects Versions: 0.10
Reporter: Markus Weimer
Priority: Minor
We frequently have the need to mirror parameters from the Driver Configuration into all Evaluator configurations. Examples include the job name and network parameters ([REEF-246] and [REEF-247]).
The current approach to do so is very cumbersome. We have the parameters injected in {{o.a.r.runtime.common.driver.evaluator.EvaluatorManager}} and then bind them to the Evaluator Configuration in {{o.a.r..runtime.common.driver.evaluator.AllocatedEvaluatorImpl#launch}}. This is error-prone and tedious.
Instead, we could follow the approach we've taken for files: We support the notion of global and local files: Global files are made available on all containers (Driver and Evaluator) in the folder {{reef/global/}} in the working directory of the container. Local files are made available only on that specific container in the folder {{reef/local}}.
We should have global and local Configuration as well, each of which is available separately for JVM and CLR containers. We can standardize the file names for them in {{o.a.r.runtime.common.files.REEFFileNames}} to make sure we don't mistype them.
What do you think?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)