You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Will McQueen (Created) (JIRA)" <ji...@apache.org> on 2011/10/31 21:07:32 UTC
[jira] [Created] (FLUME-823) The properties configuration provider
should fail if the configuration file is not found
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
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
[jira] [Updated] (FLUME-823) The properties configuration provider
should fail if the configuration file is not found
Posted by "E. Sammer (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (FLUME-823) The properties configuration
provider should fail if the configuration file is not found
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160203#comment-13160203 ]
jiraposter@reviews.apache.org commented on FLUME-823:
-----------------------------------------------------
bq. On 2011-11-30 17:58:44, Eric Sammer wrote:
bq. > flume-ng-node/src/main/java/org/apache/flume/node/Application.java, lines 135-136
bq. > <https://reviews.apache.org/r/2945/diff/2/?file=60172#file60172line135>
bq. >
bq. > At some point I think we should have a separate properties file for "static" agent level configuration like this. My guess is that there will be other global configuration in the future.
Agreed. I used the scheme that was outlined in the JIRA discussion. However, once we have service infrastructure, it makes sense to separate out such details into their own separate package/subsystem.
- Arvind
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2945/#review3577
-----------------------------------------------------------
On 2011-11-27 21:49:47, Arvind Prabhakar wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/2945/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2011-11-27 21:49:47)
bq.
bq.
bq. Review request for Flume and Eric Sammer.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. Based on the discussion in FLUME-823, this patch implements the fail-fast scenario for missing configuration file when invoked from the command line. In order to circumvent this check the system property "flume.called.from.service" should be set to a non-null value.
bq.
bq.
bq. This addresses bug FLUME-823.
bq. https://issues.apache.org/jira/browse/FLUME-823
bq.
bq.
bq. Diffs
bq. -----
bq.
bq. flume-ng-core/src/main/java/org/apache/flume/Constants.java PRE-CREATION
bq. flume-ng-node/src/main/java/org/apache/flume/node/Application.java eabeec1
bq.
bq. Diff: https://reviews.apache.org/r/2945/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq. Manually verified that if the file specified does not exist the process exits. If the file is specified but does not contain valid configuration for the node being configured, a warning is printed on the console.
bq.
bq.
bq. Thanks,
bq.
bq. Arvind
bq.
bq.
> 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
>
> Attachments: FLUME-823-1.patch
>
>
> 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
[jira] [Updated] (FLUME-823) The properties configuration provider
should fail if the configuration file is not found
Posted by "Arvind Prabhakar (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arvind Prabhakar updated FLUME-823:
-----------------------------------
Attachment: FLUME-823-1.patch
> 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
>
> Attachments: FLUME-823-1.patch
>
>
> 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
[jira] [Updated] (FLUME-823) The properties configuration provider
should fail if the configuration file is not found
Posted by "Arvind Prabhakar (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arvind Prabhakar updated FLUME-823:
-----------------------------------
Status: Patch Available (was: Open)
Implemented the logic based on discussion. The only slight difference is that the system property identifying the service based invocation is called {{flume.called.from.service}} instead of just {{called.from.service}}. This is done to ensure that flume system properties do not mistakenly clash with other systems.
> 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
>
> Attachments: FLUME-823-1.patch
>
>
> 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
[jira] [Commented] (FLUME-823) The properties configuration
provider should fail if the configuration file is not found
Posted by "Will McQueen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13154408#comment-13154408 ]
Will McQueen commented on FLUME-823:
------------------------------------
Arvind -- yes, the problem I was originally referring to was wrt a user calling the 'flumeng' script directly, you're right. And in the case of a bootstrapping VM (like Eric describes) where init would call a flume service, that flume service calls flumeng-daemon.sh (not yet implemented), which in turn would call the "flumeng" script... so ultimately the 'flumeng' script is called either way. If I'm catching your wavelength here, I think what you have in mind is that either the flume service script or the 'flumeng-daemon.sh' script would export some boolean env var flag that flumeng script would check, like:
export CALLED_FROM_SERVICE=true
The fail-fast logic would be activated in the Java code (after passing the env var to the Java main class as a sysprop, like -Dcalled.from.service={true,}), depending on the value of that var. For example:
1) If Flume NG is invoked directly via 'flumeng' script, then CALLED_FROM_SERVICE wasn't set and:
a) If the user specified file, then:
i) If the config file doesn't exist, then fail fast
ii) If the config file exists but is invalid, then agent continues running in unprovisioned mode, but enters a polling state. Warning is issued.
b) If the user didn't specify a file, then:
i) fail fast
2) If Flume NG is invoked via 'flume-daemon.sh' from a service script in /etc/init.d or from flume-daemon.sh script in FLUME_HOME/bin, then:
a) The config file will be searched-for in some well-known location, provided to 'flumeng' script by flume-daemon.sh.
b) If the file doesn't exist, then enter polling state and issue warning (Eric's scenario)
c) If the config file exists but is invalid, then agent continues running in unprovisioned mode, and enters a polling state. Warning is issued.
Was that similar to what you were thinking?
> 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
[jira] [Commented] (FLUME-823) The properties configuration
provider should fail if the configuration file is not found
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160256#comment-13160256 ]
Hudson commented on FLUME-823:
------------------------------
Integrated in flume-728 #63 (See [https://builds.apache.org/job/flume-728/63/])
FLUME-823. Agent must fail when invoked from CLI with a missing config file.
arvind : http://svn.apache.org/viewvc/?view=rev&rev=1208634
Files :
* /incubator/flume/branches/flume-728/flume-ng-core/src/main/java/org/apache/flume/Constants.java
* /incubator/flume/branches/flume-728/flume-ng-node/src/main/java/org/apache/flume/node/Application.java
> 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
>
> Attachments: FLUME-823-1.patch
>
>
> 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
[jira] [Commented] (FLUME-823) The properties configuration
provider should fail if the configuration file is not found
Posted by "Arvind Prabhakar (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145196#comment-13145196 ]
Arvind Prabhakar commented on FLUME-823:
----------------------------------------
Will - your proposed behavior makes sense. However, I think the original problem you were referring to was with respect to the command line invocation of the Agent. In that regard, if the user does specify a configuration file, then I think it is valid to fail fast in case the file does not exist. If the file exists but contains no valid configuration, that should result in a warning with the Agent going into the polling state.
> 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
[jira] [Commented] (FLUME-823) The properties configuration
provider should fail if the configuration file is not found
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158038#comment-13158038 ]
jiraposter@reviews.apache.org commented on FLUME-823:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2945/
-----------------------------------------------------------
Review request for Flume and Eric Sammer.
Summary
-------
Based on the discussion in FLUME-823, this patch implements the fail-fast scenario for missing configuration file when invoked from the command line. In order to circumvent this check the system property "flume.called.from.service" should be set to a non-null value.
This addresses bug FLUME-823.
https://issues.apache.org/jira/browse/FLUME-823
Diffs
-----
flume-ng-core/src/main/java/org/apache/flume/Constants.java PRE-CREATION
flume-ng-node/src/main/java/org/apache/flume/node/Application.java eabeec1
Diff: https://reviews.apache.org/r/2945/diff
Testing
-------
Manually verified that if the file specified does not exist the process exits. If the file is specified but does not contain valid configuration for the node being configured, a warning is printed on the console.
Thanks,
Arvind
> 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
>
> Attachments: FLUME-823-1.patch
>
>
> 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
[jira] [Updated] (FLUME-823) The properties configuration provider
should fail if the configuration file is not found
Posted by "Arvind Prabhakar (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arvind Prabhakar updated FLUME-823:
-----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Patch committed.
> 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
>
> Attachments: FLUME-823-1.patch
>
>
> 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
[jira] [Assigned] (FLUME-823) The properties configuration provider
should fail if the configuration file is not found
Posted by "Arvind Prabhakar (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arvind Prabhakar reassigned FLUME-823:
--------------------------------------
Assignee: Arvind Prabhakar
> 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
>
> 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
[jira] [Commented] (FLUME-823) The properties configuration
provider should fail if the configuration file is not found
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160186#comment-13160186 ]
jiraposter@reviews.apache.org commented on FLUME-823:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2945/#review3577
-----------------------------------------------------------
Ship it!
lgtm.
flume-ng-node/src/main/java/org/apache/flume/node/Application.java
<https://reviews.apache.org/r/2945/#comment7990>
At some point I think we should have a separate properties file for "static" agent level configuration like this. My guess is that there will be other global configuration in the future.
- Eric
On 2011-11-27 21:49:47, Arvind Prabhakar wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/2945/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2011-11-27 21:49:47)
bq.
bq.
bq. Review request for Flume and Eric Sammer.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. Based on the discussion in FLUME-823, this patch implements the fail-fast scenario for missing configuration file when invoked from the command line. In order to circumvent this check the system property "flume.called.from.service" should be set to a non-null value.
bq.
bq.
bq. This addresses bug FLUME-823.
bq. https://issues.apache.org/jira/browse/FLUME-823
bq.
bq.
bq. Diffs
bq. -----
bq.
bq. flume-ng-core/src/main/java/org/apache/flume/Constants.java PRE-CREATION
bq. flume-ng-node/src/main/java/org/apache/flume/node/Application.java eabeec1
bq.
bq. Diff: https://reviews.apache.org/r/2945/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq. Manually verified that if the file specified does not exist the process exits. If the file is specified but does not contain valid configuration for the node being configured, a warning is printed on the console.
bq.
bq.
bq. Thanks,
bq.
bq. Arvind
bq.
bq.
> 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
>
> Attachments: FLUME-823-1.patch
>
>
> 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
[jira] [Commented] (FLUME-823) The properties configuration
provider should fail if the configuration file is not found
Posted by "Will McQueen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13141714#comment-13141714 ]
Will McQueen commented on FLUME-823:
------------------------------------
+1 for Eric. I would then describe expected behavior as:
1) Launch Flume node, initially unprovisioned.
2) Flume node attempts to get provisioned with the config file that's specified on the command line. Retries every 30 secs, indefinitely.
3) When failing to load or parse the config file while the node is still *unprovisioned*, a warning is printed saying that the node is unprovisioned
4) When failing to load or parse the config file while the node is *already provisioned*, we retain the current config (we poll every 30 secs for config file changes)
5) Once the provisioned state is reached, a node cannot regress to unprovisioned state.
6) Removing a sink from the config will decommission that sink (this can be done to simulate failover to some other sink, or to allow the node's channel to empty into the source)
7) Removing a source from the config will decommission that source (in which case the node's channel would continue to grow, unless more than one source was specified, or a new source is specified).
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