[jira] [Commented] (ATLAS-602) Hooks stuck in case of failure

["Vimal Sharma (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ATLAS-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15266286#comment-15266286 ] 

Vimal Sharma commented on ATLAS-602:
------------------------------------

One way to fix this issue is to return from AtlasHook.notifyEntities() after a certain number of retries.

But this fix can complicate the cases where two notifications are related to each other.
For example, consider these two commands:

hive> create table tmp_table(a int, b string);
hive> alter table tmp_table add columns (c int)

Now, if notifyEntities() fails to send notification for first command and succeeds for second command, there will be inconsistent data in Titan database. We will have an entry for a column for a non-existent table. One workaround could be to persist the notifications until they are successfully published.

[~suma.shivaprasad][~shwethags][~yhemanth] What are your suggestions to resolve this issue. Thanks [~yhemanth] for pointing this out.

> Hooks stuck in case of failure
> ------------------------------
>
>                 Key: ATLAS-602
>                 URL: https://issues.apache.org/jira/browse/ATLAS-602
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Shwetha G S
>            Assignee: Vimal Sharma
>            Priority: Critical
>             Fix For: 0.7-incubating
>
>
> in the case of whoever uses AtlasHook.notifyEntities(), the retry loop doesn't ever exit, which is a problem as well. Thanks [~yhemanth] for reporting it



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)