[
https://issues.apache.org/jira/browse/ATLAS-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418407#comment-15418407
]
Suma Shivaprasad commented on ATLAS-1111:
-----------------------------------------
LGTM +1 . set atlas.kafka.consumer.timeout.ms=4000 in
distro/atlas-application.properties as well?
> Data loss is observed when atlas is restarted while hive_table metadata
> ingestion into kafka topic is in-progress
> -----------------------------------------------------------------------------------------------------------------
>
> Key: ATLAS-1111
> URL: https://issues.apache.org/jira/browse/ATLAS-1111
> Project: Atlas
> Issue Type: Bug
> Affects Versions: 0.8-incubating
> Reporter: Sharmadha Sainath
> Assignee: Shwetha G S
> Priority: Critical
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1111.1.patch, ATLAS-1111.2.patch, ATLAS-1111.patch
>
>
> During atlas stop, the graph is shutdown first and then the services like
> NotificationHookConsumer is shutdown. After graph is shutdown and before
> NotificationHookConsumer is shutdown, the message handling fails as the graph
> is down, but the NotificationHookConsumer commits the message(updating the
> offset). So, the messages during this time are lost
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
