You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2013/11/18 17:07:20 UTC
[jira] [Resolved] (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.
[ https://issues.apache.org/jira/browse/AMBARI-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitry Lysnichenko resolved AMBARI-3793.
----------------------------------------
Resolution: Fixed
committed to trunk
> 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)