[
https://issues.apache.org/jira/browse/LOG4J2-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402447#comment-15402447
]
Keith Laban commented on LOG4J2-1448:
-------------------------------------
I rebased my pull request against the laster master and it now applies cleanly.
I didn't have any conflicts in FlumeAppender and looking at the code, it does
not look like it has been addressed. The most recent change to anything in
flume was in this
[commit|https://github.com/apache/logging-log4j2/commit/ce4492f633fb7e54805fd8a2b98cf2bc7c44a725#diff-1db775dd9242e7cc22865433368ed1afL283]
~2 months ago. The second most recent change was 5 months ago, well before
this PR was opened.
> Allow comma separated agents, host list to be passed to FlumeAppender
> ---------------------------------------------------------------------
>
> Key: LOG4J2-1448
> URL: https://issues.apache.org/jira/browse/LOG4J2-1448
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: Keith Laban
>
> Dynamic system configuration of hosts is not possible with flume appender.
> The old
> [LoadBalancingLog4jAppender|https://flume.apache.org/releases/content/1.4.0/apidocs/org/apache/flume/clients/log4jappender/LoadBalancingLog4jAppender.html]
> accepted a space separated list.
> This ticket is to add a new parameter to the FlumeAppender which accepts a
> comma separated list of host:ports
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
