You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@atlas.apache.org by "Madhan Neethiraj (JIRA)" <ji...@apache.org> on 2018/07/27 17:56:00 UTC

[jira] [Commented] (ATLAS-2796) Default Atlas configuration of graph lock wait time seems excessive

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

Madhan Neethiraj commented on ATLAS-2796:
-----------------------------------------

[~grahamwallis] -  the wait-time was 10s even before ATLAS-833. The commit in ATLAS-833 has simply moved the config from atlas-application.properties to build profile.

That said, can you give more details on the issue seen with this default value?

> Default Atlas configuration of graph lock wait time seems excessive
> -------------------------------------------------------------------
>
>                 Key: ATLAS-2796
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2796
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: Graham Wallis
>            Priority: Major
>
> For some reason the default configuration sets a 10s timeout for internal graph locks.
> This seems to have been introduced in ATLAS-833. Does anyone know why such a high value is needed?
> I propose setting to to 100ms.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)