ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonenko Alexander (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-20510) Oozie Database URL property was changed by itself
Date Tue, 21 Mar 2017 00:55:41 GMT

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

Antonenko Alexander updated AMBARI-20510:
-----------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

committed to trunk

> Oozie Database URL property was changed by itself
> -------------------------------------------------
>
>                 Key: AMBARI-20510
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20510
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.5.0
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-20510.patch
>
>
> After investigation, I figured out, that in our tests when we trying to setup config
on Oozie tab application replaces the correct Oozie DB URL with the wrong one.
> You can see this on video 1:07-1:11. 
> Looks like StackAdvisor response received twice.
> When we choose "Existing MySQL/MaridDB Database" Database URL property changed according
the value with "Oozie Server host", test changed it as needed (according to pattern)
> OOZIE_DB_URL = "jdbc:mysql://" + AmbariProperties.INSTALL_EXTERNAL_DB_HOST_NAME + "/"
+ "ooziedb";
> and immediately this property was changed to the old one
> go to HDFS configs
> in chrome dev console select Network, set throttling -> GPRS
> change "NameNode Java heap size"
> go to Advanced (config tab) and change "NameNode new generation size"
> once you will get response for recommendations, value of "NameNode new generation size"
will be changed to recommended one
> If you have bad internet connection you can make a stack of recommendation requests,
that will hang in pending state, and once resolved will apply recommended values



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message