incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vitaly Brodetskyi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-3148) Oozie install fails with "could not connect to database" when choosing "use existing mysql database " and choosing "new mysql database" for Hive within Ambari
Date Mon, 09 Sep 2013 20:02:51 GMT

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

Vitaly Brodetskyi updated AMBARI-3148:
--------------------------------------

    Attachment: AMBARI-3148.patch
    
> Oozie install fails with "could not connect to database" when choosing "use existing
mysql database " and choosing "new mysql database" for Hive within Ambari
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-3148
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3148
>             Project: Ambari
>          Issue Type: Bug
>          Components: agent
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>             Fix For: 1.4.1
>
>         Attachments: AMBARI-3148.patch
>
>
> PROBLEM: When installing with Ambari and selecting an existing MySQL database for oozie
and a new MySQL database for Hive, then the Ambari
> install fails when installing the oozie database. The error thrown is "could not connect
to database" [it appears to drop the 'existing' database
> and you are required to start MySQL on the machine and create the database]
> BUSINESS IMPACT: This will affect all customers who choose an existing MySQL database
for oozie and a new MySQL DB for hive when installing a cluster using Ambari
> STEPS TO REPRODUCE: Choose an exisiting oozie MySQL database and point Ambari at this,
and select a new Hive MySQL database on the installation options
> ACTUAL BEHAVIOR: It seems that it drops the exisiting oozie database and then fails with
an errot of could not connect (This is due to MySQL being down, but also the Oozie database
is not there anymore)
> After starting MySQL and creating the database then the installer can continue from where
it left off.
> EXPECTED BEHAVIOR: The installer should not stop MySQL and drop the oozie database if
you select create a new Hive database and exisiting MySQL database for oozie.
> SUPPORT ANALYSIS: Reproduced in the lab in HDP 1.3.2 by following the steps above.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message