[
https://issues.apache.org/jira/browse/FLUME-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Endre Major resolved FLUME-3274.
--------------------------------
Resolution: Won't Fix
Will be fixed in FLUME-3281.
> KafkaSource and JMSSource can get stuck at startup connection exception
> -----------------------------------------------------------------------
>
> Key: FLUME-3274
> URL: https://issues.apache.org/jira/browse/FLUME-3274
> Project: Flume
> Issue Type: Bug
> Reporter: Endre Major
> Assignee: Endre Major
> Priority: Major
>
> This problem can happen in sources that are derived from
> BasicSourceSemantics. BasicSourceSemantics at startup if an exception occurs,
> it stores it. This behavior only makes sense if the start only throws an
> exception for unrecoverable configuration problems. Both KafkaSource and
> JMSSource try to connect to a Kafka or JMS server at startup, if the server
> is not available the flume agent needs to be restarted. They both can recover
> after connection errors after a successful startup.
> The start() should only throw an exception for unrecoverable problems.
> We need to make sure that the reconnect mechanism is safe and even if there
> is some configuration problem it does not start a DOS attack.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
