ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lysnichenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-18990) Auto-fix common issues found by the DB consistency checker
Date Fri, 09 Dec 2016 14:48:58 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-18990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dmitry Lysnichenko updated AMBARI-18990:
----------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed
   66c6d56078..a8222ae3b8  trunk -> trunk
   54da8c27c9..6029846c94  branch-2.5 -> branch-2.5

> 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
>             Fix For: 2.5.0
>
>         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)

Mime
View raw message