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/08/01 04:47: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=16564724#comment-16564724 ] 

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

[~grahamwallis] - 10s delay in commit is not seen in all environments. Does this mean there could be an issue In the environments where this delay is seen, that needs to be investigated instead of changing the 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)