reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Weimer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-751) Add a standard way to provide cluster-local configuration
Date Sun, 12 Mar 2017 16:56:04 GMT

    [ https://issues.apache.org/jira/browse/REEF-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906588#comment-15906588
] 

Markus Weimer commented on REEF-751:
------------------------------------

Thanks for your interest, [~madhawav]. There hasn't been progress on this issue beyond the
discussion above.

> Add a standard way to provide cluster-local configuration
> ---------------------------------------------------------
>
>                 Key: REEF-751
>                 URL: https://issues.apache.org/jira/browse/REEF-751
>             Project: REEF
>          Issue Type: Improvement
>          Components: REEF Client, REEF.NET Client
>            Reporter: Markus Weimer
>              Labels: C#, GSoC, gsoc2016, gsoc2017, java
>
> When running a REEF application on a specific cluster, we sometimes have to make cluster-specific
configuration choices beyond what's available via e.g. the YARN Configuration. One example
are clusters which only allow us to open TCP ports in a specific range.
> Right now, we require the application to add such configuration to the Driver, e.g. via
the {{DriverConfigurationProviders}} mechanism. This is awkward, because it limits the portability
of applications: In order for an app to run such a cluster, one would have to change the app's
code. This is undesirable.
> Instead, we should have a standard mechanism by which one can provide additional runtime-level
configuration to be picked up by the REEF client. Let's use this JIRA to discuss potential
solutions to this issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message