Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Mon, 18 Nov 2013 16:05:20 +0000 (UTC)
From: "Dmitry Lysnichenko (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <JIRA.12679715.1384775897284.90978.1384790720292@arcas>
In-Reply-To: <JIRA.12679715.1384775897284@arcas>
References: <JIRA.12679715.1384775897284@arcas>
Subject: [jira] [Commented] (AMBARI-3793) Do not store disks_info in DB.
 Store it as dynamic info in memory that can be used to show on the UI.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dmitry Lysnichenko commented on AMBARI-3793:
--------------------------------------------

+1

> Do not store disks_info in DB. Store it as dynamic info in memory that can be used to show on the UI.
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-3793
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3793
>             Project: Ambari
>          Issue Type: Bug
>          Components: agent
>    Affects Versions: 1.4.1
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>             Fix For: 1.5.0
>
>         Attachments: AMBARI-3793.patch
>
>
> Currently, we store disks info in DB and this information is never updated after registration. As disks details can change (space availability changes, disks get mounted/unmounted, etc.) the persisted information is not useful.
> We should instead hold the details in memory and refresh it at certain intervals (e.g. once every 10 minutes) and then alert if space availability hits some lower limit.


--
This message was sent by Atlassian JIRA
(v6.1#6144)