[jira] [Updated] (AMBARI-18441) upgrade ambari to 2.1.1 error
[ https://issues.apache.org/jira/browse/AMBARI-18441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18441: Attachment: AMBARI-18441-02.patch > upgrade ambari to 2.1.1 error > - > > Key: AMBARI-18441 > URL: https://issues.apache.org/jira/browse/AMBARI-18441 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18441-01.patch, AMBARI-18441-02.patch, > AMBARI-18441.patch, upgrade.png > > > ambari upgrade to 2.1.1, if the first time failed , excute ambari-server > upgrade again will error duplicate key value violates unique constraint > "pk_hostcomponentstate" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18818) Config changes for Atlas to Support KnoxSSO Authentication
[
https://issues.apache.org/jira/browse/AMBARI-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15669520#comment-15669520
]
Hudson commented on AMBARI-18818:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6022 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6022/])
AMBARI-18818 Config changes for Atlas to Support KnoxSSO Authentication
(mugdha:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5454bd612774d7f17704adaff24cbfa73c6a4f77])
* (edit)
ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/application-properties.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py
* (add)
ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/themes/theme_version_2.json
* (add)
ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/configuration/atlas-log4j.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/metainfo.xml
* (add)
ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/configuration/application-properties.xml
* (edit) ambari-server/src/test/python/stacks/2.6/common/test_stack_advisor.py
> Config changes for Atlas to Support KnoxSSO Authentication
> --
>
> Key: AMBARI-18818
> URL: https://issues.apache.org/jira/browse/AMBARI-18818
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18818.1.patch, AMBARI-18818.patch
>
>
> Following properties are need to be added in atlas-application.properties
> from Ambari Configs to enable Knox SSO in Atlas
> {noformat}
> atlas.sso.knox.enabled
> atlas.sso.knox.providerurl
> atlas.sso.knox.publicKey
> atlas.sso.knox.browser.useragent
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18818) Config changes for Atlas to Support KnoxSSO Authentication
[
https://issues.apache.org/jira/browse/AMBARI-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15669502#comment-15669502
]
Hudson commented on AMBARI-18818:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #333 (See
[https://builds.apache.org/job/Ambari-branch-2.5/333/])
AMBARI-18818 Config changes for Atlas to Support KnoxSSO Authentication
(mugdha:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4d4ca249ae197a86c07414920ac122fd7a65d873])
* (edit)
ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/application-properties.xml
* (edit) ambari-server/src/test/python/stacks/2.6/common/test_stack_advisor.py
* (add)
ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/configuration/application-properties.xml
* (add)
ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/themes/theme_version_2.json
* (add)
ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/configuration/atlas-log4j.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/metainfo.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py
> Config changes for Atlas to Support KnoxSSO Authentication
> --
>
> Key: AMBARI-18818
> URL: https://issues.apache.org/jira/browse/AMBARI-18818
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18818.1.patch, AMBARI-18818.patch
>
>
> Following properties are need to be added in atlas-application.properties
> from Ambari Configs to enable Knox SSO in Atlas
> {noformat}
> atlas.sso.knox.enabled
> atlas.sso.knox.providerurl
> atlas.sso.knox.publicKey
> atlas.sso.knox.browser.useragent
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18476) Ambari UI changes to support PAM authentication
[
https://issues.apache.org/jira/browse/AMBARI-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15669499#comment-15669499
]
Hadoop QA commented on AMBARI-18476:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12839118/AMBARI-18476_2.5patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9294//console
This message is automatically generated.
> Ambari UI changes to support PAM authentication
> ---
>
> Key: AMBARI-18476
> URL: https://issues.apache.org/jira/browse/AMBARI-18476
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: trunk
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Attachments: AMBARI-18476.patch, AMBARI-18476_2.5patch
>
>
> AMBARI-12263 adds support for PAM as authentication mechanism for accessing
> Ambari UI/REST.
> Since a new column group_type has been added for groups, the UI will display
> labels for group type and enable/disable group delete/add member
> functionality based on the group_type instead of the ldap_group flag.
> The user_type will be used to determine if the user can be deleted or if the
> user's password can be changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18476) Ambari UI changes to support PAM authentication
[ https://issues.apache.org/jira/browse/AMBARI-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18476: Attachment: AMBARI-18476_2.5patch patch for 2.5 > Ambari UI changes to support PAM authentication > --- > > Key: AMBARI-18476 > URL: https://issues.apache.org/jira/browse/AMBARI-18476 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Attachments: AMBARI-18476.patch, AMBARI-18476_2.5patch > > > AMBARI-12263 adds support for PAM as authentication mechanism for accessing > Ambari UI/REST. > Since a new column group_type has been added for groups, the UI will display > labels for group type and enable/disable group delete/add member > functionality based on the group_type instead of the ldap_group flag. > The user_type will be used to determine if the user can be deleted or if the > user's password can be changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18818) Config changes for Atlas to Support KnoxSSO Authentication
[
https://issues.apache.org/jira/browse/AMBARI-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-18818:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed: trunk -
https://github.com/apache/ambari/commit/5454bd612774d7f17704adaff24cbfa73c6a4f77
branch-2.5 -
https://github.com/apache/ambari/commit/4d4ca249ae197a86c07414920ac122fd7a65d873
> Config changes for Atlas to Support KnoxSSO Authentication
> --
>
> Key: AMBARI-18818
> URL: https://issues.apache.org/jira/browse/AMBARI-18818
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18818.1.patch, AMBARI-18818.patch
>
>
> Following properties are need to be added in atlas-application.properties
> from Ambari Configs to enable Knox SSO in Atlas
> {noformat}
> atlas.sso.knox.enabled
> atlas.sso.knox.providerurl
> atlas.sso.knox.publicKey
> atlas.sso.knox.browser.useragent
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18852) HostCleanup.py to be able to stop processes owned by users or java processes
[ https://issues.apache.org/jira/browse/AMBARI-18852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15669066#comment-15669066 ] Di Li commented on AMBARI-18852: The test failure listed below is unrelated to the ambari agent python script changes committed via this jira org.apache.ambari.server.state.cluster.ClusterDeadlockTest.testDeadlockWhileRestartingComponents > HostCleanup.py to be able to stop processes owned by users or java processes > - > > Key: AMBARI-18852 > URL: https://issues.apache.org/jira/browse/AMBARI-18852 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-18852.patch > > > a new feature to support stopping processes owned by users or java processes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18866) Stack advisor should limit call history it preserves
[ https://issues.apache.org/jira/browse/AMBARI-18866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15669028#comment-15669028 ] Hudson commented on AMBARI-18866: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6021 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6021/]) AMBARI-18866. Stack advisor should limit call history it preserves (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8c3ad1d6469fbe9c095fcc563f1c1a536892a727]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorHelperTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorHelper.java > Stack advisor should limit call history it preserves > > > Key: AMBARI-18866 > URL: https://issues.apache.org/jira/browse/AMBARI-18866 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-18866.patch > > > Today stack advisor uses a monotonically increasing id for each call when it > creates a local folder. This is reset only when Ambari Server is restarted. > For large clusters each call may produce 10-12 MB of files and it will result > in eventual disk space issue as there is no limit to how long call history is > preserved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18866) Stack advisor should limit call history it preserves
[ https://issues.apache.org/jira/browse/AMBARI-18866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15669003#comment-15669003 ] Hudson commented on AMBARI-18866: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #332 (See [https://builds.apache.org/job/Ambari-branch-2.5/332/]) AMBARI-18866. Stack advisor should limit call history it preserves (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3526ac503e02e44cf9210509034ea1dd7126bd9c]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorHelperTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorHelper.java > Stack advisor should limit call history it preserves > > > Key: AMBARI-18866 > URL: https://issues.apache.org/jira/browse/AMBARI-18866 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-18866.patch > > > Today stack advisor uses a monotonically increasing id for each call when it > creates a local folder. This is reset only when Ambari Server is restarted. > For large clusters each call may produce 10-12 MB of files and it will result > in eventual disk space issue as there is no limit to how long call history is > preserved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18898) Multiple kerberos name rules can not be set up for Ambari Infra Solr
[
https://issues.apache.org/jira/browse/AMBARI-18898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668962#comment-15668962
]
Hadoop QA commented on AMBARI-18898:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12839063/AMBARI-18898.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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-logsearch/ambari-logsearch-assembly ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9293//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9293//console
This message is automatically generated.
> Multiple kerberos name rules can not be set up for Ambari Infra Solr
>
>
> Key: AMBARI-18898
> URL: https://issues.apache.org/jira/browse/AMBARI-18898
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18898.patch
>
>
> If multiple rules are entered into the proprety
> Advanced infra-solr-env / Infra Solr Kerberos name rules
> There are multiple issues here:
> 1. The rules should be escaped, the $ characters in them should be handled,
> so that the expressions in the rules like $0, $1 are not replaced with the
> script directory, and the script file name. Currently the user must do this
> in the value entered, which is not even documented.
> 2. The variable SOLR_KERB_NAME_RULES in infra-solr-env.sh should have quotes
> around it's value, so that the whole string is assigned to it, not only the
> first rule.
> 3. SOLR_KERB_NAME_RULES can not be the part of SOLR_AUTHENTICATION_OPTS,
> because it is handled incorrectly, if an expression like -Dname="value1
> value2" is passed to the jvm from a bash variable. Therefore
> /usr/lib/ambari-infra-solr/bin/solr should be updated, and
> -Dsolr.kerberos.name.rules="$SOLR_KERB_NAME_RULES" should be added directly
> into the command script.
> Options
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18903) Implement Create Alerts: Create a base wizard for all steps
[ https://issues.apache.org/jira/browse/AMBARI-18903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-18903: - Attachment: AMBARI-18903.patch > Implement Create Alerts: Create a base wizard for all steps > --- > > Key: AMBARI-18903 > URL: https://issues.apache.org/jira/browse/AMBARI-18903 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Xi Wang >Assignee: Xi Wang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18903.patch > > > This is a FE task to implement the "Create Alerts Wizard " based on the > design attached. > This task is to create the the following files so that we have a blank base > wizard as a start point. > *4 controllers* in folder: controllers/main/alerts/create > wizard_controller.js (should extend App.WizardController) > step1_controller.js > step2_controller.js > step3_controller.js > *4 views* in folder: views/main/alerts/create > wizard_view.js (extend sApp.WizardMenuMixin) > step1_view.js > step2_view.js > step3_view.js > *4 templates* in folder: templates/main/alerts/create > wizard.hbs > step1.hbs > step2.hbs > step3.hbs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18890) Enable "Auto Start" feature for services & components by default
[ https://issues.apache.org/jira/browse/AMBARI-18890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668910#comment-15668910 ] Hudson commented on AMBARI-18890: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6020 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6020/]) AMBARI-18890 - Enable "Auto Start" feature for services & components by (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b7ee658d0a7802eba00805658fd50f5e9d0023b3]) * (edit) ambari-web/app/config.js > Enable "Auto Start" feature for services & components by default > > > Key: AMBARI-18890 > URL: https://issues.apache.org/jira/browse/AMBARI-18890 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-18890.patch > > > Enable "Auto Start" feature for services & components by default -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18897) HBase conf directory should not have a copy of core-site.xml and hdfs-site.xml
[
https://issues.apache.org/jira/browse/AMBARI-18897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668913#comment-15668913
]
Hadoop QA commented on AMBARI-18897:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12838998/AMBARI-18897.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 4 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-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9292//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9292//console
This message is automatically generated.
> HBase conf directory should not have a copy of core-site.xml and hdfs-site.xml
> --
>
> Key: AMBARI-18897
> URL: https://issues.apache.org/jira/browse/AMBARI-18897
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18897.patch
>
>
> /etc/hbase/conf/ contains core-site.xml and hdfs-site.xml which should not be
> needed at all. But more importantly, when we change a setting in Ambari, they
> do not get reflected in the hdfs-site.xml that is under the hbase conf
> directory. Since there are more than 1 core-site.xml in the classpath, this
> obviously causes issues since the changed configs are not picked up.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18903) Implement Create Alerts: Create a base wizard for all steps
Xi Wang created AMBARI-18903: Summary: Implement Create Alerts: Create a base wizard for all steps Key: AMBARI-18903 URL: https://issues.apache.org/jira/browse/AMBARI-18903 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.5.0 Reporter: Xi Wang Assignee: Xi Wang Priority: Critical Fix For: 2.5.0 This is a FE task to implement the "Create Alerts Wizard " based on the design attached. This task is to create the the following files so that we have a blank base wizard as a start point. *4 controllers* in folder: controllers/main/alerts/create wizard_controller.js (should extend App.WizardController) step1_controller.js step2_controller.js step3_controller.js *4 views* in folder: views/main/alerts/create wizard_view.js (extend sApp.WizardMenuMixin) step1_view.js step2_view.js step3_view.js *4 templates* in folder: templates/main/alerts/create wizard.hbs step1.hbs step2.hbs step3.hbs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18866) Stack advisor should limit call history it preserves
[ https://issues.apache.org/jira/browse/AMBARI-18866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18866: --- Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.5 > Stack advisor should limit call history it preserves > > > Key: AMBARI-18866 > URL: https://issues.apache.org/jira/browse/AMBARI-18866 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-18866.patch > > > Today stack advisor uses a monotonically increasing id for each call when it > creates a local folder. This is reset only when Ambari Server is restarted. > For large clusters each call may produce 10-12 MB of files and it will result > in eventual disk space issue as there is no limit to how long call history is > preserved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18890) Enable "Auto Start" feature for services & components by default
[ https://issues.apache.org/jira/browse/AMBARI-18890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668893#comment-15668893 ] Hudson commented on AMBARI-18890: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #331 (See [https://builds.apache.org/job/Ambari-branch-2.5/331/]) AMBARI-18890 - Enable "Auto Start" feature for services & components by (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=03bd7a6dab4d4a39e649f2c9361d07efbea1bb64]) * (edit) ambari-web/app/config.js > Enable "Auto Start" feature for services & components by default > > > Key: AMBARI-18890 > URL: https://issues.apache.org/jira/browse/AMBARI-18890 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-18890.patch > > > Enable "Auto Start" feature for services & components by default -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18898) Multiple kerberos name rules can not be set up for Ambari Infra Solr
[
https://issues.apache.org/jira/browse/AMBARI-18898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668858#comment-15668858
]
Hadoop QA commented on AMBARI-18898:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12839063/AMBARI-18898.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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-logsearch/ambari-logsearch-assembly ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9291//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9291//console
This message is automatically generated.
> Multiple kerberos name rules can not be set up for Ambari Infra Solr
>
>
> Key: AMBARI-18898
> URL: https://issues.apache.org/jira/browse/AMBARI-18898
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18898.patch
>
>
> If multiple rules are entered into the proprety
> Advanced infra-solr-env / Infra Solr Kerberos name rules
> There are multiple issues here:
> 1. The rules should be escaped, the $ characters in them should be handled,
> so that the expressions in the rules like $0, $1 are not replaced with the
> script directory, and the script file name. Currently the user must do this
> in the value entered, which is not even documented.
> 2. The variable SOLR_KERB_NAME_RULES in infra-solr-env.sh should have quotes
> around it's value, so that the whole string is assigned to it, not only the
> first rule.
> 3. SOLR_KERB_NAME_RULES can not be the part of SOLR_AUTHENTICATION_OPTS,
> because it is handled incorrectly, if an expression like -Dname="value1
> value2" is passed to the jvm from a bash variable. Therefore
> /usr/lib/ambari-infra-solr/bin/solr should be updated, and
> -Dsolr.kerberos.name.rules="$SOLR_KERB_NAME_RULES" should be added directly
> into the command script.
> Options
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18846) Custom services should be able to easily specify their own dashboards
[ https://issues.apache.org/jira/browse/AMBARI-18846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668850#comment-15668850 ] Hudson commented on AMBARI-18846: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6019 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6019/]) AMBARI-18846 - Custom services should be able to easily specify their (tthorpe: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b413d921cdeca51ad8d36088100ee13e853bb925]) * (edit) ambari-agent/src/test/python/ambari_agent/TestFileCache.py * (edit) ambari-agent/src/main/python/ambari_agent/FileCache.py * (edit) ambari-server/src/test/python/TestResourceFilesKeeper.py * (edit) ambari-agent/src/test/python/ambari_agent/TestCustomServiceOrchestrator.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py * (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py * (edit) ambari-server/src/main/python/ambari_server/resourceFilesKeeper.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/split_points.py * (edit) ambari-server/src/main/python/ambari_server/serverConfiguration.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py > Custom services should be able to easily specify their own dashboards > - > > Key: AMBARI-18846 > URL: https://issues.apache.org/jira/browse/AMBARI-18846 > Project: Ambari > Issue Type: Improvement > Components: ambari-admin, ambari-metrics, ambari-server >Affects Versions: trunk, 2.4.0, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18846.patch > > > Currently all dashboards are added directly in under the AMBARI_METRICS > package directory (package/files/grafana-dashboards). > In order for custom services to add dashboards, they need to add the files > directly under that folder. Each time the Ambari server is upgraded, those > files will be lost as the AMBARI_METRICS service definition will be replaced. > This JIRA proposes adding a new directory under the ambari-server/resources. > This will contain both the dashboards and metrics for custom services. > The dashboards here will not be organized by stack. Each service will add a > directory containing their dashboards and will add a metrics file. > resources/dashboards/grafana-dashboards/MY_SERVICE/ > resources/dashboards/service-metrics/MY_SERVICE.txt > The resources/dashboards directory will need to get sync'd to the agents. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18852) HostCleanup.py to be able to stop processes owned by users or java processes
[ https://issues.apache.org/jira/browse/AMBARI-18852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668848#comment-15668848 ] Hudson commented on AMBARI-18852: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6019 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6019/]) AMBARI-18852 HostCleanup.py to be able to stop processes owned by users (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0e8474fea1de0ed113b50bb89a18e8534f991db5]) * (edit) ambari-agent/src/main/python/ambari_agent/HostCleanup.py * (edit) ambari-agent/src/test/python/ambari_agent/TestHostCleanup.py > HostCleanup.py to be able to stop processes owned by users or java processes > - > > Key: AMBARI-18852 > URL: https://issues.apache.org/jira/browse/AMBARI-18852 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-18852.patch > > > a new feature to support stopping processes owned by users or java processes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18901) Use "Number of LLAP Nodes" selected as the driver for LLAP config calculations.
[ https://issues.apache.org/jira/browse/AMBARI-18901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-18901: - Summary: Use "Number of LLAP Nodes" selected as the driver for LLAP config calculations. (was: Use "Num of LLAP Node" selected as the driver for LLAP config calculations.) > Use "Number of LLAP Nodes" selected as the driver for LLAP config > calculations. > --- > > Key: AMBARI-18901 > URL: https://issues.apache.org/jira/browse/AMBARI-18901 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18899) Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart
[
https://issues.apache.org/jira/browse/AMBARI-18899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668809#comment-15668809
]
Hadoop QA commented on AMBARI-18899:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12839012/AMBARI-18899.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9290//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9290//console
This message is automatically generated.
> Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for
> restart
>
>
> Key: AMBARI-18899
> URL: https://issues.apache.org/jira/browse/AMBARI-18899
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-18899.patch
>
>
> I think not marking HDFS as restart required when Ambari upgrades is a good
> goal.
> In general its a difficult to get it right for all services.
> * hadoop.security.key.provider.path
> * dfs.encryption.key.provider.uri
> These two are removed by stack advisor when RANGER KMS does not exist. We
> should find out why it got added on Ambari upgrade. This seems like a bug to
> me.
> * namenode_backup_dir
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-18890) Enable "Auto Start" feature for services & components by default
[ https://issues.apache.org/jira/browse/AMBARI-18890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang resolved AMBARI-18890. --- Resolution: Fixed Committed to trunk and 2.5 03bd7a6dab4d4a39e649f2c9361d07efbea1bb64 > Enable "Auto Start" feature for services & components by default > > > Key: AMBARI-18890 > URL: https://issues.apache.org/jira/browse/AMBARI-18890 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-18890.patch > > > Enable "Auto Start" feature for services & components by default -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging
[ https://issues.apache.org/jira/browse/AMBARI-18637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668781#comment-15668781 ] Hudson commented on AMBARI-18637: - ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #6018 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6018/]) AMBARI-18637: Management pack purge option should warn user and ask for (jluniya: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d2118f58c9cf36720710222deac2d06e8024af00]) * (edit) ambari-server/src/main/python/ambari_server/setupMpacks.py > Management pack purge option should warn user and ask for confirmation before > purging > - > > Key: AMBARI-18637 > URL: https://issues.apache.org/jira/browse/AMBARI-18637 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.4.2 > > Attachments: AMBARI-18637.addendum.patch, AMBARI-18637.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18866) Stack advisor should limit call history it preserves
[
https://issues.apache.org/jira/browse/AMBARI-18866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668745#comment-15668745
]
Hadoop QA commented on AMBARI-18866:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12839016/AMBARI-18866.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 1 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-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9289//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9289//console
This message is automatically generated.
> Stack advisor should limit call history it preserves
>
>
> Key: AMBARI-18866
> URL: https://issues.apache.org/jira/browse/AMBARI-18866
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.0
>
> Attachments: AMBARI-18866.patch
>
>
> Today stack advisor uses a monotonically increasing id for each call when it
> creates a local folder. This is reset only when Ambari Server is restarted.
> For large clusters each call may produce 10-12 MB of files and it will result
> in eventual disk space issue as there is no limit to how long call history is
> preserved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18821) Logsearch support KNOX SSO (with JWT)
[
https://issues.apache.org/jira/browse/AMBARI-18821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668642#comment-15668642
]
Hadoop QA commented on AMBARI-18821:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12839035/AMBARI-18821.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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-logsearch/ambari-logsearch-portal ambari-server ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9288//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9288//console
This message is automatically generated.
> Logsearch support KNOX SSO (with JWT)
> -
>
> Key: AMBARI-18821
> URL: https://issues.apache.org/jira/browse/AMBARI-18821
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-18821.patch
>
>
> Add some new configuration properties to ambari and logsearch as well to
> handle JWT based authentication: (SSO with KNOX)
> {{logsearch.auth.jwt.enabled}}
> {{logsearch.auth.jwt.provider_url}}
> {{logsearch.auth.jwt.public_key}}
> And some more optional properties
> {{logsearch.auth.jwt.audiances}}
> {{logsearch.auth.jwt.cookie.name}}
> {{logsearch.auth.jwt.query.param.original_url}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18902) Minor typo fix in TimeliveMetricsStore class in AMS
[
https://issues.apache.org/jira/browse/AMBARI-18902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668581#comment-15668581
]
Hadoop QA commented on AMBARI-18902:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12839053/AMBARI-18902.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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-metrics/ambari-metrics-timelineservice.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9287//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9287//console
This message is automatically generated.
> Minor typo fix in TimeliveMetricsStore class in AMS
> ---
>
> Key: AMBARI-18902
> URL: https://issues.apache.org/jira/browse/AMBARI-18902
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
>Priority: Trivial
> Fix For: trunk
>
> Attachments: AMBARI-18902.patch
>
>
> Minor typo fix in TimeliveMetricsStore class in AMS
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18898) Multiple kerberos name rules can not be set up for Ambari Infra Solr
[ https://issues.apache.org/jira/browse/AMBARI-18898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-18898: Attachment: AMBARI-18898.patch > Multiple kerberos name rules can not be set up for Ambari Infra Solr > > > Key: AMBARI-18898 > URL: https://issues.apache.org/jira/browse/AMBARI-18898 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18898.patch > > > If multiple rules are entered into the proprety > Advanced infra-solr-env / Infra Solr Kerberos name rules > There are multiple issues here: > 1. The rules should be escaped, the $ characters in them should be handled, > so that the expressions in the rules like $0, $1 are not replaced with the > script directory, and the script file name. Currently the user must do this > in the value entered, which is not even documented. > 2. The variable SOLR_KERB_NAME_RULES in infra-solr-env.sh should have quotes > around it's value, so that the whole string is assigned to it, not only the > first rule. > 3. SOLR_KERB_NAME_RULES can not be the part of SOLR_AUTHENTICATION_OPTS, > because it is handled incorrectly, if an expression like -Dname="value1 > value2" is passed to the jvm from a bash variable. Therefore > /usr/lib/ambari-infra-solr/bin/solr should be updated, and > -Dsolr.kerberos.name.rules="$SOLR_KERB_NAME_RULES" should be added directly > into the command script. > Options -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18898) Multiple kerberos name rules can not be set up for Ambari Infra Solr
[ https://issues.apache.org/jira/browse/AMBARI-18898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-18898: Attachment: (was: AMBARI-18898.patch) > Multiple kerberos name rules can not be set up for Ambari Infra Solr > > > Key: AMBARI-18898 > URL: https://issues.apache.org/jira/browse/AMBARI-18898 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Critical > Fix For: 2.5.0 > > > If multiple rules are entered into the proprety > Advanced infra-solr-env / Infra Solr Kerberos name rules > There are multiple issues here: > 1. The rules should be escaped, the $ characters in them should be handled, > so that the expressions in the rules like $0, $1 are not replaced with the > script directory, and the script file name. Currently the user must do this > in the value entered, which is not even documented. > 2. The variable SOLR_KERB_NAME_RULES in infra-solr-env.sh should have quotes > around it's value, so that the whole string is assigned to it, not only the > first rule. > 3. SOLR_KERB_NAME_RULES can not be the part of SOLR_AUTHENTICATION_OPTS, > because it is handled incorrectly, if an expression like -Dname="value1 > value2" is passed to the jvm from a bash variable. Therefore > /usr/lib/ambari-infra-solr/bin/solr should be updated, and > -Dsolr.kerberos.name.rules="$SOLR_KERB_NAME_RULES" should be added directly > into the command script. > Options -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18846) Custom services should be able to easily specify their own dashboards
[ https://issues.apache.org/jira/browse/AMBARI-18846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668487#comment-15668487 ] Hudson commented on AMBARI-18846: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #330 (See [https://builds.apache.org/job/Ambari-branch-2.5/330/]) AMBARI-18846 - Custom services should be able to easily specify their (tthorpe: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8544750d46cfe02e25404cd93e629da8b3356fd9]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py * (edit) ambari-agent/src/test/python/ambari_agent/TestFileCache.py * (edit) ambari-agent/src/main/python/ambari_agent/FileCache.py * (edit) ambari-server/src/main/python/ambari_server/serverConfiguration.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/split_points.py * (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py * (edit) ambari-server/src/main/python/ambari_server/resourceFilesKeeper.py * (edit) ambari-server/src/test/python/TestResourceFilesKeeper.py * (edit) ambari-agent/src/test/python/ambari_agent/TestCustomServiceOrchestrator.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py > Custom services should be able to easily specify their own dashboards > - > > Key: AMBARI-18846 > URL: https://issues.apache.org/jira/browse/AMBARI-18846 > Project: Ambari > Issue Type: Improvement > Components: ambari-admin, ambari-metrics, ambari-server >Affects Versions: trunk, 2.4.0, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18846.patch > > > Currently all dashboards are added directly in under the AMBARI_METRICS > package directory (package/files/grafana-dashboards). > In order for custom services to add dashboards, they need to add the files > directly under that folder. Each time the Ambari server is upgraded, those > files will be lost as the AMBARI_METRICS service definition will be replaced. > This JIRA proposes adding a new directory under the ambari-server/resources. > This will contain both the dashboards and metrics for custom services. > The dashboards here will not be organized by stack. Each service will add a > directory containing their dashboards and will add a metrics file. > resources/dashboards/grafana-dashboards/MY_SERVICE/ > resources/dashboards/service-metrics/MY_SERVICE.txt > The resources/dashboards directory will need to get sync'd to the agents. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18852) HostCleanup.py to be able to stop processes owned by users or java processes
[ https://issues.apache.org/jira/browse/AMBARI-18852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-18852: --- Resolution: Fixed Status: Resolved (was: Patch Available) > HostCleanup.py to be able to stop processes owned by users or java processes > - > > Key: AMBARI-18852 > URL: https://issues.apache.org/jira/browse/AMBARI-18852 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-18852.patch > > > a new feature to support stopping processes owned by users or java processes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18852) HostCleanup.py to be able to stop processes owned by users or java processes
[ https://issues.apache.org/jira/browse/AMBARI-18852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668483#comment-15668483 ] Di Li commented on AMBARI-18852: pushed to trunk as https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=0e8474fea1de0ed113b50bb89a18e8534f991db5 > HostCleanup.py to be able to stop processes owned by users or java processes > - > > Key: AMBARI-18852 > URL: https://issues.apache.org/jira/browse/AMBARI-18852 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-18852.patch > > > a new feature to support stopping processes owned by users or java processes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18431) Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes.
[ https://issues.apache.org/jira/browse/AMBARI-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668479#comment-15668479 ] Jayush Luniya commented on AMBARI-18431: cc: [~swagle] > Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes. > - > > Key: AMBARI-18431 > URL: https://issues.apache.org/jira/browse/AMBARI-18431 > Project: Ambari > Issue Type: Improvement >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani > Fix For: 2.5.0 > > Attachments: > 0001-Changed-topology-DAG-Fixed-Kafka-Spout-Lag-data-form.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18431) Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes.
[ https://issues.apache.org/jira/browse/AMBARI-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668476#comment-15668476 ] Jayush Luniya commented on AMBARI-18431: [~sriharsha] We are almost about to kickoff a 2.4.2 release and given this is an improvement, it doesnt meet the bar for 2.4.2. We can push this in for 2.5. > Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes. > - > > Key: AMBARI-18431 > URL: https://issues.apache.org/jira/browse/AMBARI-18431 > Project: Ambari > Issue Type: Improvement >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani > Fix For: 2.5.0 > > Attachments: > 0001-Changed-topology-DAG-Fixed-Kafka-Spout-Lag-data-form.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18431) Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes.
[ https://issues.apache.org/jira/browse/AMBARI-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18431: --- Fix Version/s: (was: trunk) 2.5.0 > Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes. > - > > Key: AMBARI-18431 > URL: https://issues.apache.org/jira/browse/AMBARI-18431 > Project: Ambari > Issue Type: Improvement >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani > Fix For: 2.5.0 > > Attachments: > 0001-Changed-topology-DAG-Fixed-Kafka-Spout-Lag-data-form.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18902) Minor typo fix in TimeliveMetricsStore class in AMS
[ https://issues.apache.org/jira/browse/AMBARI-18902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-18902: --- Attachment: AMBARI-18902.patch > Minor typo fix in TimeliveMetricsStore class in AMS > --- > > Key: AMBARI-18902 > URL: https://issues.apache.org/jira/browse/AMBARI-18902 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li >Priority: Trivial > Fix For: trunk > > Attachments: AMBARI-18902.patch > > > Minor typo fix in TimeliveMetricsStore class in AMS -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18902) Minor typo fix in TimeliveMetricsStore class in AMS
[ https://issues.apache.org/jira/browse/AMBARI-18902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-18902: --- Status: Patch Available (was: Open) > Minor typo fix in TimeliveMetricsStore class in AMS > --- > > Key: AMBARI-18902 > URL: https://issues.apache.org/jira/browse/AMBARI-18902 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li >Priority: Trivial > Fix For: trunk > > Attachments: AMBARI-18902.patch > > > Minor typo fix in TimeliveMetricsStore class in AMS -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18902) Minor typo fix in TimeliveMetricsStore class in AMS
Di Li created AMBARI-18902: -- Summary: Minor typo fix in TimeliveMetricsStore class in AMS Key: AMBARI-18902 URL: https://issues.apache.org/jira/browse/AMBARI-18902 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: trunk Reporter: Di Li Assignee: Di Li Priority: Trivial Fix For: trunk Minor typo fix in TimeliveMetricsStore class in AMS -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-18380) For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward compatibility
[
https://issues.apache.org/jira/browse/AMBARI-18380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez resolved AMBARI-18380.
--
Resolution: Duplicate
Dup of AMBARI-18630
> For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward
> compatibility
>
>
> Key: AMBARI-18380
> URL: https://issues.apache.org/jira/browse/AMBARI-18380
> Project: Ambari
> Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Fix For: 2.4.2
>
>
> following properties need to be set
> {code}
> inter.broker.protocol.version=0.9.0.0
> log.message.format.version=0.9.0.0
> {code}
> after upgrade is done we should delte the inter.broker.protocol.version.
> Users should remove log.message.format.version once they update their clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18431) Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes.
[ https://issues.apache.org/jira/browse/AMBARI-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668442#comment-15668442 ] Sriharsha Chintalapani commented on AMBARI-18431: - [~jluniya] any reason for changing the fix version. The patch is tested and reviewed. Can you merge it in? > Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes. > - > > Key: AMBARI-18431 > URL: https://issues.apache.org/jira/browse/AMBARI-18431 > Project: Ambari > Issue Type: Improvement >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani > Fix For: trunk > > Attachments: > 0001-Changed-topology-DAG-Fixed-Kafka-Spout-Lag-data-form.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18380) For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward compatibility
[
https://issues.apache.org/jira/browse/AMBARI-18380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668430#comment-15668430
]
Jayush Luniya commented on AMBARI-18380:
[~afernandez]
Are you fixing this in 2.4.2? Can we move this out to 2.5.0?
> For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward
> compatibility
>
>
> Key: AMBARI-18380
> URL: https://issues.apache.org/jira/browse/AMBARI-18380
> Project: Ambari
> Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Priority: Blocker
> Fix For: 2.4.2
>
>
> following properties need to be set
> {code}
> inter.broker.protocol.version=0.9.0.0
> log.message.format.version=0.9.0.0
> {code}
> after upgrade is done we should delte the inter.broker.protocol.version.
> Users should remove log.message.format.version once they update their clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18380) For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward compatibility
[
https://issues.apache.org/jira/browse/AMBARI-18380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-18380:
---
Assignee: Alejandro Fernandez
> For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward
> compatibility
>
>
> Key: AMBARI-18380
> URL: https://issues.apache.org/jira/browse/AMBARI-18380
> Project: Ambari
> Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Fix For: 2.4.2
>
>
> following properties need to be set
> {code}
> inter.broker.protocol.version=0.9.0.0
> log.message.format.version=0.9.0.0
> {code}
> after upgrade is done we should delte the inter.broker.protocol.version.
> Users should remove log.message.format.version once they update their clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging
[ https://issues.apache.org/jira/browse/AMBARI-18637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668355#comment-15668355 ] Hudson commented on AMBARI-18637: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #329 (See [https://builds.apache.org/job/Ambari-branch-2.5/329/]) AMBARI-18637: Management pack purge option should warn user and ask for (jluniya: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fb056d9c5aa9b383b38cdd59a4b54a3c0fd36852]) * (edit) ambari-server/src/main/python/ambari_server/setupMpacks.py > Management pack purge option should warn user and ask for confirmation before > purging > - > > Key: AMBARI-18637 > URL: https://issues.apache.org/jira/browse/AMBARI-18637 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.4.2 > > Attachments: AMBARI-18637.addendum.patch, AMBARI-18637.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18901) Use "Num of LLAP Node" selected as the driver for LLAP config calculations.
Swapan Shridhar created AMBARI-18901: Summary: Use "Num of LLAP Node" selected as the driver for LLAP config calculations. Key: AMBARI-18901 URL: https://issues.apache.org/jira/browse/AMBARI-18901 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.2 Reporter: Swapan Shridhar Assignee: Swapan Shridhar Priority: Critical Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18846) Custom services should be able to easily specify their own dashboards
[ https://issues.apache.org/jira/browse/AMBARI-18846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-18846: Resolution: Fixed Status: Resolved (was: Patch Available) > Custom services should be able to easily specify their own dashboards > - > > Key: AMBARI-18846 > URL: https://issues.apache.org/jira/browse/AMBARI-18846 > Project: Ambari > Issue Type: Improvement > Components: ambari-admin, ambari-metrics, ambari-server >Affects Versions: trunk, 2.4.0, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18846.patch > > > Currently all dashboards are added directly in under the AMBARI_METRICS > package directory (package/files/grafana-dashboards). > In order for custom services to add dashboards, they need to add the files > directly under that folder. Each time the Ambari server is upgraded, those > files will be lost as the AMBARI_METRICS service definition will be replaced. > This JIRA proposes adding a new directory under the ambari-server/resources. > This will contain both the dashboards and metrics for custom services. > The dashboards here will not be organized by stack. Each service will add a > directory containing their dashboards and will add a metrics file. > resources/dashboards/grafana-dashboards/MY_SERVICE/ > resources/dashboards/service-metrics/MY_SERVICE.txt > The resources/dashboards directory will need to get sync'd to the agents. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18794) Remove PHD stack from Ambari source code
[ https://issues.apache.org/jira/browse/AMBARI-18794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668305#comment-15668305 ] Jayush Luniya commented on AMBARI-18794: Moving out of 2.4.2 > Remove PHD stack from Ambari source code > > > Key: AMBARI-18794 > URL: https://issues.apache.org/jira/browse/AMBARI-18794 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Matt >Assignee: Matt >Priority: Minor > Fix For: trunk, 2.5.0 > > > PHD stack is no longer used. Hence it should be removed from Ambari 2.4+ > branches. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18794) Remove PHD stack from Ambari source code
[ https://issues.apache.org/jira/browse/AMBARI-18794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18794: --- Fix Version/s: (was: 2.4.2) > Remove PHD stack from Ambari source code > > > Key: AMBARI-18794 > URL: https://issues.apache.org/jira/browse/AMBARI-18794 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Matt >Assignee: Matt >Priority: Minor > Fix For: trunk, 2.5.0 > > > PHD stack is no longer used. Hence it should be removed from Ambari 2.4+ > branches. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18770) Service check and Ambari Alerting for RM fails against Yarn with HA and SPNEGO
[ https://issues.apache.org/jira/browse/AMBARI-18770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18770: --- Resolution: Fixed Status: Resolved (was: Patch Available) Resolving since its already committed. > Service check and Ambari Alerting for RM fails against Yarn with HA and > SPNEGO > --- > > Key: AMBARI-18770 > URL: https://issues.apache.org/jira/browse/AMBARI-18770 > Project: Ambari > Issue Type: Bug > Components: ambari-agent, ambari-server >Affects Versions: 2.4.0, 2.4.2 > Environment: Hortonworks HDP 2.5 and HDP 2.4 >Reporter: Greg Senia >Assignee: Attila Magyar > Fix For: 2.4.2 > > Attachments: AMBARI-18770.patch, AMBARI-18770_branch-2.4.patch, > AMBARI-18770_branch-2.5.patch, AMBARI-18770_trunk.patch > > > If both HA and SPNEGO is configured for the cluster, the service check and > ambari Alerting for RM fails for Yarn. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18597) Rename service to "Microsoft R Server" and component to "Microsoft R Node Client"
[ https://issues.apache.org/jira/browse/AMBARI-18597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18597: --- Resolution: Fixed Status: Resolved (was: Patch Available) Looks like its already committed to 2.4.2 as well. > Rename service to "Microsoft R Server" and component to "Microsoft R Node > Client" > - > > Key: AMBARI-18597 > URL: https://issues.apache.org/jira/browse/AMBARI-18597 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Critical > Fix For: trunk, 2.5.0, 2.4.2 > > Attachments: AMBARI-18597-rename-to-node-client.patch > > > Rename service to "Microsoft R Server" and component to "Microsoft R Node > Client" in the Microsoft R management pack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18666) Move HAWQ and PXF RCO from stacks to common-services
[ https://issues.apache.org/jira/browse/AMBARI-18666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668296#comment-15668296 ] Jayush Luniya commented on AMBARI-18666: Moving this out of 2.4.2 as its not a blocker for 2.4.2 > Move HAWQ and PXF RCO from stacks to common-services > > > Key: AMBARI-18666 > URL: https://issues.apache.org/jira/browse/AMBARI-18666 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.5.0, 2.4.2 >Reporter: Matt >Assignee: Matt >Priority: Minor > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18666-trunk-orig.patch > > > Move HAWQ and PXF RCO from stacks to common-services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18666) Move HAWQ and PXF RCO from stacks to common-services
[ https://issues.apache.org/jira/browse/AMBARI-18666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18666: --- Fix Version/s: (was: 2.4.2) > Move HAWQ and PXF RCO from stacks to common-services > > > Key: AMBARI-18666 > URL: https://issues.apache.org/jira/browse/AMBARI-18666 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.5.0, 2.4.2 >Reporter: Matt >Assignee: Matt >Priority: Minor > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18666-trunk-orig.patch > > > Move HAWQ and PXF RCO from stacks to common-services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18431) Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes.
[ https://issues.apache.org/jira/browse/AMBARI-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18431: --- Fix Version/s: (was: 2.4.2) trunk > Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes. > - > > Key: AMBARI-18431 > URL: https://issues.apache.org/jira/browse/AMBARI-18431 > Project: Ambari > Issue Type: Improvement >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani > Fix For: trunk > > Attachments: > 0001-Changed-topology-DAG-Fixed-Kafka-Spout-Lag-data-form.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18578) Grafana fails to start after deployment
[ https://issues.apache.org/jira/browse/AMBARI-18578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18578: --- Fix Version/s: (was: 2.4.2) 2.5.0 > Grafana fails to start after deployment > --- > > Key: AMBARI-18578 > URL: https://issues.apache.org/jira/browse/AMBARI-18578 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > > Noticed this issue in Ambari system tests clusters that run on YCloud, that > Grafana fails to start after deployment with the below error > > > > "stderr" : "Traceback (most recent call last):\n File > \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\", > line 67, in \nAmsGrafana().execute()\n File > \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\", > line 280, in execute\nmethod(env)\n File > \"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py\", > line 46, in start\nuser=params.ams_user\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line > 155, in __init__\nself.env.run()\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", > line 160, in run\nself.run_action(resource, action)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", > line 124, in run_action\nprovider_action()\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\", > line 273, in action_run\ntries=self.resource.tries, > try_sleep=self.resource.try_sleep)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 71, in inner\nresult = function(command, **kwargs)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 93, in checked_call\ntries=tries, try_sleep=try_sleep)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 141, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n File > \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line > 294, in _call\nraise > Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of > '/usr/sbin/ambari-metrics-grafana start' returned 1. Hortonworks > #\nThis is MOTD message, added for testing in qe infra\nStarting > Ambari Metrics Grafana: FAILED", > > > Please find the artifacts for the run [here](http://qelog.hortonworks.com/log > /nat-yc-ambari-2-4-2-0-amb-r7-dmyu-ambari-config-6/test-logs/ambari-config/art > ifacts/screenshots/com.hw.ambari.ui.tests.installer.InstallHadoop/install/_8_2 > 3_23_7_Component__Phoenix_Query_Server__is_not__STARTED__on_host__ctr_e45_1475 > 874954070_0581_01_/lastAvailableRequests.txt) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-18317) ambari-agent script does not check for unset variables. (Leading to chown root:root /)
[
https://issues.apache.org/jira/browse/AMBARI-18317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya resolved AMBARI-18317.
Resolution: Fixed
> ambari-agent script does not check for unset variables. (Leading to chown
> root:root /)
> --
>
> Key: AMBARI-18317
> URL: https://issues.apache.org/jira/browse/AMBARI-18317
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.4.0
> Environment: Ubuntu 14.04
> Hortonworks provided package: ambari-agent 4.2.0.1-1
>Reporter: Ryan Walder
>Assignee: Andrew Onischuk
> Fix For: 2.4.2
>
>
> Using the following config (unchanged from a previous install, so missing
> options relevant to 2.4.0.1) with ambari-agent 2.4.0.1 causes the
> ambari-agent script to chown the entire filesystem as root.
> {noformat}
> [logging]
> syslog_enabled=0
> [agent]
> ping_port=8670
> data_cleanup_max_size_MB=100
> prefix=/var/lib/ambari-agent/data
> cache_dir=/var/lib/ambari-agent/cache
> tolerate_download_failures=true
> parallel_execution=0
> data_cleanup_interval=86400
> tolerate_download_failuresf=false
> data_cleanup_max_age=2592000
> loglevel=INFO
> run_as_user=root
> [server]
> secured_url_port=8441
> hostname=cs-vagrant-hadoop-ambarimaster-01.gel.zone
> url_port=8440
> [services]
> pidLookupPath=/var/run/
> [heartbeat]
> dirs=/etc/hadoop,/etc/hadoop/conf,/etc/hbase,/etc/hcatalog,/etc/hive,/etc/oozie,/etc/sqoop,/etc/ganglia,/var/run/hadoop,/var/run/zookeeper,/var/run/hbase,/var/run/templeton,/var/run/oozie,/var/log/hadoop,/var/log/zookeeper,/var/log/hbase,/var/run/templeton,/var/log/hive
> log_lines_count=300
> state_interval=6
> [security]
> server_crt=ca.crt
> keysdir=/var/lib/ambari-agent/keys
> passphrase_env_var_name=AMBARI_PASSPHRASE
> ryanwalder@ryanwlaptop:~$ vi old
> ryanwalder@ryanwlaptop:~$ vi old
> ryanwalder@ryanwlaptop:~$ vi old
> ryanwalder@ryanwlaptop:~$ cat old
> [logging]
> syslog_enabled=0
> [agent]
> ping_port=8670
> data_cleanup_max_size_MB=100
> prefix=/var/lib/ambari-agent/data
> cache_dir=/var/lib/ambari-agent/cache
> tolerate_download_failures=true
> parallel_execution=0
> data_cleanup_interval=86400
> tolerate_download_failuresf=false
> data_cleanup_max_age=2592000
> loglevel=INFO
> run_as_user=root
> [server]
> secured_url_port=8441
> hostname=cs-vagrant-hadoop-ambarimaster-01.gel.zone
> url_port=8440
> [services]
> pidLookupPath=/var/run/
> [heartbeat]
> dirs=/etc/hadoop,/etc/hadoop/conf,/etc/hbase,/etc/hcatalog,/etc/hive,/etc/oozie,/etc/sqoop,/etc/ganglia,/var/run/hadoop,/var/run/zookeeper,/var/run/hbase,/var/run/templeton,/var/run/oozie,/var/log/hadoop,/var/log/zookeeper,/var/log/hbase,/var/run/templeton,/var/log/hive
> log_lines_count=300
> state_interval=6
> [security]
> server_crt=ca.crt
> keysdir=/var/lib/ambari-agent/keys
> passphrase_env_var_name=AMBARI_PASSPHRASE
> {noformat}
> It looks like the following lines are to blame
> {noformat}
> ambari-sudo.sh chown -R $current_user "$AMBARI_PID_DIR/"
> ambari-sudo.sh mkdir -p "$AMBARI_AGENT_LOG_DIR"
> ambari-sudo.sh chown -R $current_user:$current_group
> "$AMBARI_AGENT_LOG_DIR/"
> {noformat}
> No checking for unset variables in 2016? Top notch.
> http://www.davidpashley.com/articles/writing-robust-shell-scripts/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18317) ambari-agent script does not check for unset variables. (Leading to chown root:root /)
[
https://issues.apache.org/jira/browse/AMBARI-18317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668271#comment-15668271
]
Jayush Luniya commented on AMBARI-18317:
Looks like this is already in 2.4. Resolving JIRA.
commit ec16e4975f03294e2edacbd6884798c0cd5fdd23
Author: Andrew Onishuk
Date: Mon Sep 19 19:37:21 2016 +0300
AMBARI-18360. ambari-agent check for unset variables (AMBARI-18317)
(aonishuk)
> ambari-agent script does not check for unset variables. (Leading to chown
> root:root /)
> --
>
> Key: AMBARI-18317
> URL: https://issues.apache.org/jira/browse/AMBARI-18317
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.4.0
> Environment: Ubuntu 14.04
> Hortonworks provided package: ambari-agent 4.2.0.1-1
>Reporter: Ryan Walder
>Assignee: Andrew Onischuk
> Fix For: 2.4.2
>
>
> Using the following config (unchanged from a previous install, so missing
> options relevant to 2.4.0.1) with ambari-agent 2.4.0.1 causes the
> ambari-agent script to chown the entire filesystem as root.
> {noformat}
> [logging]
> syslog_enabled=0
> [agent]
> ping_port=8670
> data_cleanup_max_size_MB=100
> prefix=/var/lib/ambari-agent/data
> cache_dir=/var/lib/ambari-agent/cache
> tolerate_download_failures=true
> parallel_execution=0
> data_cleanup_interval=86400
> tolerate_download_failuresf=false
> data_cleanup_max_age=2592000
> loglevel=INFO
> run_as_user=root
> [server]
> secured_url_port=8441
> hostname=cs-vagrant-hadoop-ambarimaster-01.gel.zone
> url_port=8440
> [services]
> pidLookupPath=/var/run/
> [heartbeat]
> dirs=/etc/hadoop,/etc/hadoop/conf,/etc/hbase,/etc/hcatalog,/etc/hive,/etc/oozie,/etc/sqoop,/etc/ganglia,/var/run/hadoop,/var/run/zookeeper,/var/run/hbase,/var/run/templeton,/var/run/oozie,/var/log/hadoop,/var/log/zookeeper,/var/log/hbase,/var/run/templeton,/var/log/hive
> log_lines_count=300
> state_interval=6
> [security]
> server_crt=ca.crt
> keysdir=/var/lib/ambari-agent/keys
> passphrase_env_var_name=AMBARI_PASSPHRASE
> ryanwalder@ryanwlaptop:~$ vi old
> ryanwalder@ryanwlaptop:~$ vi old
> ryanwalder@ryanwlaptop:~$ vi old
> ryanwalder@ryanwlaptop:~$ cat old
> [logging]
> syslog_enabled=0
> [agent]
> ping_port=8670
> data_cleanup_max_size_MB=100
> prefix=/var/lib/ambari-agent/data
> cache_dir=/var/lib/ambari-agent/cache
> tolerate_download_failures=true
> parallel_execution=0
> data_cleanup_interval=86400
> tolerate_download_failuresf=false
> data_cleanup_max_age=2592000
> loglevel=INFO
> run_as_user=root
> [server]
> secured_url_port=8441
> hostname=cs-vagrant-hadoop-ambarimaster-01.gel.zone
> url_port=8440
> [services]
> pidLookupPath=/var/run/
> [heartbeat]
> dirs=/etc/hadoop,/etc/hadoop/conf,/etc/hbase,/etc/hcatalog,/etc/hive,/etc/oozie,/etc/sqoop,/etc/ganglia,/var/run/hadoop,/var/run/zookeeper,/var/run/hbase,/var/run/templeton,/var/run/oozie,/var/log/hadoop,/var/log/zookeeper,/var/log/hbase,/var/run/templeton,/var/log/hive
> log_lines_count=300
> state_interval=6
> [security]
> server_crt=ca.crt
> keysdir=/var/lib/ambari-agent/keys
> passphrase_env_var_name=AMBARI_PASSPHRASE
> {noformat}
> It looks like the following lines are to blame
> {noformat}
> ambari-sudo.sh chown -R $current_user "$AMBARI_PID_DIR/"
> ambari-sudo.sh mkdir -p "$AMBARI_AGENT_LOG_DIR"
> ambari-sudo.sh chown -R $current_user:$current_group
> "$AMBARI_AGENT_LOG_DIR/"
> {noformat}
> No checking for unset variables in 2016? Top notch.
> http://www.davidpashley.com/articles/writing-robust-shell-scripts/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-18314) Users page after LDAP sync shows blank
[ https://issues.apache.org/jira/browse/AMBARI-18314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-18314. Resolution: Incomplete > Users page after LDAP sync shows blank > -- > > Key: AMBARI-18314 > URL: https://issues.apache.org/jira/browse/AMBARI-18314 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Shreya Bhat > Fix For: 2.5.0 > > > The network shows 500 Server error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18314) Users page after LDAP sync shows blank
[ https://issues.apache.org/jira/browse/AMBARI-18314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668254#comment-15668254 ] Jayush Luniya commented on AMBARI-18314: [~shreyabh...@gmail.com] There is not enough details on this JIRA. I will go ahead and close this JIRA for now, please reopen if you can repro and provide detailed logs. cc: [~rlevas] > Users page after LDAP sync shows blank > -- > > Key: AMBARI-18314 > URL: https://issues.apache.org/jira/browse/AMBARI-18314 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Shreya Bhat > Fix For: 2.5.0 > > > The network shows 500 Server error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18314) Users page after LDAP sync shows blank
[ https://issues.apache.org/jira/browse/AMBARI-18314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18314: --- Fix Version/s: (was: 2.4.2) 2.5.0 > Users page after LDAP sync shows blank > -- > > Key: AMBARI-18314 > URL: https://issues.apache.org/jira/browse/AMBARI-18314 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Shreya Bhat > Fix For: 2.5.0 > > > The network shows 500 Server error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-15537) Service Level Extensions for Add-On Services
[ https://issues.apache.org/jira/browse/AMBARI-15537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-15537. Resolution: Fixed > Service Level Extensions for Add-On Services > > > Key: AMBARI-15537 > URL: https://issues.apache.org/jira/browse/AMBARI-15537 > Project: Ambari > Issue Type: Epic >Affects Versions: 2.1.0, 2.2.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.4.2 > > > In order to make add-on services self contained we need to support following > extension points > - Upgrade Pack Extensions > - Stack Advisor Extensions > - Role Command Order Extensions. This is covered in AMBARI-9363 (service > level RCO extension) > - Repo Extensions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18724) Add dependency of HSI config 'hive.llap.zk.sm.connectionString' on 'enable_hive_interactive', so as to cover the HDP 2.4 -> 2.5 upgrade case, to get 'hive.llap.zk.sm.co
[ https://issues.apache.org/jira/browse/AMBARI-18724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-18724: - Resolution: Fixed Status: Resolved (was: Patch Available) > Add dependency of HSI config 'hive.llap.zk.sm.connectionString' on > 'enable_hive_interactive', so as to cover the HDP 2.4 -> 2.5 upgrade case, to > get 'hive.llap.zk.sm.connectionString' updated. > > > Key: AMBARI-18724 > URL: https://issues.apache.org/jira/browse/AMBARI-18724 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0, 2.4.2 > > Attachments: AMBARI-18724.patch > > > - After upgrading from HDP 2.4 to 2.5 (which has Hive Server Interactive > (HSI) available for 1st time), the HSI zk connection string > 'hive.llap.zk.sm.connectionString' doesn't get updated with the correct > values, when HSI is made ON. > - The same things works fine on a fresh HDP 2.5 cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18666) Move HAWQ and PXF RCO from stacks to common-services
[ https://issues.apache.org/jira/browse/AMBARI-18666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668244#comment-15668244 ] Jayush Luniya commented on AMBARI-18666: [~mithmatt] What's the latest on this JIRA? Looks like its already committed. Can you close this JIRA or move it out of 2.4.2? > Move HAWQ and PXF RCO from stacks to common-services > > > Key: AMBARI-18666 > URL: https://issues.apache.org/jira/browse/AMBARI-18666 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.5.0, 2.4.2 >Reporter: Matt >Assignee: Matt >Priority: Minor > Fix For: trunk, 2.5.0, 2.4.2 > > Attachments: AMBARI-18666-trunk-orig.patch > > > Move HAWQ and PXF RCO from stacks to common-services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18821) Logsearch support KNOX SSO (with JWT)
[
https://issues.apache.org/jira/browse/AMBARI-18821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-18821:
--
Description:
Add some new configuration properties to ambari and logsearch as well to handle
JWT based authentication: (SSO with KNOX)
{{logsearch.auth.jwt.enabled}}
{{logsearch.auth.jwt.provider_url}}
{{logsearch.auth.jwt.public_key}}
And some more optional properties
{{logsearch.auth.jwt.audiances}}
{{logsearch.auth.jwt.cookie.name}}
{{logsearch.auth.jwt.query.param.original_url}}
was:
Add some new configuration properties to ambari and logsearch as well to handle
JWT based authentication: (SSO with KNOX)
{{logsearch.auth.jwt.enabled}}
{{logsearch.auth.jwt.provider_url}}
{{logsearch.auth.jwt.public_key}}
And some more pptional properties
{{logsearch.auth.jwt.audiances}}
{{logsearch.auth.jwt.cookie.name}}
{{logsearch.auth.jwt.query.param.original_url}}
> Logsearch support KNOX SSO (with JWT)
> -
>
> Key: AMBARI-18821
> URL: https://issues.apache.org/jira/browse/AMBARI-18821
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-18821.patch
>
>
> Add some new configuration properties to ambari and logsearch as well to
> handle JWT based authentication: (SSO with KNOX)
> {{logsearch.auth.jwt.enabled}}
> {{logsearch.auth.jwt.provider_url}}
> {{logsearch.auth.jwt.public_key}}
> And some more optional properties
> {{logsearch.auth.jwt.audiances}}
> {{logsearch.auth.jwt.cookie.name}}
> {{logsearch.auth.jwt.query.param.original_url}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18821) Logsearch support KNOX SSO (with JWT)
[
https://issues.apache.org/jira/browse/AMBARI-18821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-18821:
--
Attachment: (was: AMBARI-18821.patch)
> Logsearch support KNOX SSO (with JWT)
> -
>
> Key: AMBARI-18821
> URL: https://issues.apache.org/jira/browse/AMBARI-18821
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-18821.patch
>
>
> Add some new configuration properties to ambari and logsearch as well to
> handle JWT based authentication: (SSO with KNOX)
> {{logsearch.auth.jwt.enabled}}
> {{logsearch.auth.jwt.provider_url}}
> {{logsearch.auth.jwt.public_key}}
> And some more pptional properties
> {{logsearch.auth.jwt.audiances}}
> {{logsearch.auth.jwt.cookie.name}}
> {{logsearch.auth.jwt.query.param.original_url}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18821) Logsearch support KNOX SSO (with JWT)
[
https://issues.apache.org/jira/browse/AMBARI-18821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-18821:
--
Attachment: AMBARI-18821.patch
> Logsearch support KNOX SSO (with JWT)
> -
>
> Key: AMBARI-18821
> URL: https://issues.apache.org/jira/browse/AMBARI-18821
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-18821.patch, AMBARI-18821.patch
>
>
> Add some new configuration properties to ambari and logsearch as well to
> handle JWT based authentication: (SSO with KNOX)
> {{logsearch.auth.jwt.enabled}}
> {{logsearch.auth.jwt.provider_url}}
> {{logsearch.auth.jwt.public_key}}
> And some more pptional properties
> {{logsearch.auth.jwt.audiances}}
> {{logsearch.auth.jwt.cookie.name}}
> {{logsearch.auth.jwt.query.param.original_url}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16828) Support round-robin scheduling with failover for Sinks with distributed collector
[ https://issues.apache.org/jira/browse/AMBARI-16828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668176#comment-15668176 ] Hudson commented on AMBARI-16828: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See [https://builds.apache.org/job/Ambari-branch-2.5/328/]) AMBARI-16828. Support round-robin scheduling with failover for Sinks (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=954e61ee07416bc20b52bfda84dde5ea57876130]) * (edit) ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSink.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricStore.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/webapp/TimelineWebServices.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/templates/hadoop-metrics2.properties.j2 * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/solr/metrics/SolrAmsClient.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/v2/TimelineMetricHostAggregator.java * (delete) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/availability/TimelineMetricHAControllerTest.java * (edit) ambari-metrics/ambari-metrics-common/pom.xml * (edit) ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsReporter.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/availability/AggregationTaskRunner.java * (delete) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/availability/TimelineMetricHAController.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py * (edit) ambari-metrics/ambari-metrics-kafka-sink/src/test/java/org/apache/hadoop/metrics2/sink/kafka/KafkaTimelineMetricsReporterTest.java * (add) ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/availability/MetricSinkWriteShardStrategy.java * (add) ambari-metrics/ambari-metrics-common/src/test/java/org/apache/hadoop/metrics2/sink/timeline/availability/MetricCollectorHATest.java * (add) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/availability/MetricCollectorHAControllerTest.java * (add) ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/MetricsSinkInitializationException.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricHostAggregator.java * (edit) ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/package/scripts/params.py * (edit) ambari-metrics/ambari-metrics-storm-sink-legacy/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsReporter.java * (add) ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/availability/MetricSinkWriteShardHostnameHashingStrategy.java * (edit) ambari-metrics/ambari-metrics-hadoop-sink/src/main/java/org/apache/hadoop/metrics2/sink/timeline/HadoopTimelineMetricsSink.java * (edit) ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/params_linux.py * (add) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/availability/MetricCollectorHAController.java * (edit) ambari-metrics/ambari-metrics-common/src/test/java/org/apache/hadoop/metrics2/sink/timeline/cache/HandleConnectExceptionTest.java * (edit) ambari-server/src/main/resources/common-services/STORM/0.9.1/package/templates/storm-metrics2.properties.j2 * (edit) ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/templates/hadoop-metrics2-hbase.properties-GANGLIA-MASTER.j2 * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricClusterAggregator.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/AbstractTimelineAggregator.java * (add) ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/availability/Met
[jira] [Commented] (AMBARI-15902) Refactor Metadata manager for supporting distributed collector
[ https://issues.apache.org/jira/browse/AMBARI-15902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668174#comment-15668174 ] Hudson commented on AMBARI-15902: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See [https://builds.apache.org/job/Ambari-branch-2.5/328/]) AMBARI-15902. Refactor Metadata manager for supporting distributed (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=798a70e76eebb71d5b62accbecbb8e5cdeda1d52]) * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/discovery/TimelineMetricMetadataManager.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricConfiguration.java * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-site.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/discovery/TestMetadataManager.java * (add) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/discovery/TestMetadataSync.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/discovery/TimelineMetricMetadataSync.java > Refactor Metadata manager for supporting distributed collector > -- > > Key: AMBARI-15902 > URL: https://issues.apache.org/jira/browse/AMBARI-15902 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.4.1 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.4.1 > > Attachments: AMBARI-15902.patch > > > Presently metadata is served from a write through cache, we need a bounded > cache that gets refreshed periodically to allow sharded writes to succeed. > Additionally the metadata cache needs ability to skip certain metrics, > example: YARN Container metrics with too many unique names using a config. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18517) Changes in upgrade path for Kafka metrics collector hosts config
[ https://issues.apache.org/jira/browse/AMBARI-18517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668171#comment-15668171 ] Hudson commented on AMBARI-18517: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See [https://builds.apache.org/job/Ambari-branch-2.5/328/]) AMBARI-18517 : Changes in upgrade path for Kafka metrics collector hosts (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8431557b21e46c470b49e3071865d27d56e6cc98]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java > Changes in upgrade path for Kafka metrics collector hosts config > > > Key: AMBARI-18517 > URL: https://issues.apache.org/jira/browse/AMBARI-18517 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 3.0.0 > > Attachments: AMBARI-18517.patch, Screen Shot 2016-08-22 at 11.00.37 > AM.png > > > Config change for Kafka was added through AMBARI-18170 (Seen in attached > screensot). This jira is used to track Upgrade path changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17726) ArrayIndexOutOfBounds exception thrown on shard calculation
[
https://issues.apache.org/jira/browse/AMBARI-17726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668170#comment-15668170
]
Hudson commented on AMBARI-17726:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See
[https://builds.apache.org/job/Ambari-branch-2.5/328/])
AMBARI-17726. ArrayIndexOutOfBounds exception thrown on shard (avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a549b43989670ee2c0caa64ff34f03dee90fd884])
* (edit)
ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/AbstractTimelineMetricsSink.java
* (edit)
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/availability/MetricCollectorHAController.java
* (edit)
ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/availability/MetricSinkWriteShardHostnameHashingStrategy.java
* (edit)
ambari-metrics/ambari-metrics-common/src/test/java/org/apache/hadoop/metrics2/sink/timeline/availability/ShardingStrategyTest.java
> ArrayIndexOutOfBounds exception thrown on shard calculation
> ---
>
> Key: AMBARI-17726
> URL: https://issues.apache.org/jira/browse/AMBARI-17726
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-17726.patch
>
>
> {code}
> java.lang.ArrayIndexOutOfBoundsException: -1
> at java.util.ArrayList.elementData(ArrayList.java:418)
> at java.util.ArrayList.get(ArrayList.java:431)
> at
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricSinkWriteShardHostnameHashingStrategy.findCollectorShard(MetricSinkWriteShardHostnameHashingStrategy.java:40)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink$1.get(AbstractTimelineMetricsSink.java:371)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink$1.get(AbstractTimelineMetricsSink.java:368)
> at
> org.apache.hadoop.metrics2.sink.relocated.google.common.base.Suppliers$ExpiringMemoizingSupplier.get(Suppliers.java:192)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:380)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.emitMetrics(AbstractTimelineMetricsSink.java:209)
> at
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.putMetrics(HadoopTimelineMetricsSink.java:315)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:186)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
> at
> org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:134)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17716) AMS HA not working in secure cluster
[
https://issues.apache.org/jira/browse/AMBARI-17716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668168#comment-15668168
]
Hudson commented on AMBARI-17716:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See
[https://builds.apache.org/job/Ambari-branch-2.5/328/])
AMBARI-17716. AMS HA not working in secure cluster. (swagle) (avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=80e12b621ab280317ef5c8a496ed72235022d743])
* (edit)
ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/availability/MetricCollectorHAControllerTest.java
* (edit) ambari-metrics/ambari-metrics-timelineservice/pom.xml
* (edit)
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricConfiguration.java
* (edit)
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/availability/OnlineOfflineStateModelFactory.java
* (edit)
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/availability/AggregationTaskRunner.java
* (edit)
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/availability/MetricCollectorHAController.java
> AMS HA not working in secure cluster
>
>
> Key: AMBARI-17716
> URL: https://issues.apache.org/jira/browse/AMBARI-17716
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-17716.patch
>
>
> Helix not able to connect to Zk while starting up.
> {code}
> 2016-07-13 17:56:41,263 INFO org.apache.helix.manager.zk.ZKHelixManager:
> KeeperState: SyncConnected, zookeeper:State:CONNECTED Timeout:3
> sessionid:0x355e190123e001d local:/10.240.0.32:54434
> remoteserver:ambari-sid-3.c.pramod-thangali.internal/10.240.0.30:2181
> lastZxid:8589
> 935298 xid:9 sent:9 recv:11 queuedpkts:0 pendingresp:0 queuedevents:0
> 2016-07-13 17:57:41,264 ERROR org.apache.helix.manager.zk.ZKHelixManager:
> fail to connect zkserver:
> ambari-sid-1.c.pramod-thangali.internal:2181,ambari-sid-2.c.pramod-thangali.internal:2181,ambari-sid-3.c.pramod-thangali.internal:2181
> in 6ms. expiredSessionId: null, clusterName: ambari-metrics-cluster
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18518) Sinks should not try to read collector hosts from Zk if AMS is in embedded mode
[
https://issues.apache.org/jira/browse/AMBARI-18518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668165#comment-15668165
]
Hudson commented on AMBARI-18518:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See
[https://builds.apache.org/job/Ambari-branch-2.5/328/])
AMBARI-18518 : Sinks should not try to read collector hosts from Zk if
(avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8e212903f5c650ef153b34afd5498b60b5088e80])
* (edit)
ambari-metrics/ambari-metrics-common/src/test/java/org/apache/hadoop/metrics2/sink/timeline/availability/MetricCollectorHATest.java
* (edit)
ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/availability/MetricCollectorHAHelper.java
> Sinks should not try to read collector hosts from Zk if AMS is in embedded
> mode
> ---
>
> Key: AMBARI-18518
> URL: https://issues.apache.org/jira/browse/AMBARI-18518
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 3.0.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18518.patch
>
>
> Currently, an exception is constantly being thrown in sink logs.
> {code}
> 2016-10-03 21:01:06,537 WARN availability.MetricCollectorHAHelper
> (MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(91)) - Unable
> to connect to z
> ookeeper.
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException$ConnectionLossException:
> KeeperErrorCode = ConnectionLoss for /ambari-metrics-cluster
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException.create(KeeperException.java:99)
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException.create(KeeperException.java:51)
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.ZooKeeper.exists(ZooKeeper.java:1045)
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.ZooKeeper.exists(ZooKeeper.java:1073)
> at
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper.findLiveCollectorHostsFromZNode(MetricCollectorHAHelper.java:78)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:344)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.emitMetrics(AbstractTimelineMetricsSink.java:216)
> at
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.putMetrics(HadoopTimelineMetricsSink.java:345)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:186)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
> at
> org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:134)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
> {code}
> After the change
> {code}
> 2016-10-03 21:08:31,494 INFO availability.MetricCollectorHAHelper
> (MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(80)) -
> /ambari-metrics-cluster znode does not exist. Skipping requesting live
> instances from zookeeper
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18171) AMS, Accumulo, Hive metrics do not show up in AMS HA clusters.
[ https://issues.apache.org/jira/browse/AMBARI-18171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668130#comment-15668130 ] Hudson commented on AMBARI-18171: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See [https://builds.apache.org/job/Ambari-branch-2.5/328/]) AMBARI-18171. AMS, Accumulo, Hive metrics do not show up in AMS HA (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a105d582cf5bf042d43fbfc98e5343a1074e315e]) * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/templates/hadoop-metrics2-llapdaemon.j2 * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/templates/hadoop-metrics2-hbase.properties.j2 * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/templates/hadoop-metrics2-hiveserver2.properties.j2 * (edit) ambari-server/src/main/resources/common-services/ACCUMULO/1.6.1.2.2.0/package/templates/hadoop-metrics2-accumulo.properties.j2 * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/templates/hadoop-metrics2-llaptaskscheduler.j2 * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/templates/hadoop-metrics2-hivemetastore.properties.j2 > AMS, Accumulo, Hive metrics do not show up in AMS HA clusters. > -- > > Key: AMBARI-18171 > URL: https://issues.apache.org/jira/browse/AMBARI-18171 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: trunk >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-18171.patch > > > There is an issue in the jinja template that causes the the metrics collector > protocol to be duplicated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16834) Any start command fails if AMS is installed.
[ https://issues.apache.org/jira/browse/AMBARI-16834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668161#comment-15668161 ] Hudson commented on AMBARI-16834: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See [https://builds.apache.org/job/Ambari-branch-2.5/328/]) AMBARI-16834. Any start command fails if AMS is installed. (aonischuk (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2845140b070da184f91e375c9da0955a546a58f9]) * (edit) ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/package/scripts/params.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/templates/hadoop-metrics2.properties.j2 * (edit) ambari-agent/src/test/python/ambari_agent/TestRecoveryManager.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py > Any start command fails if AMS is installed. > > > Key: AMBARI-16834 > URL: https://issues.apache.org/jira/browse/AMBARI-16834 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Labels: ambari-metrics, ambari-server > Fix For: 2.5.0 > > Attachments: AMBARI-16834.patch > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py", > line 39, in > BeforeStartHook().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 254, in execute > method(env) > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py", > line 28, in hook > import params > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py", > line 145, in > metric_collector_hosts += host + ':' + metric_collector_port + ',' > TypeError: unsupported operand type(s) for +=: 'NoneType' and 'str' > Error: Error: Unable to run the custom hook script ['/usr/bin/python', > '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py', > 'START', '/var/lib/ambari-agent/data/command-9.json', > '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START', > '/var/lib/ambari-agent/data/structured-out-9.json', 'INFO', > '/var/lib/ambari-agent/tmp'] > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15623) Support distributed aggregation for multiple AMS instances
[ https://issues.apache.org/jira/browse/AMBARI-15623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668159#comment-15668159 ] Hudson commented on AMBARI-15623: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See [https://builds.apache.org/job/Ambari-branch-2.5/328/]) AMBARI-15623. Support distributed aggregation for multiple AMS (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=14a4f97082045969702e3725a318e2a38639a3c3]) * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricAggregatorFactory.java * (add) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/availability/CheckpointManager.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricAggregator.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-env.xml * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/v2/TimelineMetricClusterAggregator.java * (edit) ambari-metrics/ambari-metrics-timelineservice/pom.xml * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/DefaultPhoenixDataSource.java * (add) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/availability/AggregationTaskRunner.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/v2/TimelineMetricHostAggregator.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/webapp/TimelineWebServices.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/ITPhoenixHBaseAccessor.java * (add) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/availability/TimelineMetricHAControllerTest.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TestTimelineMetricStore.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/AbstractTimelineAggregator.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/AbstractTimelineAggregatorTest.java * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/metainfo.xml * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricClusterAggregatorSecondTest.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricClusterAggregator.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricClusterAggregatorSecond.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricHostAggregator.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricStore.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricConfiguration.java * (add) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/availability/TimelineMetricHAController.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricStore.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/tim
[jira] [Commented] (AMBARI-18487) Test and refine Collector writes w.r.t sharing and timeouts
[ https://issues.apache.org/jira/browse/AMBARI-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668157#comment-15668157 ] Hudson commented on AMBARI-18487: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See [https://builds.apache.org/job/Ambari-branch-2.5/328/]) AMBARI-18487 : Test and refine Collector writes w.r.t sharing and (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=abd19c61e063a3918b71df6321255dd1c94c352d]) * (edit) ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/AbstractTimelineMetricsSink.java * (edit) ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/config_reader.py * (edit) ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/blacklisted_set.py * (edit) ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/availability/MetricCollectorHAHelper.java > Test and refine Collector writes w.r.t sharing and timeouts > --- > > Key: AMBARI-18487 > URL: https://issues.apache.org/jira/browse/AMBARI-18487 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18487-trunk.patch > > > Change metric monitor sharding strategy to hostname based. > Fix issues in AbstractTimelineMetricSink > Change Sink Zk retry policy to BoundedExponentialBackoffRetry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18851) Collector host refresh in Ambari Server is not working in single Metrics collector deployments.
[ https://issues.apache.org/jira/browse/AMBARI-18851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668151#comment-15668151 ] Hudson commented on AMBARI-18851: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See [https://builds.apache.org/job/Ambari-branch-2.5/328/]) AMBARI-18851 : Collector host refresh in Ambari Server is not working in (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b33c4fcf45c8438bdd054f298c5ebc0bc59c6afb]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsCollectorHAClusterState.java > Collector host refresh in Ambari Server is not working in single Metrics > collector deployments. > --- > > Key: AMBARI-18851 > URL: https://issues.apache.org/jira/browse/AMBARI-18851 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18851.patch > > > Collector host refresh in Ambari Server is not working in single Metrics > collector deployments. > STR > 1. Deploy Ambari with 1 Metrics collector instance. > 2. Stop Metrics Collector. > 3. Start Metrics collector after a few minutes. > 4. Metrics are not displayed on Ambari, though they show up on Grafana. > BUG > AmbariServer Metrics Collector HA State component does not refresh collector > host if current collector host is null. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16991) Fix metric sink
[ https://issues.apache.org/jira/browse/AMBARI-16991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668147#comment-15668147 ] Hudson commented on AMBARI-16991: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See [https://builds.apache.org/job/Ambari-branch-2.5/328/]) AMBARI-16991 : Fix metric sink. (Miklos Gergely via avijayan) (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fd42b6a2a7b75667dd63fa7963d41eda2ca56393]) * (edit) ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/AbstractTimelineMetricsSink.java > Fix metric sink > --- > > Key: AMBARI-16991 > URL: https://issues.apache.org/jira/browse/AMBARI-16991 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.1 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: trunk > > Attachments: AMBARI-16991.patch > > > After a recent change the AbstractTimelineMetricsSink class has an abstract > function called getZookeeperQuorum(). If the extending class is returning > null, then the sink is not working (neither does it if it returns a valid > zookeeper connection string). Fixed the first issue, now it is working > without a zookeeper connect string. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17080) Support Storm 1.0 in Ambari Metrics for Storm
[ https://issues.apache.org/jira/browse/AMBARI-17080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668121#comment-15668121 ] Hudson commented on AMBARI-17080: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See [https://builds.apache.org/job/Ambari-branch-2.5/328/]) AMBARI-17080 Support Storm 1.0 in Ambari Metrics for Storm (additional (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2b2ad27f0df16b6383f91e080c2d3fb012c33f34]) * (edit) ambari-metrics/ambari-metrics-common/pom.xml > Support Storm 1.0 in Ambari Metrics for Storm > - > > Key: AMBARI-17080 > URL: https://issues.apache.org/jira/browse/AMBARI-17080 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim >Assignee: Dmytro Sen > Fix For: 2.4.0 > > Attachments: AMBARI-17080-trunk_6.patch, AMBARI-17080-v1.patch, > AMBARI-17080-v2.patch, AMBARI-17080-v3.patch > > > Since there was package name change on Apache Storm 1.0.0, Ambari Metrics > Reporter / Sink for Storm will not work when Ambari supports Apache Storm > 1.0.0 or upper. > This issue is for addressing this. > Please note that it will incur compile failure unless Ambari Metrics pom file > depends on Storm 1.x version, so decision for version of Storm should be made > first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18362) Update sinks to read multiple collector hostnames from configs
[ https://issues.apache.org/jira/browse/AMBARI-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668144#comment-15668144 ] Hudson commented on AMBARI-18362: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See [https://builds.apache.org/job/Ambari-branch-2.5/328/]) AMBARI-18362 : Update sinks to read multiple collector hostnames from (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0d01ab25857a3b073f7cc78a508ed41d5436f069]) * (edit) ambari-server/src/main/resources/common-services/ACCUMULO/1.6.1.2.2.0/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/package/scripts/flume.py * (edit) ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/templates/hadoop-metrics2-llapdaemon.j2 * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/templates/hadoop-metrics2-llaptaskscheduler.j2 * (edit) ambari-server/src/main/resources/common-services/KAFKA/0.8.1/configuration/kafka-broker.xml * (edit) ambari-server/src/main/resources/common-services/STORM/0.9.1/package/templates/storm-metrics2.properties.j2 * (edit) ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/package/templates/flume-metrics2.properties.j2 * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/solr/metrics/SolrAmsClient.java * (edit) ambari-metrics/ambari-metrics-hadoop-sink/src/main/java/org/apache/hadoop/metrics2/sink/timeline/HadoopTimelineMetricsSink.java * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hadoop-metrics2.properties.xml * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/templates/hadoop-metrics2-hiveserver2.properties.j2 * (edit) ambari-metrics/ambari-metrics-storm-sink-legacy/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsReporter.java * (edit) ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/templates/hadoop-metrics2-hbase.properties-GANGLIA-MASTER.j2 * (edit) ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/AbstractTimelineMetricsSink.java * (edit) ambari-metrics/ambari-metrics-hadoop-sink/src/test/java/org/apache/hadoop/metrics2/sink/timeline/HadoopTimelineMetricsSinkTest.java * (edit) ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/templates/hadoop-metrics2-hbase.properties-GANGLIA-RS.j2 * (edit) ambari-metrics/ambari-metrics-flume-sink/src/main/java/org/apache/hadoop/metrics2/sink/flume/FlumeTimelineMetricsSink.java * (edit) ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSink.java * (edit) ambari-metrics/ambari-metrics-storm-sink-legacy/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSink.java * (edit) ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsReporter.java * (edit) ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/templates/hadoop-metrics2.properties.j2 * (edit) ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/params_linux.py * (edit) ambari-metrics/ambari-metrics-common/src/test/java/org/apache/hadoop/metrics2/sink/timeline/cache/HandleConnectExceptionTest.java * (edit) ambari-server/src/main/resources/common-services/STORM/0.9.1/package/templates/config.yaml.j2 * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/templates/hadoop-metrics2-hbase.properties.j2 * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py * (edit) ambari-metrics/ambari-metrics-common/src/test/java/org/apache/hadoop/metrics2/sink/timeline/availability/MetricCollectorHATest.java * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/templates/hadoop-metrics2-hivemetastore.properties.j2 * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py * (edit) ambari-metrics/ambari-metrics-kafka-sink/src/main/java/org/apache/hadoop/metrics2/sink/kafka/KafkaTimelineMetricsReporter.java * (edit) ambari-server/src/main/resources/common-services/ACCUMULO/1.6.1.2.2.0/package/templates/hadoop-metrics2-accumulo.properties.j2 * (edit) ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/kafka.py AMBARI-18362 : Update sinks
[jira] [Commented] (AMBARI-17184) HBase doesn't start because of lacking of variable
[
https://issues.apache.org/jira/browse/AMBARI-17184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668139#comment-15668139
]
Hudson commented on AMBARI-17184:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See
[https://builds.apache.org/job/Ambari-branch-2.5/328/])
AMBARI-17184. HBase doesn't start because of lacking of variable. (avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=23a23a5e2d77dac00b036634cf114138f0f01bae])
* (edit)
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/templates/hadoop-metrics2-hbase.properties-GANGLIA-RS.j2
> HBase doesn't start because of lacking of variable
> --
>
> Key: AMBARI-17184
> URL: https://issues.apache.org/jira/browse/AMBARI-17184
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
> Environment: CentOS6.5
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Critical
> Attachments: AMBARI-17184.1.patch, AMBARI-17184.patch
>
>
> When we wanted to restart HBase, we got an error
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_master.py",
> line 159, in
> HbaseMaster().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 257, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 686, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_master.py",
> line 86, in start
> self.configure(env) # for security
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_master.py",
> line 41, in configure
> hbase(name='master')
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase.py",
> line 166, in hbase
> tag = 'GANGLIA-MASTER' if name == 'master' else 'GANGLIA-RS'
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase.py",
> line 233, in hbase_TemplateConfig
> template_tag = tag
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/template_config.py",
> line 46, in action_create
> content = Template(template_name,
> extra_imports=self.resource.extra_imports)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 123, in action_create
> content = self._get_content()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 160, in _get_content
> return content()
> File "/usr/lib/python2.6/site-packages/resource_management/core/source.py",
> line 51, in __call__
> return self.get_content()
> File "/usr/lib/python2.6/site-packages/resource_management/core/source.py",
> line 142, in get_content
> rendered = self.template.render(self.context)
> File "/usr/lib/python2.6/site-packages/ambari_jinja2/environment.py", line
> 891, in render
> return self.environment.handle_exception(exc_info, True)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/templates/hadoop-metrics2-hbase.properties-GANGLIA-MASTER.j2",
> line 76, in top-level template code
> hbase.sink.timeline.truststore.password = {{metric_truststore_password}}
> ambari_jinja2.exceptions.UndefinedError: 'metric_collector_hosts' is undefined
> {code}
> We should define {{metric_collector_hosts}} in
> ambari/ambari-server/src/main/resources/common-services/HBASE
[jira] [Commented] (AMBARI-18265) Make sure AMS embedded works after AMS HA changes
[ https://issues.apache.org/jira/browse/AMBARI-18265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668135#comment-15668135 ] Hudson commented on AMBARI-18265: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See [https://builds.apache.org/job/Ambari-branch-2.5/328/]) AMBARI-18265. Make sure AMS embedded works after AMS HA changes. (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2b86690da4646dcf804a90fe5f02728e723e1890]) * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricStore.java > Make sure AMS embedded works after AMS HA changes > - > > Key: AMBARI-18265 > URL: https://issues.apache.org/jira/browse/AMBARI-18265 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: trunk >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Fix For: trunk > > Attachments: AMBARI-18265.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18199) Wrong hostname in timeline.metrics.service.webapp.address breaks AMS HA
[
https://issues.apache.org/jira/browse/AMBARI-18199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668137#comment-15668137
]
Hudson commented on AMBARI-18199:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See
[https://builds.apache.org/job/Ambari-branch-2.5/328/])
AMBARI-18199. Wrong hostname in timeline.metrics.service.webapp.address
(avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0e75b99d1f6dd8515d9acbd898ca29d6a9312288])
* (edit)
ambari-server/src/test/python/stacks/2.2/configs/journalnode-upgrade.json
* (edit)
ambari-server/src/main/resources/stacks/HDPWIN/2.1/hooks/before-START/scripts/params.py
* (edit)
ambari-server/src/test/python/stacks/2.2/configs/journalnode-upgrade-hdfs-secure.json
* (edit) ambari-agent/src/test/python/ambari_agent/TestAlerts.py
* (edit)
ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/params.py
* (edit)
ambari-server/src/test/python/stacks/2.2/configs/ranger-admin-upgrade.json
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
* (edit) ambari-server/src/test/python/stacks/2.3/configs/ats_1_5.json
* (edit) ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py
* (edit)
ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/package/scripts/params.py
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-site.xml
* (add) ambari-common/src/main/python/ambari_commons/ambari_metrics_helper.py
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_metrics_deviation.py
* (edit)
ambari-server/src/main/resources/common-services/ACCUMULO/1.6.1.2.2.0/package/scripts/params.py
* (edit)
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/params_linux.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/configs/default.json
* (edit)
contrib/views/slider/src/main/java/org/apache/ambari/view/slider/SliderAppsViewControllerImpl.java
* (edit)
ambari-server/src/test/python/stacks/2.0.6/configs/default_ams_embedded.json
* (edit)
ambari-server/src/test/python/stacks/2.0.6/HDFS/test_alert_metrics_deviation.py
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py
* (edit) ambari-server/src/test/python/stacks/2.5/configs/hsi_default.json
* (edit)
ambari-server/src/test/python/stacks/2.0.6/configs/default_with_bucket.json
* (edit)
ambari-server/src/test/python/stacks/2.2/configs/ranger-usersync-upgrade.json
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
* (edit)
ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/params_linux.py
* (edit)
ambari-server/src/test/python/stacks/2.0.6/configs/default_hive_non_hdfs.json
> Wrong hostname in timeline.metrics.service.webapp.address breaks AMS HA
> ---
>
> Key: AMBARI-18199
> URL: https://issues.apache.org/jira/browse/AMBARI-18199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18199.patch, AMBARI-18199_2.patch
>
>
> On adding additional Collector the webapp address contains wrong hostname.
> {noformat}
> java.net.BindException: Port in use: ambari-sid-5.com:6188
> at
> org.apache.hadoop.http.HttpServer2.openListeners(HttpServer2.java:919)
> at org.apache.hadoop.http.HttpServer2.start(HttpServer2.java:856)
> at
> org.apache.hadoop.yarn.webapp.WebApps$Builder.start(WebApps.java:374)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.startWebApp(ApplicationHistoryServer.java:180)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceStart(ApplicationHistoryServer.java:92)
> at
> org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:138)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:147)
> Caused by: java.net.BindException: Cannot assign req
[jira] [Commented] (AMBARI-18012) Metrics Sink unable to connect to zookeeper to locate collector host.
[
https://issues.apache.org/jira/browse/AMBARI-18012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668132#comment-15668132
]
Hudson commented on AMBARI-18012:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See
[https://builds.apache.org/job/Ambari-branch-2.5/328/])
AMBARI-18012 : AMS Metrics Sink unable to connect to zookeeper to locate
(avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=47e8ff49a3adc146344ce234ca9cfad4b4506930])
* (edit)
ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/availability/MetricCollectorHAHelper.java
> Metrics Sink unable to connect to zookeeper to locate collector host.
> -
>
> Key: AMBARI-18012
> URL: https://issues.apache.org/jira/browse/AMBARI-18012
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18012.patch
>
>
> Test and validate sink fallback connect to ZK for finding collector
> {code}
> 2016-07-14 20:37:01,212 INFO timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:findPreferredCollectHost(353)) - Collector
> ambari-sid-5.c.pramod-thangali.internal is not longer live. Removing it from
> list of know live collector hosts : []
> 2016-07-14 20:37:03,213 WARN availability.MetricCollectorHAHelper
> (MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(83)) - Unable
> to connect to zookeeper.
> java.lang.IllegalStateException: Client is not started
> at
> org.apache.hadoop.metrics2.sink.relocated.google.common.base.Preconditions.checkState(Preconditions.java:149)
> at
> org.apache.hadoop.metrics2.sink.relocated.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
> at
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper$1.call(MetricCollectorHAHelper.java:77)
> at
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper$1.call(MetricCollectorHAHelper.java:74)
> at
> org.apache.hadoop.metrics2.sink.relocated.curator.RetryLoop.callWithRetry(RetryLoop.java:107)
> at
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper.findLiveCollectorHostsFromZNode(MetricCollectorHAHelper.java:74)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:363)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.emitMetrics(AbstractTimelineMetricsSink.java:209)
> at
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.putMetrics(HadoopTimelineMetricsSink.java:315)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:186)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
> at
> org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:134)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
> 2016-07-14 20:37:03,245 WARN timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:findLiveCollectorHostsFromKnownCollector(433))
> - Unable to conne
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18170) Kafka Metrics do not show up in AMS HA enabled cluster
[ https://issues.apache.org/jira/browse/AMBARI-18170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668124#comment-15668124 ] Hudson commented on AMBARI-18170: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See [https://builds.apache.org/job/Ambari-branch-2.5/328/]) AMBARI-18170 : Kafka Metrics do not show up in AMS HA enabled cluster. (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a7f9090a349f1a11460e114e1bf9066b7267201e]) * (edit) ambari-server/src/test/python/stacks/2.2/configs/ranger-admin-upgrade.json * (edit) ambari-web/app/assets/data/stacks/HDP-2.2/configurations.json * (edit) ambari-metrics/ambari-metrics-kafka-sink/src/test/java/org/apache/hadoop/metrics2/sink/kafka/KafkaTimelineMetricsReporterTest.java * (edit) ambari-server/src/main/resources/common-services/KAFKA/0.8.1/configuration/kafka-broker.xml * (edit) ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/kafka.py * (edit) ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/params.py * (edit) ambari-metrics/ambari-metrics-kafka-sink/src/main/java/org/apache/hadoop/metrics2/sink/kafka/KafkaTimelineMetricsReporter.java * (edit) ambari-server/src/test/python/stacks/2.2/configs/ranger-usersync-upgrade.json > Kafka Metrics do not show up in AMS HA enabled cluster > -- > > Key: AMBARI-18170 > URL: https://issues.apache.org/jira/browse/AMBARI-18170 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: trunk >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-18170-2.patch > > > No kafka metrics are seen in trunk deployments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging
[ https://issues.apache.org/jira/browse/AMBARI-18637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668037#comment-15668037 ] Sumit Mohanty commented on AMBARI-18637: Addendum patch looks good. > Management pack purge option should warn user and ask for confirmation before > purging > - > > Key: AMBARI-18637 > URL: https://issues.apache.org/jira/browse/AMBARI-18637 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.4.2 > > Attachments: AMBARI-18637.addendum.patch, AMBARI-18637.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging
[ https://issues.apache.org/jira/browse/AMBARI-18637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18637: --- Attachment: AMBARI-18637.addendum.patch > Management pack purge option should warn user and ask for confirmation before > purging > - > > Key: AMBARI-18637 > URL: https://issues.apache.org/jira/browse/AMBARI-18637 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.4.2 > > Attachments: AMBARI-18637.addendum.patch, AMBARI-18637.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18900) Zookeeper service check fails after deployment
Dhanya Balasundaran created AMBARI-18900:
Summary: Zookeeper service check fails after deployment
Key: AMBARI-18900
URL: https://issues.apache.org/jira/browse/AMBARI-18900
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.5.0
Reporter: Dhanya Balasundaran
Fix For: 2.5.0
Zookeeper service check fails after deployment with below error
{code}
:WARN No appenders could be found for logger
(org.apache.zookeeper.ZooKeeper).\nlog4j:WARN Please initialize the log4j
system properly.\nlog4j:WARN See
http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.\nWelcome
to ZooKeeper!\nJLine support is enabled\n[zk: :2181(CONNECTING) 0] delete
/zk_smoketest\n\nWATCHER::\n\nWatchedEvent state:SyncConnected type:None
path:null\n\nWATCHER::\n\nWatchedEvent state:SaslAuthenticated type:None
path:null\n[zk: :2181(CONNECTED) 1] Zookeeper Smoke Test: Failed"
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18889) ambari-server should use persisted status of the stage and request for computation when queried
[ https://issues.apache.org/jira/browse/AMBARI-18889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-18889: -- Summary: ambari-server should use persisted status of the stage and request for computation when queried (was: ambari-server should use persisted status of the stage and request for computation) > ambari-server should use persisted status of the stage and request for > computation when queried > --- > > Key: AMBARI-18889 > URL: https://issues.apache.org/jira/browse/AMBARI-18889 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18425) Support PAM as an authentication option for Ranger in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667921#comment-15667921 ] Shi Wang commented on AMBARI-18425: --- This patch adds an authentication option "PAM" in ambari for ranger user login since RANGER-842 supports PAM authentication. How this patch works: 1. If user select "PAM" from Ranger authentication method, during ranger service restart, it will create two new pam file under either /etc/pam.d or /etc/pam.conf according to the pam version on the operating system. And ranger-admin module will be used for ranger PAM authentication, ranger-remote module is for remote user login. 2. By default, the setting in these two PAM file is: authsufficientpam_unix.so authsufficientpam_sss.so account sufficientpam_unix.so account sufficientpam_sss.so This default setting will allow user authenticate either against unix or sssd, sssd could be configured with different backends such as ldap, AD, FreeAPI... User could also configure the pam file as needed by directly modifying the pam file. 3. One thing needs to be pointed out is if using pam_unix.so module, ranger-admin must be started as root user, because it will look up password in /etc/show file and it is only readable by root. > Support PAM as an authentication option for Ranger in Ambari > > > Key: AMBARI-18425 > URL: https://issues.apache.org/jira/browse/AMBARI-18425 > Project: Ambari > Issue Type: Task > Components: ambari-server, ambari-web >Affects Versions: trunk >Reporter: Shi Wang >Assignee: Shi Wang > Labels: security > Fix For: trunk > > Attachments: > 0001-AMBARI-18425-Support-PAM-as-an-authentication-option.patch > > > Ranger-842 has added PAM support for ranger, we need to add this part to > ambari, to do automatic setup for ranger to use PAM authentication. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18866) Stack advisor should limit call history it preserves
[ https://issues.apache.org/jira/browse/AMBARI-18866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-18866: --- Attachment: (was: AMBARI-18866.patch) > Stack advisor should limit call history it preserves > > > Key: AMBARI-18866 > URL: https://issues.apache.org/jira/browse/AMBARI-18866 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-18866.patch > > > Today stack advisor uses a monotonically increasing id for each call when it > creates a local folder. This is reset only when Ambari Server is restarted. > For large clusters each call may produce 10-12 MB of files and it will result > in eventual disk space issue as there is no limit to how long call history is > preserved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18866) Stack advisor should limit call history it preserves
[ https://issues.apache.org/jira/browse/AMBARI-18866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-18866: --- Status: Patch Available (was: Open) > Stack advisor should limit call history it preserves > > > Key: AMBARI-18866 > URL: https://issues.apache.org/jira/browse/AMBARI-18866 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-18866.patch > > > Today stack advisor uses a monotonically increasing id for each call when it > creates a local folder. This is reset only when Ambari Server is restarted. > For large clusters each call may produce 10-12 MB of files and it will result > in eventual disk space issue as there is no limit to how long call history is > preserved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18866) Stack advisor should limit call history it preserves
[ https://issues.apache.org/jira/browse/AMBARI-18866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-18866: --- Attachment: AMBARI-18866.patch > Stack advisor should limit call history it preserves > > > Key: AMBARI-18866 > URL: https://issues.apache.org/jira/browse/AMBARI-18866 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-18866.patch > > > Today stack advisor uses a monotonically increasing id for each call when it > creates a local folder. This is reset only when Ambari Server is restarted. > For large clusters each call may produce 10-12 MB of files and it will result > in eventual disk space issue as there is no limit to how long call history is > preserved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18866) Stack advisor should limit call history it preserves
[ https://issues.apache.org/jira/browse/AMBARI-18866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-18866: --- Status: Open (was: Patch Available) Will attach a new patch with fix for the Test case failure > Stack advisor should limit call history it preserves > > > Key: AMBARI-18866 > URL: https://issues.apache.org/jira/browse/AMBARI-18866 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-18866.patch > > > Today stack advisor uses a monotonically increasing id for each call when it > creates a local folder. This is reset only when Ambari Server is restarted. > For large clusters each call may produce 10-12 MB of files and it will result > in eventual disk space issue as there is no limit to how long call history is > preserved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18836) Remove group readable from hdfs headless keytab
[ https://issues.apache.org/jira/browse/AMBARI-18836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667873#comment-15667873 ] Shi Wang commented on AMBARI-18836: --- Hi [~lpuskas] [~aonishuk] Do you have any suggestion on this issue? > Remove group readable from hdfs headless keytab > --- > > Key: AMBARI-18836 > URL: https://issues.apache.org/jira/browse/AMBARI-18836 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Shi Wang >Assignee: Shi Wang > Fix For: trunk > > Attachments: > 0001-AMBARI-18836-Remove-group-readable-from-hdfs-headles.patch > > > The Smoke and “Headless” Service users are used by Ambari to perform service > “smoke” checks and run alert health checks. > The permission for hdfs.headless.keytab is 440. But it will cause security > concern to allow other service user in hadoop group to kinit hdfs headless > principal using hdfs.headless.keytab. In this way, other service user could > "pretend" to be hdfs user and be granted hdfs user's authorities. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18899) Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart
[ https://issues.apache.org/jira/browse/AMBARI-18899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18899: Fix Version/s: 2.5.0 > Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for > restart > > > Key: AMBARI-18899 > URL: https://issues.apache.org/jira/browse/AMBARI-18899 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: 2.5.0 > > Attachments: AMBARI-18899.patch > > > I think not marking HDFS as restart required when Ambari upgrades is a good > goal. > In general its a difficult to get it right for all services. > * hadoop.security.key.provider.path > * dfs.encryption.key.provider.uri > These two are removed by stack advisor when RANGER KMS does not exist. We > should find out why it got added on Ambari upgrade. This seems like a bug to > me. > * namenode_backup_dir -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18899) Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart
[ https://issues.apache.org/jira/browse/AMBARI-18899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18899: Affects Version/s: 2.4.2 > Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for > restart > > > Key: AMBARI-18899 > URL: https://issues.apache.org/jira/browse/AMBARI-18899 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: 2.5.0 > > Attachments: AMBARI-18899.patch > > > I think not marking HDFS as restart required when Ambari upgrades is a good > goal. > In general its a difficult to get it right for all services. > * hadoop.security.key.provider.path > * dfs.encryption.key.provider.uri > These two are removed by stack advisor when RANGER KMS does not exist. We > should find out why it got added on Ambari upgrade. This seems like a bug to > me. > * namenode_backup_dir -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18899) Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart
[ https://issues.apache.org/jira/browse/AMBARI-18899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18899: Status: Patch Available (was: Open) > Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for > restart > > > Key: AMBARI-18899 > URL: https://issues.apache.org/jira/browse/AMBARI-18899 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Attachments: AMBARI-18899.patch > > > I think not marking HDFS as restart required when Ambari upgrades is a good > goal. > In general its a difficult to get it right for all services. > * hadoop.security.key.provider.path > * dfs.encryption.key.provider.uri > These two are removed by stack advisor when RANGER KMS does not exist. We > should find out why it got added on Ambari upgrade. This seems like a bug to > me. > * namenode_backup_dir -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18899) Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart
[ https://issues.apache.org/jira/browse/AMBARI-18899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18899: Attachment: AMBARI-18899.patch > Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for > restart > > > Key: AMBARI-18899 > URL: https://issues.apache.org/jira/browse/AMBARI-18899 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Attachments: AMBARI-18899.patch > > > I think not marking HDFS as restart required when Ambari upgrades is a good > goal. > In general its a difficult to get it right for all services. > * hadoop.security.key.provider.path > * dfs.encryption.key.provider.uri > These two are removed by stack advisor when RANGER KMS does not exist. We > should find out why it got added on Ambari upgrade. This seems like a bug to > me. > * namenode_backup_dir -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18899) Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart
[ https://issues.apache.org/jira/browse/AMBARI-18899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18899: Component/s: ambari-server > Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for > restart > > > Key: AMBARI-18899 > URL: https://issues.apache.org/jira/browse/AMBARI-18899 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Attachments: AMBARI-18899.patch > > > I think not marking HDFS as restart required when Ambari upgrades is a good > goal. > In general its a difficult to get it right for all services. > * hadoop.security.key.provider.path > * dfs.encryption.key.provider.uri > These two are removed by stack advisor when RANGER KMS does not exist. We > should find out why it got added on Ambari upgrade. This seems like a bug to > me. > * namenode_backup_dir -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18899) Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart
Dmitry Lysnichenko created AMBARI-18899: --- Summary: Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart Key: AMBARI-18899 URL: https://issues.apache.org/jira/browse/AMBARI-18899 Project: Ambari Issue Type: Bug Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Attachments: AMBARI-18899.patch I think not marking HDFS as restart required when Ambari upgrades is a good goal. In general its a difficult to get it right for all services. * hadoop.security.key.provider.path * dfs.encryption.key.provider.uri These two are removed by stack advisor when RANGER KMS does not exist. We should find out why it got added on Ambari upgrade. This seems like a bug to me. * namenode_backup_dir -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18876) Remove old UpgradeCatalog and tests
[
https://issues.apache.org/jira/browse/AMBARI-18876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667785#comment-15667785
]
Hadoop QA commented on AMBARI-18876:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12838982/AMBARI-18876.patch.1
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 3 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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.upgrade.UpgradeCatalogTest
org.apache.ambari.server.controller.metrics.JMXPropertyProviderTest
org.apache.ambari.server.state.svccomphost.ServiceComponentHostTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9286//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9286//console
This message is automatically generated.
> Remove old UpgradeCatalog and tests
> ---
>
> Key: AMBARI-18876
> URL: https://issues.apache.org/jira/browse/AMBARI-18876
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18876.patch, AMBARI-18876.patch.1
>
>
> Remove UpgradeCatalog and tests till 2.0.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18846) Custom services should be able to easily specify their own dashboards
[
https://issues.apache.org/jira/browse/AMBARI-18846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667702#comment-15667702
]
Hadoop QA commented on AMBARI-18846:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12838996/AMBARI-18846.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 3 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-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9285//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9285//console
This message is automatically generated.
> Custom services should be able to easily specify their own dashboards
> -
>
> Key: AMBARI-18846
> URL: https://issues.apache.org/jira/browse/AMBARI-18846
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-admin, ambari-metrics, ambari-server
>Affects Versions: trunk, 2.4.0, 2.5.0
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18846.patch
>
>
> Currently all dashboards are added directly in under the AMBARI_METRICS
> package directory (package/files/grafana-dashboards).
> In order for custom services to add dashboards, they need to add the files
> directly under that folder. Each time the Ambari server is upgraded, those
> files will be lost as the AMBARI_METRICS service definition will be replaced.
> This JIRA proposes adding a new directory under the ambari-server/resources.
> This will contain both the dashboards and metrics for custom services.
> The dashboards here will not be organized by stack. Each service will add a
> directory containing their dashboards and will add a metrics file.
> resources/dashboards/grafana-dashboards/MY_SERVICE/
> resources/dashboards/service-metrics/MY_SERVICE.txt
> The resources/dashboards directory will need to get sync'd to the agents.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
