[
https://issues.apache.org/jira/browse/ATLAS-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suma Shivaprasad updated ATLAS-1111:
------------------------------------
Attachment: ATLAS-1111.5.patch
Uploading patch with minor changes
1. Altered destruction order of GuiceServletConfig before Log4j listener and
logs are now shpwing up wrt stopping services
2. Added logger for failed messages in tests
> 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.3.patch, ATLAS-1111.4.patch, ATLAS-1111.5.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)
