You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flume.apache.org by "Ralph Goers (Jira)" <ji...@apache.org> on 2022/08/07 18:48:00 UTC

[jira] [Resolved] (FLUME-3432) Add support for a fallback configuration if the primary is unavailable.

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

Ralph Goers resolved FLUME-3432.
--------------------------------
    Resolution: Invalid

It seems I already implemented this and forgot.

> Add support for a fallback configuration if the primary is unavailable.
> -----------------------------------------------------------------------
>
>                 Key: FLUME-3432
>                 URL: https://issues.apache.org/jira/browse/FLUME-3432
>             Project: Flume
>          Issue Type: Improvement
>          Components: Configuration
>    Affects Versions: 1.10.0
>            Reporter: Ralph Goers
>            Assignee: Ralph Goers
>            Priority: Major
>
> Flume can now be configured from a remote configuration. However, if that configuration is unavailable Flume should still be able to start. This should be accomplished by Flume creating a "fallback configuration file" upon startup that can be used if the primary configuration is unavailable.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@flume.apache.org
For additional commands, e-mail: issues-help@flume.apache.org