[
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
