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 2020/05/18 05:14:00 UTC

[jira] [Updated] (ATLAS-3801) NotificationHookConsumer: Introduce Retry Logic for PermanentLockingException

     [ https://issues.apache.org/jira/browse/ATLAS-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ashutosh Mestry updated ATLAS-3801:
-----------------------------------
    Attachment: ATLAS-3801-NotificationHookConsumer-Introduce-rollba.patch

> NotificationHookConsumer: Introduce Retry Logic for PermanentLockingException
> -----------------------------------------------------------------------------
>
>                 Key: ATLAS-3801
>                 URL: https://issues.apache.org/jira/browse/ATLAS-3801
>             Project: Atlas
>          Issue Type: Improvement
>          Components:  atlas-core
>    Affects Versions: trunk
>            Reporter: Ashutosh Mestry
>            Assignee: Ashutosh Mestry
>            Priority: Major
>             Fix For: trunk
>
>         Attachments: ATLAS-3801-NotificationHookConsumer-Introduce-rollba.patch
>
>
> *Background*
> _NotificationHookConsumer_ when performing graph commit can potentially encounter _JanusGraph's PermanentLockingException_.
> JanusGraph [documentation|https://docs.janusgraph.org/basics/transactions/] details the cases in which this exception occurs. The way past this exception is rollback, pause and replay the data being committed.
> *Solution*
> Introduce the rollback, pause and retry mechanism in _NotificationHookConsumer_.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)