ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myroslav Papirkovskyy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15492) Status commands fail randomly
Date Mon, 21 Mar 2016 16:34:25 GMT

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

Myroslav Papirkovskyy commented on AMBARI-15492:
------------------------------------------------

Environment class was working incorrectly in case of concurrent usage.
We had other threads using it in same time with status commands (some alerts for example).
Previously this class used stack-like storage which didn't expect change of context (thread).
Fix is to use of thread local storage inside this class to avoid such issues.

Also patch adds logging of failures to make possible issues easier to detect in future.



> Status commands fail randomly
> -----------------------------
>
>                 Key: AMBARI-15492
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15492
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.2
>            Reporter: Myroslav Papirkovskyy
>            Assignee: Myroslav Papirkovskyy
>            Priority: Critical
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-15492.patch
>
>
> We experience random failures of status commands sometimes.
> As we treat any status command failure as "stopped"("installed") result, this causes
component (or even service if component is master) to appear as stopped until next status
command fixes status (1 minute interval).
> This tends to be completely random and appear once in 6-8 hours on average.



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

Mime
View raw message