You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2016/11/25 15:52:58 UTC
[jira] [Updated] (AMBARI-18990) Auto-fix common issues found by the
DB consistency checker
[ https://issues.apache.org/jira/browse/AMBARI-18990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitry Lysnichenko updated AMBARI-18990:
----------------------------------------
Component/s: ambari-server
> Auto-fix common issues found by the DB consistency checker
> ----------------------------------------------------------
>
> Key: AMBARI-18990
> URL: https://issues.apache.org/jira/browse/AMBARI-18990
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-18990.patch
>
>
> Proposed auto-fixes
> *Inconsistency for table hostcomponentdesiredstate and hostcomponentstate for stack upgrade.
> *Deleted services cause config table inconsistent
> *Primary key constrain issue from old Ambari version
> *Schema name in postgres is not ambari
> *Inconsistency view
> # If there are missing states (service, component, host), etc, then automatically add one with a value of UNKNOWN or INSTALLED.
> # If there are no selected configs, then select the latest ones (could be a bit dangerous)
> # If there are multiple selected configs for the same type, then unselect all but the most recent (could be a bit dangerous)
> For dangerous options, by default fail with warning, and provide console option to perform fixes anyway (like the fsck does)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)