[jira] [Commented] (ATLAS-592) Queue for failed hook messages
[ https://issues.apache.org/jira/browse/ATLAS-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329093#comment-15329093 ] Shwetha G S commented on ATLAS-592: --- Yes, separate logger for now sounds fine > Queue for failed hook messages > -- > > Key: ATLAS-592 > URL: https://issues.apache.org/jira/browse/ATLAS-592 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > > If NotificationHookConsumer fails to process a message, its just logged and > the message is lost. Instead, it should be added to failed queue, possibly > for manual intervention -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-592) Queue for failed hook messages
[ https://issues.apache.org/jira/browse/ATLAS-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329060#comment-15329060 ] Hemanth Yamijala commented on ATLAS-592: [~shwethags], moved this out of 0.7 release. For now the logging is probably our best bet. Maybe we can write using a separate logger so that they can be better managed. Thoughts? > Queue for failed hook messages > -- > > Key: ATLAS-592 > URL: https://issues.apache.org/jira/browse/ATLAS-592 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > > If NotificationHookConsumer fails to process a message, its just logged and > the message is lost. Instead, it should be added to failed queue, possibly > for manual intervention -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-592) Queue for failed hook messages
[ https://issues.apache.org/jira/browse/ATLAS-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15217630#comment-15217630 ] Shwetha G S commented on ATLAS-592: --- AtlasHook is client side, this bug was for failures in atlas server side. Will create another bug for it. Thanks > Queue for failed hook messages > -- > > Key: ATLAS-592 > URL: https://issues.apache.org/jira/browse/ATLAS-592 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > Fix For: 0.7-incubating > > > If NotificationHookConsumer fails to process a message, its just logged and > the message is lost. Instead, it should be added to failed queue, possibly > for manual intervention -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-592) Queue for failed hook messages
[ https://issues.apache.org/jira/browse/ATLAS-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15213421#comment-15213421 ] Hemanth Yamijala commented on ATLAS-592: Actually, in the case of whoever uses AtlasHook, the retry loop doesn't ever exit, which is a problem as well. (Found this while reviewing ATLAS-577) > Queue for failed hook messages > -- > > Key: ATLAS-592 > URL: https://issues.apache.org/jira/browse/ATLAS-592 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > Fix For: 0.7-incubating > > > If NotificationHookConsumer fails to process a message, its just logged and > the message is lost. Instead, it should be added to failed queue, possibly > for manual intervention -- This message was sent by Atlassian JIRA (v6.3.4#6332)
