You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Ashutosh Mestry (JIRA)" <ji...@apache.org> on 2017/08/15 16:50:00 UTC
[jira] [Created] (ATLAS-2047) NotificationHookConsumer: Exception
Thrown by Kafka Consumer Ends up Filling Logs Due to Incorrect Handling
Ashutosh Mestry created ATLAS-2047:
--------------------------------------
Summary: NotificationHookConsumer: Exception Thrown by Kafka Consumer Ends up Filling Logs Due to Incorrect Handling
Key: ATLAS-2047
URL: https://issues.apache.org/jira/browse/ATLAS-2047
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.8-incubating, trunk
Reporter: Ashutosh Mestry
Assignee: Ashutosh Mestry
Fix For: trunk
*Background*
_KafkaConsumer_ is abstracted by _AtlasKafkaConsumer_. This is run using _HookConsumer_ which is derived from _kafka.utils.ShutdownableThread_.
The _ShutdownableThread_ manages the thread. It handles exceptions thrown in the _doWork_ method and logs them.
*Problem*
Exception reported in the bug is thrown by _KafkaConsumer_ is handed by _HookConsumer_. Exception is logged but the thread keeps running. In cases where Kafa is in irrecoverable state, this behavior ends up filling up logs and providing no value in return.
*Solution*
Let _ShutdownableThread_ hand exceptions thrown by _KafkaConsumer_. Stop the thread if _KafkaConsumer_ suffers from irrecoverable error. This will avoid the situation described in the problem section.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)