[
https://issues.apache.org/jira/browse/AMBARI-20510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933577#comment-15933577
]
Hadoop QA commented on AMBARI-20510:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12859630/AMBARI-20510.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/11091//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11091//console
This message is automatically generated.
> 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)
