You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "E. Sammer (Updated) (JIRA)" <ji...@apache.org> on 2011/11/01 05:44:32 UTC
[jira] [Updated] (FLUME-823) The properties configuration provider
should fail if the configuration file is not found
[ https://issues.apache.org/jira/browse/FLUME-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
E. Sammer updated FLUME-823:
----------------------------
Fix Version/s: NG alpha 2
Targeting for NG alpha 2.
As a larger question about expected behavior, should we fail fast (as Will suggests) or should we leave Flume running "unprovisioned" and polling for the file (with a WARNing in the logs about it being unprovisioned on each poll)? The reason I bring this up is because I can easily see a case where a bootstrapping VM (e.g. EC2 node) comes up with Flume which starts from init, and then fetches or receives configuration from something like puppet. In automated cases like this, you'd want Flume to wait for config deployment rather than exit with a failure. It has the potential dangerous side effect of appearing healthy when it's not, in fact, doing anything (although we could provide metrics such as counters around successful config loads or number of active sources, sinks, and channels to mitigate this).
Thoughts?
> The properties configuration provider should fail if the configuration file is not found
> ----------------------------------------------------------------------------------------
>
> Key: FLUME-823
> URL: https://issues.apache.org/jira/browse/FLUME-823
> Project: Flume
> Issue Type: Bug
> Components: Configuration
> Affects Versions: NG alpha 1
> Reporter: Will McQueen
> Assignee: Arvind Prabhakar
> Fix For: NG alpha 2
>
>
> When specifying a props file (eg, flume.properties) that doesn't exist, the logs don't indicate any failure to read the config file. The configuration provider should probably just fail if the config file isn't found.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira