[
https://issues.apache.org/jira/browse/FLUME-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491952#comment-13491952
]
Mike Percy commented on FLUME-1502:
-----------------------------------
I agree that people would want some interface to trigger a reconfiguration. Not
to confuse this with the specifics of the log4j2 integration, but in the case
of log4j it's possible to trigger an app to re-read log4j.properties. It would
likely be a desired feature of Flume to re-read a flume.conf file or something
based on some trigger... maybe just an API hook, and the application decides
how to trigger it, like a reconfigure() call.
I think people may also want to have a flume.conf file controlling the
configuration, but it may be difficult / confusing when trying to enforce
different constraints on it, such as only one channel, etc. So I'd be OK with
leaving that out of the initial implementation, as long as we provide room to
grow into it.
> Support for running simple configurations embedded in host process
> ------------------------------------------------------------------
>
> Key: FLUME-1502
> URL: https://issues.apache.org/jira/browse/FLUME-1502
> Project: Flume
> Issue Type: Improvement
> Affects Versions: v1.2.0
> Reporter: Arvind Prabhakar
> Assignee: Brock Noland
> Attachments: embeeded-agent-1.pdf
>
>
> Flume should provide a light-weight embeddable node manager that can be
> started in process where necessary. This will allow the users to embed
> light-weight agents within the host process where necessary.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
