[jira] [Commented] (AMBARI-19123) Update zeppelin configuration for ambari 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15750672#comment-15750672 ] Hudson commented on AMBARI-19123: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6237 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6237/]) AMBARI-19123 Update zeppelin configuration for ambari 2.5 (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=61255affedf34ea0c29bfe513945e81f4a1d6a74]) * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-env.xml > Update zeppelin configuration for ambari 2.5 > > > Key: AMBARI-19123 > URL: https://issues.apache.org/jira/browse/AMBARI-19123 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Fix For: 2.5.0 > > Attachments: AMBARI-19123_branch-2.5-v1.patch, > AMBARI-19123_branch-2.5-v2.patch, AMBARI-19123_branch-2.5-v3.patch, > AMBARI-19123_branch-2.5-v4.patch, AMBARI-19123_branch-2.5-v5.patch, > AMBARI-19123_branch-2.5-v6.patch > > > Update zeppelin configuration for ambari 2.5, and add more configuration > template for shiro.ini -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19123) Update zeppelin configuration for ambari 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15750654#comment-15750654 ] Hudson commented on AMBARI-19123: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #532 (See [https://builds.apache.org/job/Ambari-branch-2.5/532/]) AMBARI-19123 Update zeppelin configuration for ambari 2.5 (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=34aa7559fc25e357709bca0c9869e950a1de]) * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-env.xml > Update zeppelin configuration for ambari 2.5 > > > Key: AMBARI-19123 > URL: https://issues.apache.org/jira/browse/AMBARI-19123 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Fix For: 2.5.0 > > Attachments: AMBARI-19123_branch-2.5-v1.patch, > AMBARI-19123_branch-2.5-v2.patch, AMBARI-19123_branch-2.5-v3.patch, > AMBARI-19123_branch-2.5-v4.patch, AMBARI-19123_branch-2.5-v5.patch, > AMBARI-19123_branch-2.5-v6.patch > > > Update zeppelin configuration for ambari 2.5, and add more configuration > template for shiro.ini -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19126) Spark 2.x interpreter confgurations in Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-19126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15750653#comment-15750653 ] Hudson commented on AMBARI-19126: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #532 (See [https://builds.apache.org/job/Ambari-branch-2.5/532/]) AMBARI-19126 Spark 2.x interpreter confgurations in Zeppelin (r-kamath) (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2d8a776423f341e5a0282a28a1c663c5bb758d08]) * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-env.xml * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py * (add) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/spark2_config_template.py > Spark 2.x interpreter confgurations in Zeppelin > --- > > Key: AMBARI-19126 > URL: https://issues.apache.org/jira/browse/AMBARI-19126 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Renjith Kamath >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-19126-branch-2.5-v1.patch, > AMBARI-19126-branch-2.5-v2.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19126) Spark 2.x interpreter confgurations in Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-19126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15750605#comment-15750605 ] Hudson commented on AMBARI-19126: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6236 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6236/]) AMBARI-19126 Spark 2.x interpreter confgurations in Zeppelin (r-kamath) (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b77b2fac39bc06df1d5b6a59d1be4d6bdd8b0386]) * (add) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/spark2_config_template.py * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-env.xml * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/params.py > Spark 2.x interpreter confgurations in Zeppelin > --- > > Key: AMBARI-19126 > URL: https://issues.apache.org/jira/browse/AMBARI-19126 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Renjith Kamath >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-19126-branch-2.5-v1.patch, > AMBARI-19126-branch-2.5-v2.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19172) 'Backup Oozie DB' message is masked when FixOozieAdminUsers code is invoked in EU wizard
[
https://issues.apache.org/jira/browse/AMBARI-19172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15750564#comment-15750564
]
Hadoop QA commented on AMBARI-19172:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843353/AMBARI-19172.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9674//console
This message is automatically generated.
> 'Backup Oozie DB' message is masked when FixOozieAdminUsers code is invoked
> in EU wizard
>
>
> Key: AMBARI-19172
> URL: https://issues.apache.org/jira/browse/AMBARI-19172
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Dmytro Grinenko
>Priority: Critical
> Labels: express_upgrade
> Fix For: 2.5.0
>
> Attachments: AMBARI-19172.patch, Error.png, Working.png
>
>
> EU path from HDP-2.3.6.0 to 2.6.0.0 with Ambari-2.5.0.0
> In upgrade pack:
> There are two tasks:
> a. Fix oozie admin users
> b. Manual prompt to 'Backup Oozie Database'
> When a.) gets invoked then the manual prompt message to backup Oozie DB gets
> suppressed. As a result user is not informed to backup the Oozie DB before
> the actual upgrade
> Please see attached screenshots
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19123) Update zeppelin configuration for ambari 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith Kamath updated AMBARI-19123: Resolution: Fixed Status: Resolved (was: Patch Available) > Update zeppelin configuration for ambari 2.5 > > > Key: AMBARI-19123 > URL: https://issues.apache.org/jira/browse/AMBARI-19123 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Fix For: 2.5.0 > > Attachments: AMBARI-19123_branch-2.5-v1.patch, > AMBARI-19123_branch-2.5-v2.patch, AMBARI-19123_branch-2.5-v3.patch, > AMBARI-19123_branch-2.5-v4.patch, AMBARI-19123_branch-2.5-v5.patch, > AMBARI-19123_branch-2.5-v6.patch > > > Update zeppelin configuration for ambari 2.5, and add more configuration > template for shiro.ini -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19126) Spark 2.x interpreter confgurations in Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-19126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15750561#comment-15750561 ] Renjith Kamath commented on AMBARI-19126: - committed to trunk and branch-2.5 > Spark 2.x interpreter confgurations in Zeppelin > --- > > Key: AMBARI-19126 > URL: https://issues.apache.org/jira/browse/AMBARI-19126 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Renjith Kamath >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-19126-branch-2.5-v1.patch, > AMBARI-19126-branch-2.5-v2.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19126) Spark 2.x interpreter confgurations in Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-19126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith Kamath updated AMBARI-19126: Resolution: Fixed Status: Resolved (was: Patch Available) > Spark 2.x interpreter confgurations in Zeppelin > --- > > Key: AMBARI-19126 > URL: https://issues.apache.org/jira/browse/AMBARI-19126 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Renjith Kamath >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-19126-branch-2.5-v1.patch, > AMBARI-19126-branch-2.5-v2.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19123) Update zeppelin configuration for ambari 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15750560#comment-15750560 ] Renjith Kamath commented on AMBARI-19123: - committed to trunk and branch-2.5 > Update zeppelin configuration for ambari 2.5 > > > Key: AMBARI-19123 > URL: https://issues.apache.org/jira/browse/AMBARI-19123 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Fix For: 2.5.0 > > Attachments: AMBARI-19123_branch-2.5-v1.patch, > AMBARI-19123_branch-2.5-v2.patch, AMBARI-19123_branch-2.5-v3.patch, > AMBARI-19123_branch-2.5-v4.patch, AMBARI-19123_branch-2.5-v5.patch, > AMBARI-19123_branch-2.5-v6.patch > > > Update zeppelin configuration for ambari 2.5, and add more configuration > template for shiro.ini -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19031) AMBARI-19031: UI Enhancements, import/export assets and smart version configuration
[
https://issues.apache.org/jira/browse/AMBARI-19031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15750552#comment-15750552
]
Hadoop QA commented on AMBARI-19031:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843355/AMBARI-19031_branch-2.5.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9673//console
This message is automatically generated.
> AMBARI-19031: UI Enhancements, import/export assets and smart version
> configuration
> ---
>
> Key: AMBARI-19031
> URL: https://issues.apache.org/jira/browse/AMBARI-19031
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Padma Priya Nagaraj
> Fix For: 2.5.0
>
> Attachments: AMBARI-19031_branch-2.5.patch, AMBARI-19031_trunk.patch
>
>
> UX Enhancemenets
> - Dashboard as a tab
> - Coordinator UI changes
> - Bundle smart name autofil
> Features
> - Version setting picked up from Oozie
> - Ability to import/export assets(actions)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19031) AMBARI-19031: UI Enhancements, import/export assets and smart version configuration
[ https://issues.apache.org/jira/browse/AMBARI-19031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-19031: - Attachment: AMBARI-19031_trunk.patch > AMBARI-19031: UI Enhancements, import/export assets and smart version > configuration > --- > > Key: AMBARI-19031 > URL: https://issues.apache.org/jira/browse/AMBARI-19031 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Padma Priya Nagaraj > Fix For: 2.5.0 > > Attachments: AMBARI-19031_branch-2.5.patch, AMBARI-19031_trunk.patch > > > UX Enhancemenets > - Dashboard as a tab > - Coordinator UI changes > - Bundle smart name autofil > Features > - Version setting picked up from Oozie > - Ability to import/export assets(actions) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19031) AMBARI-19031: UI Enhancements, import/export assets and smart version configuration
[ https://issues.apache.org/jira/browse/AMBARI-19031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-19031: - Attachment: AMBARI-19031_branch-2.5.patch > AMBARI-19031: UI Enhancements, import/export assets and smart version > configuration > --- > > Key: AMBARI-19031 > URL: https://issues.apache.org/jira/browse/AMBARI-19031 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Padma Priya Nagaraj > Fix For: 2.5.0 > > Attachments: AMBARI-19031_branch-2.5.patch, AMBARI-19031_trunk.patch > > > UX Enhancemenets > - Dashboard as a tab > - Coordinator UI changes > - Bundle smart name autofil > Features > - Version setting picked up from Oozie > - Ability to import/export assets(actions) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19031) AMBARI-19031: UI Enhancements, import/export assets and smart version configuration
[ https://issues.apache.org/jira/browse/AMBARI-19031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-19031: - Attachment: (was: AMBARI-19031.02.patch) > AMBARI-19031: UI Enhancements, import/export assets and smart version > configuration > --- > > Key: AMBARI-19031 > URL: https://issues.apache.org/jira/browse/AMBARI-19031 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Padma Priya Nagaraj > Fix For: 2.5.0 > > > UX Enhancemenets > - Dashboard as a tab > - Coordinator UI changes > - Bundle smart name autofil > Features > - Version setting picked up from Oozie > - Ability to import/export assets(actions) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19031) AMBARI-19031: UI Enhancements, import/export assets and smart version configuration
[ https://issues.apache.org/jira/browse/AMBARI-19031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-19031: - Attachment: (was: AMBARI-19031.01.patch) > AMBARI-19031: UI Enhancements, import/export assets and smart version > configuration > --- > > Key: AMBARI-19031 > URL: https://issues.apache.org/jira/browse/AMBARI-19031 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Padma Priya Nagaraj > Fix For: 2.5.0 > > > UX Enhancemenets > - Dashboard as a tab > - Coordinator UI changes > - Bundle smart name autofil > Features > - Version setting picked up from Oozie > - Ability to import/export assets(actions) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19172) 'Backup Oozie DB' message is masked when FixOozieAdminUsers code is invoked in EU wizard
[ https://issues.apache.org/jira/browse/AMBARI-19172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-19172: - Status: Patch Available (was: In Progress) > 'Backup Oozie DB' message is masked when FixOozieAdminUsers code is invoked > in EU wizard > > > Key: AMBARI-19172 > URL: https://issues.apache.org/jira/browse/AMBARI-19172 > Project: Ambari > Issue Type: Bug > Components: ambari-upgrade >Affects Versions: 2.5.0 >Reporter: Vivek Sharma >Assignee: Dmytro Grinenko >Priority: Critical > Labels: express_upgrade > Fix For: 2.5.0 > > Attachments: AMBARI-19172.patch, Error.png, Working.png > > > EU path from HDP-2.3.6.0 to 2.6.0.0 with Ambari-2.5.0.0 > In upgrade pack: > There are two tasks: > a. Fix oozie admin users > b. Manual prompt to 'Backup Oozie Database' > When a.) gets invoked then the manual prompt message to backup Oozie DB gets > suppressed. As a result user is not informed to backup the Oozie DB before > the actual upgrade > Please see attached screenshots -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19172) 'Backup Oozie DB' message is masked when FixOozieAdminUsers code is invoked in EU wizard
[ https://issues.apache.org/jira/browse/AMBARI-19172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-19172: - Attachment: AMBARI-19172.patch > 'Backup Oozie DB' message is masked when FixOozieAdminUsers code is invoked > in EU wizard > > > Key: AMBARI-19172 > URL: https://issues.apache.org/jira/browse/AMBARI-19172 > Project: Ambari > Issue Type: Bug > Components: ambari-upgrade >Affects Versions: 2.5.0 >Reporter: Vivek Sharma >Assignee: Dmytro Grinenko >Priority: Critical > Labels: express_upgrade > Fix For: 2.5.0 > > Attachments: AMBARI-19172.patch, Error.png, Working.png > > > EU path from HDP-2.3.6.0 to 2.6.0.0 with Ambari-2.5.0.0 > In upgrade pack: > There are two tasks: > a. Fix oozie admin users > b. Manual prompt to 'Backup Oozie Database' > When a.) gets invoked then the manual prompt message to backup Oozie DB gets > suppressed. As a result user is not informed to backup the Oozie DB before > the actual upgrade > Please see attached screenshots -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19206) When Namenode HA is enabled, hbase.rootdir property for ambari-metrics (distributed) does not get updated
[ https://issues.apache.org/jira/browse/AMBARI-19206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-19206: Attachment: NNHAWizard2.jpg NNHAWizard1.jpg AMSHbaseRootdirPostNNHAEnabling.jpg > When Namenode HA is enabled, hbase.rootdir property for ambari-metrics > (distributed) does not get updated > - > > Key: AMBARI-19206 > URL: https://issues.apache.org/jira/browse/AMBARI-19206 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0, 2.4.2 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Attachments: AMSHbaseRootdirPostNNHAEnabling.jpg, NNHAWizard1.jpg, > NNHAWizard2.jpg > > > On a cluster with ambari-metrics in distributed operation mode, enable > Namenode HA. > After HA wizard is run, the amabri-metrics property for hbase.rootdir should > point to hdfs://, but it actually still points to the > explicit Namenode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19206) When Namenode HA is enabled, hbase.rootdir property for ambari-metrics (distributed) does not get updated
Sangeeta Ravindran created AMBARI-19206: --- Summary: When Namenode HA is enabled, hbase.rootdir property for ambari-metrics (distributed) does not get updated Key: AMBARI-19206 URL: https://issues.apache.org/jira/browse/AMBARI-19206 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0, 2.4.2 Reporter: Sangeeta Ravindran Assignee: Sangeeta Ravindran On a cluster with ambari-metrics in distributed operation mode, enable Namenode HA. After HA wizard is run, the amabri-metrics property for hbase.rootdir should point to hdfs://, but it actually still points to the explicit Namenode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19105) Ambari LogSearch REST Layer should use a configurable timeout for HTTP connections to LogSearch Server
[
https://issues.apache.org/jira/browse/AMBARI-19105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15749689#comment-15749689
]
Hadoop QA commented on AMBARI-19105:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843282/AMBARI-19105.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 5 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.serveraction.upgrades.UpgradeActionTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9672//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9672//console
This message is automatically generated.
> Ambari LogSearch REST Layer should use a configurable timeout for HTTP
> connections to LogSearch Server
> --
>
> Key: AMBARI-19105
> URL: https://issues.apache.org/jira/browse/AMBARI-19105
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Nettleton
>Assignee: Robert Nettleton
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19105.patch
>
>
> The HTTP connection used to make REST calls on the LogSearch Server is
> currently using a hard-coded timeout, which was introduced in:
> AMBARI-17510
> as part of a fix for a performance issue in LogSearch.
> This issue tracks the work to make the connection and read timeouts
> configurable for the LogSearch integration code. These timeouts should be
> configurable in ambari.properties, and should have valid defaults if not set
> by the customer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19204) Metrics monitor start failed after deleting AMS and reinstalling with different user
[
https://issues.apache.org/jira/browse/AMBARI-19204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15749576#comment-15749576
]
Hadoop QA commented on AMBARI-19204:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843283/AMBARI-19204.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:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9671//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9671//console
This message is automatically generated.
> Metrics monitor start failed after deleting AMS and reinstalling with
> different user
>
>
> Key: AMBARI-19204
> URL: https://issues.apache.org/jira/browse/AMBARI-19204
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19204.patch
>
>
> STR:
> 1) Delete Service AMS along with Tez,HBase, Sqoop, Oozie, Falcon, Storm,
> Ambari Infra, Ambari Metrics, Kafka, Knox, Log Search, Smartsense, Mahout,
> Slider
> 2) Add all the deleted services back
> Metrics collector fails to start with
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py",
> line 68, in
> AmsMonitor().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 282, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py",
> line 42, in start
> action = 'start'
> 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/AMBARI_METRICS/0.1.0/package/scripts/ams_service.py",
> line 103, in ams_service
> user=params.ams_user
> 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 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/sbin/ambari-metrics-monitor --config /etc/ambari-metrics-monitor/conf
> start' returned 255. Hortonworks #
> This is MOTD message, added for testing in qe infra
> psutil build directory is not empty, continuing...
> Verifying Python version compatibility...
> Using python /usr/bin/python2.6
> Checking for previously running Metric Monitor...
> Starting ambari-metrics-monitor
> /usr/sbin/ambari-metrics-monitor: line 148:
> /grid/0/log/metric_monitor/ambari-metrics-monitor.out: Permission denied
> Verifying ambari-metrics-monitor process status...
> ERROR: ambari-metrics-monitor start failed. For more details, see
> /grid/0/log/metric_monitor/ambari-metrics-monitor.out:
>
[jira] [Commented] (AMBARI-17591) Collect JVM Heap, GC and thread pool metrics from Ambari Server and push to AMS
[ https://issues.apache.org/jira/browse/AMBARI-17591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15749528#comment-15749528 ] Hudson commented on AMBARI-17591: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #530 (See [https://builds.apache.org/job/Ambari-branch-2.5/530/]) AMBARI-17591 : Collect JVM Heap, GC and thread pool metrics from Ambari (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=98c5d98442099799f961736b7f7264e6f84b5858]) * (add) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/JvmMetricsSource.java * (add) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/MetricsServiceImpl.java * (add) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/Configuration.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * (add) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/AmbariMetricSink.java * (add) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/default/grafana-ambari-server.json * (edit) ambari-server/pom.xml * (add) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/MetricsSource.java * (add) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/AbstractMetricsSource.java * (add) ambari-server/conf/unix/metrics.properties * (add) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/AmbariMetricSinkImpl.java * (add) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/MetricsService.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/ControllerModule.java > Collect JVM Heap, GC and thread pool metrics from Ambari Server and push to > AMS > --- > > Key: AMBARI-17591 > URL: https://issues.apache.org/jira/browse/AMBARI-17591 > Project: Ambari > Issue Type: Task > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Li-Wei Tseng >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-17591.patch > > > 1. Collect JVM Heap, GC and thread pool metrics from Ambari Server > 2. Implement/Refine an AmbariServer Metrics Sink to push metrics to AMS. > 3. Visualize using Grafana -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-14958) Alerts: Create new Alerts Notification type for SNMP to handle Ambari MIB
[ https://issues.apache.org/jira/browse/AMBARI-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15749518#comment-15749518 ] Hudson commented on AMBARI-14958: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6235 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6235/]) AMBARI-14958. Alerts: Create new Alerts Notification type for SNMP to (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f936fd04ddbffa0cd78e827d61c2a27c4be1270c]) * (edit) ambari-web/app/controllers/main/alerts/manage_alert_notifications_controller.js * (edit) ambari-web/app/templates/main/alerts/create_alert_notification.hbs * (edit) ambari-web/app/views/main/alerts/manage_alert_notifications_view.js > Alerts: Create new Alerts Notification type for SNMP to handle Ambari MIB > - > > Key: AMBARI-14958 > URL: https://issues.apache.org/jira/browse/AMBARI-14958 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-14958.patch, AMBARI-14958.v0.patch, > AMBARI-14958.v1.branch-2.5.patch, AMBARI-14958.v1.trunk.patch > > > 1) Rename current notification type "SNMP" to "Custom SNMP" > 2) Create a new notification type "SNMP" that prompts for version, community, > hosts, ports > 3) When this is chosen, Ambari under-the-hood generates the SNMP traps based > on the MIB. > 4) The MIB file should be shipped with Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19193) Add common log rotation settings to YARN Configs
[ https://issues.apache.org/jira/browse/AMBARI-19193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15749526#comment-15749526 ] Hudson commented on AMBARI-19193: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #530 (See [https://builds.apache.org/job/Ambari-branch-2.5/530/]) AMBARI-19193. Add common log rotation settings to YARN Configs (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e1f7795ba1e64945c539b0c5639bbbddb4c123a5]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/YARN/configuration/yarn-log4j.xml > Add common log rotation settings to YARN Configs > > > Key: AMBARI-19193 > URL: https://issues.apache.org/jira/browse/AMBARI-19193 > Project: Ambari > Issue Type: Task >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-19193.patch > > > Add common log rotation settings to YARN. > log4j.appender.RMSUMMARY.MaxFileSize > log4j.appender.RMSUMMARY.MaxBackupIndex -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17666) Ambari agent can't start when TLSv1 is disabled in Java security
[ https://issues.apache.org/jira/browse/AMBARI-17666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15749525#comment-15749525 ] Hudson commented on AMBARI-17666: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #530 (See [https://builds.apache.org/job/Ambari-branch-2.5/530/]) AMBARI-17666. Ambari agent can't start when TLSv1 is disabled in Java (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ecc916bbc1345e0dbc80ee1bd3a42f8545bc52f2]) * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/service_check.py * (edit) ambari-common/src/main/python/resource_management/libraries/script/script.py * (edit) ambari-agent/src/test/python/ambari_agent/TestCustomServiceOrchestrator.py * (edit) ambari-agent/src/main/python/ambari_agent/AmbariConfig.py * (edit) ambari-agent/src/main/python/ambari_agent/NetUtil.py * (edit) ambari-common/src/main/python/ambari_commons/inet_utils.py * (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py * (edit) ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/service_check.py * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/utils.py * (edit) ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/params.py * (edit) ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/files/checkWebUI.py > Ambari agent can't start when TLSv1 is disabled in Java security > > > Key: AMBARI-17666 > URL: https://issues.apache.org/jira/browse/AMBARI-17666 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.2.0 >Reporter: Tuong Truong >Assignee: Dmitry Lysnichenko > Labels: security > Fix For: 2.5.0 > > > Currently, the commit for https://issues.apache.org/jira/browse/AMBARI-14236 > explicit force the SSL protocol to TLSv1 in > ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py. Unfortunate, > this setting in effect whenever web_alert pacackged is loaded > (ambari-agent/src/main/python/ambari_agent/AlertSchedulerHandler.py) > regardless whether ssl is used or not. > As a result, disabling TLSv1 in Ambari server will cause the agent to fail to > start. > Recreate: > In Ambari's acitve JDK on Ambari server node, in java.security file, set > jdk.tls.disabledAlgorithms=MD5, SSLv2, SSLv3, TLSv1, DSA, RC4, RSA keySize < > 2048 > restart ambari-server, and you will see errors in ambari agent logs: > ERROR 2016-07-11 15:11:15,269 NetUtil.py:84 - [Errno 8] _ssl.c:492: EOF > occurred in violation of protocol > ERROR 2016-07-11 15:11:15,269 NetUtil.py:85 - SSLError: Failed to connect. > Please check openssl library versions. > Refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1022468 for more > details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19203) LLAP app package cleanup fails after Hive Interactive start failure in non-root
[ https://issues.apache.org/jira/browse/AMBARI-19203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15749519#comment-15749519 ] Hudson commented on AMBARI-19203: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #530 (See [https://builds.apache.org/job/Ambari-branch-2.5/530/]) AMBARI-19203. LLAP app package cleanup fails after Hive Interactive (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0d2ceecd2a3bceca26d783ad5db8b78472c83708]) * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py > LLAP app package cleanup fails after Hive Interactive start failure in > non-root > --- > > Key: AMBARI-19203 > URL: https://issues.apache.org/jira/browse/AMBARI-19203 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-19203.patch > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py", > line 380, in _cleanup_past_llap_package_dirs > shutil.rmtree(abs_path) > File "/usr/lib64/python2.7/shutil.py", line 239, in rmtree > onerror(os.listdir, path, sys.exc_info()) > File "/usr/lib64/python2.7/shutil.py", line 237, in rmtree > names = os.listdir(path) > OSError: [Errno 13] Permission denied: > '/var/lib/ambari-agent/tmp/llap-slider2016-12-13_09-11-04' > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19127) hbase_regionserver_shutdown_timeout should be editable all the time
[ https://issues.apache.org/jira/browse/AMBARI-19127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15749523#comment-15749523 ] Hudson commented on AMBARI-19127: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #530 (See [https://builds.apache.org/job/Ambari-branch-2.5/530/]) AMBARI-19127. hbase_regionserver_shutdown_timeout should be editable all (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=10cb81af4fb0ae21391db489485a93398b92bca5]) * (edit) ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/configuration/hbase-env.xml * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-hbase-env.xml > hbase_regionserver_shutdown_timeout should be editable all the time > --- > > Key: AMBARI-19127 > URL: https://issues.apache.org/jira/browse/AMBARI-19127 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-19127.patch, AMBARI-19127.patch > > > hbase_regionserver_shutdown_timeout should be editable any time. Its now only > editable during install. > > > > > hbase_regionserver_shutdown_timeout > 30 > HBase RegionServer shutdown timeout > > After this number of seconds waiting for graceful stop of HBase Master it > will be forced to exit with SIGKILL. > The timeout is introduced because there is a known bug when from time to > time HBase RegionServer hangs forever on stop if NN safemode is on. > > > int > false > true > > > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18868) Stage and Request status should be persisted in the database
[
https://issues.apache.org/jira/browse/AMBARI-18868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15749509#comment-15749509
]
Hadoop QA commented on AMBARI-18868:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843286/AMBARI-18868.4.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 8 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.agent.AgentResourceTest
org.apache.ambari.server.state.cluster.ClusterEffectiveVersionTest
org.apache.ambari.server.utils.StageUtilsTest
org.apache.ambari.server.controller.internal.StackUpgradeConfigurationMergeTest
org.apache.ambari.server.controller.internal.ActiveWidgetLayoutResourceProviderTest
org.apache.ambari.server.controller.internal.UserAuthorizationResourceProviderTest
org.apache.ambari.server.controller.internal.UpgradeResourceProviderTest
org.apache.ambari.server.state.ConfigHelperTest
org.apache.ambari.server.alerts.AmbariPerformanceRunnableTest
org.apache.ambari.server.controller.KerberosHelperTest
org.apache.ambari.server.controller.internal.UserResourceProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9670//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9670//console
This message is automatically generated.
> Stage and Request status should be persisted in the database
>
>
> Key: AMBARI-18868
> URL: https://issues.apache.org/jira/browse/AMBARI-18868
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Jaimin Jetly
>Assignee: Jaimin Jetly
> Fix For: 3.0.0
>
> Attachments: AMBARI-18868.2.patch, AMBARI-18868.3.patch,
> AMBARI-18868.4.patch, AMBARI-18868.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19156) Install Packages fails with the old stack has services removed in the new stack
[ https://issues.apache.org/jira/browse/AMBARI-19156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15749474#comment-15749474 ] Di Li commented on AMBARI-19156: AMBARI-19156 Pushed to Trunk as https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=162ee83c552e2c418cc2ee97dbb3687ffc8e1ae3 Pushed to Branch-2.5 as https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=a74bf6b2b943642d579f497747adf385ae2340a1 > Install Packages fails with the old stack has services removed in the new > stack > --- > > Key: AMBARI-19156 > URL: https://issues.apache.org/jira/browse/AMBARI-19156 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19156-v2.patch, AMBARI-19156-v3.patch, > AMBARI-19156.patch > > > Install packages step (before RU/EU) fails with err "Cannot enumerate > services" if the current stack has services that have been removed in the new > stack. For example, mystack-1.0 has Spark, but mystakc-2.0 only has Spark2, > where Spark's metainfo.xml in mystack-2.0 has the true > section. > Workaround is to remove Spark before attempting the install packages. > The error is below: > 02 Dec 2016 12:53:43,928 ERROR [ambari-client-thread-27] > BaseManagementHandler:61 - Caught a system exception while attempting to > create a resource: Cannot enumerate services > org.apache.ambari.server.controller.spi.SystemException: Cannot enumerate > services > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.getHostVersionInstallCommand(ClusterStackVersionResourceProvider.java:606) > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createResourcesAuthorized(ClusterStackVersionResourceProvider.java:508) > at > org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:220) > at > org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298) > at > org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97) > at > org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37) > at > org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterStackVersionService.createRequests(ClusterStackVersionService.java:121) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19156) Install Packages fails with the old stack has services removed in the new stack
[ https://issues.apache.org/jira/browse/AMBARI-19156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19156: --- Resolution: Fixed Fix Version/s: 2.5.0 trunk Status: Resolved (was: Patch Available) > Install Packages fails with the old stack has services removed in the new > stack > --- > > Key: AMBARI-19156 > URL: https://issues.apache.org/jira/browse/AMBARI-19156 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19156-v2.patch, AMBARI-19156-v3.patch, > AMBARI-19156.patch > > > Install packages step (before RU/EU) fails with err "Cannot enumerate > services" if the current stack has services that have been removed in the new > stack. For example, mystack-1.0 has Spark, but mystakc-2.0 only has Spark2, > where Spark's metainfo.xml in mystack-2.0 has the true > section. > Workaround is to remove Spark before attempting the install packages. > The error is below: > 02 Dec 2016 12:53:43,928 ERROR [ambari-client-thread-27] > BaseManagementHandler:61 - Caught a system exception while attempting to > create a resource: Cannot enumerate services > org.apache.ambari.server.controller.spi.SystemException: Cannot enumerate > services > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.getHostVersionInstallCommand(ClusterStackVersionResourceProvider.java:606) > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createResourcesAuthorized(ClusterStackVersionResourceProvider.java:508) > at > org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:220) > at > org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298) > at > org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97) > at > org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37) > at > org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterStackVersionService.createRequests(ClusterStackVersionService.java:121) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19156) Install Packages fails with the old stack has services removed in the new stack
[ https://issues.apache.org/jira/browse/AMBARI-19156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15749470#comment-15749470 ] Di Li commented on AMBARI-19156: [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (python-test) on project ambari-server: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1] The error existed (in https://builds.apache.org/job/Ambari-trunk-Commit/6233/) before changes from this JIRA were committed. > Install Packages fails with the old stack has services removed in the new > stack > --- > > Key: AMBARI-19156 > URL: https://issues.apache.org/jira/browse/AMBARI-19156 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19156-v2.patch, AMBARI-19156-v3.patch, > AMBARI-19156.patch > > > Install packages step (before RU/EU) fails with err "Cannot enumerate > services" if the current stack has services that have been removed in the new > stack. For example, mystack-1.0 has Spark, but mystakc-2.0 only has Spark2, > where Spark's metainfo.xml in mystack-2.0 has the true > section. > Workaround is to remove Spark before attempting the install packages. > The error is below: > 02 Dec 2016 12:53:43,928 ERROR [ambari-client-thread-27] > BaseManagementHandler:61 - Caught a system exception while attempting to > create a resource: Cannot enumerate services > org.apache.ambari.server.controller.spi.SystemException: Cannot enumerate > services > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.getHostVersionInstallCommand(ClusterStackVersionResourceProvider.java:606) > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createResourcesAuthorized(ClusterStackVersionResourceProvider.java:508) > at > org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:220) > at > org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298) > at > org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97) > at > org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37) > at > org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterStackVersionService.createRequests(ClusterStackVersionService.java:121) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19205) Technical Preview services should not be enabled by default
[ https://issues.apache.org/jira/browse/AMBARI-19205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15749462#comment-15749462 ] Sumit Mohanty commented on AMBARI-19205: Tested with the patch manually applied - https://issues.apache.org/jira/secure/attachment/12843294/Screen%20Shot%202016-12-14%20at%2012.53.23%20PM.png > Technical Preview services should not be enabled by default > --- > > Key: AMBARI-19205 > URL: https://issues.apache.org/jira/browse/AMBARI-19205 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty > Fix For: 2.5.0 > > Attachments: AMBARI-19205.patch, Screen Shot 2016-12-14 at 12.53.23 > PM.png > > > Technical Preview services should not be enabled by default. Use the > "selection" tag to set the services as TECH_PREVIEW. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19205) Technical Preview services should not be enabled by default
Sumit Mohanty created AMBARI-19205: -- Summary: Technical Preview services should not be enabled by default Key: AMBARI-19205 URL: https://issues.apache.org/jira/browse/AMBARI-19205 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.5.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Fix For: 2.5.0 Attachments: AMBARI-19205.patch, Screen Shot 2016-12-14 at 12.53.23 PM.png Technical Preview services should not be enabled by default. Use the "selection" tag to set the services as TECH_PREVIEW. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19156) Install Packages fails with the old stack has services removed in the new stack
[ https://issues.apache.org/jira/browse/AMBARI-19156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15749438#comment-15749438 ] Hudson commented on AMBARI-19156: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6234 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6234/]) AMBARI-19156 Install Packages fails with the old stack has services (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=162ee83c552e2c418cc2ee97dbb3687ffc8e1ae3]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/StackInfo.java * (add) ambari-server/src/test/resources/stacks/HDP/2.0.8/services/SPARK2/metainfo.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java * (add) ambari-server/src/test/resources/stacks/HDP/2.0.6/services/SPARK/metainfo.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerTest.java * (add) ambari-server/src/test/resources/stacks/HDP/2.0.7/services/SPARK/metainfo.xml * (add) ambari-server/src/test/resources/stacks/HDP/2.0.7/services/SPARK2/metainfo.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/StackModule.java * (add) ambari-server/src/test/resources/stacks/HDP/2.0.8/services/SPARK3/metainfo.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/ExtensionModule.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/BaseModule.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/StackModuleTest.java > Install Packages fails with the old stack has services removed in the new > stack > --- > > Key: AMBARI-19156 > URL: https://issues.apache.org/jira/browse/AMBARI-19156 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19156-v2.patch, AMBARI-19156-v3.patch, > AMBARI-19156.patch > > > Install packages step (before RU/EU) fails with err "Cannot enumerate > services" if the current stack has services that have been removed in the new > stack. For example, mystack-1.0 has Spark, but mystakc-2.0 only has Spark2, > where Spark's metainfo.xml in mystack-2.0 has the true > section. > Workaround is to remove Spark before attempting the install packages. > The error is below: > 02 Dec 2016 12:53:43,928 ERROR [ambari-client-thread-27] > BaseManagementHandler:61 - Caught a system exception while attempting to > create a resource: Cannot enumerate services > org.apache.ambari.server.controller.spi.SystemException: Cannot enumerate > services > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.getHostVersionInstallCommand(ClusterStackVersionResourceProvider.java:606) > at > org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createResourcesAuthorized(ClusterStackVersionResourceProvider.java:508) > at > org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:220) > at > org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298) > at > org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97) > at > org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37) > at > org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterStackVersionService.createRequests(ClusterStackVersionService.java:121) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at >
[jira] [Commented] (AMBARI-19202) Devdeploy: Database check failed
[
https://issues.apache.org/jira/browse/AMBARI-19202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15749434#comment-15749434
]
Hudson commented on AMBARI-19202:
-
ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #529 (See
[https://builds.apache.org/job/Ambari-branch-2.5/529/])
AMBARI-19202. Devdeploy: Database check failed.(vbrodetskyi) (vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fe828aef7b2cc646fdd9decb431f96d8047b943a])
* (edit) ambari-common/src/main/python/ambari_commons/os_linux.py
* (edit) ambari-server/src/main/python/ambari_server/checkDatabase.py
> Devdeploy: Database check failed
>
>
> Key: AMBARI-19202
> URL: https://issues.apache.org/jira/browse/AMBARI-19202
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19202.patch
>
>
> From ambari-server-command.log:
> {noformat}
> ERROR 2016-12-13 15:58:09,344 ambari-server.py:865 - 'Fatal exception:
> Database check failed to complete. Please check
> /var/log/ambari-server/ambari-server.log and
> /var/log/ambari-server/ambari-server-check-database.log for more
> information., exit code 1'
> Traceback (most recent call last):
> File "/usr/sbin/ambari-server.py", line 848, in main
> action_obj.execute()
> File "/usr/sbin/ambari-server.py", line 77, in execute
> self.fn(*self.args, **self.kwargs)
> File "/usr/lib/python2.6/site-packages/ambari_server/checkDatabase.py",
> line 85, in check_database
> ' and ' + configDefaults.DB_CHECK_LOG + ' for more information.')
> FatalException: 'Fatal exception: Database check failed to complete. Please
> check /var/log/ambari-server/ambari-server.log and
> /var/log/ambari-server/ambari-server-check-database.log for more
> information., exit code 1'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19164) Add PK to hostcomponentdesiredstate Table To Support FK Relationships
[
https://issues.apache.org/jira/browse/AMBARI-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-19164:
--
Attachment: (was: AMBARI-19164.v1.patch)
> Add PK to hostcomponentdesiredstate Table To Support FK Relationships
> -
>
> Key: AMBARI-19164
> URL: https://issues.apache.org/jira/browse/AMBARI-19164
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19164.v2.patch
>
>
> The {{hostcomponentdesiredstate}} table currently uses a compound PK based
> off of the cluster ID, service name, host id and component name. There are
> several problems with this approach:
> * Primary Keys should be data that's not part of the business logic of the
> system and not subject to be changed potentially (as strings are).
> * Other tables referencing the {{hostcomponentdesiredstate}} table would now
> need knowledge of cluster/service/component/host in order to make the correct
> FK association. This leads to extra data being tracked as well as data
> duplication.
> * Some databases, such as SQL Server, have problems with the indexing of
> compound PKs and may lead to deadlocks when querying and updating
> concurrently.
> This table needs to be changed so that it uses a simple PK for referencing.
> FK relationships as they exist today can still be maintained as long as a
> {{UNIQUE}} constraint is placed on the table. We should:
> * Add a {{UNIQUE}} constraint to the former PK columns
> * Add an {{INDEX}} to the former PK columns
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19164) Add PK to hostcomponentdesiredstate Table To Support FK Relationships
[
https://issues.apache.org/jira/browse/AMBARI-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-19164:
--
Attachment: AMBARI-19164.v2.patch
> Add PK to hostcomponentdesiredstate Table To Support FK Relationships
> -
>
> Key: AMBARI-19164
> URL: https://issues.apache.org/jira/browse/AMBARI-19164
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19164.v2.patch
>
>
> The {{hostcomponentdesiredstate}} table currently uses a compound PK based
> off of the cluster ID, service name, host id and component name. There are
> several problems with this approach:
> * Primary Keys should be data that's not part of the business logic of the
> system and not subject to be changed potentially (as strings are).
> * Other tables referencing the {{hostcomponentdesiredstate}} table would now
> need knowledge of cluster/service/component/host in order to make the correct
> FK association. This leads to extra data being tracked as well as data
> duplication.
> * Some databases, such as SQL Server, have problems with the indexing of
> compound PKs and may lead to deadlocks when querying and updating
> concurrently.
> This table needs to be changed so that it uses a simple PK for referencing.
> FK relationships as they exist today can still be maintained as long as a
> {{UNIQUE}} constraint is placed on the table. We should:
> * Add a {{UNIQUE}} constraint to the former PK columns
> * Add an {{INDEX}} to the former PK columns
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18868) Stage and Request status should be persisted in the database
[ https://issues.apache.org/jira/browse/AMBARI-18868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-18868: -- Attachment: AMBARI-18868.4.patch > Stage and Request status should be persisted in the database > > > Key: AMBARI-18868 > URL: https://issues.apache.org/jira/browse/AMBARI-18868 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 3.0.0 > > Attachments: AMBARI-18868.2.patch, AMBARI-18868.3.patch, > AMBARI-18868.4.patch, AMBARI-18868.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19204) Metrics monitor start failed after deleting AMS and reinstalling with different user
[
https://issues.apache.org/jira/browse/AMBARI-19204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15749325#comment-15749325
]
Aravindan Vijayan commented on AMBARI-19204:
Verified manually.
Python unit test failures are unrelated.
> Metrics monitor start failed after deleting AMS and reinstalling with
> different user
>
>
> Key: AMBARI-19204
> URL: https://issues.apache.org/jira/browse/AMBARI-19204
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19204.patch
>
>
> STR:
> 1) Delete Service AMS along with Tez,HBase, Sqoop, Oozie, Falcon, Storm,
> Ambari Infra, Ambari Metrics, Kafka, Knox, Log Search, Smartsense, Mahout,
> Slider
> 2) Add all the deleted services back
> Metrics collector fails to start with
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py",
> line 68, in
> AmsMonitor().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 282, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py",
> line 42, in start
> action = 'start'
> 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/AMBARI_METRICS/0.1.0/package/scripts/ams_service.py",
> line 103, in ams_service
> user=params.ams_user
> 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 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/sbin/ambari-metrics-monitor --config /etc/ambari-metrics-monitor/conf
> start' returned 255. Hortonworks #
> This is MOTD message, added for testing in qe infra
> psutil build directory is not empty, continuing...
> Verifying Python version compatibility...
> Using python /usr/bin/python2.6
> Checking for previously running Metric Monitor...
> Starting ambari-metrics-monitor
> /usr/sbin/ambari-metrics-monitor: line 148:
> /grid/0/log/metric_monitor/ambari-metrics-monitor.out: Permission denied
> Verifying ambari-metrics-monitor process status...
> ERROR: ambari-metrics-monitor start failed. For more details, see
> /grid/0/log/metric_monitor/ambari-metrics-monitor.out:
>
> 2016-12-14 05:37:41,956 [ERROR] host_info.py:194 - Failed to read disk_usage
> for a mountpoint : [Errno 13] Permission denied:
> '/ycloud-grid/0/hadoop/yarn/local/usercache/root/appcache/application_1481604818073_0640'
> 2016-12-14 05:37:41,956 [ERROR] host_info.py:194 - Failed to read disk_usage
> for a mountpoint : [Errno 13] Permission denied:
> '/ycloud-grid/0/hadoop/yarn/local/usercache/root/appcache/application_1481604818073_0640/container_e83_1481604818073_0640_01_07'
> 2016-12-14 05:37:51,956 [ERROR] host_info.py:194 - Failed to read disk_usage
> for a mountpoint : [Errno 13] Permission denied:
> '/ycloud-grid/0/hadoop/yarn/local/usercache/root/appcache/application_1481604818073_0640'
> 2016-12-14 05:37:51,956 [ERROR] host_info.py:194 - Failed to read disk_usage
> for a mountpoint : [Errno 13] Permission denied:
> '/ycloud-grid/0/hadoop/yarn/local/usercache/root/appcache/application_1481604818073_0640/container_e83_1481604818073_0640_01_07'
> 2016-12-14 05:38:01,957
[jira] [Updated] (AMBARI-19204) Metrics monitor start failed after deleting AMS and reinstalling with different user
[
https://issues.apache.org/jira/browse/AMBARI-19204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-19204:
---
Status: Patch Available (was: Open)
> Metrics monitor start failed after deleting AMS and reinstalling with
> different user
>
>
> Key: AMBARI-19204
> URL: https://issues.apache.org/jira/browse/AMBARI-19204
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19204.patch
>
>
> STR:
> 1) Delete Service AMS along with Tez,HBase, Sqoop, Oozie, Falcon, Storm,
> Ambari Infra, Ambari Metrics, Kafka, Knox, Log Search, Smartsense, Mahout,
> Slider
> 2) Add all the deleted services back
> Metrics collector fails to start with
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py",
> line 68, in
> AmsMonitor().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 282, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py",
> line 42, in start
> action = 'start'
> 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/AMBARI_METRICS/0.1.0/package/scripts/ams_service.py",
> line 103, in ams_service
> user=params.ams_user
> 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 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/sbin/ambari-metrics-monitor --config /etc/ambari-metrics-monitor/conf
> start' returned 255. Hortonworks #
> This is MOTD message, added for testing in qe infra
> psutil build directory is not empty, continuing...
> Verifying Python version compatibility...
> Using python /usr/bin/python2.6
> Checking for previously running Metric Monitor...
> Starting ambari-metrics-monitor
> /usr/sbin/ambari-metrics-monitor: line 148:
> /grid/0/log/metric_monitor/ambari-metrics-monitor.out: Permission denied
> Verifying ambari-metrics-monitor process status...
> ERROR: ambari-metrics-monitor start failed. For more details, see
> /grid/0/log/metric_monitor/ambari-metrics-monitor.out:
>
> 2016-12-14 05:37:41,956 [ERROR] host_info.py:194 - Failed to read disk_usage
> for a mountpoint : [Errno 13] Permission denied:
> '/ycloud-grid/0/hadoop/yarn/local/usercache/root/appcache/application_1481604818073_0640'
> 2016-12-14 05:37:41,956 [ERROR] host_info.py:194 - Failed to read disk_usage
> for a mountpoint : [Errno 13] Permission denied:
> '/ycloud-grid/0/hadoop/yarn/local/usercache/root/appcache/application_1481604818073_0640/container_e83_1481604818073_0640_01_07'
> 2016-12-14 05:37:51,956 [ERROR] host_info.py:194 - Failed to read disk_usage
> for a mountpoint : [Errno 13] Permission denied:
> '/ycloud-grid/0/hadoop/yarn/local/usercache/root/appcache/application_1481604818073_0640'
> 2016-12-14 05:37:51,956 [ERROR] host_info.py:194 - Failed to read disk_usage
> for a mountpoint : [Errno 13] Permission denied:
> '/ycloud-grid/0/hadoop/yarn/local/usercache/root/appcache/application_1481604818073_0640/container_e83_1481604818073_0640_01_07'
> 2016-12-14 05:38:01,957 [ERROR] host_info.py:194 - Failed to read disk_usage
> for a
[jira] [Updated] (AMBARI-19105) Ambari LogSearch REST Layer should use a configurable timeout for HTTP connections to LogSearch Server
[ https://issues.apache.org/jira/browse/AMBARI-19105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Nettleton updated AMBARI-19105: -- Status: Patch Available (was: In Progress) > Ambari LogSearch REST Layer should use a configurable timeout for HTTP > connections to LogSearch Server > -- > > Key: AMBARI-19105 > URL: https://issues.apache.org/jira/browse/AMBARI-19105 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Robert Nettleton >Assignee: Robert Nettleton >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19105.patch > > > The HTTP connection used to make REST calls on the LogSearch Server is > currently using a hard-coded timeout, which was introduced in: > AMBARI-17510 > as part of a fix for a performance issue in LogSearch. > This issue tracks the work to make the connection and read timeouts > configurable for the LogSearch integration code. These timeouts should be > configurable in ambari.properties, and should have valid defaults if not set > by the customer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19204) Metrics monitor start failed after deleting AMS and reinstalling with different user
Aravindan Vijayan created AMBARI-19204:
--
Summary: Metrics monitor start failed after deleting AMS and
reinstalling with different user
Key: AMBARI-19204
URL: https://issues.apache.org/jira/browse/AMBARI-19204
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: 2.5.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Fix For: 2.5.0
STR:
1) Delete Service AMS along with Tez,HBase, Sqoop, Oozie, Falcon, Storm, Ambari
Infra, Ambari Metrics, Kafka, Knox, Log Search, Smartsense, Mahout, Slider
2) Add all the deleted services back
Metrics collector fails to start with
{noformat}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py",
line 68, in
AmsMonitor().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 282, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py",
line 42, in start
action = 'start'
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/AMBARI_METRICS/0.1.0/package/scripts/ams_service.py",
line 103, in ams_service
user=params.ams_user
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 262, in action_run
tries=self.resource.tries, try_sleep=self.resource.try_sleep)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 72, in inner
result = function(command, **kwargs)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 102, in checked_call
tries=tries, try_sleep=try_sleep,
timeout_kill_strategy=timeout_kill_strategy)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 150, in _call_wrapper
result = _call(command, **kwargs_copy)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 303, in _call
raise ExecutionFailed(err_msg, code, out, err)
resource_management.core.exceptions.ExecutionFailed: Execution of
'/usr/sbin/ambari-metrics-monitor --config /etc/ambari-metrics-monitor/conf
start' returned 255. Hortonworks #
This is MOTD message, added for testing in qe infra
psutil build directory is not empty, continuing...
Verifying Python version compatibility...
Using python /usr/bin/python2.6
Checking for previously running Metric Monitor...
Starting ambari-metrics-monitor
/usr/sbin/ambari-metrics-monitor: line 148:
/grid/0/log/metric_monitor/ambari-metrics-monitor.out: Permission denied
Verifying ambari-metrics-monitor process status...
ERROR: ambari-metrics-monitor start failed. For more details, see
/grid/0/log/metric_monitor/ambari-metrics-monitor.out:
2016-12-14 05:37:41,956 [ERROR] host_info.py:194 - Failed to read disk_usage
for a mountpoint : [Errno 13] Permission denied:
'/ycloud-grid/0/hadoop/yarn/local/usercache/root/appcache/application_1481604818073_0640'
2016-12-14 05:37:41,956 [ERROR] host_info.py:194 - Failed to read disk_usage
for a mountpoint : [Errno 13] Permission denied:
'/ycloud-grid/0/hadoop/yarn/local/usercache/root/appcache/application_1481604818073_0640/container_e83_1481604818073_0640_01_07'
2016-12-14 05:37:51,956 [ERROR] host_info.py:194 - Failed to read disk_usage
for a mountpoint : [Errno 13] Permission denied:
'/ycloud-grid/0/hadoop/yarn/local/usercache/root/appcache/application_1481604818073_0640'
2016-12-14 05:37:51,956 [ERROR] host_info.py:194 - Failed to read disk_usage
for a mountpoint : [Errno 13] Permission denied:
'/ycloud-grid/0/hadoop/yarn/local/usercache/root/appcache/application_1481604818073_0640/container_e83_1481604818073_0640_01_07'
2016-12-14 05:38:01,957 [ERROR] host_info.py:194 - Failed to read disk_usage
for a mountpoint : [Errno 13] Permission denied:
'/ycloud-grid/0/hadoop/yarn/local/usercache/root/appcache/application_1481604818073_0640'
2016-12-14 05:38:01,957 [ERROR] host_info.py:194 - Failed to read disk_usage
for a mountpoint : [Errno 13] Permission denied:
'/ycloud-grid/0/hadoop/yarn/local/usercache/root/appcache/application_1481604818073_0640/container_e83_1481604818073_0640_01_07'
2016-12-14 05:38:11,958 [ERROR] host_info.py:194 - Failed to read
[jira] [Commented] (AMBARI-17591) Collect JVM Heap, GC and thread pool metrics from Ambari Server and push to AMS
[
https://issues.apache.org/jira/browse/AMBARI-17591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15749224#comment-15749224
]
Aravindan Vijayan commented on AMBARI-17591:
Pushed to branch-2.5
{code}
commit 98c5d98442099799f961736b7f7264e6f84b5858
Author: Aravindan Vijayan
Date: Wed Dec 14 10:51:46 2016 -0800
AMBARI-17591 : Collect JVM Heap, GC and thread pool metrics from Ambari
Server and push to AMS (Li-Wei Tseng via avijayan)
{code}
> Collect JVM Heap, GC and thread pool metrics from Ambari Server and push to
> AMS
> ---
>
> Key: AMBARI-17591
> URL: https://issues.apache.org/jira/browse/AMBARI-17591
> Project: Ambari
> Issue Type: Task
> Components: ambari-metrics, ambari-server
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Li-Wei Tseng
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-17591.patch
>
>
> 1. Collect JVM Heap, GC and thread pool metrics from Ambari Server
> 2. Implement/Refine an AmbariServer Metrics Sink to push metrics to AMS.
> 3. Visualize using Grafana
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-19202) Devdeploy: Database check failed
[
https://issues.apache.org/jira/browse/AMBARI-19202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi resolved AMBARI-19202.
Resolution: Fixed
Committed to trunk and branch-2.5
> Devdeploy: Database check failed
>
>
> Key: AMBARI-19202
> URL: https://issues.apache.org/jira/browse/AMBARI-19202
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19202.patch
>
>
> From ambari-server-command.log:
> {noformat}
> ERROR 2016-12-13 15:58:09,344 ambari-server.py:865 - 'Fatal exception:
> Database check failed to complete. Please check
> /var/log/ambari-server/ambari-server.log and
> /var/log/ambari-server/ambari-server-check-database.log for more
> information., exit code 1'
> Traceback (most recent call last):
> File "/usr/sbin/ambari-server.py", line 848, in main
> action_obj.execute()
> File "/usr/sbin/ambari-server.py", line 77, in execute
> self.fn(*self.args, **self.kwargs)
> File "/usr/lib/python2.6/site-packages/ambari_server/checkDatabase.py",
> line 85, in check_database
> ' and ' + configDefaults.DB_CHECK_LOG + ' for more information.')
> FatalException: 'Fatal exception: Database check failed to complete. Please
> check /var/log/ambari-server/ambari-server.log and
> /var/log/ambari-server/ambari-server-check-database.log for more
> information., exit code 1'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17591) Collect JVM Heap, GC and thread pool metrics from Ambari Server and push to AMS
[ https://issues.apache.org/jira/browse/AMBARI-17591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-17591: --- Affects Version/s: (was: 3.0.0) 2.5.0 > Collect JVM Heap, GC and thread pool metrics from Ambari Server and push to > AMS > --- > > Key: AMBARI-17591 > URL: https://issues.apache.org/jira/browse/AMBARI-17591 > Project: Ambari > Issue Type: Task > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Li-Wei Tseng >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-17591.patch > > > 1. Collect JVM Heap, GC and thread pool metrics from Ambari Server > 2. Implement/Refine an AmbariServer Metrics Sink to push metrics to AMS. > 3. Visualize using Grafana -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19127) hbase_regionserver_shutdown_timeout should be editable all the time
[ https://issues.apache.org/jira/browse/AMBARI-19127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15749116#comment-15749116 ] Hudson commented on AMBARI-19127: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6233 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6233/]) AMBARI-19127. hbase_regionserver_shutdown_timeout should be editable all (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cb8182e9adaaa29427f4a8d95a04e50f55fde2e8]) * (edit) ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/configuration/hbase-env.xml * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-hbase-env.xml > hbase_regionserver_shutdown_timeout should be editable all the time > --- > > Key: AMBARI-19127 > URL: https://issues.apache.org/jira/browse/AMBARI-19127 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-19127.patch, AMBARI-19127.patch > > > hbase_regionserver_shutdown_timeout should be editable any time. Its now only > editable during install. > > > > > hbase_regionserver_shutdown_timeout > 30 > HBase RegionServer shutdown timeout > > After this number of seconds waiting for graceful stop of HBase Master it > will be forced to exit with SIGKILL. > The timeout is introduced because there is a known bug when from time to > time HBase RegionServer hangs forever on stop if NN safemode is on. > > > int > false > true > > > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19203) LLAP app package cleanup fails after Hive Interactive start failure in non-root
[ https://issues.apache.org/jira/browse/AMBARI-19203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15749112#comment-15749112 ] Hudson commented on AMBARI-19203: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6233 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6233/]) AMBARI-19203. LLAP app package cleanup fails after Hive Interactive (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7dcabf5656963a2b81dae13fa03ac51638b1eb26]) * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py > LLAP app package cleanup fails after Hive Interactive start failure in > non-root > --- > > Key: AMBARI-19203 > URL: https://issues.apache.org/jira/browse/AMBARI-19203 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-19203.patch > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py", > line 380, in _cleanup_past_llap_package_dirs > shutil.rmtree(abs_path) > File "/usr/lib64/python2.7/shutil.py", line 239, in rmtree > onerror(os.listdir, path, sys.exc_info()) > File "/usr/lib64/python2.7/shutil.py", line 237, in rmtree > names = os.listdir(path) > OSError: [Errno 13] Permission denied: > '/var/lib/ambari-agent/tmp/llap-slider2016-12-13_09-11-04' > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17999) Typo in property name "yarn.nodemanager.log.retain-second", should be "seconds"
[ https://issues.apache.org/jira/browse/AMBARI-17999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-17999: --- Fix Version/s: (was: trunk) 2.5.0 > Typo in property name "yarn.nodemanager.log.retain-second", should be > "seconds" > --- > > Key: AMBARI-17999 > URL: https://issues.apache.org/jira/browse/AMBARI-17999 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Ying Zhang >Assignee: Ying Zhang >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-17999.patch, AMBARI-17999.rebased.patch > > > In Ambari code, property name "yarn.nodemanager.log.retain-second" is wrong. > It should be "yarn.nodemanager.log.retain-seconds" instead, which is the > property name being looked up in Hadoop code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17999) Typo in property name "yarn.nodemanager.log.retain-second", should be "seconds"
[
https://issues.apache.org/jira/browse/AMBARI-17999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15749026#comment-15749026
]
Aravindan Vijayan commented on AMBARI-17999:
Pushed to branch-2.5
{code}
commit fb86ef73906f33ffc1d488b97eff127409c256c3
Author: Aravindan Vijayan
Date: Tue Dec 13 13:23:30 2016 -0800
AMBARI-17999 Typo in property name yarn.nodemanager.log.retain-second,
should be seconds. (Ying Zhang via avijayan)
{code}
> Typo in property name "yarn.nodemanager.log.retain-second", should be
> "seconds"
> ---
>
> Key: AMBARI-17999
> URL: https://issues.apache.org/jira/browse/AMBARI-17999
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Ying Zhang
>Assignee: Ying Zhang
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-17999.patch, AMBARI-17999.rebased.patch
>
>
> In Ambari code, property name "yarn.nodemanager.log.retain-second" is wrong.
> It should be "yarn.nodemanager.log.retain-seconds" instead, which is the
> property name being looked up in Hadoop code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19203) LLAP app package cleanup fails after Hive Interactive start failure in non-root
[ https://issues.apache.org/jira/browse/AMBARI-19203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-19203: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > LLAP app package cleanup fails after Hive Interactive start failure in > non-root > --- > > Key: AMBARI-19203 > URL: https://issues.apache.org/jira/browse/AMBARI-19203 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-19203.patch > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py", > line 380, in _cleanup_past_llap_package_dirs > shutil.rmtree(abs_path) > File "/usr/lib64/python2.7/shutil.py", line 239, in rmtree > onerror(os.listdir, path, sys.exc_info()) > File "/usr/lib64/python2.7/shutil.py", line 237, in rmtree > names = os.listdir(path) > OSError: [Errno 13] Permission denied: > '/var/lib/ambari-agent/tmp/llap-slider2016-12-13_09-11-04' > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19127) hbase_regionserver_shutdown_timeout should be editable all the time
[ https://issues.apache.org/jira/browse/AMBARI-19127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-19127: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > hbase_regionserver_shutdown_timeout should be editable all the time > --- > > Key: AMBARI-19127 > URL: https://issues.apache.org/jira/browse/AMBARI-19127 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-19127.patch, AMBARI-19127.patch > > > hbase_regionserver_shutdown_timeout should be editable any time. Its now only > editable during install. > > > > > hbase_regionserver_shutdown_timeout > 30 > HBase RegionServer shutdown timeout > > After this number of seconds waiting for graceful stop of HBase Master it > will be forced to exit with SIGKILL. > The timeout is introduced because there is a known bug when from time to > time HBase RegionServer hangs forever on stop if NN safemode is on. > > > int > false > true > > > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19193) Add common log rotation settings to YARN Configs
[ https://issues.apache.org/jira/browse/AMBARI-19193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748980#comment-15748980 ] Hudson commented on AMBARI-19193: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6232 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6232/]) AMBARI-19193. Add common log rotation settings to YARN Configs (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=30511fad8a454f57c90b5a0bcde9c6e188495f3b]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/YARN/configuration/yarn-log4j.xml > Add common log rotation settings to YARN Configs > > > Key: AMBARI-19193 > URL: https://issues.apache.org/jira/browse/AMBARI-19193 > Project: Ambari > Issue Type: Task >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-19193.patch > > > Add common log rotation settings to YARN. > log4j.appender.RMSUMMARY.MaxFileSize > log4j.appender.RMSUMMARY.MaxBackupIndex -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17666) Ambari agent can't start when TLSv1 is disabled in Java security
[ https://issues.apache.org/jira/browse/AMBARI-17666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748978#comment-15748978 ] Hudson commented on AMBARI-17666: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6232 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6232/]) AMBARI-17666. Ambari agent can't start when TLSv1 is disabled in Java (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=db9dfd60a1930c3ee18322179a1ebe3d795263e8]) * (edit) ambari-common/src/main/python/resource_management/libraries/script/script.py * (edit) ambari-agent/src/main/python/ambari_agent/AmbariConfig.py * (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/service_check.py * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/utils.py * (edit) ambari-common/src/main/python/ambari_commons/inet_utils.py * (edit) ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/params.py * (edit) ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/service_check.py * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params.py * (edit) ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/files/checkWebUI.py * (edit) ambari-agent/src/test/python/ambari_agent/TestCustomServiceOrchestrator.py * (edit) ambari-agent/src/main/python/ambari_agent/NetUtil.py > Ambari agent can't start when TLSv1 is disabled in Java security > > > Key: AMBARI-17666 > URL: https://issues.apache.org/jira/browse/AMBARI-17666 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.2.0 >Reporter: Tuong Truong >Assignee: Dmitry Lysnichenko > Labels: security > Fix For: 2.5.0 > > > Currently, the commit for https://issues.apache.org/jira/browse/AMBARI-14236 > explicit force the SSL protocol to TLSv1 in > ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py. Unfortunate, > this setting in effect whenever web_alert pacackged is loaded > (ambari-agent/src/main/python/ambari_agent/AlertSchedulerHandler.py) > regardless whether ssl is used or not. > As a result, disabling TLSv1 in Ambari server will cause the agent to fail to > start. > Recreate: > In Ambari's acitve JDK on Ambari server node, in java.security file, set > jdk.tls.disabledAlgorithms=MD5, SSLv2, SSLv3, TLSv1, DSA, RC4, RSA keySize < > 2048 > restart ambari-server, and you will see errors in ambari agent logs: > ERROR 2016-07-11 15:11:15,269 NetUtil.py:84 - [Errno 8] _ssl.c:492: EOF > occurred in violation of protocol > ERROR 2016-07-11 15:11:15,269 NetUtil.py:85 - SSLError: Failed to connect. > Please check openssl library versions. > Refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1022468 for more > details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19126) Spark 2.x interpreter confgurations in Zeppelin
[
https://issues.apache.org/jira/browse/AMBARI-19126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748952#comment-15748952
]
Hadoop QA commented on AMBARI-19126:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843262/AMBARI-19126-branch-2.5-v2.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:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9668//console
This message is automatically generated.
> Spark 2.x interpreter confgurations in Zeppelin
> ---
>
> Key: AMBARI-19126
> URL: https://issues.apache.org/jira/browse/AMBARI-19126
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Reporter: Renjith Kamath
>Assignee: Renjith Kamath
> Fix For: 2.5.0
>
> Attachments: AMBARI-19126-branch-2.5-v1.patch,
> AMBARI-19126-branch-2.5-v2.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (AMBARI-19172) 'Backup Oozie DB' message is masked when FixOozieAdminUsers code is invoked in EU wizard
[ https://issues.apache.org/jira/browse/AMBARI-19172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko reassigned AMBARI-19172: Assignee: Dmytro Grinenko > 'Backup Oozie DB' message is masked when FixOozieAdminUsers code is invoked > in EU wizard > > > Key: AMBARI-19172 > URL: https://issues.apache.org/jira/browse/AMBARI-19172 > Project: Ambari > Issue Type: Bug > Components: ambari-upgrade >Affects Versions: 2.5.0 >Reporter: Vivek Sharma >Assignee: Dmytro Grinenko >Priority: Critical > Labels: express_upgrade > Fix For: 2.5.0 > > Attachments: Error.png, Working.png > > > EU path from HDP-2.3.6.0 to 2.6.0.0 with Ambari-2.5.0.0 > In upgrade pack: > There are two tasks: > a. Fix oozie admin users > b. Manual prompt to 'Backup Oozie Database' > When a.) gets invoked then the manual prompt message to backup Oozie DB gets > suppressed. As a result user is not informed to backup the Oozie DB before > the actual upgrade > Please see attached screenshots -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19202) Devdeploy: Database check failed
[
https://issues.apache.org/jira/browse/AMBARI-19202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748915#comment-15748915
]
Hudson commented on AMBARI-19202:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6231 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6231/])
AMBARI-19202. Devdeploy: Database check failed.(vbrodetskyi) (vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4910de95e36e3d15144b8e61f98499d117c6692d])
* (edit) ambari-common/src/main/python/ambari_commons/os_linux.py
* (edit) ambari-server/src/main/python/ambari_server/checkDatabase.py
> Devdeploy: Database check failed
>
>
> Key: AMBARI-19202
> URL: https://issues.apache.org/jira/browse/AMBARI-19202
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19202.patch
>
>
> From ambari-server-command.log:
> {noformat}
> ERROR 2016-12-13 15:58:09,344 ambari-server.py:865 - 'Fatal exception:
> Database check failed to complete. Please check
> /var/log/ambari-server/ambari-server.log and
> /var/log/ambari-server/ambari-server-check-database.log for more
> information., exit code 1'
> Traceback (most recent call last):
> File "/usr/sbin/ambari-server.py", line 848, in main
> action_obj.execute()
> File "/usr/sbin/ambari-server.py", line 77, in execute
> self.fn(*self.args, **self.kwargs)
> File "/usr/lib/python2.6/site-packages/ambari_server/checkDatabase.py",
> line 85, in check_database
> ' and ' + configDefaults.DB_CHECK_LOG + ' for more information.')
> FatalException: 'Fatal exception: Database check failed to complete. Please
> check /var/log/ambari-server/ambari-server.log and
> /var/log/ambari-server/ambari-server-check-database.log for more
> information., exit code 1'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19126) Spark 2.x interpreter confgurations in Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-19126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith Kamath updated AMBARI-19126: Attachment: AMBARI-19126-branch-2.5-v2.patch > Spark 2.x interpreter confgurations in Zeppelin > --- > > Key: AMBARI-19126 > URL: https://issues.apache.org/jira/browse/AMBARI-19126 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Renjith Kamath >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-19126-branch-2.5-v1.patch, > AMBARI-19126-branch-2.5-v2.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17666) Ambari agent can't start when TLSv1 is disabled in Java security
[ https://issues.apache.org/jira/browse/AMBARI-17666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17666: Resolution: Fixed Status: Resolved (was: Patch Available) Committed To https://git-wip-us.apache.org/repos/asf/ambari.git e1f7795..ecc916b branch-2.5 -> branch-2.5 30511fa..db9dfd6 trunk -> trunk > Ambari agent can't start when TLSv1 is disabled in Java security > > > Key: AMBARI-17666 > URL: https://issues.apache.org/jira/browse/AMBARI-17666 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.2.0 >Reporter: Tuong Truong >Assignee: Dmitry Lysnichenko > Labels: security > Fix For: 2.5.0 > > > Currently, the commit for https://issues.apache.org/jira/browse/AMBARI-14236 > explicit force the SSL protocol to TLSv1 in > ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py. Unfortunate, > this setting in effect whenever web_alert pacackged is loaded > (ambari-agent/src/main/python/ambari_agent/AlertSchedulerHandler.py) > regardless whether ssl is used or not. > As a result, disabling TLSv1 in Ambari server will cause the agent to fail to > start. > Recreate: > In Ambari's acitve JDK on Ambari server node, in java.security file, set > jdk.tls.disabledAlgorithms=MD5, SSLv2, SSLv3, TLSv1, DSA, RC4, RSA keySize < > 2048 > restart ambari-server, and you will see errors in ambari agent logs: > ERROR 2016-07-11 15:11:15,269 NetUtil.py:84 - [Errno 8] _ssl.c:492: EOF > occurred in violation of protocol > ERROR 2016-07-11 15:11:15,269 NetUtil.py:85 - SSLError: Failed to connect. > Please check openssl library versions. > Refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1022468 for more > details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19203) LLAP app package cleanup fails after Hive Interactive start failure in non-root
[
https://issues.apache.org/jira/browse/AMBARI-19203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748882#comment-15748882
]
Hadoop QA commented on AMBARI-19203:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843249/AMBARI-19203.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/9667//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9667//console
This message is automatically generated.
> LLAP app package cleanup fails after Hive Interactive start failure in
> non-root
> ---
>
> Key: AMBARI-19203
> URL: https://issues.apache.org/jira/browse/AMBARI-19203
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19203.patch
>
>
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py",
> line 380, in _cleanup_past_llap_package_dirs
> shutil.rmtree(abs_path)
> File "/usr/lib64/python2.7/shutil.py", line 239, in rmtree
> onerror(os.listdir, path, sys.exc_info())
> File "/usr/lib64/python2.7/shutil.py", line 237, in rmtree
> names = os.listdir(path)
> OSError: [Errno 13] Permission denied:
> '/var/lib/ambari-agent/tmp/llap-slider2016-12-13_09-11-04'
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19193) Add common log rotation settings to YARN Configs
[ https://issues.apache.org/jira/browse/AMBARI-19193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19193: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > Add common log rotation settings to YARN Configs > > > Key: AMBARI-19193 > URL: https://issues.apache.org/jira/browse/AMBARI-19193 > Project: Ambari > Issue Type: Task >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-19193.patch > > > Add common log rotation settings to YARN. > log4j.appender.RMSUMMARY.MaxFileSize > log4j.appender.RMSUMMARY.MaxBackupIndex -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19164) Add PK to hostcomponentdesiredstate Table To Support FK Relationships
[
https://issues.apache.org/jira/browse/AMBARI-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748835#comment-15748835
]
Sebastian Toader commented on AMBARI-19164:
---
The failing
{{org.apache.ambari.server.controller.metrics.JMXPropertyProviderTest}} seems
to be intermittent and is not caused by this patch.
> Add PK to hostcomponentdesiredstate Table To Support FK Relationships
> -
>
> Key: AMBARI-19164
> URL: https://issues.apache.org/jira/browse/AMBARI-19164
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19164.v1.patch
>
>
> The {{hostcomponentdesiredstate}} table currently uses a compound PK based
> off of the cluster ID, service name, host id and component name. There are
> several problems with this approach:
> * Primary Keys should be data that's not part of the business logic of the
> system and not subject to be changed potentially (as strings are).
> * Other tables referencing the {{hostcomponentdesiredstate}} table would now
> need knowledge of cluster/service/component/host in order to make the correct
> FK association. This leads to extra data being tracked as well as data
> duplication.
> * Some databases, such as SQL Server, have problems with the indexing of
> compound PKs and may lead to deadlocks when querying and updating
> concurrently.
> This table needs to be changed so that it uses a simple PK for referencing.
> FK relationships as they exist today can still be maintained as long as a
> {{UNIQUE}} constraint is placed on the table. We should:
> * Add a {{UNIQUE}} constraint to the former PK columns
> * Add an {{INDEX}} to the former PK columns
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19164) Add PK to hostcomponentdesiredstate Table To Support FK Relationships
[
https://issues.apache.org/jira/browse/AMBARI-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748807#comment-15748807
]
Hadoop QA commented on AMBARI-19164:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843228/AMBARI-19164.v1.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 5 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.controller.metrics.JMXPropertyProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9666//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9666//console
This message is automatically generated.
> Add PK to hostcomponentdesiredstate Table To Support FK Relationships
> -
>
> Key: AMBARI-19164
> URL: https://issues.apache.org/jira/browse/AMBARI-19164
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19164.v1.patch
>
>
> The {{hostcomponentdesiredstate}} table currently uses a compound PK based
> off of the cluster ID, service name, host id and component name. There are
> several problems with this approach:
> * Primary Keys should be data that's not part of the business logic of the
> system and not subject to be changed potentially (as strings are).
> * Other tables referencing the {{hostcomponentdesiredstate}} table would now
> need knowledge of cluster/service/component/host in order to make the correct
> FK association. This leads to extra data being tracked as well as data
> duplication.
> * Some databases, such as SQL Server, have problems with the indexing of
> compound PKs and may lead to deadlocks when querying and updating
> concurrently.
> This table needs to be changed so that it uses a simple PK for referencing.
> FK relationships as they exist today can still be maintained as long as a
> {{UNIQUE}} constraint is placed on the table. We should:
> * Add a {{UNIQUE}} constraint to the former PK columns
> * Add an {{INDEX}} to the former PK columns
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19203) LLAP app package cleanup fails after Hive Interactive start failure in non-root
[ https://issues.apache.org/jira/browse/AMBARI-19203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-19203: - Attachment: AMBARI-19203.patch > LLAP app package cleanup fails after Hive Interactive start failure in > non-root > --- > > Key: AMBARI-19203 > URL: https://issues.apache.org/jira/browse/AMBARI-19203 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-19203.patch > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py", > line 380, in _cleanup_past_llap_package_dirs > shutil.rmtree(abs_path) > File "/usr/lib64/python2.7/shutil.py", line 239, in rmtree > onerror(os.listdir, path, sys.exc_info()) > File "/usr/lib64/python2.7/shutil.py", line 237, in rmtree > names = os.listdir(path) > OSError: [Errno 13] Permission denied: > '/var/lib/ambari-agent/tmp/llap-slider2016-12-13_09-11-04' > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19203) LLAP app package cleanup fails after Hive Interactive start failure in non-root
[ https://issues.apache.org/jira/browse/AMBARI-19203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-19203: - Status: Patch Available (was: Open) > LLAP app package cleanup fails after Hive Interactive start failure in > non-root > --- > > Key: AMBARI-19203 > URL: https://issues.apache.org/jira/browse/AMBARI-19203 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-19203.patch > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py", > line 380, in _cleanup_past_llap_package_dirs > shutil.rmtree(abs_path) > File "/usr/lib64/python2.7/shutil.py", line 239, in rmtree > onerror(os.listdir, path, sys.exc_info()) > File "/usr/lib64/python2.7/shutil.py", line 237, in rmtree > names = os.listdir(path) > OSError: [Errno 13] Permission denied: > '/var/lib/ambari-agent/tmp/llap-slider2016-12-13_09-11-04' > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19203) LLAP app package cleanup fails after Hive Interactive start failure in non-root
Andrew Onischuk created AMBARI-19203: Summary: LLAP app package cleanup fails after Hive Interactive start failure in non-root Key: AMBARI-19203 URL: https://issues.apache.org/jira/browse/AMBARI-19203 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.5.0 Attachments: AMBARI-19203.patch Traceback (most recent call last): File "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py", line 380, in _cleanup_past_llap_package_dirs shutil.rmtree(abs_path) File "/usr/lib64/python2.7/shutil.py", line 239, in rmtree onerror(os.listdir, path, sys.exc_info()) File "/usr/lib64/python2.7/shutil.py", line 237, in rmtree names = os.listdir(path) OSError: [Errno 13] Permission denied: '/var/lib/ambari-agent/tmp/llap-slider2016-12-13_09-11-04' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19200) Turning OFF maintenance mode shows a popup on all hosts
[ https://issues.apache.org/jira/browse/AMBARI-19200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748749#comment-15748749 ] Hudson commented on AMBARI-19200: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6230 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6230/]) AMBARI-19200 Turning OFF maintenance mode shows a popup on all hosts. (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b028fc86ab8898c9e9621bdd0907826431301e65]) * (edit) ambari-web/app/controllers/global/cluster_controller.js * (edit) ambari-web/test/controllers/global/cluster_controller_test.js > Turning OFF maintenance mode shows a popup on all hosts > --- > > Key: AMBARI-19200 > URL: https://issues.apache.org/jira/browse/AMBARI-19200 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19200.patch > > > STEPS TO REPRODUCE: > # Complete upgrade > # Pick a random node > # Set Maintenance mode ON > # Set Maintenance mode OFF -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19200) Turning OFF maintenance mode shows a popup on all hosts
[ https://issues.apache.org/jira/browse/AMBARI-19200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748745#comment-15748745 ] Hudson commented on AMBARI-19200: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #528 (See [https://builds.apache.org/job/Ambari-branch-2.5/528/]) AMBARI-19200 Turning OFF maintenance mode shows a popup on all hosts. (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d29220d8a09df7eef509b8cc4f7792d28980943e]) * (edit) ambari-web/test/controllers/global/cluster_controller_test.js * (edit) ambari-web/app/controllers/global/cluster_controller.js > Turning OFF maintenance mode shows a popup on all hosts > --- > > Key: AMBARI-19200 > URL: https://issues.apache.org/jira/browse/AMBARI-19200 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19200.patch > > > STEPS TO REPRODUCE: > # Complete upgrade > # Pick a random node > # Set Maintenance mode ON > # Set Maintenance mode OFF -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19202) Devdeploy: Database check failed
[
https://issues.apache.org/jira/browse/AMBARI-19202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-19202:
---
Attachment: AMBARI-19202.patch
> Devdeploy: Database check failed
>
>
> Key: AMBARI-19202
> URL: https://issues.apache.org/jira/browse/AMBARI-19202
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19202.patch
>
>
> From ambari-server-command.log:
> {noformat}
> ERROR 2016-12-13 15:58:09,344 ambari-server.py:865 - 'Fatal exception:
> Database check failed to complete. Please check
> /var/log/ambari-server/ambari-server.log and
> /var/log/ambari-server/ambari-server-check-database.log for more
> information., exit code 1'
> Traceback (most recent call last):
> File "/usr/sbin/ambari-server.py", line 848, in main
> action_obj.execute()
> File "/usr/sbin/ambari-server.py", line 77, in execute
> self.fn(*self.args, **self.kwargs)
> File "/usr/lib/python2.6/site-packages/ambari_server/checkDatabase.py",
> line 85, in check_database
> ' and ' + configDefaults.DB_CHECK_LOG + ' for more information.')
> FatalException: 'Fatal exception: Database check failed to complete. Please
> check /var/log/ambari-server/ambari-server.log and
> /var/log/ambari-server/ambari-server-check-database.log for more
> information., exit code 1'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19202) Devdeploy: Database check failed
Vitaly Brodetskyi created AMBARI-19202:
--
Summary: Devdeploy: Database check failed
Key: AMBARI-19202
URL: https://issues.apache.org/jira/browse/AMBARI-19202
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Critical
Fix For: 2.5.0
>From ambari-server-command.log:
{noformat}
ERROR 2016-12-13 15:58:09,344 ambari-server.py:865 - 'Fatal exception: Database
check failed to complete. Please check /var/log/ambari-server/ambari-server.log
and /var/log/ambari-server/ambari-server-check-database.log for more
information., exit code 1'
Traceback (most recent call last):
File "/usr/sbin/ambari-server.py", line 848, in main
action_obj.execute()
File "/usr/sbin/ambari-server.py", line 77, in execute
self.fn(*self.args, **self.kwargs)
File "/usr/lib/python2.6/site-packages/ambari_server/checkDatabase.py", line
85, in check_database
' and ' + configDefaults.DB_CHECK_LOG + ' for more information.')
FatalException: 'Fatal exception: Database check failed to complete. Please
check /var/log/ambari-server/ambari-server.log and
/var/log/ambari-server/ambari-server-check-database.log for more information.,
exit code 1'
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19188) Provide Atlas Hook support for Hive2
[
https://issues.apache.org/jira/browse/AMBARI-19188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748690#comment-15748690
]
Hadoop QA commented on AMBARI-19188:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843226/AMBARI-19188.1.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:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9665//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9665//console
This message is automatically generated.
> Provide Atlas Hook support for Hive2
>
>
> Key: AMBARI-19188
> URL: https://issues.apache.org/jira/browse/AMBARI-19188
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-19188.1.patch, AMBARI-19188.patch
>
>
> Need to provide Atlas hook configuration support for HiveServer-Interactive.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17666) Ambari agent can't start when TLSv1 is disabled in Java security
[ https://issues.apache.org/jira/browse/AMBARI-17666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17666: Status: Patch Available (was: Open) > Ambari agent can't start when TLSv1 is disabled in Java security > > > Key: AMBARI-17666 > URL: https://issues.apache.org/jira/browse/AMBARI-17666 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.2.0 >Reporter: Tuong Truong >Assignee: Dmitry Lysnichenko > Labels: security > Fix For: 2.5.0 > > > Currently, the commit for https://issues.apache.org/jira/browse/AMBARI-14236 > explicit force the SSL protocol to TLSv1 in > ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py. Unfortunate, > this setting in effect whenever web_alert pacackged is loaded > (ambari-agent/src/main/python/ambari_agent/AlertSchedulerHandler.py) > regardless whether ssl is used or not. > As a result, disabling TLSv1 in Ambari server will cause the agent to fail to > start. > Recreate: > In Ambari's acitve JDK on Ambari server node, in java.security file, set > jdk.tls.disabledAlgorithms=MD5, SSLv2, SSLv3, TLSv1, DSA, RC4, RSA keySize < > 2048 > restart ambari-server, and you will see errors in ambari agent logs: > ERROR 2016-07-11 15:11:15,269 NetUtil.py:84 - [Errno 8] _ssl.c:492: EOF > occurred in violation of protocol > ERROR 2016-07-11 15:11:15,269 NetUtil.py:85 - SSLError: Failed to connect. > Please check openssl library versions. > Refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1022468 for more > details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17666) Ambari agent can't start when TLSv1 is disabled in Java security
[ https://issues.apache.org/jira/browse/AMBARI-17666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-17666: Fix Version/s: 2.5.0 > Ambari agent can't start when TLSv1 is disabled in Java security > > > Key: AMBARI-17666 > URL: https://issues.apache.org/jira/browse/AMBARI-17666 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.2.0 >Reporter: Tuong Truong >Assignee: Robert Levas > Labels: security > Fix For: 2.5.0 > > > Currently, the commit for https://issues.apache.org/jira/browse/AMBARI-14236 > explicit force the SSL protocol to TLSv1 in > ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py. Unfortunate, > this setting in effect whenever web_alert pacackged is loaded > (ambari-agent/src/main/python/ambari_agent/AlertSchedulerHandler.py) > regardless whether ssl is used or not. > As a result, disabling TLSv1 in Ambari server will cause the agent to fail to > start. > Recreate: > In Ambari's acitve JDK on Ambari server node, in java.security file, set > jdk.tls.disabledAlgorithms=MD5, SSLv2, SSLv3, TLSv1, DSA, RC4, RSA keySize < > 2048 > restart ambari-server, and you will see errors in ambari agent logs: > ERROR 2016-07-11 15:11:15,269 NetUtil.py:84 - [Errno 8] _ssl.c:492: EOF > occurred in violation of protocol > ERROR 2016-07-11 15:11:15,269 NetUtil.py:85 - SSLError: Failed to connect. > Please check openssl library versions. > Refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1022468 for more > details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19200) Turning OFF maintenance mode shows a popup on all hosts
[ https://issues.apache.org/jira/browse/AMBARI-19200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19200: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Turning OFF maintenance mode shows a popup on all hosts > --- > > Key: AMBARI-19200 > URL: https://issues.apache.org/jira/browse/AMBARI-19200 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19200.patch > > > STEPS TO REPRODUCE: > # Complete upgrade > # Pick a random node > # Set Maintenance mode ON > # Set Maintenance mode OFF -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19200) Turning OFF maintenance mode shows a popup on all hosts
[ https://issues.apache.org/jira/browse/AMBARI-19200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748651#comment-15748651 ] Andrii Tkach commented on AMBARI-19200: --- committed to trunk and branch-2.5 > Turning OFF maintenance mode shows a popup on all hosts > --- > > Key: AMBARI-19200 > URL: https://issues.apache.org/jira/browse/AMBARI-19200 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19200.patch > > > STEPS TO REPRODUCE: > # Complete upgrade > # Pick a random node > # Set Maintenance mode ON > # Set Maintenance mode OFF -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19200) Turning OFF maintenance mode shows a popup on all hosts
[
https://issues.apache.org/jira/browse/AMBARI-19200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748639#comment-15748639
]
Hadoop QA commented on AMBARI-19200:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843223/AMBARI-19200.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-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9664//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9664//console
This message is automatically generated.
> Turning OFF maintenance mode shows a popup on all hosts
> ---
>
> Key: AMBARI-19200
> URL: https://issues.apache.org/jira/browse/AMBARI-19200
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19200.patch
>
>
> STEPS TO REPRODUCE:
> # Complete upgrade
> # Pick a random node
> # Set Maintenance mode ON
> # Set Maintenance mode OFF
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19201) Log size of status command queue size on Ambari agent
Sandor Magyari created AMBARI-19201: --- Summary: Log size of status command queue size on Ambari agent Key: AMBARI-19201 URL: https://issues.apache.org/jira/browse/AMBARI-19201 Project: Ambari Issue Type: Improvement Components: ambari-agent Reporter: Sandor Magyari Assignee: Sandor Magyari Fix For: 2.5.0 Before adding new status commands to agent statusCommandQueue, we delete old ones. Sometimes status command execution may take too long therefore would be useful to log statusCommandQueue size before emptying. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19196) BG operations modal windows are too small to show the content (in certain scenarios) [Chrome]
[
https://issues.apache.org/jira/browse/AMBARI-19196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748560#comment-15748560
]
Hadoop QA commented on AMBARI-19196:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843201/AMBARI-19196_branch-2.5.patch
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/9663//console
This message is automatically generated.
> BG operations modal windows are too small to show the content (in certain
> scenarios) [Chrome]
> -
>
> Key: AMBARI-19196
> URL: https://issues.apache.org/jira/browse/AMBARI-19196
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-19196.patch, AMBARI-19196_branch-2.5.patch
>
>
> 1. Login to Ambari
> 2. Click on BG operations.
> 3. Click on some action link which have relatively lesser content, e.g Hosts,
> with only one host link.
> 4. Click on the link to get more details
> 5. Intermittently the details window also have the same dimension of the
> previous window and as a result the user is not able to view the content
> BG operations modal window should be resizable as intermittently modal
> windows are too small to view the content[Chrome].
> This behavior is observed when we navigate to the granular details and the
> previous window was smaller size due to lesser content. Please see the
> screenshots
> Intermittently the details window also have the same dimension of the
> previous window and as a result the user is not able to view the content
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19031) AMBARI-19031: UI Enhancements, import/export assets and smart version configuration
[
https://issues.apache.org/jira/browse/AMBARI-19031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748557#comment-15748557
]
Hadoop QA commented on AMBARI-19031:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843206/AMBARI-19031.02.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 7 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 test build failed in
contrib/views/wfmanager/src/main/resources/ui contrib/views/wfmanager
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9662//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9662//console
This message is automatically generated.
> AMBARI-19031: UI Enhancements, import/export assets and smart version
> configuration
> ---
>
> Key: AMBARI-19031
> URL: https://issues.apache.org/jira/browse/AMBARI-19031
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Padma Priya Nagaraj
> Fix For: 2.5.0
>
> Attachments: AMBARI-19031.01.patch, AMBARI-19031.02.patch
>
>
> UX Enhancemenets
> - Dashboard as a tab
> - Coordinator UI changes
> - Bundle smart name autofil
> Features
> - Version setting picked up from Oozie
> - Ability to import/export assets(actions)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19197) Kerberos advanced tab. Page wasn't refreshed after save changes. Save button is disabled.
[ https://issues.apache.org/jira/browse/AMBARI-19197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748547#comment-15748547 ] Hudson commented on AMBARI-19197: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #527 (See [https://builds.apache.org/job/Ambari-branch-2.5/527/]) AMBARI-19197. Kerberos advanced tab. Page wasn't refreshed after save (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2e5d2a9d3ce1168741bc846c1d20c58484d2b9dd]) * (edit) ambari-web/app/templates/main/admin/kerberos.hbs > Kerberos advanced tab. Page wasn't refreshed after save changes. Save button > is disabled. > - > > Key: AMBARI-19197 > URL: https://issues.apache.org/jira/browse/AMBARI-19197 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Denys Buzhor >Assignee: Denys Buzhor > Fix For: 2.5.0 > > Attachments: AMBARI-19197.patch, AMBARI-19197_branch_2.5.patch > > > STR: > # change properties on kerb advanced tab > # save and regenerate keytab > # wait for complete > # change properties on kerb advanced tab > Result: > Save button is disabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19196) BG operations modal windows are too small to show the content (in certain scenarios) [Chrome]
[ https://issues.apache.org/jira/browse/AMBARI-19196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748542#comment-15748542 ] Hudson commented on AMBARI-19196: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #527 (See [https://builds.apache.org/job/Ambari-branch-2.5/527/]) AMBARI-19196. BG operations modal windows are too small to show the (onechiporenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=22b027efb782cb4b33cc0a487262ad8de9cc097e]) * (edit) ambari-web/app/views/common/modal_popup.js > BG operations modal windows are too small to show the content (in certain > scenarios) [Chrome] > - > > Key: AMBARI-19196 > URL: https://issues.apache.org/jira/browse/AMBARI-19196 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 2.5.0 > > Attachments: AMBARI-19196.patch, AMBARI-19196_branch-2.5.patch > > > 1. Login to Ambari > 2. Click on BG operations. > 3. Click on some action link which have relatively lesser content, e.g Hosts, > with only one host link. > 4. Click on the link to get more details > 5. Intermittently the details window also have the same dimension of the > previous window and as a result the user is not able to view the content > BG operations modal window should be resizable as intermittently modal > windows are too small to view the content[Chrome]. > This behavior is observed when we navigate to the granular details and the > previous window was smaller size due to lesser content. Please see the > screenshots > Intermittently the details window also have the same dimension of the > previous window and as a result the user is not able to view the content -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19197) Kerberos advanced tab. Page wasn't refreshed after save changes. Save button is disabled.
[ https://issues.apache.org/jira/browse/AMBARI-19197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748519#comment-15748519 ] Hudson commented on AMBARI-19197: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6229 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6229/]) AMBARI-19197. Kerberos advanced tab. Page wasn't refreshed after save (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b0e4c938935b3eaee076b419d081439dec6c7812]) * (edit) ambari-web/app/templates/main/admin/kerberos.hbs > Kerberos advanced tab. Page wasn't refreshed after save changes. Save button > is disabled. > - > > Key: AMBARI-19197 > URL: https://issues.apache.org/jira/browse/AMBARI-19197 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Denys Buzhor >Assignee: Denys Buzhor > Fix For: 2.5.0 > > Attachments: AMBARI-19197.patch, AMBARI-19197_branch_2.5.patch > > > STR: > # change properties on kerb advanced tab > # save and regenerate keytab > # wait for complete > # change properties on kerb advanced tab > Result: > Save button is disabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19196) BG operations modal windows are too small to show the content (in certain scenarios) [Chrome]
[ https://issues.apache.org/jira/browse/AMBARI-19196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748516#comment-15748516 ] Hudson commented on AMBARI-19196: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6229 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6229/]) AMBARI-19196. BG operations modal windows are too small to show the (onechiporenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6153b03725d41bbfbd7c801643ec808184817dc7]) * (edit) ambari-web/app/views/common/modal_popup.js * (edit) ambari-web/test/controllers/main/admin/kerberos/step1_controller_test.js > BG operations modal windows are too small to show the content (in certain > scenarios) [Chrome] > - > > Key: AMBARI-19196 > URL: https://issues.apache.org/jira/browse/AMBARI-19196 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 2.5.0 > > Attachments: AMBARI-19196.patch, AMBARI-19196_branch-2.5.patch > > > 1. Login to Ambari > 2. Click on BG operations. > 3. Click on some action link which have relatively lesser content, e.g Hosts, > with only one host link. > 4. Click on the link to get more details > 5. Intermittently the details window also have the same dimension of the > previous window and as a result the user is not able to view the content > BG operations modal window should be resizable as intermittently modal > windows are too small to view the content[Chrome]. > This behavior is observed when we navigate to the granular details and the > previous window was smaller size due to lesser content. Please see the > screenshots > Intermittently the details window also have the same dimension of the > previous window and as a result the user is not able to view the content -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748455#comment-15748455
]
Hadoop QA commented on AMBARI-19149:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843210/AMBARI-19149-3.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/9661//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9661//console
This message is automatically generated.
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, AMBARI-19149-3.patch,
> IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19199) AMS config types created by upgrade were never marked as selected
[
https://issues.apache.org/jira/browse/AMBARI-19199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748434#comment-15748434
]
Hudson commented on AMBARI-19199:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #526 (See
[https://builds.apache.org/job/Ambari-branch-2.5/526/])
AMBARI-19199 AMS config types created by upgrade were never marked as (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=18ed887263cc66cd3c6063425109ad1e2c504e93])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java
> AMS config types created by upgrade were never marked as selected
> -
>
> Key: AMBARI-19199
> URL: https://issues.apache.org/jira/browse/AMBARI-19199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.4.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19199.patch
>
>
> Query to identify the problem:
> {noformat}
> ambari=> select type_name, sum(selected),
> MAX(to_timestamp(create_timestamp/1000)) from clusterconfigmapping group by
> type_name order by sum;
> type_name | sum | max
> -+-+
> ams-hbase-policy| 0 | 2015-11-05 15:57:28+00
> ams-hbase-security-site | 0 | 2016-05-02 18:09:34+00
> ams-log4j | 0 | 2015-11-05 15:57:28+00
> ams-hbase-log4j | 0 | 2015-11-05 15:57:28+00
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19199) AMS config types created by upgrade were never marked as selected
[
https://issues.apache.org/jira/browse/AMBARI-19199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748412#comment-15748412
]
Hudson commented on AMBARI-19199:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6228 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6228/])
AMBARI-19199 AMS config types created by upgrade were never marked as (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b50546e0cfa1fdb415d10d0e197c72fd7c9a195f])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java
> AMS config types created by upgrade were never marked as selected
> -
>
> Key: AMBARI-19199
> URL: https://issues.apache.org/jira/browse/AMBARI-19199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.4.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19199.patch
>
>
> Query to identify the problem:
> {noformat}
> ambari=> select type_name, sum(selected),
> MAX(to_timestamp(create_timestamp/1000)) from clusterconfigmapping group by
> type_name order by sum;
> type_name | sum | max
> -+-+
> ams-hbase-policy| 0 | 2015-11-05 15:57:28+00
> ams-hbase-security-site | 0 | 2016-05-02 18:09:34+00
> ams-log4j | 0 | 2015-11-05 15:57:28+00
> ams-hbase-log4j | 0 | 2015-11-05 15:57:28+00
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19196) BG operations modal windows are too small to show the content (in certain scenarios) [Chrome]
[ https://issues.apache.org/jira/browse/AMBARI-19196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748391#comment-15748391 ] Oleg Nechiporenko commented on AMBARI-19196: Committed to trunk and 2.5 > BG operations modal windows are too small to show the content (in certain > scenarios) [Chrome] > - > > Key: AMBARI-19196 > URL: https://issues.apache.org/jira/browse/AMBARI-19196 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 2.5.0 > > Attachments: AMBARI-19196.patch, AMBARI-19196_branch-2.5.patch > > > 1. Login to Ambari > 2. Click on BG operations. > 3. Click on some action link which have relatively lesser content, e.g Hosts, > with only one host link. > 4. Click on the link to get more details > 5. Intermittently the details window also have the same dimension of the > previous window and as a result the user is not able to view the content > BG operations modal window should be resizable as intermittently modal > windows are too small to view the content[Chrome]. > This behavior is observed when we navigate to the granular details and the > previous window was smaller size due to lesser content. Please see the > screenshots > Intermittently the details window also have the same dimension of the > previous window and as a result the user is not able to view the content -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19197) Kerberos advanced tab. Page wasn't refreshed after save changes. Save button is disabled.
[ https://issues.apache.org/jira/browse/AMBARI-19197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-19197: - Resolution: Fixed Status: Resolved (was: Patch Available) > Kerberos advanced tab. Page wasn't refreshed after save changes. Save button > is disabled. > - > > Key: AMBARI-19197 > URL: https://issues.apache.org/jira/browse/AMBARI-19197 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Denys Buzhor >Assignee: Denys Buzhor > Fix For: 2.5.0 > > Attachments: AMBARI-19197.patch, AMBARI-19197_branch_2.5.patch > > > STR: > # change properties on kerb advanced tab > # save and regenerate keytab > # wait for complete > # change properties on kerb advanced tab > Result: > Save button is disabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19197) Kerberos advanced tab. Page wasn't refreshed after save changes. Save button is disabled.
[ https://issues.apache.org/jira/browse/AMBARI-19197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748385#comment-15748385 ] Antonenko Alexander commented on AMBARI-19197: -- committed to 2.5 > Kerberos advanced tab. Page wasn't refreshed after save changes. Save button > is disabled. > - > > Key: AMBARI-19197 > URL: https://issues.apache.org/jira/browse/AMBARI-19197 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Denys Buzhor >Assignee: Denys Buzhor > Fix For: 2.5.0 > > Attachments: AMBARI-19197.patch, AMBARI-19197_branch_2.5.patch > > > STR: > # change properties on kerb advanced tab > # save and regenerate keytab > # wait for complete > # change properties on kerb advanced tab > Result: > Save button is disabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19197) Kerberos advanced tab. Page wasn't refreshed after save changes. Save button is disabled.
[ https://issues.apache.org/jira/browse/AMBARI-19197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Buzhor updated AMBARI-19197: -- Attachment: AMBARI-19197_branch_2.5.patch > Kerberos advanced tab. Page wasn't refreshed after save changes. Save button > is disabled. > - > > Key: AMBARI-19197 > URL: https://issues.apache.org/jira/browse/AMBARI-19197 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Denys Buzhor >Assignee: Denys Buzhor > Fix For: 2.5.0 > > Attachments: AMBARI-19197.patch, AMBARI-19197_branch_2.5.patch > > > STR: > # change properties on kerb advanced tab > # save and regenerate keytab > # wait for complete > # change properties on kerb advanced tab > Result: > Save button is disabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19197) Kerberos advanced tab. Page wasn't refreshed after save changes. Save button is disabled.
[ https://issues.apache.org/jira/browse/AMBARI-19197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748374#comment-15748374 ] Antonenko Alexander commented on AMBARI-19197: -- committed to trunk > Kerberos advanced tab. Page wasn't refreshed after save changes. Save button > is disabled. > - > > Key: AMBARI-19197 > URL: https://issues.apache.org/jira/browse/AMBARI-19197 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Denys Buzhor >Assignee: Denys Buzhor > Fix For: 2.5.0 > > Attachments: AMBARI-19197.patch > > > STR: > # change properties on kerb advanced tab > # save and regenerate keytab > # wait for complete > # change properties on kerb advanced tab > Result: > Save button is disabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19197) Kerberos advanced tab. Page wasn't refreshed after save changes. Save button is disabled.
[
https://issues.apache.org/jira/browse/AMBARI-19197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748368#comment-15748368
]
Hadoop QA commented on AMBARI-19197:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843214/AMBARI-19197.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-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9660//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9660//console
This message is automatically generated.
> Kerberos advanced tab. Page wasn't refreshed after save changes. Save button
> is disabled.
> -
>
> Key: AMBARI-19197
> URL: https://issues.apache.org/jira/browse/AMBARI-19197
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Denys Buzhor
>Assignee: Denys Buzhor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19197.patch
>
>
> STR:
> # change properties on kerb advanced tab
> # save and regenerate keytab
> # wait for complete
> # change properties on kerb advanced tab
> Result:
> Save button is disabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19199) AMS config types created by upgrade were never marked as selected
[
https://issues.apache.org/jira/browse/AMBARI-19199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-19199:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.5
> AMS config types created by upgrade were never marked as selected
> -
>
> Key: AMBARI-19199
> URL: https://issues.apache.org/jira/browse/AMBARI-19199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.4.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19199.patch
>
>
> Query to identify the problem:
> {noformat}
> ambari=> select type_name, sum(selected),
> MAX(to_timestamp(create_timestamp/1000)) from clusterconfigmapping group by
> type_name order by sum;
> type_name | sum | max
> -+-+
> ams-hbase-policy| 0 | 2015-11-05 15:57:28+00
> ams-hbase-security-site | 0 | 2016-05-02 18:09:34+00
> ams-log4j | 0 | 2015-11-05 15:57:28+00
> ams-hbase-log4j | 0 | 2015-11-05 15:57:28+00
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19164) Add PK to hostcomponentdesiredstate Table To Support FK Relationships
[
https://issues.apache.org/jira/browse/AMBARI-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-19164:
--
Status: Patch Available (was: In Progress)
> Add PK to hostcomponentdesiredstate Table To Support FK Relationships
> -
>
> Key: AMBARI-19164
> URL: https://issues.apache.org/jira/browse/AMBARI-19164
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19164.v1.patch
>
>
> The {{hostcomponentdesiredstate}} table currently uses a compound PK based
> off of the cluster ID, service name, host id and component name. There are
> several problems with this approach:
> * Primary Keys should be data that's not part of the business logic of the
> system and not subject to be changed potentially (as strings are).
> * Other tables referencing the {{hostcomponentdesiredstate}} table would now
> need knowledge of cluster/service/component/host in order to make the correct
> FK association. This leads to extra data being tracked as well as data
> duplication.
> * Some databases, such as SQL Server, have problems with the indexing of
> compound PKs and may lead to deadlocks when querying and updating
> concurrently.
> This table needs to be changed so that it uses a simple PK for referencing.
> FK relationships as they exist today can still be maintained as long as a
> {{UNIQUE}} constraint is placed on the table. We should:
> * Add a {{UNIQUE}} constraint to the former PK columns
> * Add an {{INDEX}} to the former PK columns
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19164) Add PK to hostcomponentdesiredstate Table To Support FK Relationships
[
https://issues.apache.org/jira/browse/AMBARI-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-19164:
--
Attachment: AMBARI-19164.v1.patch
> Add PK to hostcomponentdesiredstate Table To Support FK Relationships
> -
>
> Key: AMBARI-19164
> URL: https://issues.apache.org/jira/browse/AMBARI-19164
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19164.v1.patch
>
>
> The {{hostcomponentdesiredstate}} table currently uses a compound PK based
> off of the cluster ID, service name, host id and component name. There are
> several problems with this approach:
> * Primary Keys should be data that's not part of the business logic of the
> system and not subject to be changed potentially (as strings are).
> * Other tables referencing the {{hostcomponentdesiredstate}} table would now
> need knowledge of cluster/service/component/host in order to make the correct
> FK association. This leads to extra data being tracked as well as data
> duplication.
> * Some databases, such as SQL Server, have problems with the indexing of
> compound PKs and may lead to deadlocks when querying and updating
> concurrently.
> This table needs to be changed so that it uses a simple PK for referencing.
> FK relationships as they exist today can still be maintained as long as a
> {{UNIQUE}} constraint is placed on the table. We should:
> * Add a {{UNIQUE}} constraint to the former PK columns
> * Add an {{INDEX}} to the former PK columns
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19188) Provide Atlas Hook support for Hive2
[ https://issues.apache.org/jira/browse/AMBARI-19188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19188: Attachment: AMBARI-19188.1.patch > Provide Atlas Hook support for Hive2 > > > Key: AMBARI-19188 > URL: https://issues.apache.org/jira/browse/AMBARI-19188 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19188.1.patch, AMBARI-19188.patch > > > Need to provide Atlas hook configuration support for HiveServer-Interactive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19177) kafka Consumer Alerting to check if the Kafka topics are able to read the data
[ https://issues.apache.org/jira/browse/AMBARI-19177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Sudheer Kumar M updated AMBARI-19177: - Status: Patch Available (was: Open) https://reviews.apache.org/r/53987/ > kafka Consumer Alerting to check if the Kafka topics are able to read the data > -- > > Key: AMBARI-19177 > URL: https://issues.apache.org/jira/browse/AMBARI-19177 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.2.2 > Environment: HDP 2.3.4 >Reporter: Venkata Sudheer Kumar M > Labels: patch > Fix For: 2.4.1 > > > customer needs alerting for the Kafka topic when they are not able to consume > to data -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19200) Turning OFF maintenance mode shows a popup on all hosts
[ https://issues.apache.org/jira/browse/AMBARI-19200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748286#comment-15748286 ] Andrii Tkach commented on AMBARI-19200: --- 19726 passing (28s) 153 pending > Turning OFF maintenance mode shows a popup on all hosts > --- > > Key: AMBARI-19200 > URL: https://issues.apache.org/jira/browse/AMBARI-19200 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19200.patch > > > STEPS TO REPRODUCE: > # Complete upgrade > # Pick a random node > # Set Maintenance mode ON > # Set Maintenance mode OFF -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19200) Turning OFF maintenance mode shows a popup on all hosts
[ https://issues.apache.org/jira/browse/AMBARI-19200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19200: -- Status: Patch Available (was: Open) > Turning OFF maintenance mode shows a popup on all hosts > --- > > Key: AMBARI-19200 > URL: https://issues.apache.org/jira/browse/AMBARI-19200 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19200.patch > > > STEPS TO REPRODUCE: > # Complete upgrade > # Pick a random node > # Set Maintenance mode ON > # Set Maintenance mode OFF -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19200) Turning OFF maintenance mode shows a popup on all hosts
[ https://issues.apache.org/jira/browse/AMBARI-19200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19200: -- Attachment: AMBARI-19200.patch > Turning OFF maintenance mode shows a popup on all hosts > --- > > Key: AMBARI-19200 > URL: https://issues.apache.org/jira/browse/AMBARI-19200 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19200.patch > > > STEPS TO REPRODUCE: > # Complete upgrade > # Pick a random node > # Set Maintenance mode ON > # Set Maintenance mode OFF -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19200) Turning OFF maintenance mode shows a popup on all hosts
Andrii Tkach created AMBARI-19200: - Summary: Turning OFF maintenance mode shows a popup on all hosts Key: AMBARI-19200 URL: https://issues.apache.org/jira/browse/AMBARI-19200 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Fix For: 2.5.0 STEPS TO REPRODUCE: # Complete upgrade # Pick a random node # Set Maintenance mode ON # Set Maintenance mode OFF -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19198) Oozie Restart is not prompted on changing MapReduce2 properties
[ https://issues.apache.org/jira/browse/AMBARI-19198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748260#comment-15748260 ] Hudson commented on AMBARI-19198: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6227 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6227/]) AMBARI-19198. Oozie Restart is not prompted on changing MapReduce2 (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1f38a7094da22846576f856233d4d17faa22144c]) * (edit) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.2.3/metainfo.xml > Oozie Restart is not prompted on changing MapReduce2 properties > --- > > Key: AMBARI-19198 > URL: https://issues.apache.org/jira/browse/AMBARI-19198 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19198.patch > > > 1]Login to Ambari as cluster administrator > 2] Change the property mapreduce.map.memory.mb > 3] Service Restart against affects services is displayed. > Actual Result: > Oozie service is not prompted for restart. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
