reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yunseong Lee (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (REEF-1000) Allow more configuration in VortexLauncher
Date Thu, 25 Feb 2016 06:31:19 GMT

     [ https://issues.apache.org/jira/browse/REEF-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yunseong Lee updated REEF-1000:
-------------------------------
    Fix Version/s: 0.14

> Allow more configuration in VortexLauncher
> ------------------------------------------
>
>                 Key: REEF-1000
>                 URL: https://issues.apache.org/jira/browse/REEF-1000
>             Project: REEF
>          Issue Type: Improvement
>          Components: Vortex
>            Reporter: Yunseong Lee
>            Assignee: Yunseong Lee
>             Fix For: 0.14
>
>
> Vortex launcher takes fixed type of configuration variables, and most of them are related
to resource configuration: numWorkers, workerMemory, workerCores, workerCapacity. In our HelloVortex
example, the launcher code looks like following.
> {code:title=HelloVortex.java}
> VortexLauncher.launchLocal("Vortex_Example_HelloVortex", HelloVortexStart.class, 1, 1024,
1, 2000);
> {code}
> The launcher code looks very simple, and user can easily figure out which parameters
are needed from IDE. But this is quite rigid.
> # When user wants to change the configuration, she/he should rebuild the project.
> # There would be more parameters than the current configuration. We already have REEF-517,
but that issue is not about the way we set values.
> # Users may want to set configuration specific to application. For example, in {{AddOne}}
example, we may want to set the dimension of Vector at runtime.
> It would be great for users to do this without much effort. Using Tang would be awesome
because they provide {{CommandLine}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message