[jira] [Created] (AMBARI-17110) [Log Search portal ]Date range on comparison tab are different from date range of selected logs for comparison
Dharmesh Makwana created AMBARI-17110: - Summary: [Log Search portal ]Date range on comparison tab are different from date range of selected logs for comparison Key: AMBARI-17110 URL: https://issues.apache.org/jira/browse/AMBARI-17110 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.4.0 Reporter: Dharmesh Makwana Fix For: 2.4.0 Currently the default date range in comparison tab is "Last one hour" making it to the dates selected on Service logs tab. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17109) Capacity scheduler view - problem with queue percent rounding
[ https://issues.apache.org/jira/browse/AMBARI-17109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated AMBARI-17109: -- Status: Patch Available (was: Open) > Capacity scheduler view - problem with queue percent rounding > - > > Key: AMBARI-17109 > URL: https://issues.apache.org/jira/browse/AMBARI-17109 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.1.0 >Reporter: Akhil PB > Fix For: ambari-2.4.0 > > Attachments: AMBARI-17109.1.patch, CapSchedViewCalc.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17109) Capacity scheduler view - problem with queue percent rounding
[ https://issues.apache.org/jira/browse/AMBARI-17109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated AMBARI-17109: -- Attachment: AMBARI-17109.1.patch > Capacity scheduler view - problem with queue percent rounding > - > > Key: AMBARI-17109 > URL: https://issues.apache.org/jira/browse/AMBARI-17109 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.1.0 >Reporter: Akhil PB > Fix For: ambari-2.4.0 > > Attachments: AMBARI-17109.1.patch, CapSchedViewCalc.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17109) Capacity scheduler view - problem with queue percent rounding
[ https://issues.apache.org/jira/browse/AMBARI-17109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated AMBARI-17109: -- Fix Version/s: (was: ambari-2.4.0) 2.4.0 > Capacity scheduler view - problem with queue percent rounding > - > > Key: AMBARI-17109 > URL: https://issues.apache.org/jira/browse/AMBARI-17109 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.1.0 >Reporter: Akhil PB > Fix For: ambari-2.4.0 > > Attachments: CapSchedViewCalc.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17109) Capacity scheduler view - problem with queue percent rounding
[ https://issues.apache.org/jira/browse/AMBARI-17109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated AMBARI-17109: -- Fix Version/s: (was: 2.4.0) ambari-2.4.0 > Capacity scheduler view - problem with queue percent rounding > - > > Key: AMBARI-17109 > URL: https://issues.apache.org/jira/browse/AMBARI-17109 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.1.0 >Reporter: Akhil PB > Fix For: ambari-2.4.0 > > Attachments: CapSchedViewCalc.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17109) Capacity scheduler view - problem with queue percent rounding
[ https://issues.apache.org/jira/browse/AMBARI-17109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB updated AMBARI-17109: -- Attachment: CapSchedViewCalc.png > Capacity scheduler view - problem with queue percent rounding > - > > Key: AMBARI-17109 > URL: https://issues.apache.org/jira/browse/AMBARI-17109 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.1.0 >Reporter: Akhil PB > Fix For: ambari-2.4.0 > > Attachments: CapSchedViewCalc.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17109) Capacity scheduler view - problem with queue percent rounding
Akhil PB created AMBARI-17109: - Summary: Capacity scheduler view - problem with queue percent rounding Key: AMBARI-17109 URL: https://issues.apache.org/jira/browse/AMBARI-17109 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.1.0 Reporter: Akhil PB Fix For: ambari-2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17104) Conflicts supported OS version
[
https://issues.apache.org/jira/browse/AMBARI-17104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320064#comment-15320064
]
Hadoop QA commented on AMBARI-17104:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12808800/AMBARI-17104.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7234//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7234//console
This message is automatically generated.
> Conflicts supported OS version
> --
>
> Key: AMBARI-17104
> URL: https://issues.apache.org/jira/browse/AMBARI-17104
> Project: Ambari
> Issue Type: Bug
> Components: documentation
>Affects Versions: trunk
> Environment: Apache Ambari website
>Reporter: Masahiro Tanaka
>Priority: Trivial
> Labels: easyfix
> Attachments: AMBARI-17104.patch
>
>
> [Apache Ambari Website|https://ambari.apache.org/] says Ambari Apache
> supports RHEL 5,6, CentOS 5,6, and OEL 5,6.
> But [docs at Hortonworks
> webpage|http://docs.hortonworks.com/HDPDocuments/Ambari-2.2.2.0/bk_Installing_HDP_AMB/content/_operating_systems_requirements.html]
> says RHEL 6,7, CentOS 6,7, and OEL 6,7.
> We should fix this conflicts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17027) Metrics Collector API: Introduce basic series aggregation functions
[ https://issues.apache.org/jira/browse/AMBARI-17027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated AMBARI-17027: -- Status: Patch Available (was: Open) > Metrics Collector API: Introduce basic series aggregation functions > --- > > Key: AMBARI-17027 > URL: https://issues.apache.org/jira/browse/AMBARI-17027 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim > Attachments: AMBARI-17027-trunk-v1.patch, > AMS-grafana-query-metric-wildcard-with-series-aggregation-avg-v2.png, > AMS-grafana-query-metric-wildcard-with-series-aggregation-sum-v2.png > > > AMS doesn't provide tag so metric is identified by appId, metric name, > hostname, instanceId. In this situation metric name is normally consist of > origin metric name and tag values, like graphite, but unlike Graphite, AMS > also doesn't provide series aggregation functions so aggregation should be > done from caller side. > It would be great if Ambari Metrics Collector provides series aggregation > functions, like sumSeries / averageSeries / minSeries / maxSeries on Graphite. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17027) Metrics Collector API: Introduce basic series aggregation functions
[ https://issues.apache.org/jira/browse/AMBARI-17027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated AMBARI-17027: -- Attachment: AMBARI-17027-trunk-v1.patch Attaching patch against trunk. I tested on cluster with branch-2.4 and confirmed it works. > Metrics Collector API: Introduce basic series aggregation functions > --- > > Key: AMBARI-17027 > URL: https://issues.apache.org/jira/browse/AMBARI-17027 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim > Attachments: AMBARI-17027-trunk-v1.patch, > AMS-grafana-query-metric-wildcard-with-series-aggregation-avg-v2.png, > AMS-grafana-query-metric-wildcard-with-series-aggregation-sum-v2.png > > > AMS doesn't provide tag so metric is identified by appId, metric name, > hostname, instanceId. In this situation metric name is normally consist of > origin metric name and tag values, like graphite, but unlike Graphite, AMS > also doesn't provide series aggregation functions so aggregation should be > done from caller side. > It would be great if Ambari Metrics Collector provides series aggregation > functions, like sumSeries / averageSeries / minSeries / maxSeries on Graphite. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17108) Hive view 2.0.0 Error on searching columns when they don't exist
[ https://issues.apache.org/jira/browse/AMBARI-17108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-17108: --- Attachment: AMBARI-17108.trunk.patch > Hive view 2.0.0 Error on searching columns when they don't exist > > > Key: AMBARI-17108 > URL: https://issues.apache.org/jira/browse/AMBARI-17108 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.0 > > Attachments: AMBARI-17108.trunk.patch > > > Steps:- > 1) Drop table > 2) Create table with columns > 3) Dropping the column from the created table > 4) Searching for the respective column > After searching for column, "E090 NullPointerException " error is displayed. > java.lang.NullPointerException > java.lang.NullPointerException > at > org.apache.ambari.view.hive2.resources.jobs.ResultsPaginationController.filter(ResultsPaginationController.java:207) > at > org.apache.ambari.view.hive2.resources.jobs.ResultsPaginationController.request(ResultsPaginationController.java:151) > at > org.apache.ambari.view.hive2.resources.browser.HiveBrowserService.describeTablePaginated(HiveBrowserService.java:244) > 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) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17108) Hive view 2.0.0 Error on searching columns when they don't exist
[ https://issues.apache.org/jira/browse/AMBARI-17108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-17108: --- Status: Patch Available (was: Open) > Hive view 2.0.0 Error on searching columns when they don't exist > > > Key: AMBARI-17108 > URL: https://issues.apache.org/jira/browse/AMBARI-17108 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.0 > > Attachments: AMBARI-17108.trunk.patch > > > Steps:- > 1) Drop table > 2) Create table with columns > 3) Dropping the column from the created table > 4) Searching for the respective column > After searching for column, "E090 NullPointerException " error is displayed. > java.lang.NullPointerException > java.lang.NullPointerException > at > org.apache.ambari.view.hive2.resources.jobs.ResultsPaginationController.filter(ResultsPaginationController.java:207) > at > org.apache.ambari.view.hive2.resources.jobs.ResultsPaginationController.request(ResultsPaginationController.java:151) > at > org.apache.ambari.view.hive2.resources.browser.HiveBrowserService.describeTablePaginated(HiveBrowserService.java:244) > 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) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17108) Hive view 2.0.0 Error on searching columns when they don't exist
[ https://issues.apache.org/jira/browse/AMBARI-17108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-17108: --- Description: Steps:- 1) Drop table 2) Create table with columns 3) Dropping the column from the created table 4) Searching for the respective column After searching for column, "E090 NullPointerException " error is been displayed. java.lang.NullPointerException java.lang.NullPointerException at org.apache.ambari.view.hive2.resources.jobs.ResultsPaginationController.filter(ResultsPaginationController.java:207) at org.apache.ambari.view.hive2.resources.jobs.ResultsPaginationController.request(ResultsPaginationController.java:151) at org.apache.ambari.view.hive2.resources.browser.HiveBrowserService.describeTablePaginated(HiveBrowserService.java:244) 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) > Hive view 2.0.0 Error on searching columns when they don't exist > > > Key: AMBARI-17108 > URL: https://issues.apache.org/jira/browse/AMBARI-17108 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.0 > > Attachments: AMBARI-17108.trunk.patch > > > Steps:- > 1) Drop table > 2) Create table with columns > 3) Dropping the column from the created table > 4) Searching for the respective column > After searching for column, "E090 NullPointerException " error is been > displayed. > java.lang.NullPointerException > java.lang.NullPointerException > at > org.apache.ambari.view.hive2.resources.jobs.ResultsPaginationController.filter(ResultsPaginationController.java:207) > at > org.apache.ambari.view.hive2.resources.jobs.ResultsPaginationController.request(ResultsPaginationController.java:151) > at > org.apache.ambari.view.hive2.resources.browser.HiveBrowserService.describeTablePaginated(HiveBrowserService.java:244) > 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) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17108) Hive view 2.0.0 Error on searching columns when they don't exist
[ https://issues.apache.org/jira/browse/AMBARI-17108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-17108: --- Description: Steps:- 1) Drop table 2) Create table with columns 3) Dropping the column from the created table 4) Searching for the respective column After searching for column, "E090 NullPointerException " error is displayed. java.lang.NullPointerException java.lang.NullPointerException at org.apache.ambari.view.hive2.resources.jobs.ResultsPaginationController.filter(ResultsPaginationController.java:207) at org.apache.ambari.view.hive2.resources.jobs.ResultsPaginationController.request(ResultsPaginationController.java:151) at org.apache.ambari.view.hive2.resources.browser.HiveBrowserService.describeTablePaginated(HiveBrowserService.java:244) 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) was: Steps:- 1) Drop table 2) Create table with columns 3) Dropping the column from the created table 4) Searching for the respective column After searching for column, "E090 NullPointerException " error is been displayed. java.lang.NullPointerException java.lang.NullPointerException at org.apache.ambari.view.hive2.resources.jobs.ResultsPaginationController.filter(ResultsPaginationController.java:207) at org.apache.ambari.view.hive2.resources.jobs.ResultsPaginationController.request(ResultsPaginationController.java:151) at org.apache.ambari.view.hive2.resources.browser.HiveBrowserService.describeTablePaginated(HiveBrowserService.java:244) 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) > Hive view 2.0.0 Error on searching columns when they don't exist > > > Key: AMBARI-17108 > URL: https://issues.apache.org/jira/browse/AMBARI-17108 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.0 > > Attachments: AMBARI-17108.trunk.patch > > > Steps:- > 1) Drop table > 2) Create table with columns > 3) Dropping the column from the created table > 4) Searching for the respective column > After searching for column, "E090 NullPointerException " error is displayed. > java.lang.NullPointerException > java.lang.NullPointerException > at > org.apache.ambari.view.hive2.resources.jobs.ResultsPaginationController.filter(ResultsPaginationController.java:207) > at > org.apache.ambari.view.hive2.resources.jobs.ResultsPaginationController.request(ResultsPaginationController.java:151) > at > org.apache.ambari.view.hive2.resources.browser.HiveBrowserService.describeTablePaginated(HiveBrowserService.java:244) > 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) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17108) Hive view 2.0.0 Error on searching columns when they don't exist
Ashwin Rajeev created AMBARI-17108: -- Summary: Hive view 2.0.0 Error on searching columns when they don't exist Key: AMBARI-17108 URL: https://issues.apache.org/jira/browse/AMBARI-17108 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.4.0 Reporter: Ashwin Rajeev Assignee: Ashwin Rajeev Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17027) Metrics Collector API: Introduce basic series aggregation functions
[ https://issues.apache.org/jira/browse/AMBARI-17027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated AMBARI-17027: -- Attachment: (was: AMS-grafana-query-metric-wildcard-with-series-aggregation-avg-with-host.png) > Metrics Collector API: Introduce basic series aggregation functions > --- > > Key: AMBARI-17027 > URL: https://issues.apache.org/jira/browse/AMBARI-17027 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim > Attachments: > AMS-grafana-query-metric-wildcard-with-series-aggregation-avg-v2.png, > AMS-grafana-query-metric-wildcard-with-series-aggregation-sum-v2.png > > > AMS doesn't provide tag so metric is identified by appId, metric name, > hostname, instanceId. In this situation metric name is normally consist of > origin metric name and tag values, like graphite, but unlike Graphite, AMS > also doesn't provide series aggregation functions so aggregation should be > done from caller side. > It would be great if Ambari Metrics Collector provides series aggregation > functions, like sumSeries / averageSeries / minSeries / maxSeries on Graphite. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17107) Ambari Alert for HDFS Last Checkpoint in HA
[
https://issues.apache.org/jira/browse/AMBARI-17107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Pathak updated AMBARI-17107:
--
Description:
As can been seen in
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_checkpoint_time.py
At line
{code}NN_HTTP_ADDRESS_KEY = '{{hdfs-site/dfs.namenode.http-address}}'{code}
It will not work in case of HA enabled cluster.
In case of HA this property will not exist and alert will fail.
was:
As can been seen in
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_checkpoint_time.py
At line NN_HTTP_ADDRESS_KEY = '{{hdfs-site/dfs.namenode.http-address}}'
It will not work in case of HA enabled cluster.
In case of HA this property will not exist and alert will fail.
> Ambari Alert for HDFS Last Checkpoint in HA
> ---
>
> Key: AMBARI-17107
> URL: https://issues.apache.org/jira/browse/AMBARI-17107
> Project: Ambari
> Issue Type: Bug
> Components: alerts
> Environment: Hortonworks hadoop HDP 2.4.2 with HDFS HA enabled.
>Reporter: Rahul Pathak
> Labels: easyfix
>
> As can been seen in
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_checkpoint_time.py
> At line
> {code}NN_HTTP_ADDRESS_KEY = '{{hdfs-site/dfs.namenode.http-address}}'{code}
> It will not work in case of HA enabled cluster.
> In case of HA this property will not exist and alert will fail.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17027) Metrics Collector API: Introduce basic series aggregation functions
[ https://issues.apache.org/jira/browse/AMBARI-17027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated AMBARI-17027: -- Attachment: (was: AMS-grafana-query-metric-wildcard-with-series-aggregation-sum.png) > Metrics Collector API: Introduce basic series aggregation functions > --- > > Key: AMBARI-17027 > URL: https://issues.apache.org/jira/browse/AMBARI-17027 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim > Attachments: > AMS-grafana-query-metric-wildcard-with-series-aggregation-avg-v2.png, > AMS-grafana-query-metric-wildcard-with-series-aggregation-sum-v2.png > > > AMS doesn't provide tag so metric is identified by appId, metric name, > hostname, instanceId. In this situation metric name is normally consist of > origin metric name and tag values, like graphite, but unlike Graphite, AMS > also doesn't provide series aggregation functions so aggregation should be > done from caller side. > It would be great if Ambari Metrics Collector provides series aggregation > functions, like sumSeries / averageSeries / minSeries / maxSeries on Graphite. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17027) Metrics Collector API: Introduce basic series aggregation functions
[ https://issues.apache.org/jira/browse/AMBARI-17027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated AMBARI-17027: -- Attachment: (was: AMS-grafana-query-metric-wildcard-without-series-aggregation.png) > Metrics Collector API: Introduce basic series aggregation functions > --- > > Key: AMBARI-17027 > URL: https://issues.apache.org/jira/browse/AMBARI-17027 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim > Attachments: > AMS-grafana-query-metric-wildcard-with-series-aggregation-avg-v2.png, > AMS-grafana-query-metric-wildcard-with-series-aggregation-avg-with-host.png, > AMS-grafana-query-metric-wildcard-with-series-aggregation-sum-v2.png, > AMS-grafana-query-metric-wildcard-with-series-aggregation-sum.png > > > AMS doesn't provide tag so metric is identified by appId, metric name, > hostname, instanceId. In this situation metric name is normally consist of > origin metric name and tag values, like graphite, but unlike Graphite, AMS > also doesn't provide series aggregation functions so aggregation should be > done from caller side. > It would be great if Ambari Metrics Collector provides series aggregation > functions, like sumSeries / averageSeries / minSeries / maxSeries on Graphite. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17107) Ambari Alert for HDFS Last Checkpoint in HA
[
https://issues.apache.org/jira/browse/AMBARI-17107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Pathak updated AMBARI-17107:
--
Description:
As can been seen in
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_checkpoint_time.py
At line NN_HTTP_ADDRESS_KEY = '{{hdfs-site/dfs.namenode.http-address}}'
It will not work in case of HA enabled cluster.
In case of HA this property will not exist and alert will fail.
was:
As can been seen tin
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_checkpoint_time.py
At line NN_HTTP_ADDRESS_KEY = '{{hdfs-site/dfs.namenode.http-address}}'
It will not work in case of HA enabled cluster.
In case of HA this property will not exist and alert will fail.
> Ambari Alert for HDFS Last Checkpoint in HA
> ---
>
> Key: AMBARI-17107
> URL: https://issues.apache.org/jira/browse/AMBARI-17107
> Project: Ambari
> Issue Type: Bug
> Components: alerts
> Environment: Hortonworks hadoop HDP 2.4.2 with HDFS HA enabled.
>Reporter: Rahul Pathak
> Labels: easyfix
>
> As can been seen in
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_checkpoint_time.py
> At line NN_HTTP_ADDRESS_KEY = '{{hdfs-site/dfs.namenode.http-address}}'
> It will not work in case of HA enabled cluster.
> In case of HA this property will not exist and alert will fail.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17027) Metrics Collector API: Introduce basic series aggregation functions
[ https://issues.apache.org/jira/browse/AMBARI-17027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated AMBARI-17027: -- Attachment: (was: AMS-grafana-query-metric-wildcard-without-series-aggregation-avg.png) > Metrics Collector API: Introduce basic series aggregation functions > --- > > Key: AMBARI-17027 > URL: https://issues.apache.org/jira/browse/AMBARI-17027 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim > Attachments: > AMS-grafana-query-metric-wildcard-with-series-aggregation-avg-v2.png, > AMS-grafana-query-metric-wildcard-with-series-aggregation-avg-with-host.png, > AMS-grafana-query-metric-wildcard-with-series-aggregation-sum-v2.png, > AMS-grafana-query-metric-wildcard-with-series-aggregation-sum.png > > > AMS doesn't provide tag so metric is identified by appId, metric name, > hostname, instanceId. In this situation metric name is normally consist of > origin metric name and tag values, like graphite, but unlike Graphite, AMS > also doesn't provide series aggregation functions so aggregation should be > done from caller side. > It would be great if Ambari Metrics Collector provides series aggregation > functions, like sumSeries / averageSeries / minSeries / maxSeries on Graphite. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17107) Ambari Alert for HDFS Last Checkpoint in HA
Rahul Pathak created AMBARI-17107:
-
Summary: Ambari Alert for HDFS Last Checkpoint in HA
Key: AMBARI-17107
URL: https://issues.apache.org/jira/browse/AMBARI-17107
Project: Ambari
Issue Type: Bug
Components: alerts
Environment: Hortonworks hadoop HDP 2.4.2 with HDFS HA enabled.
Reporter: Rahul Pathak
As can been seen tin
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_checkpoint_time.py
At line NN_HTTP_ADDRESS_KEY = '{{hdfs-site/dfs.namenode.http-address}}'
It will not work in case of HA enabled cluster.
In case of HA this property will not exist and alert will fail.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17027) Metrics Collector API: Introduce basic series aggregation functions
[ https://issues.apache.org/jira/browse/AMBARI-17027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated AMBARI-17027: -- Attachment: AMS-grafana-query-metric-wildcard-with-series-aggregation-sum-v2.png AMS-grafana-query-metric-wildcard-with-series-aggregation-avg-v2.png > Metrics Collector API: Introduce basic series aggregation functions > --- > > Key: AMBARI-17027 > URL: https://issues.apache.org/jira/browse/AMBARI-17027 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim > Attachments: > AMS-grafana-query-metric-wildcard-with-series-aggregation-avg-v2.png, > AMS-grafana-query-metric-wildcard-with-series-aggregation-avg-with-host.png, > AMS-grafana-query-metric-wildcard-with-series-aggregation-sum-v2.png, > AMS-grafana-query-metric-wildcard-with-series-aggregation-sum.png, > AMS-grafana-query-metric-wildcard-without-series-aggregation-avg.png, > AMS-grafana-query-metric-wildcard-without-series-aggregation.png > > > AMS doesn't provide tag so metric is identified by appId, metric name, > hostname, instanceId. In this situation metric name is normally consist of > origin metric name and tag values, like graphite, but unlike Graphite, AMS > also doesn't provide series aggregation functions so aggregation should be > done from caller side. > It would be great if Ambari Metrics Collector provides series aggregation > functions, like sumSeries / averageSeries / minSeries / maxSeries on Graphite. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17027) Metrics Collector API: Introduce basic series aggregation functions
[ https://issues.apache.org/jira/browse/AMBARI-17027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320024#comment-15320024 ] Jungtaek Lim commented on AMBARI-17027: --- I've modified a bit around Collector API and Grafana plugin after uploading gist / attaching screenshot. For Collector API, there would be easy to just have one additional parameter (seriesAggregateFunction) instead of having function pattern like SUM(metricPattern) on metric names. Updated version of API output is here: https://gist.github.com/HeartSaVioR/f4f28b5b8b7bf2e5477e59d7fd56090f I'll attach new snapshots and remove old snapshots. > Metrics Collector API: Introduce basic series aggregation functions > --- > > Key: AMBARI-17027 > URL: https://issues.apache.org/jira/browse/AMBARI-17027 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim > Attachments: > AMS-grafana-query-metric-wildcard-with-series-aggregation-avg-with-host.png, > AMS-grafana-query-metric-wildcard-with-series-aggregation-sum.png, > AMS-grafana-query-metric-wildcard-without-series-aggregation-avg.png, > AMS-grafana-query-metric-wildcard-without-series-aggregation.png > > > AMS doesn't provide tag so metric is identified by appId, metric name, > hostname, instanceId. In this situation metric name is normally consist of > origin metric name and tag values, like graphite, but unlike Graphite, AMS > also doesn't provide series aggregation functions so aggregation should be > done from caller side. > It would be great if Ambari Metrics Collector provides series aggregation > functions, like sumSeries / averageSeries / minSeries / maxSeries on Graphite. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17039) Takes long time to start or fail to start service after enabling SSL due to "dfs.https.enable"
[
https://issues.apache.org/jira/browse/AMBARI-17039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319994#comment-15319994
]
Matt commented on AMBARI-17039:
---
Committed to trunk:
{code}
commit 49d5d587be687e1aef12bd39df777824b96e36c9
Author: Matt
Date: Tue Jun 7 21:47:51 2016 -0700
{code}
> Takes long time to start or fail to start service after enabling SSL due to
> "dfs.https.enable"
> --
>
> Key: AMBARI-17039
> URL: https://issues.apache.org/jira/browse/AMBARI-17039
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.2.1.1
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17039.patch
>
>
> *SYMPTOM:*
> After enabling SSL on HDFS, starting services, such as YARN takes long time
> because Ambari keeps checking http:// , not https://
> {noformat}
> 2016-06-02 23:07:22,221 - Getting jmx metrics from NN failed. URL:
> http://dev-hdp-mas-w2a-a.corporate.t-mobile.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesys...
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 38, in get_value_from_jmx
> _, data, _ = get_user_call_output(cmd, user=run_user, quiet=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py",
> line 61, in get_user_call_output
> raise Fail(err_msg)
> Fail: Execution of 'curl --negotiate -u : -s
> 'http://dev-hdp-mas-w2a-a.corporate.t-mobile.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesys...'
> 1>/tmp/tmpOGkdi9 2>/tmp/tmpCUfr6B' returned 7.
> 2016-06-02 23:07:24,506 - Getting jmx metrics from NN failed. URL:
> http://dev-hdp-mas-w2b-a.corporate.t-mobile.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesys...
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 38, in get_value_from_jmx
> _, data, _ = get_user_call_output(cmd, user=run_user, quiet=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py",
> line 61, in get_user_call_output
> raise Fail(err_msg)
> Fail: Execution of 'curl --negotiate -u : -s
> 'http://dev-hdp-mas-w2b-a.corporate.t-mobile.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesys...'
> 1>/tmp/tmpDF9Kqb 2>/tmp/tmpBgbC4P' returned 7.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17039) Takes long time to start or fail to start service after enabling SSL due to "dfs.https.enable"
[
https://issues.apache.org/jira/browse/AMBARI-17039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319987#comment-15319987
]
Matt commented on AMBARI-17039:
---
[~rzang]
I found the issue:
It's missing an import in hdfs_utils.py:
{code}
from resource_management.libraries.functions.is_empty import is_empty
{code}
I'll be committing this line directly to the code, since it looks like you guys
have discussed it in the review board already. But missed out on the commit to
trunk.
> Takes long time to start or fail to start service after enabling SSL due to
> "dfs.https.enable"
> --
>
> Key: AMBARI-17039
> URL: https://issues.apache.org/jira/browse/AMBARI-17039
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.2.1.1
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17039.patch
>
>
> *SYMPTOM:*
> After enabling SSL on HDFS, starting services, such as YARN takes long time
> because Ambari keeps checking http:// , not https://
> {noformat}
> 2016-06-02 23:07:22,221 - Getting jmx metrics from NN failed. URL:
> http://dev-hdp-mas-w2a-a.corporate.t-mobile.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesys...
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 38, in get_value_from_jmx
> _, data, _ = get_user_call_output(cmd, user=run_user, quiet=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py",
> line 61, in get_user_call_output
> raise Fail(err_msg)
> Fail: Execution of 'curl --negotiate -u : -s
> 'http://dev-hdp-mas-w2a-a.corporate.t-mobile.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesys...'
> 1>/tmp/tmpOGkdi9 2>/tmp/tmpCUfr6B' returned 7.
> 2016-06-02 23:07:24,506 - Getting jmx metrics from NN failed. URL:
> http://dev-hdp-mas-w2b-a.corporate.t-mobile.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesys...
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 38, in get_value_from_jmx
> _, data, _ = get_user_call_output(cmd, user=run_user, quiet=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py",
> line 61, in get_user_call_output
> raise Fail(err_msg)
> Fail: Execution of 'curl --negotiate -u : -s
> 'http://dev-hdp-mas-w2b-a.corporate.t-mobile.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesys...'
> 1>/tmp/tmpDF9Kqb 2>/tmp/tmpBgbC4P' returned 7.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17039) Takes long time to start or fail to start service after enabling SSL due to "dfs.https.enable"
[
https://issues.apache.org/jira/browse/AMBARI-17039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319970#comment-15319970
]
Matt commented on AMBARI-17039:
---
[~rzang]
I hit an issue recently (see log below). It looks like it is related to the
patch that was committed as part of this JIRA.
I'm investigating further from my side.
```
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py",
line 174, in
DataNode().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 257, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py",
line 47, in install
import params
File
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/params.py",
line 25, in
from params_linux import *
File
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py",
line 426, in
config['configurations']['hdfs-site']['dfs.https.enable'])
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/hdfs_utils.py",
line 29, in is_https_enabled_in_hdfs
if not is_empty(dfs_http_policy):
NameError: global name 'is_empty' is not defined
```
> Takes long time to start or fail to start service after enabling SSL due to
> "dfs.https.enable"
> --
>
> Key: AMBARI-17039
> URL: https://issues.apache.org/jira/browse/AMBARI-17039
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.2.1.1
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17039.patch
>
>
> *SYMPTOM:*
> After enabling SSL on HDFS, starting services, such as YARN takes long time
> because Ambari keeps checking http:// , not https://
> {noformat}
> 2016-06-02 23:07:22,221 - Getting jmx metrics from NN failed. URL:
> http://dev-hdp-mas-w2a-a.corporate.t-mobile.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesys...
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 38, in get_value_from_jmx
> _, data, _ = get_user_call_output(cmd, user=run_user, quiet=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py",
> line 61, in get_user_call_output
> raise Fail(err_msg)
> Fail: Execution of 'curl --negotiate -u : -s
> 'http://dev-hdp-mas-w2a-a.corporate.t-mobile.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesys...'
> 1>/tmp/tmpOGkdi9 2>/tmp/tmpCUfr6B' returned 7.
> 2016-06-02 23:07:24,506 - Getting jmx metrics from NN failed. URL:
> http://dev-hdp-mas-w2b-a.corporate.t-mobile.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesys...
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 38, in get_value_from_jmx
> _, data, _ = get_user_call_output(cmd, user=run_user, quiet=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py",
> line 61, in get_user_call_output
> raise Fail(err_msg)
> Fail: Execution of 'curl --negotiate -u : -s
> 'http://dev-hdp-mas-w2b-a.corporate.t-mobile.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesys...'
> 1>/tmp/tmpDF9Kqb 2>/tmp/tmpBgbC4P' returned 7.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17106) Deadlock While Updating Stale Configuration Cache During Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-17106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-17106:
-
Description:
ambari-server --hash
dc340e8c6cb4fa6c062f805cc1917f62299a5f50
ambari-server-2.4.0.0-622.x86_64
*Steps*
# Deploy HDP-2.4.0.0 cluster with Ambari 2.4.0.0 (unsecure, non-HA cluster, SSL
enabled)
# Start EU to HDP-2.5.0.0-609
*Result*
While EU is in progress, found that Ambari server seems to have hung; the login
page loads, but unable to login; The following API call hangs too --
https://server:8443/api/v1/clusters/cl1/
There is a deadlock when trying to update the stale configuration cache:
{code}
"Server Action Executor Worker 401" #225 prio=5 os_prio=0
tid=0x7fa07c03e800 nid=0x65df waiting on condition [0x7fa0737ef000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0xa059d4f0> (a
java.util.concurrent.locks.ReentrantReadWriteLock$FairSync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199)
at
java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.lock(ReentrantReadWriteLock.java:943)
--> @TransactionalLock(lockArea = LockArea.STALE_CONFIG_CACHE, lockType =
LockType.WRITE)
at
org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.lockTransaction(AmbariJpaLocalTxnInterceptor.java:291)
at
org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:114)
at
com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
at
com.google.inject.internal.InterceptorStackCallback.intercept(InterceptorStackCallback.java:52)
at
org.apache.ambari.server.state.cluster.ClusterImpl$$EnhancerByGuice$$991b84fc.applyConfigs()
--> clusterGlobalLock.writeLock().lock();
at
org.apache.ambari.server.state.cluster.ClusterImpl.addDesiredConfig(ClusterImpl.java:2340)
at
org.apache.ambari.server.state.ConfigHelper.createConfigTypes(ConfigHelper.java:897)
at
org.apache.ambari.server.controller.internal.UpgradeResourceProvider.applyStackAndProcessConfigurations(UpgradeResourceProvider.java:1174)
{code}
{code}
"ambari-hearbeat-monitor" #23 prio=5 os_prio=0 tid=0x7fa07476c000
nid=0x20ad waiting on condition [0x7fa07bbfb000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0xa32d44a0> (a
java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:967)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1283)
at
java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.lock(ReentrantReadWriteLock.java:727)
at
org.apache.ambari.server.state.cluster.ClusterImpl.getDesiredStackVersion(ClusterImpl.java:1052)
at
org.apache.ambari.server.state.ConfigHelper.calculateIsStaleConfigs(ConfigHelper.java:1075)
--> @TransactionalLock(lockArea = LockArea.STALE_CONFIG_CACHE, lockType =
LockType.READ)
at
org.apache.ambari.server.state.ConfigHelper.isStaleConfigs(ConfigHelper.java:456)
at
org.apache.ambari.server.agent.HeartbeatMonitor.createStatusCommand(HeartbeatMonitor.java:311)
{code}
This is another case of an Ambari cache competing with a JPA transaction.
Consider these steps:
- A new configuration is created within the context of a Transaction
- Within that same Transaction, the stale configuration cache is told to
invalidate
- After purging the old data, but before the Transaction is committed, another
thread tries to read from the cache. It ends up re-populating the old data.
Sometimes the code works because the Transaction is able to committ before the
cache is re-populated by another thread. In theory, we should be locking around
reading the cache to ensure that there isn't a transaction writing to it.
However, this is what caused the deadlock since it interferes with our wonder
"cluster global lock of doom".
Instead, it's safer in this case to just invalidate the cache after the
Transaction completes.
- We do this invalidate on a separate thread to
[jira] [Commented] (AMBARI-17100) EU - HDP 2.4 to 2.5 fails restarting DRPC server on a kerberized cluster, need to use org.apache.storm.security.auth.KerberosPrincipalToLocal
[
https://issues.apache.org/jira/browse/AMBARI-17100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319933#comment-15319933
]
Hudson commented on AMBARI-17100:
-
FAILURE: Integrated in Ambari-trunk-Commit #5028 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5028/])
AMBARI-17100. EU - HDP 2.4 to 2.5 fails restarting DRPC server on a
(afernandez:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6fbb4c1830ced4c3f600aa4d7fdb510d2249ddfa])
* ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml
* ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml
> EU - HDP 2.4 to 2.5 fails restarting DRPC server on a kerberized cluster,
> need to use org.apache.storm.security.auth.KerberosPrincipalToLocal
> -
>
> Key: AMBARI-17100
> URL: https://issues.apache.org/jira/browse/AMBARI-17100
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.4.0
>
> Attachments: AMBARI-17100.branch-2.4.patch, AMBARI-17100.trunk.patch
>
>
> STR:
> * Install Ambari 2.4
> * Install HDP 2.4
> * Kerberize the cluster
> * Perform EU to HDP 2.5
> Storm UI Server and DRPC Server:
> {code}
> 2016-06-07 06:16:19.395 b.s.s.a.a.SimpleACLAuthorizer [INFO] [req 5] Access
> from: null principal:ambari-server-...@example.com op:getClusterInfo
> ==> /grid/0/log/storm/ui.out <==
> Running: /usr/jdk64/jdk1.8.0_77/bin/java -server -Ddaemon.name=ui
> -Dstorm.options= -Dstorm.home=/grid/0/hdp/2.5.0.0-664/storm
> -Dstorm.log.dir=/grid/0/log/storm
> -Djava.library.path=/usr/local/lib:/opt/local/lib:/usr/lib:/usr/hdp/current/storm-client/lib
> -Dstorm.conf.file= -cp
> /grid/0/hdp/2.5.0.0-664/storm/lib/log4j-core-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/storm-rename-hack-1.0.1.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/slf4j-api-1.7.7.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/ambari-metrics-storm-sink.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/log4j-over-slf4j-1.6.6.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/servlet-api-2.5.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/clojure-1.7.0.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/asm-5.0.3.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/kryo-3.0.3.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/log4j-slf4j-impl-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/zookeeper.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/disruptor-3.3.2.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/reflectasm-1.10.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/storm-core-1.0.1.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/objenesis-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/minlog-1.3.0.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/log4j-api-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/extlib-daemon/ranger-storm-plugin-shim-0.6.0.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm/extlib-daemon/ojdbc6.jar:/grid/0/hdp/2.5.0.0-664/storm/extlib-daemon/ranger-plugin-classloader-0.6.0.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm:/usr/hdp/current/storm-client/conf
> -Xmx768m
> -Djava.security.auth.login.config=/usr/hdp/current/storm-client/conf/storm_jaas.conf
> -Dlogfile.name=ui.log
> -DLog4jContextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector
> -Dlog4j.configurationFile=/grid/0/hdp/2.5.0.0-664/storm/log4j2/cluster.xml
> org.apache.storm.ui.core
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at clojure.lang.RT.classForName(RT.java:2154)
> at clojure.lang.RT.classForName(RT.java:2163)
> at clojure.lang.RT.loadClassForName(RT.java:2182)
> at clojure.lang.RT.load(RT.java:436)
> at clojure.lang.RT.load(RT.java:412)
> at clojure.core$load$fn__5448.invoke(core.clj:5866)
> at clojure.core$load.doInvoke(core.clj:5865)
> at clojure.lang.RestFn.invoke(RestFn.java:408)
> at clojure.lang.Var.invoke(Var.java:379)
> at org.apache.storm.ui.core.(Unknown Source)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> backtype.storm.security.auth.KerberosPrincipalToLocal
> at
> org.apache.storm.security.auth.AuthUtils.GetPrincipalToLocalPlugin(AuthUtils.java:125)
> at
> org.apache.storm.security.auth.authorizer.SimpleACLAuthorizer.prepare(SimpleACLAuthorizer.java:101)
> at
> org.apache.storm.daemon.common$mk_authorization_handler.invoke(common.clj:414)
> at org.apache.storm.ui.core__init.load(Unknown Source)
> at org.apache.storm.ui.core__init.(Unknown Source)
> ... 12 more
> Caused by: java.lang.ClassNotFoundException:
> backtype.storm.security.auth.KerberosPrincipalToL
[jira] [Created] (AMBARI-17106) Deadlock While Updating Stale Configuration Cache During Upgrade
Jonathan Hurley created AMBARI-17106:
Summary: Deadlock While Updating Stale Configuration Cache During
Upgrade
Key: AMBARI-17106
URL: https://issues.apache.org/jira/browse/AMBARI-17106
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Blocker
Fix For: 2.4.0
ambari-server --hash
dc340e8c6cb4fa6c062f805cc1917f62299a5f50
ambari-server-2.4.0.0-622.x86_64
*Steps*
# Deploy HDP-2.4.0.0 cluster with Ambari 2.4.0.0 (unsecure, non-HA cluster, SSL
enabled)
# Start EU to HDP-2.5.0.0-609
*Result*
While EU is in progress, found that Ambari server seems to have hung; the login
page loads, but unable to login; The following API call hangs too --
https://server:8443/api/v1/clusters/cl1/
There is a deadlock when trying to update the stale configuration cache:
{code}
"Server Action Executor Worker 401" #225 prio=5 os_prio=0
tid=0x7fa07c03e800 nid=0x65df waiting on condition [0x7fa0737ef000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0xa059d4f0> (a
java.util.concurrent.locks.ReentrantReadWriteLock$FairSync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199)
at
java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.lock(ReentrantReadWriteLock.java:943)
--> @TransactionalLock(lockArea = LockArea.STALE_CONFIG_CACHE, lockType =
LockType.WRITE)
at
org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.lockTransaction(AmbariJpaLocalTxnInterceptor.java:291)
at
org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:114)
at
com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
at
com.google.inject.internal.InterceptorStackCallback.intercept(InterceptorStackCallback.java:52)
at
org.apache.ambari.server.state.cluster.ClusterImpl$$EnhancerByGuice$$991b84fc.applyConfigs()
--> clusterGlobalLock.writeLock().lock();
at
org.apache.ambari.server.state.cluster.ClusterImpl.addDesiredConfig(ClusterImpl.java:2340)
at
org.apache.ambari.server.state.ConfigHelper.createConfigTypes(ConfigHelper.java:897)
at
org.apache.ambari.server.controller.internal.UpgradeResourceProvider.applyStackAndProcessConfigurations(UpgradeResourceProvider.java:1174)
{code}
{code}
"ambari-hearbeat-monitor" #23 prio=5 os_prio=0 tid=0x7fa07476c000
nid=0x20ad waiting on condition [0x7fa07bbfb000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0xa32d44a0> (a
java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:967)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1283)
at
java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.lock(ReentrantReadWriteLock.java:727)
at
org.apache.ambari.server.state.cluster.ClusterImpl.getDesiredStackVersion(ClusterImpl.java:1052)
at
org.apache.ambari.server.state.ConfigHelper.calculateIsStaleConfigs(ConfigHelper.java:1075)
--> @TransactionalLock(lockArea = LockArea.STALE_CONFIG_CACHE, lockType =
LockType.READ)
at
org.apache.ambari.server.state.ConfigHelper.isStaleConfigs(ConfigHelper.java:456)
at
org.apache.ambari.server.agent.HeartbeatMonitor.createStatusCommand(HeartbeatMonitor.java:311)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17105) Ambari Server Unit Test failures on trunk
Aravindan Vijayan created AMBARI-17105:
--
Summary: Ambari Server Unit Test failures on trunk
Key: AMBARI-17105
URL: https://issues.apache.org/jira/browse/AMBARI-17105
Project: Ambari
Issue Type: Bug
Affects Versions: 2.4.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Priority: Critical
Fix For: 2.4.0
These errors are gone in the latest runs.
Now the latest shows a failure for
*org.apache.ambari.server.controller.internal.HostResourceProviderTest.testUpdateResourcesAsServiceAdministrator*:
https://builds.apache.org/job/Ambari-trunk-Commit/5023/testReport/org.apache.ambari.server.controller.internal/HostResourceProviderTest/testUpdateResourcesAsServiceAdministrator/
{code}
Error Message
Unexpected exception,
expected
but was
Stacktrace
java.lang.Exception: Unexpected exception,
expected
but was
at
org.apache.ambari.server.controller.internal.HostResourceProviderTest.testUpdateResources(HostResourceProviderTest.java:1036)
at
org.apache.ambari.server.controller.internal.HostResourceProviderTest.testUpdateResourcesAsServiceAdministrator(HostResourceProviderTest.java:966)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17051) Falcon startup properties changes for 2.5
[ https://issues.apache.org/jira/browse/AMBARI-17051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319839#comment-15319839 ] Hudson commented on AMBARI-17051: - FAILURE: Integrated in Ambari-trunk-Commit #5027 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5027/]) AMBARI-17051. Falcon startup properties changes for HDP 2.5 (Venkat (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e70bd21bbce01370d43fdcb29c0167fc86bb08fb]) * ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml * ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/params_linux.py * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml * ambari-server/src/main/resources/stacks/HDP/2.5/services/FALCON/configuration/falcon-startup.properties.xml * ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml * ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml > Falcon startup properties changes for 2.5 > - > > Key: AMBARI-17051 > URL: https://issues.apache.org/jira/browse/AMBARI-17051 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan > Fix For: 2.4.0 > > Attachments: AMBARI-17051-2.patch, AMBARI-17051.patch > > > We need to add extension service, information on extension and lifecycle > policy changes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17099) Update tez-site for HDP 2.5 stack version
[ https://issues.apache.org/jira/browse/AMBARI-17099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319838#comment-15319838 ] Hudson commented on AMBARI-17099: - FAILURE: Integrated in Ambari-trunk-Commit #5027 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5027/]) AMBARI-17099. Add tez-site and update tez-interactive-site for HDP stack (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b3241e3f03948f9e2de2acc8f01e1432640d1c1c]) * ambari-server/src/main/resources/stacks/HDP/2.5/services/TEZ/configuration/tez-site.xml * ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/tez-interactive-site.xml > Update tez-site for HDP 2.5 stack version > - > > Key: AMBARI-17099 > URL: https://issues.apache.org/jira/browse/AMBARI-17099 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > Attachments: AMBARI-17099.01.patch > > > This needs some additional settings. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17027) Metrics Collector API: Introduce basic series aggregation functions
[ https://issues.apache.org/jira/browse/AMBARI-17027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated AMBARI-17027: -- Attachment: AMS-grafana-query-metric-wildcard-without-series-aggregation.png AMS-grafana-query-metric-wildcard-without-series-aggregation-avg.png AMS-grafana-query-metric-wildcard-with-series-aggregation-sum.png AMS-grafana-query-metric-wildcard-with-series-aggregation-avg-with-host.png Attached screenshot. Note: Graph seems odd when we provide hostname. It's just a limitation of current Storm metrics (measure time mismatch between tasks), and it would be fine when we use 'minute' precision or remove hostname. > Metrics Collector API: Introduce basic series aggregation functions > --- > > Key: AMBARI-17027 > URL: https://issues.apache.org/jira/browse/AMBARI-17027 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim > Attachments: > AMS-grafana-query-metric-wildcard-with-series-aggregation-avg-with-host.png, > AMS-grafana-query-metric-wildcard-with-series-aggregation-sum.png, > AMS-grafana-query-metric-wildcard-without-series-aggregation-avg.png, > AMS-grafana-query-metric-wildcard-without-series-aggregation.png > > > AMS doesn't provide tag so metric is identified by appId, metric name, > hostname, instanceId. In this situation metric name is normally consist of > origin metric name and tag values, like graphite, but unlike Graphite, AMS > also doesn't provide series aggregation functions so aggregation should be > done from caller side. > It would be great if Ambari Metrics Collector provides series aggregation > functions, like sumSeries / averageSeries / minSeries / maxSeries on Graphite. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17101) Select Stack Page : "Next" button disabled for blank repo fields
[
https://issues.apache.org/jira/browse/AMBARI-17101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319799#comment-15319799
]
Hadoop QA commented on AMBARI-17101:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12808783/AMBARI-17101.v0.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7233//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7233//console
This message is automatically generated.
> Select Stack Page : "Next" button disabled for blank repo fields
>
>
> Key: AMBARI-17101
> URL: https://issues.apache.org/jira/browse/AMBARI-17101
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17101.v0.patch
>
>
> 1. Provide better regex and checking. Make it more clear to handle blanks and
> bad URLs (missing protocol, etc)
> 2. Treat blank entries as removed, when the user hits Next, as long as they
> complete ONE OS (or choose Satellite).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17104) Conflicts supported OS version
[ https://issues.apache.org/jira/browse/AMBARI-17104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319796#comment-15319796 ] Masahiro Tanaka commented on AMBARI-17104: -- Submit a patch > Conflicts supported OS version > -- > > Key: AMBARI-17104 > URL: https://issues.apache.org/jira/browse/AMBARI-17104 > Project: Ambari > Issue Type: Bug > Components: documentation >Affects Versions: trunk > Environment: Apache Ambari website >Reporter: Masahiro Tanaka >Priority: Trivial > Labels: easyfix > Attachments: AMBARI-17104.patch > > > [Apache Ambari Website|https://ambari.apache.org/] says Ambari Apache > supports RHEL 5,6, CentOS 5,6, and OEL 5,6. > But [docs at Hortonworks > webpage|http://docs.hortonworks.com/HDPDocuments/Ambari-2.2.2.0/bk_Installing_HDP_AMB/content/_operating_systems_requirements.html] > says RHEL 6,7, CentOS 6,7, and OEL 6,7. > We should fix this conflicts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17104) Conflicts supported OS version
[ https://issues.apache.org/jira/browse/AMBARI-17104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka updated AMBARI-17104: - Attachment: AMBARI-17104.patch > Conflicts supported OS version > -- > > Key: AMBARI-17104 > URL: https://issues.apache.org/jira/browse/AMBARI-17104 > Project: Ambari > Issue Type: Bug > Components: documentation >Affects Versions: trunk > Environment: Apache Ambari website >Reporter: Masahiro Tanaka >Priority: Trivial > Labels: easyfix > Attachments: AMBARI-17104.patch > > > [Apache Ambari Website|https://ambari.apache.org/] says Ambari Apache > supports RHEL 5,6, CentOS 5,6, and OEL 5,6. > But [docs at Hortonworks > webpage|http://docs.hortonworks.com/HDPDocuments/Ambari-2.2.2.0/bk_Installing_HDP_AMB/content/_operating_systems_requirements.html] > says RHEL 6,7, CentOS 6,7, and OEL 6,7. > We should fix this conflicts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17104) Conflicts supported OS version
[ https://issues.apache.org/jira/browse/AMBARI-17104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka updated AMBARI-17104: - Status: Patch Available (was: Open) > Conflicts supported OS version > -- > > Key: AMBARI-17104 > URL: https://issues.apache.org/jira/browse/AMBARI-17104 > Project: Ambari > Issue Type: Bug > Components: documentation >Affects Versions: trunk > Environment: Apache Ambari website >Reporter: Masahiro Tanaka >Priority: Trivial > Labels: easyfix > Attachments: AMBARI-17104.patch > > > [Apache Ambari Website|https://ambari.apache.org/] says Ambari Apache > supports RHEL 5,6, CentOS 5,6, and OEL 5,6. > But [docs at Hortonworks > webpage|http://docs.hortonworks.com/HDPDocuments/Ambari-2.2.2.0/bk_Installing_HDP_AMB/content/_operating_systems_requirements.html] > says RHEL 6,7, CentOS 6,7, and OEL 6,7. > We should fix this conflicts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17104) Conflicts supported OS version
Masahiro Tanaka created AMBARI-17104: Summary: Conflicts supported OS version Key: AMBARI-17104 URL: https://issues.apache.org/jira/browse/AMBARI-17104 Project: Ambari Issue Type: Bug Components: documentation Affects Versions: trunk Environment: Apache Ambari website Reporter: Masahiro Tanaka Priority: Trivial [Apache Ambari Website|https://ambari.apache.org/] says Ambari Apache supports RHEL 5,6, CentOS 5,6, and OEL 5,6. But [docs at Hortonworks webpage|http://docs.hortonworks.com/HDPDocuments/Ambari-2.2.2.0/bk_Installing_HDP_AMB/content/_operating_systems_requirements.html] says RHEL 6,7, CentOS 6,7, and OEL 6,7. We should fix this conflicts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17103) Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" using tez/tez-site.xml. Also, removing 'hive.tez.java.opts' config from hive2/hive-site.xml
[ https://issues.apache.org/jira/browse/AMBARI-17103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-17103: - Summary: Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" using tez/tez-site.xml. Also, removing 'hive.tez.java.opts' config from hive2/hive-site.xml as it would be got via inheritance from hive/hive-site.xml (was: Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" using tez/tez-site.xml.) > Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" > using tez/tez-site.xml. Also, removing 'hive.tez.java.opts' config from > hive2/hive-site.xml as it would be got via inheritance from hive/hive-site.xml > --- > > Key: AMBARI-17103 > URL: https://issues.apache.org/jira/browse/AMBARI-17103 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > > - As tez_hive2/tez-interactive-site.xml have only the new/change configs, we > will do the inheritance for other Tez properties from tez/tez-site.xml. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17103) Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" using tez/tez-site.xml. Also, removing 'hive.tez.java.opts' config from hive2/hive-site.xml
[ https://issues.apache.org/jira/browse/AMBARI-17103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-17103: - Description: - As tez_hive2/tez-interactive-site.xml have only the new/change configs, we will do the inheritance for other Tez properties from tez/tez-site.xml. - Also, removing 'hive.tez.java.opts' config from hive2/hive-site.xml as it would be got via inheritance from hive/hive-site.xml was:- As tez_hive2/tez-interactive-site.xml have only the new/change configs, we will do the inheritance for other Tez properties from tez/tez-site.xml. > Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" > using tez/tez-site.xml. Also, removing 'hive.tez.java.opts' config from > hive2/hive-site.xml as it would be got via inheritance from hive/hive-site.xml > --- > > Key: AMBARI-17103 > URL: https://issues.apache.org/jira/browse/AMBARI-17103 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > > - As tez_hive2/tez-interactive-site.xml have only the new/change configs, we > will do the inheritance for other Tez properties from tez/tez-site.xml. > - Also, removing 'hive.tez.java.opts' config from hive2/hive-site.xml as it > would be got via inheritance from hive/hive-site.xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17103) incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" using tez/tez-site.xml.
Swapan Shridhar created AMBARI-17103: Summary: incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" using tez/tez-site.xml. Key: AMBARI-17103 URL: https://issues.apache.org/jira/browse/AMBARI-17103 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Swapan Shridhar Assignee: Swapan Shridhar Fix For: 2.4.0 - As tez_hive2/tez-interactive-site.xml have only the new/change configs, we will do the inheritance for other Tez properties from tez/tez-site.xml. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17103) Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" using tez/tez-site.xml.
[ https://issues.apache.org/jira/browse/AMBARI-17103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-17103: - Summary: Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" using tez/tez-site.xml. (was: incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" using tez/tez-site.xml.) > Incorporating the inheritance logic for "tez_hive2/tez-interactive-site.xml" > using tez/tez-site.xml. > > > Key: AMBARI-17103 > URL: https://issues.apache.org/jira/browse/AMBARI-17103 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > > - As tez_hive2/tez-interactive-site.xml have only the new/change configs, we > will do the inheritance for other Tez properties from tez/tez-site.xml. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17100) EU - HDP 2.4 to 2.5 fails restarting DRPC server on a kerberized cluster, need to use org.apache.storm.security.auth.KerberosPrincipalToLocal
[
https://issues.apache.org/jira/browse/AMBARI-17100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-17100:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to trunk, commit 6fbb4c1830ced4c3f600aa4d7fdb510d2249ddfa
branch-2.4, commit 8b88170daf054f55403e8178160bc96d87d1ce94
> EU - HDP 2.4 to 2.5 fails restarting DRPC server on a kerberized cluster,
> need to use org.apache.storm.security.auth.KerberosPrincipalToLocal
> -
>
> Key: AMBARI-17100
> URL: https://issues.apache.org/jira/browse/AMBARI-17100
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.4.0
>
> Attachments: AMBARI-17100.branch-2.4.patch, AMBARI-17100.trunk.patch
>
>
> STR:
> * Install Ambari 2.4
> * Install HDP 2.4
> * Kerberize the cluster
> * Perform EU to HDP 2.5
> Storm UI Server and DRPC Server:
> {code}
> 2016-06-07 06:16:19.395 b.s.s.a.a.SimpleACLAuthorizer [INFO] [req 5] Access
> from: null principal:ambari-server-...@example.com op:getClusterInfo
> ==> /grid/0/log/storm/ui.out <==
> Running: /usr/jdk64/jdk1.8.0_77/bin/java -server -Ddaemon.name=ui
> -Dstorm.options= -Dstorm.home=/grid/0/hdp/2.5.0.0-664/storm
> -Dstorm.log.dir=/grid/0/log/storm
> -Djava.library.path=/usr/local/lib:/opt/local/lib:/usr/lib:/usr/hdp/current/storm-client/lib
> -Dstorm.conf.file= -cp
> /grid/0/hdp/2.5.0.0-664/storm/lib/log4j-core-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/storm-rename-hack-1.0.1.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/slf4j-api-1.7.7.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/ambari-metrics-storm-sink.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/log4j-over-slf4j-1.6.6.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/servlet-api-2.5.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/clojure-1.7.0.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/asm-5.0.3.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/kryo-3.0.3.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/log4j-slf4j-impl-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/zookeeper.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/disruptor-3.3.2.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/reflectasm-1.10.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/storm-core-1.0.1.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/objenesis-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/minlog-1.3.0.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/log4j-api-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/extlib-daemon/ranger-storm-plugin-shim-0.6.0.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm/extlib-daemon/ojdbc6.jar:/grid/0/hdp/2.5.0.0-664/storm/extlib-daemon/ranger-plugin-classloader-0.6.0.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm:/usr/hdp/current/storm-client/conf
> -Xmx768m
> -Djava.security.auth.login.config=/usr/hdp/current/storm-client/conf/storm_jaas.conf
> -Dlogfile.name=ui.log
> -DLog4jContextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector
> -Dlog4j.configurationFile=/grid/0/hdp/2.5.0.0-664/storm/log4j2/cluster.xml
> org.apache.storm.ui.core
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at clojure.lang.RT.classForName(RT.java:2154)
> at clojure.lang.RT.classForName(RT.java:2163)
> at clojure.lang.RT.loadClassForName(RT.java:2182)
> at clojure.lang.RT.load(RT.java:436)
> at clojure.lang.RT.load(RT.java:412)
> at clojure.core$load$fn__5448.invoke(core.clj:5866)
> at clojure.core$load.doInvoke(core.clj:5865)
> at clojure.lang.RestFn.invoke(RestFn.java:408)
> at clojure.lang.Var.invoke(Var.java:379)
> at org.apache.storm.ui.core.(Unknown Source)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> backtype.storm.security.auth.KerberosPrincipalToLocal
> at
> org.apache.storm.security.auth.AuthUtils.GetPrincipalToLocalPlugin(AuthUtils.java:125)
> at
> org.apache.storm.security.auth.authorizer.SimpleACLAuthorizer.prepare(SimpleACLAuthorizer.java:101)
> at
> org.apache.storm.daemon.common$mk_authorization_handler.invoke(common.clj:414)
> at org.apache.storm.ui.core__init.load(Unknown Source)
> at org.apache.storm.ui.core__init.(Unknown Source)
> ... 12 more
> Caused by: java.lang.ClassNotFoundException:
> backtype.storm.security.auth.KerberosPrincipalToLocal
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.la
[jira] [Commented] (AMBARI-17098) Atlas Integration : Ambari overwrites users-credentials.properties and policy-store.txt
[ https://issues.apache.org/jira/browse/AMBARI-17098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319724#comment-15319724 ] Hudson commented on AMBARI-17098: - FAILURE: Integrated in Ambari-trunk-Commit #5026 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5026/]) AMBARI-17098 - Atlas Integration : Ambari overwrites (tbeerbower: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b71109eeda4a892e8d41dad16cc6134f647d0ba7]) * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java > Atlas Integration : Ambari overwrites users-credentials.properties and > policy-store.txt > --- > > Key: AMBARI-17098 > URL: https://issues.apache.org/jira/browse/AMBARI-17098 > Project: Ambari > Issue Type: Bug >Reporter: Tom Beerbower >Assignee: Tom Beerbower > > The Atlas users-credentials.properties and policy-store.txt are managed by > Ambari but can not be changed. Ambari overwrites any changes when the Atlas > server is restarted. > Make the files un-managed by Ambari so that they can be edited and will pick > up the latest changes from the Atlas distro on installation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-17040) Update tez-interactive-site for HDP stack 2.5
[ https://issues.apache.org/jira/browse/AMBARI-17040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar reopened AMBARI-17040: -- > Update tez-interactive-site for HDP stack 2.5 > - > > Key: AMBARI-17040 > URL: https://issues.apache.org/jira/browse/AMBARI-17040 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth >Assignee: Swapan Shridhar > Attachments: AMBARI-17040.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17040) Update tez-interactive-site for HDP stack 2.5
[ https://issues.apache.org/jira/browse/AMBARI-17040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-17040: - Status: Patch Available (was: Reopened) > Update tez-interactive-site for HDP stack 2.5 > - > > Key: AMBARI-17040 > URL: https://issues.apache.org/jira/browse/AMBARI-17040 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth >Assignee: Swapan Shridhar > Attachments: AMBARI-17040.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17099) Update tez-site for HDP 2.5 stack version
[ https://issues.apache.org/jira/browse/AMBARI-17099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-17099: - Status: Patch Available (was: Open) > Update tez-site for HDP 2.5 stack version > - > > Key: AMBARI-17099 > URL: https://issues.apache.org/jira/browse/AMBARI-17099 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > Attachments: AMBARI-17099.01.patch > > > This needs some additional settings. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17040) Update tez-interactive-site for HDP stack 2.5
[ https://issues.apache.org/jira/browse/AMBARI-17040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-17040: - Resolution: Fixed Status: Resolved (was: Patch Available) > Update tez-interactive-site for HDP stack 2.5 > - > > Key: AMBARI-17040 > URL: https://issues.apache.org/jira/browse/AMBARI-17040 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth >Assignee: Swapan Shridhar > Attachments: AMBARI-17040.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17099) Update tez-site for HDP 2.5 stack version
[ https://issues.apache.org/jira/browse/AMBARI-17099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-17099: - Resolution: Fixed Status: Resolved (was: Patch Available) > Update tez-site for HDP 2.5 stack version > - > > Key: AMBARI-17099 > URL: https://issues.apache.org/jira/browse/AMBARI-17099 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > Attachments: AMBARI-17099.01.patch > > > This needs some additional settings. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17099) Update tez-site for HDP 2.5 stack version
[
https://issues.apache.org/jira/browse/AMBARI-17099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319719#comment-15319719
]
Swapan Shridhar commented on AMBARI-17099:
--
Commits :
trunk:
{code}
commit b3241e3f03948f9e2de2acc8f01e1432640d1c1c
Author: Swapan Shridhar
Date: Tue Jun 7 16:48:50 2016 -0700
AMBARI-17099. Add tez-site and update tez-interactive-site for HDP stack
2.5. (Siddharth Seth via Swapan Shridhar).
{code}
branch-2.4:
{code}
commit c48d964562b9ee54b466a2274f9c018af3b80b7d
Author: Swapan Shridhar
Date: Tue Jun 7 16:53:19 2016 -0700
AMBARI-17099. Add tez-site and update tez-interactive-site for HDP stack
2.5. (Siddharth Seth via Swapan Shridhar).
{code}
> Update tez-site for HDP 2.5 stack version
> -
>
> Key: AMBARI-17099
> URL: https://issues.apache.org/jira/browse/AMBARI-17099
> Project: Ambari
> Issue Type: Task
>Reporter: Siddharth Seth
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17099.01.patch
>
>
> This needs some additional settings.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (AMBARI-17099) Update tez-site for HDP 2.5 stack version
[ https://issues.apache.org/jira/browse/AMBARI-17099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar reassigned AMBARI-17099: Assignee: Swapan Shridhar > Update tez-site for HDP 2.5 stack version > - > > Key: AMBARI-17099 > URL: https://issues.apache.org/jira/browse/AMBARI-17099 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > Attachments: AMBARI-17099.01.patch > > > This needs some additional settings. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17102) Pig view fails when execute/explain/syntax check in kerberos environment
Keta Patel created AMBARI-17102:
---
Summary: Pig view fails when execute/explain/syntax check in
kerberos environment
Key: AMBARI-17102
URL: https://issues.apache.org/jira/browse/AMBARI-17102
Project: Ambari
Issue Type: Bug
Components: ambari-views, contrib
Affects Versions: trunk
Reporter: Keta Patel
Assignee: Keta Patel
Steps to reproduce the issue:
1. Install a cluster containing Pig and Hive services.
2. Create a Pig View Instance following the steps from
http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.0.0/bk_ambari_views_guide/bk_ambari_views_guide-20150721.pdf
3. Go to the Pig View instance and create a new script with some content and
save it. I have used the following content in my script:
A = load '/tmp/passwd' using PigStorage(':');
4. Kerberize the Cluster from Admin -> Kerberos page
5. Kerberize the ambari-server following the link
https://docs.hortonworks.com/HDPDocuments/Ambari-2.1.2.1/bk_Ambari_Security_Guide/content/_optional_set_up_kerberos_for_ambari_server.html
6. Make sure to update the Pig View configuration with the correct Settings for
"WebHDFS Authentication" and "WebHCat Username". Also ensure that the "Cluster
Configuration" is "Custom" with the correct values set for "WebHDFS FileSystem
URI*", "WebHCat Hostname" and "WebHCat Port".
7. Go to the Pig View instance and open the script created earlier. Click the
"Execute" button to run the script.
8. The following error shows up:
java.lang.IllegalArgumentException: Path segment is null
java.lang.IllegalArgumentException: Path segment is null
at
com.sun.jersey.api.uri.UriBuilderImpl.appendPath(UriBuilderImpl.java:547)
at
com.sun.jersey.api.uri.UriBuilderImpl.appendPath(UriBuilderImpl.java:542)
at com.sun.jersey.api.uri.UriBuilderImpl.path(UriBuilderImpl.java:267)
at com.sun.jersey.api.client.WebResource.path(WebResource.java:390)
at
org.apache.ambari.view.pig.templeton.client.TempletonApi.checkJob(TempletonApi.java:128)
at
org.apache.ambari.view.pig.resources.jobs.JobResourceManager.retrieveJobStatus(JobResourceManager.java:245)
at
org.apache.ambari.view.pig.resources.jobs.JobService.getJob(JobService.java:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17101) Select Stack Page : "Next" button disabled for blank repo fields
[ https://issues.apache.org/jira/browse/AMBARI-17101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17101: Status: Patch Available (was: Open) > Select Stack Page : "Next" button disabled for blank repo fields > > > Key: AMBARI-17101 > URL: https://issues.apache.org/jira/browse/AMBARI-17101 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-17101.v0.patch > > > 1. Provide better regex and checking. Make it more clear to handle blanks and > bad URLs (missing protocol, etc) > 2. Treat blank entries as removed, when the user hits Next, as long as they > complete ONE OS (or choose Satellite). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17101) Select Stack Page : "Next" button disabled for blank repo fields
[ https://issues.apache.org/jira/browse/AMBARI-17101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17101: Attachment: AMBARI-17101.v0.patch Modified unit test. Local ambari-web test passed. 28665 tests complete (24 seconds) 154 tests pending Manual testing done. > Select Stack Page : "Next" button disabled for blank repo fields > > > Key: AMBARI-17101 > URL: https://issues.apache.org/jira/browse/AMBARI-17101 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-17101.v0.patch > > > 1. Provide better regex and checking. Make it more clear to handle blanks and > bad URLs (missing protocol, etc) > 2. Treat blank entries as removed, when the user hits Next, as long as they > complete ONE OS (or choose Satellite). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17101) Select Stack Page : "Next" button disabled for blank repo fields
Zhe (Joe) Wang created AMBARI-17101: --- Summary: Select Stack Page : "Next" button disabled for blank repo fields Key: AMBARI-17101 URL: https://issues.apache.org/jira/browse/AMBARI-17101 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.4.0 Reporter: Zhe (Joe) Wang Assignee: Zhe (Joe) Wang Fix For: 2.4.0 1. Provide better regex and checking. Make it more clear to handle blanks and bad URLs (missing protocol, etc) 2. Treat blank entries as removed, when the user hits Next, as long as they complete ONE OS (or choose Satellite). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17041) Support password type for custom properties
[ https://issues.apache.org/jira/browse/AMBARI-17041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tuong Truong updated AMBARI-17041: -- Assignee: Keta Patel > Support password type for custom properties > --- > > Key: AMBARI-17041 > URL: https://issues.apache.org/jira/browse/AMBARI-17041 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Tuong Truong >Assignee: Keta Patel > > Currently, services can define properties in the XML configuration files that > is flagged as type password: > > my.special.password > > PASSWORD > Password to be masked > > and it will be masked properly in the UI as well as blueprint. > Custom property should also support this option so that password can be added > as custom property and treat accordingly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17100) EU - HDP 2.4 to 2.5 fails restarting DRPC server on a kerberized cluster, need to use org.apache.storm.security.auth.KerberosPrincipalToLocal
[
https://issues.apache.org/jira/browse/AMBARI-17100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-17100:
-
Description:
STR:
* Install Ambari 2.4
* Install HDP 2.4
* Kerberize the cluster
* Perform EU to HDP 2.5
Storm UI Server and DRPC Server:
{code}
2016-06-07 06:16:19.395 b.s.s.a.a.SimpleACLAuthorizer [INFO] [req 5] Access
from: null principal:ambari-server-...@example.com op:getClusterInfo
==> /grid/0/log/storm/ui.out <==
Running: /usr/jdk64/jdk1.8.0_77/bin/java -server -Ddaemon.name=ui
-Dstorm.options= -Dstorm.home=/grid/0/hdp/2.5.0.0-664/storm
-Dstorm.log.dir=/grid/0/log/storm
-Djava.library.path=/usr/local/lib:/opt/local/lib:/usr/lib:/usr/hdp/current/storm-client/lib
-Dstorm.conf.file= -cp
/grid/0/hdp/2.5.0.0-664/storm/lib/log4j-core-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/storm-rename-hack-1.0.1.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/slf4j-api-1.7.7.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/ambari-metrics-storm-sink.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/log4j-over-slf4j-1.6.6.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/servlet-api-2.5.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/clojure-1.7.0.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/asm-5.0.3.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/kryo-3.0.3.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/log4j-slf4j-impl-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/zookeeper.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/disruptor-3.3.2.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/reflectasm-1.10.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/storm-core-1.0.1.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/objenesis-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/minlog-1.3.0.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/log4j-api-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/extlib-daemon/ranger-storm-plugin-shim-0.6.0.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm/extlib-daemon/ojdbc6.jar:/grid/0/hdp/2.5.0.0-664/storm/extlib-daemon/ranger-plugin-classloader-0.6.0.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm:/usr/hdp/current/storm-client/conf
-Xmx768m
-Djava.security.auth.login.config=/usr/hdp/current/storm-client/conf/storm_jaas.conf
-Dlogfile.name=ui.log
-DLog4jContextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector
-Dlog4j.configurationFile=/grid/0/hdp/2.5.0.0-664/storm/log4j2/cluster.xml
org.apache.storm.ui.core
Exception in thread "main" java.lang.ExceptionInInitializerError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:348)
at clojure.lang.RT.classForName(RT.java:2154)
at clojure.lang.RT.classForName(RT.java:2163)
at clojure.lang.RT.loadClassForName(RT.java:2182)
at clojure.lang.RT.load(RT.java:436)
at clojure.lang.RT.load(RT.java:412)
at clojure.core$load$fn__5448.invoke(core.clj:5866)
at clojure.core$load.doInvoke(core.clj:5865)
at clojure.lang.RestFn.invoke(RestFn.java:408)
at clojure.lang.Var.invoke(Var.java:379)
at org.apache.storm.ui.core.(Unknown Source)
Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
backtype.storm.security.auth.KerberosPrincipalToLocal
at
org.apache.storm.security.auth.AuthUtils.GetPrincipalToLocalPlugin(AuthUtils.java:125)
at
org.apache.storm.security.auth.authorizer.SimpleACLAuthorizer.prepare(SimpleACLAuthorizer.java:101)
at
org.apache.storm.daemon.common$mk_authorization_handler.invoke(common.clj:414)
at org.apache.storm.ui.core__init.load(Unknown Source)
at org.apache.storm.ui.core__init.(Unknown Source)
... 12 more
Caused by: java.lang.ClassNotFoundException:
backtype.storm.security.auth.KerberosPrincipalToLocal
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at
org.apache.storm.security.auth.AuthUtils.GetPrincipalToLocalPlugin(AuthUtils.java:121)
... 16 more
{code}
During RU, it made config changes to storm-site,
{code}
storm-site/client.jartransformer.class changed to
"org.apache.storm.hack.StormShadeTransformer"
String "backtype.storm.security.auth.SimpleTransportPlugin" was not found in
storm-site/_storm.thrift.nonsecure.transport
String "backtype.storm.security.auth.KerberosSaslTransportPlugin" was not found
in storm-site/_storm.thrift.secure.transport
String "backtype.storm.messaging.netty.Context" was not found in
storm-site/storm.messaging.transport
String "backtype.storm.nimbus.DefaultTopologyValidator" was not found in
storm-site/nimbus.topology.validator
String "backtype.storm.spout.SleepSpoutWaitStrategy" was not found in
storm-site/topology.spout.wait.strategy
String "backtype.sto
[jira] [Updated] (AMBARI-17100) EU - HDP 2.4 to 2.5 fails restarting DRPC server on a kerberized cluster, need to use org.apache.storm.security.auth.KerberosPrincipalToLocal
[
https://issues.apache.org/jira/browse/AMBARI-17100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-17100:
-
Status: Patch Available (was: Open)
> EU - HDP 2.4 to 2.5 fails restarting DRPC server on a kerberized cluster,
> need to use org.apache.storm.security.auth.KerberosPrincipalToLocal
> -
>
> Key: AMBARI-17100
> URL: https://issues.apache.org/jira/browse/AMBARI-17100
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.4.0
>
> Attachments: AMBARI-17100.branch-2.4.patch, AMBARI-17100.trunk.patch
>
>
> STR:
> * Install Ambari 2.4
> * Install HDP 2.4
> * Kerberize the cluster
> * Perform EU to HDP 2.5
> https://172.22.73.132:8443
> Storm UI Server and DRPC Server:
> {code}
> 2016-06-07 06:16:19.395 b.s.s.a.a.SimpleACLAuthorizer [INFO] [req 5] Access
> from: null principal:ambari-server-...@example.com op:getClusterInfo
> ==> /grid/0/log/storm/ui.out <==
> Running: /usr/jdk64/jdk1.8.0_77/bin/java -server -Ddaemon.name=ui
> -Dstorm.options= -Dstorm.home=/grid/0/hdp/2.5.0.0-664/storm
> -Dstorm.log.dir=/grid/0/log/storm
> -Djava.library.path=/usr/local/lib:/opt/local/lib:/usr/lib:/usr/hdp/current/storm-client/lib
> -Dstorm.conf.file= -cp
> /grid/0/hdp/2.5.0.0-664/storm/lib/log4j-core-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/storm-rename-hack-1.0.1.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/slf4j-api-1.7.7.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/ambari-metrics-storm-sink.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/log4j-over-slf4j-1.6.6.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/servlet-api-2.5.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/clojure-1.7.0.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/asm-5.0.3.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/kryo-3.0.3.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/log4j-slf4j-impl-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/zookeeper.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/disruptor-3.3.2.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/reflectasm-1.10.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/storm-core-1.0.1.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/objenesis-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/minlog-1.3.0.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/log4j-api-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/extlib-daemon/ranger-storm-plugin-shim-0.6.0.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm/extlib-daemon/ojdbc6.jar:/grid/0/hdp/2.5.0.0-664/storm/extlib-daemon/ranger-plugin-classloader-0.6.0.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm:/usr/hdp/current/storm-client/conf
> -Xmx768m
> -Djava.security.auth.login.config=/usr/hdp/current/storm-client/conf/storm_jaas.conf
> -Dlogfile.name=ui.log
> -DLog4jContextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector
> -Dlog4j.configurationFile=/grid/0/hdp/2.5.0.0-664/storm/log4j2/cluster.xml
> org.apache.storm.ui.core
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at clojure.lang.RT.classForName(RT.java:2154)
> at clojure.lang.RT.classForName(RT.java:2163)
> at clojure.lang.RT.loadClassForName(RT.java:2182)
> at clojure.lang.RT.load(RT.java:436)
> at clojure.lang.RT.load(RT.java:412)
> at clojure.core$load$fn__5448.invoke(core.clj:5866)
> at clojure.core$load.doInvoke(core.clj:5865)
> at clojure.lang.RestFn.invoke(RestFn.java:408)
> at clojure.lang.Var.invoke(Var.java:379)
> at org.apache.storm.ui.core.(Unknown Source)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> backtype.storm.security.auth.KerberosPrincipalToLocal
> at
> org.apache.storm.security.auth.AuthUtils.GetPrincipalToLocalPlugin(AuthUtils.java:125)
> at
> org.apache.storm.security.auth.authorizer.SimpleACLAuthorizer.prepare(SimpleACLAuthorizer.java:101)
> at
> org.apache.storm.daemon.common$mk_authorization_handler.invoke(common.clj:414)
> at org.apache.storm.ui.core__init.load(Unknown Source)
> at org.apache.storm.ui.core__init.(Unknown Source)
> ... 12 more
> Caused by: java.lang.ClassNotFoundException:
> backtype.storm.security.auth.KerberosPrincipalToLocal
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.storm.security.aut
[jira] [Updated] (AMBARI-17100) EU - HDP 2.4 to 2.5 fails restarting DRPC server on a kerberized cluster, need to use org.apache.storm.security.auth.KerberosPrincipalToLocal
[
https://issues.apache.org/jira/browse/AMBARI-17100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-17100:
-
Attachment: AMBARI-17100.branch-2.4.patch
AMBARI-17100.trunk.patch
> EU - HDP 2.4 to 2.5 fails restarting DRPC server on a kerberized cluster,
> need to use org.apache.storm.security.auth.KerberosPrincipalToLocal
> -
>
> Key: AMBARI-17100
> URL: https://issues.apache.org/jira/browse/AMBARI-17100
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.4.0
>
> Attachments: AMBARI-17100.branch-2.4.patch, AMBARI-17100.trunk.patch
>
>
> STR:
> * Install Ambari 2.4
> * Install HDP 2.4
> * Kerberize the cluster
> * Perform EU to HDP 2.5
> https://172.22.73.132:8443
> Storm UI Server and DRPC Server:
> {code}
> 2016-06-07 06:16:19.395 b.s.s.a.a.SimpleACLAuthorizer [INFO] [req 5] Access
> from: null principal:ambari-server-...@example.com op:getClusterInfo
> ==> /grid/0/log/storm/ui.out <==
> Running: /usr/jdk64/jdk1.8.0_77/bin/java -server -Ddaemon.name=ui
> -Dstorm.options= -Dstorm.home=/grid/0/hdp/2.5.0.0-664/storm
> -Dstorm.log.dir=/grid/0/log/storm
> -Djava.library.path=/usr/local/lib:/opt/local/lib:/usr/lib:/usr/hdp/current/storm-client/lib
> -Dstorm.conf.file= -cp
> /grid/0/hdp/2.5.0.0-664/storm/lib/log4j-core-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/storm-rename-hack-1.0.1.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/slf4j-api-1.7.7.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/ambari-metrics-storm-sink.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/log4j-over-slf4j-1.6.6.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/servlet-api-2.5.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/clojure-1.7.0.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/asm-5.0.3.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/kryo-3.0.3.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/log4j-slf4j-impl-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/zookeeper.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/disruptor-3.3.2.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/reflectasm-1.10.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/storm-core-1.0.1.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/objenesis-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/minlog-1.3.0.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/log4j-api-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/extlib-daemon/ranger-storm-plugin-shim-0.6.0.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm/extlib-daemon/ojdbc6.jar:/grid/0/hdp/2.5.0.0-664/storm/extlib-daemon/ranger-plugin-classloader-0.6.0.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm:/usr/hdp/current/storm-client/conf
> -Xmx768m
> -Djava.security.auth.login.config=/usr/hdp/current/storm-client/conf/storm_jaas.conf
> -Dlogfile.name=ui.log
> -DLog4jContextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector
> -Dlog4j.configurationFile=/grid/0/hdp/2.5.0.0-664/storm/log4j2/cluster.xml
> org.apache.storm.ui.core
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at clojure.lang.RT.classForName(RT.java:2154)
> at clojure.lang.RT.classForName(RT.java:2163)
> at clojure.lang.RT.loadClassForName(RT.java:2182)
> at clojure.lang.RT.load(RT.java:436)
> at clojure.lang.RT.load(RT.java:412)
> at clojure.core$load$fn__5448.invoke(core.clj:5866)
> at clojure.core$load.doInvoke(core.clj:5865)
> at clojure.lang.RestFn.invoke(RestFn.java:408)
> at clojure.lang.Var.invoke(Var.java:379)
> at org.apache.storm.ui.core.(Unknown Source)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> backtype.storm.security.auth.KerberosPrincipalToLocal
> at
> org.apache.storm.security.auth.AuthUtils.GetPrincipalToLocalPlugin(AuthUtils.java:125)
> at
> org.apache.storm.security.auth.authorizer.SimpleACLAuthorizer.prepare(SimpleACLAuthorizer.java:101)
> at
> org.apache.storm.daemon.common$mk_authorization_handler.invoke(common.clj:414)
> at org.apache.storm.ui.core__init.load(Unknown Source)
> at org.apache.storm.ui.core__init.(Unknown Source)
> ... 12 more
> Caused by: java.lang.ClassNotFoundException:
> backtype.storm.security.auth.KerberosPrincipalToLocal
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:26
[jira] [Created] (AMBARI-17100) EU - HDP 2.4 to 2.5 fails restarting DRPC server on a kerberized cluster, need to use org.apache.storm.security.auth.KerberosPrincipalToLocal
Alejandro Fernandez created AMBARI-17100:
Summary: EU - HDP 2.4 to 2.5 fails restarting DRPC server on a
kerberized cluster, need to use
org.apache.storm.security.auth.KerberosPrincipalToLocal
Key: AMBARI-17100
URL: https://issues.apache.org/jira/browse/AMBARI-17100
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 2.4.0
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
Fix For: 2.4.0
STR:
* Install Ambari 2.4
* Install HDP 2.4
* Kerberize the cluster
* Perform EU to HDP 2.5
https://172.22.73.132:8443
Storm UI Server and DRPC Server:
{code}
2016-06-07 06:16:19.395 b.s.s.a.a.SimpleACLAuthorizer [INFO] [req 5] Access
from: null principal:ambari-server-...@example.com op:getClusterInfo
==> /grid/0/log/storm/ui.out <==
Running: /usr/jdk64/jdk1.8.0_77/bin/java -server -Ddaemon.name=ui
-Dstorm.options= -Dstorm.home=/grid/0/hdp/2.5.0.0-664/storm
-Dstorm.log.dir=/grid/0/log/storm
-Djava.library.path=/usr/local/lib:/opt/local/lib:/usr/lib:/usr/hdp/current/storm-client/lib
-Dstorm.conf.file= -cp
/grid/0/hdp/2.5.0.0-664/storm/lib/log4j-core-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/storm-rename-hack-1.0.1.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/slf4j-api-1.7.7.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/ambari-metrics-storm-sink.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/log4j-over-slf4j-1.6.6.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/servlet-api-2.5.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/clojure-1.7.0.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/asm-5.0.3.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/kryo-3.0.3.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/log4j-slf4j-impl-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/zookeeper.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/disruptor-3.3.2.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/reflectasm-1.10.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/storm-core-1.0.1.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/objenesis-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/minlog-1.3.0.jar:/grid/0/hdp/2.5.0.0-664/storm/lib/log4j-api-2.1.jar:/grid/0/hdp/2.5.0.0-664/storm/extlib-daemon/ranger-storm-plugin-shim-0.6.0.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm/extlib-daemon/ojdbc6.jar:/grid/0/hdp/2.5.0.0-664/storm/extlib-daemon/ranger-plugin-classloader-0.6.0.2.5.0.0-664.jar:/grid/0/hdp/2.5.0.0-664/storm:/usr/hdp/current/storm-client/conf
-Xmx768m
-Djava.security.auth.login.config=/usr/hdp/current/storm-client/conf/storm_jaas.conf
-Dlogfile.name=ui.log
-DLog4jContextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector
-Dlog4j.configurationFile=/grid/0/hdp/2.5.0.0-664/storm/log4j2/cluster.xml
org.apache.storm.ui.core
Exception in thread "main" java.lang.ExceptionInInitializerError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:348)
at clojure.lang.RT.classForName(RT.java:2154)
at clojure.lang.RT.classForName(RT.java:2163)
at clojure.lang.RT.loadClassForName(RT.java:2182)
at clojure.lang.RT.load(RT.java:436)
at clojure.lang.RT.load(RT.java:412)
at clojure.core$load$fn__5448.invoke(core.clj:5866)
at clojure.core$load.doInvoke(core.clj:5865)
at clojure.lang.RestFn.invoke(RestFn.java:408)
at clojure.lang.Var.invoke(Var.java:379)
at org.apache.storm.ui.core.(Unknown Source)
Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
backtype.storm.security.auth.KerberosPrincipalToLocal
at
org.apache.storm.security.auth.AuthUtils.GetPrincipalToLocalPlugin(AuthUtils.java:125)
at
org.apache.storm.security.auth.authorizer.SimpleACLAuthorizer.prepare(SimpleACLAuthorizer.java:101)
at
org.apache.storm.daemon.common$mk_authorization_handler.invoke(common.clj:414)
at org.apache.storm.ui.core__init.load(Unknown Source)
at org.apache.storm.ui.core__init.(Unknown Source)
... 12 more
Caused by: java.lang.ClassNotFoundException:
backtype.storm.security.auth.KerberosPrincipalToLocal
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at
org.apache.storm.security.auth.AuthUtils.GetPrincipalToLocalPlugin(AuthUtils.java:121)
... 16 more
{code}
During RU, it made config changes to storm-site,
{code}
storm-site/client.jartransformer.class changed to
"org.apache.storm.hack.StormShadeTransformer"
String "backtype.storm.security.auth.SimpleTransportPlugin" was not found in
storm-site/_storm.thrift.nonsecure.transport
String "backtype.storm.security.auth.KerberosSaslTransportPlugin" was not found
in sto
[jira] [Updated] (AMBARI-17051) Falcon startup properties changes for 2.5
[ https://issues.apache.org/jira/browse/AMBARI-17051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-17051: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk, commit e70bd21bbce01370d43fdcb29c0167fc86bb08fb branch-2.4, commit 4452d0b4e5f028aef00dfdc28d731e7b1d94961f > Falcon startup properties changes for 2.5 > - > > Key: AMBARI-17051 > URL: https://issues.apache.org/jira/browse/AMBARI-17051 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan > Fix For: 2.4.0 > > Attachments: AMBARI-17051-2.patch, AMBARI-17051.patch > > > We need to add extension service, information on extension and lifecycle > policy changes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17051) Falcon startup properties changes for 2.5
[ https://issues.apache.org/jira/browse/AMBARI-17051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-17051: - Fix Version/s: 2.4.0 > Falcon startup properties changes for 2.5 > - > > Key: AMBARI-17051 > URL: https://issues.apache.org/jira/browse/AMBARI-17051 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan > Fix For: 2.4.0 > > Attachments: AMBARI-17051-2.patch, AMBARI-17051.patch > > > We need to add extension service, information on extension and lifecycle > policy changes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17022) VDF: install wizard "Select Version" UI issues
[ https://issues.apache.org/jira/browse/AMBARI-17022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319537#comment-15319537 ] Hudson commented on AMBARI-17022: - FAILURE: Integrated in Ambari-trunk-Commit #5025 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5025/]) AMBARI-17022. VDF: install wizard 'Select Version' UI issues.(xiwang) (xiwang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=edf85a3837519b9c4e5704531627f4985a56b5ea]) * ambari-web/app/styles/common.less * ambari-web/app/styles/application.less * ambari-web/app/models/stack.js > VDF: install wizard "Select Version" UI issues > -- > > Key: AMBARI-17022 > URL: https://issues.apache.org/jira/browse/AMBARI-17022 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Xi Wang >Assignee: Xi Wang >Priority: Critical > Labels: vdf > Fix For: 2.4.0 > > Attachments: AMBARI-17022.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17022) VDF: install wizard "Select Version" UI issues
[ https://issues.apache.org/jira/browse/AMBARI-17022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-17022: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 > VDF: install wizard "Select Version" UI issues > -- > > Key: AMBARI-17022 > URL: https://issues.apache.org/jira/browse/AMBARI-17022 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Xi Wang >Assignee: Xi Wang >Priority: Critical > Labels: vdf > Fix For: 2.4.0 > > Attachments: AMBARI-17022.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17099) Update tez-site for HDP 2.5 stack version
[ https://issues.apache.org/jira/browse/AMBARI-17099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319380#comment-15319380 ] Swapan Shridhar commented on AMBARI-17099: -- +1 for the patch. > Update tez-site for HDP 2.5 stack version > - > > Key: AMBARI-17099 > URL: https://issues.apache.org/jira/browse/AMBARI-17099 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth > Fix For: 2.4.0 > > Attachments: AMBARI-17099.01.patch > > > This needs some additional settings. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17040) Update tez-interactive-site for HDP stack 2.5
[ https://issues.apache.org/jira/browse/AMBARI-17040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319357#comment-15319357 ] Hudson commented on AMBARI-17040: - FAILURE: Integrated in Ambari-trunk-Commit #5024 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5024/]) AMBARI-17040. Update tez-interactive-site for HDP stack 2.5. (Siddharth (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8edd1869e89eb783c9349078031740f7e90ea80f]) * ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/tez-interactive-site.xml > Update tez-interactive-site for HDP stack 2.5 > - > > Key: AMBARI-17040 > URL: https://issues.apache.org/jira/browse/AMBARI-17040 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth >Assignee: Swapan Shridhar > Attachments: AMBARI-17040.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17098) Atlas Integration : Ambari overwrites users-credentials.properties and policy-store.txt
[ https://issues.apache.org/jira/browse/AMBARI-17098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319354#comment-15319354 ] Hudson commented on AMBARI-17098: - FAILURE: Integrated in Ambari-trunk-Commit #5024 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5024/]) AMBARI-17098 - Atlas Integration : Ambari overwrites (tbeerbower: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ea2cbfcf3957258501e04583776b346adc478d96]) * ambari-server/src/main/resources/stacks/HDP/2.5/services/ATLAS/configuration/application-properties.xml * ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java * ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py * ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java * ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/params.py AMBARI-17098 - Atlas Integration : Ambari overwrites (tbeerbower: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=62e124c9817e6400c71c775a45f388a2c8c18cb0]) * ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/files/policy-store.txt * ambari-server/src/test/python/stacks/2.3/ATLAS/test_metadata_server.py * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java * ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/files/users-credentials.properties * ambari-server/src/test/python/stacks/2.5/ATLAS/test_atlas_server.py * ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata.py * ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/params.py * ambari-server/src/main/resources/stacks/HDP/2.5/services/ATLAS/configuration/application-properties.xml > Atlas Integration : Ambari overwrites users-credentials.properties and > policy-store.txt > --- > > Key: AMBARI-17098 > URL: https://issues.apache.org/jira/browse/AMBARI-17098 > Project: Ambari > Issue Type: Bug >Reporter: Tom Beerbower >Assignee: Tom Beerbower > > The Atlas users-credentials.properties and policy-store.txt are managed by > Ambari but can not be changed. Ambari overwrites any changes when the Atlas > server is restarted. > Make the files un-managed by Ambari so that they can be edited and will pick > up the latest changes from the Atlas distro on installation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17077) Unable to change user role in list view
[
https://issues.apache.org/jira/browse/AMBARI-17077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319356#comment-15319356
]
Hudson commented on AMBARI-17077:
-
FAILURE: Integrated in Ambari-trunk-Commit #5024 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5024/])
AMBARI-17077 - Unable to change user role in list view (rzang) (rzang:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9e15b2b652be4097e61b104bccea310b0e23196a])
*
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/clusters/UserAccessListCtrl.js
> Unable to change user role in list view
> ---
>
> Key: AMBARI-17077
> URL: https://issues.apache.org/jira/browse/AMBARI-17077
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: 2.4.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17077.patch
>
>
> STR:
> 1. Go to Manage Ambari.
> 2. Create user.
> 3. Go to Roles menu, list view.
> 4. Set role for newly created user.
> 5. Change role for that user.
> {noformat}Cannot save permissions
> t's effective privilege through its Group(s) is higher than your selected
> privilege.{noformat}
> No goups was created.
> Workaround: change role to None and then change to desired value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17043) Fix description of SERVICE.ADD_DELETE_SERVICES permission
[
https://issues.apache.org/jira/browse/AMBARI-17043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319355#comment-15319355
]
Hudson commented on AMBARI-17043:
-
FAILURE: Integrated in Ambari-trunk-Commit #5024 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5024/])
AMBARI-17043. Fix description of SERVICE.ADD_DELETE_SERVICES permission
(rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c85d0d15e5c015a069c888c25583e7bfe767acd8])
* ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
*
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java
* ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog230.java
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java
> Fix description of SERVICE.ADD_DELETE_SERVICES permission
> -
>
> Key: AMBARI-17043
> URL: https://issues.apache.org/jira/browse/AMBARI-17043
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.3.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: rbac
> Fix For: 2.4.0
>
> Attachments: AMBARI-17043_branch-2.4_01.patch,
> AMBARI-17043_trunk_01.patch
>
>
> The description of the SERVICE.ADD_DELETE_SERVICES permission currently reads
> {quote}
> Add Service to cluster
> {quote}
> This should be changed to
> {quote}
> Add/delete services
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17076) Hive view 2.0.0 Instance has issues connecting to database in secure mode
[ https://issues.apache.org/jira/browse/AMBARI-17076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319309#comment-15319309 ] Hudson commented on AMBARI-17076: - FAILURE: Integrated in Ambari-trunk-Commit #5023 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5023/]) AMBARI-17076 Hive view 2.0.0 Instance has issues connecting to database (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4d622167d94779cb9fd291b12fc406378b06ef54]) * contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/resources/jobs/ResultsPaginationController.java * contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/HiveActor.java * contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/DeathWatch.java * contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/OperationController.java * contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/ConnectionFactory.java * contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/AsyncJdbcConnector.java > Hive view 2.0.0 Instance has issues connecting to database in secure mode > - > > Key: AMBARI-17076 > URL: https://issues.apache.org/jira/browse/AMBARI-17076 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.0 > > Attachments: AMBARI-17076.trunk.2.patch, AMBARI-17076.trunk.4.patch, > AMBARI-17076.trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17092) LogSearch https support.
[ https://issues.apache.org/jira/browse/AMBARI-17092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319307#comment-15319307 ] Hudson commented on AMBARI-17092: - FAILURE: Integrated in Ambari-trunk-Commit #5023 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5023/]) AMBARI-17092. LogSearch https support (Dharmesh Makwana via oleewere) (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4468e1624d83e9d7547f81d3ea9b1e6772ccae20]) * ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/util/PropertiesUtil.java * ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/LogSearch.java * ambari-logsearch/ambari-logsearch-portal/src/main/resources/logsearch.properties > LogSearch https support. > > > Key: AMBARI-17092 > URL: https://issues.apache.org/jira/browse/AMBARI-17092 > Project: Ambari > Issue Type: New Feature > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Dharmesh Makwana >Assignee: Dharmesh Makwana > Fix For: 2.4.0 > > > LogSearch portal should support HTTPS to ensure secure communication -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17073) HDF Management install does not allow one to select public repo
[ https://issues.apache.org/jira/browse/AMBARI-17073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319308#comment-15319308 ] Hudson commented on AMBARI-17073: - FAILURE: Integrated in Ambari-trunk-Commit #5023 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5023/]) AMBARI-17073 HDF Management install does not allow one to select public (zhewang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=237715f04d00e8fcf90bfbbc9ca19939b2457539]) * ambari-web/app/views/wizard/step1_view.js * ambari-web/app/templates/wizard/step1.hbs * ambari-web/app/messages.js * ambari-web/app/templates/wizard/step1/public_option_disabled_window_body.hbs > HDF Management install does not allow one to select public repo > --- > > Key: AMBARI-17073 > URL: https://issues.apache.org/jira/browse/AMBARI-17073 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-17073.v0.patch, AMBARI-17073.v1.patch > > > To fulfill the requirement of enforcing users to choose local repo when they > don’t have internet access, in FE we use the logic of checking whether all > versions are stack_default versions. That logic is true for HDP for now, but > not for HDF. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16017) Update Moment.js to latest stable version 2.13.0
[ https://issues.apache.org/jira/browse/AMBARI-16017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319306#comment-15319306 ] Hudson commented on AMBARI-16017: - FAILURE: Integrated in Ambari-trunk-Commit #5023 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5023/]) Ambari-16017: Update Moment.js to latest stable version 2.13.0 (Sangeeta (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4e2d4aff33ff466581b8da79ef9ce7175cc8d53f]) * contrib/views/slider/src/main/resources/ui/vendor/scripts/common/moment.js * ambari-web/config.coffee * contrib/views/slider/src/main/resources/ui/vendor/scripts/common/moment.min.js * ambari-web/vendor/scripts/moment.js * ambari-web/karma.conf.js * ambari-web/vendor/scripts/moment.min.js * contrib/views/slider/src/main/resources/ui/config.js > Update Moment.js to latest stable version 2.13.0 > > > Key: AMBARI-16017 > URL: https://issues.apache.org/jira/browse/AMBARI-16017 > Project: Ambari > Issue Type: Task > Components: ambari-views, ambari-web >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Labels: patch > Fix For: trunk > > Attachments: AMBARI-16017_0602.patch > > > The latest stable version of Moment.js is 2.13.0. > This task is for updating the version of Moment.js used in > contrib/views/slider/src/main/resources/ui/vendor/scripts/common/ > ambari-web/vendor/scripts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-10908) Usability: ability to perform bulk delete host
[ https://issues.apache.org/jira/browse/AMBARI-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319310#comment-15319310 ] Hudson commented on AMBARI-10908: - FAILURE: Integrated in Ambari-trunk-Commit #5023 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5023/]) AMBARI-10908 Usability: ability to perform bulk delete host (zhewang) (zhewang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bd58a5038032445831996a33ae52a08f387a2335]) * ambari-web/app/styles/application.less * ambari-web/app/templates/main/host/delete_hosts_popup.hbs * ambari-web/app/views/main/host/hosts_table_menu_view.js * ambari-web/app/templates/main/host/delete_hosts_result_popup.hbs * ambari-web/app/utils/ajax/ajax.js * ambari-web/app/templates/main/host/delete_hosts_dry_run_popup.hbs * ambari-web/app/controllers/main/host/bulk_operations_controller.js * ambari-web/app/messages.js > Usability: ability to perform bulk delete host > -- > > Key: AMBARI-10908 > URL: https://issues.apache.org/jira/browse/AMBARI-10908 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Jeff Sposetti >Assignee: Zhe (Joe) Wang > Fix For: 3.0.0 > > Attachments: AMBARI-10908.v0.patch, AMBARI-10908.v1.patch > > > On Hosts page, provide ability to delete hosts in bulk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17051) Falcon startup properties changes for 2.5
[
https://issues.apache.org/jira/browse/AMBARI-17051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319296#comment-15319296
]
Hadoop QA commented on AMBARI-17051:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12808738/AMBARI-17051-2.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/7232//console
This message is automatically generated.
> Falcon startup properties changes for 2.5
> -
>
> Key: AMBARI-17051
> URL: https://issues.apache.org/jira/browse/AMBARI-17051
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
> Attachments: AMBARI-17051-2.patch, AMBARI-17051.patch
>
>
> We need to add extension service, information on extension and lifecycle
> policy changes
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17099) Update tez-site for HDP 2.5 stack version
[ https://issues.apache.org/jira/browse/AMBARI-17099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319295#comment-15319295 ] Siddharth Seth commented on AMBARI-17099: - cc [~swapanshridhar], [~hitesh] - could you please review. > Update tez-site for HDP 2.5 stack version > - > > Key: AMBARI-17099 > URL: https://issues.apache.org/jira/browse/AMBARI-17099 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth > Fix For: 2.4.0 > > Attachments: AMBARI-17099.01.patch > > > This needs some additional settings. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17099) Update tez-site for HDP 2.5 stack version
[ https://issues.apache.org/jira/browse/AMBARI-17099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated AMBARI-17099: Attachment: AMBARI-17099.01.patch > Update tez-site for HDP 2.5 stack version > - > > Key: AMBARI-17099 > URL: https://issues.apache.org/jira/browse/AMBARI-17099 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth > Fix For: 2.4.0 > > Attachments: AMBARI-17099.01.patch > > > This needs some additional settings. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17099) Update tez-site for HDP 2.5 stack version
Siddharth Seth created AMBARI-17099: --- Summary: Update tez-site for HDP 2.5 stack version Key: AMBARI-17099 URL: https://issues.apache.org/jira/browse/AMBARI-17099 Project: Ambari Issue Type: Task Reporter: Siddharth Seth Fix For: 2.4.0 This needs some additional settings. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17097) Unable to uncheck Ranger Tagsync in Add Service wizard
[
https://issues.apache.org/jira/browse/AMBARI-17097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319286#comment-15319286
]
Hadoop QA commented on AMBARI-17097:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12808688/AMBARI-17097.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/7231//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7231//console
This message is automatically generated.
> Unable to uncheck Ranger Tagsync in Add Service wizard
> --
>
> Key: AMBARI-17097
> URL: https://issues.apache.org/jira/browse/AMBARI-17097
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-17097.patch
>
>
> If we install Ranger without Ranger Tagsync components, then during running
> Add Service wizard on Assign Slaves and Clients page user sees checked
> checkbox and is unable to uncheck it. Actually it should not be checked, as
> we do not have installed Tagsyncs. And it is expected, that it is disabled,
> as in Add Service wizard we can select slaves only for service, that is going
> to be installed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-14887) Atlas Integration : Fix Atlas-Kafka properties for Blueprints
[
https://issues.apache.org/jira/browse/AMBARI-14887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Beerbower updated AMBARI-14887:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Atlas Integration : Fix Atlas-Kafka properties for Blueprints
> -
>
> Key: AMBARI-14887
> URL: https://issues.apache.org/jira/browse/AMBARI-14887
> Project: Ambari
> Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
>
> The mechanism of setting the topology related properties(kafka and zk) in the
> agent will result in issues with blueprint installs.
> Because each node in a blueprint provisioned cluster is provisioned
> independently of other nodes, the blueprint topology manager needs to block
> provisioning of all nodes until all hosts required for configuration topology
> resolution are known. This is determined in BlueprintConfigurationProcessor.
> Because these configurations are not registered with the blueprint
> configuration processor it is possible for the atlas host to be provisioned
> prior to the Kafka hosts being known which result in the failure of the agent
> to set these topology related properties.
> In BlueprintConfigurationProcessor you will need too register updaters for
> all of the topology related properties, in this case
> "atlas.kafka.bootstrap.servers" and "atlas.kafka.zookeeper.connect".
> For example:
> atlasPropsMap.put("atlas.kafka.bootstrap.servers", new
> MultipleHostTopologyUpdater("KAFKA_BROKER"));
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17031) Atlas Integration : Deploying HA Blueprint with Atlas does not work
[ https://issues.apache.org/jira/browse/AMBARI-17031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Beerbower updated AMBARI-17031: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Atlas Integration : Deploying HA Blueprint with Atlas does not work > --- > > Key: AMBARI-17031 > URL: https://issues.apache.org/jira/browse/AMBARI-17031 > Project: Ambari > Issue Type: Bug >Reporter: Tom Beerbower >Assignee: Tom Beerbower > > When deploying a blueprint that specified ha enabled > (atlas.server.ha.enabled=true), the atlas.server.address.id1, > atlas.server.address.id2 (etc) needs to be replaced with the hostnames for > the host group. This does not occur today, instead the > atlas.server.address.id1 is tokenized with (for example): > atlas.server.host.id1: "server_hosts", which is not quite correct. I believe > the blueprint runtime generator needs to create the proper entries with a > different token that is replaced with each host where Atlas server is > deployed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17088) Zeppelin service: Update default zeppelin_pid_dir to /var/run/zeppelin
[
https://issues.apache.org/jira/browse/AMBARI-17088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319250#comment-15319250
]
Hadoop QA commented on AMBARI-17088:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12808651/AMBARI-17088_trunk%2Bbranch-2.4.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/7229//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7229//console
This message is automatically generated.
> Zeppelin service: Update default zeppelin_pid_dir to /var/run/zeppelin
> --
>
> Key: AMBARI-17088
> URL: https://issues.apache.org/jira/browse/AMBARI-17088
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: ambari-2.4.0
>Reporter: Renjith Kamath
>Assignee: Renjith Kamath
> Fix For: ambari-2.4.0
>
> Attachments: AMBARI-17088_trunk+branch-2.4.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17098) Atlas Integration : Ambari overwrites users-credentials.properties and policy-store.txt
[ https://issues.apache.org/jira/browse/AMBARI-17098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Beerbower updated AMBARI-17098: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Atlas Integration : Ambari overwrites users-credentials.properties and > policy-store.txt > --- > > Key: AMBARI-17098 > URL: https://issues.apache.org/jira/browse/AMBARI-17098 > Project: Ambari > Issue Type: Bug >Reporter: Tom Beerbower >Assignee: Tom Beerbower > > The Atlas users-credentials.properties and policy-store.txt are managed by > Ambari but can not be changed. Ambari overwrites any changes when the Atlas > server is restarted. > Make the files un-managed by Ambari so that they can be edited and will pick > up the latest changes from the Atlas distro on installation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17096) Pause Upgrade does not work correctly first time at 'Finalize Upgrade pre-check' step
[
https://issues.apache.org/jira/browse/AMBARI-17096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319217#comment-15319217
]
Hadoop QA commented on AMBARI-17096:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12808679/AMBARI-17096.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/7228//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7228//console
This message is automatically generated.
> Pause Upgrade does not work correctly first time at 'Finalize Upgrade
> pre-check' step
> -
>
> Key: AMBARI-17096
> URL: https://issues.apache.org/jira/browse/AMBARI-17096
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17096.patch, e2.png
>
>
> *Steps*
> # Tried EU from HDP 2.4.2.0 to 2.5.x
> # EU ran into failures
> # At finalize Upgrade Pre-check screen - hit Pause Upgrade
> # EU wizard disappears and UI shows "Action required" icon
> # Click on the icon and EU wizard opens again with options to 'Pause Upgrade'
> again
> # This time when I pause, the upgrade is correctly paused
> Screenshots attached for reference
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (AMBARI-17040) Update tez-interactive-site for HDP stack 2.5
[ https://issues.apache.org/jira/browse/AMBARI-17040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar reassigned AMBARI-17040: Assignee: Swapan Shridhar > Update tez-interactive-site for HDP stack 2.5 > - > > Key: AMBARI-17040 > URL: https://issues.apache.org/jira/browse/AMBARI-17040 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth >Assignee: Swapan Shridhar > Attachments: AMBARI-17040.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-17040) Update tez-interactive-site for HDP stack 2.5
[ https://issues.apache.org/jira/browse/AMBARI-17040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar resolved AMBARI-17040. -- Resolution: Fixed > Update tez-interactive-site for HDP stack 2.5 > - > > Key: AMBARI-17040 > URL: https://issues.apache.org/jira/browse/AMBARI-17040 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth > Attachments: AMBARI-17040.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17040) Update tez-interactive-site for HDP stack 2.5
[
https://issues.apache.org/jira/browse/AMBARI-17040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319207#comment-15319207
]
Swapan Shridhar commented on AMBARI-17040:
--
Commits :
trunk:
{code}
commit 8edd1869e89eb783c9349078031740f7e90ea80f
Author: Swapan Shridhar
Date: Tue Jun 7 12:38:26 2016 -0700
AMBARI-17040. Update tez-interactive-site for HDP stack 2.5. (Siddharth
Seth via Swapan Shridhar).
{code}
branch-2.4:
{code}
commit d81fce8dfcf2d8a31a45b365602e98a851065851
Author: Swapan Shridhar
Date: Tue Jun 7 12:40:21 2016 -0700
AMBARI-17040. Update tez-interactive-site for HDP stack 2.5. (Siddharth
Seth via Swapan Shridhar).
{code}
> Update tez-interactive-site for HDP stack 2.5
> -
>
> Key: AMBARI-17040
> URL: https://issues.apache.org/jira/browse/AMBARI-17040
> Project: Ambari
> Issue Type: Task
>Reporter: Siddharth Seth
> Attachments: AMBARI-17040.01.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17091) Add spinner to Assign master view
[
https://issues.apache.org/jira/browse/AMBARI-17091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319185#comment-15319185
]
Hadoop QA commented on AMBARI-17091:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12808666/AMBARI-17091.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/7225//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7225//console
This message is automatically generated.
> Add spinner to Assign master view
> --
>
> Key: AMBARI-17091
> URL: https://issues.apache.org/jira/browse/AMBARI-17091
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-17091.patch
>
>
> Assign Master view on all wizards and while enabling interactive query should
> show a spinner in place of missing section until content on the page are
> loaded.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17090) Next and Back buttons in Ambari UI install wizard should follow common patterns
[
https://issues.apache.org/jira/browse/AMBARI-17090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319162#comment-15319162
]
Hadoop QA commented on AMBARI-17090:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12808665/AMBARI-17090.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/7224//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7224//console
This message is automatically generated.
> Next and Back buttons in Ambari UI install wizard should follow common
> patterns
> ---
>
> Key: AMBARI-17090
> URL: https://issues.apache.org/jira/browse/AMBARI-17090
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-17090.patch
>
>
> Next and Back buttons in Ambari UI install wizard should follow common
> patterns to keep the UI automation maintenance simpler.
> Discrepancy:
> 1. Next buttons in Get Started, Stack Selection, Confirm Hosts, Choose
> Service,Assign Slave,Customize service,Review,Install page are
> 2. Next button in Host Registration,Assign Masters, page are
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17051) Falcon startup properties changes for 2.5
[ https://issues.apache.org/jira/browse/AMBARI-17051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Ranganathan updated AMBARI-17051: Attachment: AMBARI-17051-2.patch > Falcon startup properties changes for 2.5 > - > > Key: AMBARI-17051 > URL: https://issues.apache.org/jira/browse/AMBARI-17051 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan > Attachments: AMBARI-17051-2.patch, AMBARI-17051.patch > > > We need to add extension service, information on extension and lifecycle > policy changes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17043) Fix description of SERVICE.ADD_DELETE_SERVICES permission
[
https://issues.apache.org/jira/browse/AMBARI-17043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-17043:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit c85d0d15e5c015a069c888c25583e7bfe767acd8
Author: Robert Levas
Date: Tue Jun 7 15:07:59 2016 -0400
{noformat}
Committed to branch-2.4
{noformat}
HW10868:ambari rlevas$ git show
commit 8ae8d0bece67ed34fbf898cb9182d20cb3755ad8
Author: Robert Levas
Date: Tue Jun 7 15:08:49 2016 -0400
{noformat}
> Fix description of SERVICE.ADD_DELETE_SERVICES permission
> -
>
> Key: AMBARI-17043
> URL: https://issues.apache.org/jira/browse/AMBARI-17043
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.3.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: rbac
> Fix For: 2.4.0
>
> Attachments: AMBARI-17043_branch-2.4_01.patch,
> AMBARI-17043_trunk_01.patch
>
>
> The description of the SERVICE.ADD_DELETE_SERVICES permission currently reads
> {quote}
> Add Service to cluster
> {quote}
> This should be changed to
> {quote}
> Add/delete services
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17063) Retrieve specific metrics when Ambari queries NameNode HA states
[
https://issues.apache.org/jira/browse/AMBARI-17063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319124#comment-15319124
]
Hadoop QA commented on AMBARI-17063:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12808658/AMBARI-17063.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7223//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7223//console
This message is automatically generated.
> Retrieve specific metrics when Ambari queries NameNode HA states
>
>
> Key: AMBARI-17063
> URL: https://issues.apache.org/jira/browse/AMBARI-17063
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17063.patch
>
>
> This is a follow-on jira of BUG-53459: when Ambari queries NameNode's HA
> states, currently it retrieves a group of metrics including some unnecessary
> ones that may compete for NameNode lock. It would be better for Ambari to only
> retrieve HA state metrics from NameNode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17077) Unable to change user role in list view
[
https://issues.apache.org/jira/browse/AMBARI-17077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zang updated AMBARI-17077:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and 2.4 9e15b2b652be4097e61b104bccea310b0e23196a
> Unable to change user role in list view
> ---
>
> Key: AMBARI-17077
> URL: https://issues.apache.org/jira/browse/AMBARI-17077
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: 2.4.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17077.patch
>
>
> STR:
> 1. Go to Manage Ambari.
> 2. Create user.
> 3. Go to Roles menu, list view.
> 4. Set role for newly created user.
> 5. Change role for that user.
> {noformat}Cannot save permissions
> t's effective privilege through its Group(s) is higher than your selected
> privilege.{noformat}
> No goups was created.
> Workaround: change role to None and then change to desired value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17071) VDF: exception when trying to register -> add versions
[ https://issues.apache.org/jira/browse/AMBARI-17071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319083#comment-15319083 ] Hudson commented on AMBARI-17071: - FAILURE: Integrated in Ambari-trunk-Commit #5022 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5022/]) AMBARI-17071. VDF: exception when trying to register -> add versions (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8098350a43c3006825ee12bd8944bd9465196eed]) * ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProvider.java * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProviderTest.java > VDF: exception when trying to register -> add versions > -- > > Key: AMBARI-17071 > URL: https://issues.apache.org/jira/browse/AMBARI-17071 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17071.patch > > > # Start install wizard, select HDP-2.4, Add Version -> use 2.4.0.0 VDF > # Click local, click Satellite, confirm, next to move on > # HDFS + ZK + AMS, install > # all is fine so far > # go to Register version > # click on HDP 2.4 -> add version-> use 2.4.2.0 VDF, which uses the same url > as (1) > # Click local, click Satellite, confirm, click save, EXCEPTION -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17082) Ambari server failed to start METRICS_COLLECTOR via BP
[
https://issues.apache.org/jira/browse/AMBARI-17082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319082#comment-15319082
]
Hudson commented on AMBARI-17082:
-
FAILURE: Integrated in Ambari-trunk-Commit #5022 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5022/])
AMBARI-17082 Ambari server failed to start METRICS_COLLECTOR via BP (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=db7f25505349c3a12688fc893676f84c3d7c4d59])
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
> Ambari server failed to start METRICS_COLLECTOR via BP
> --
>
> Key: AMBARI-17082
> URL: https://issues.apache.org/jira/browse/AMBARI-17082
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17082_2-trunk.patch
>
>
> If blueprint contains 2 AMS collectors, Ambari server failed to start
> METRICS_COLLECTOR with
> {code}
> 03 Jun 2016 04:18:49,545 ERROR [pool-16-thread-1] TopologyManager:782 -
> TopologyManager.ConfigureClusterTask: An exception occurred while attempting
> to process cluster configs and set on cluster:
> java.lang.IllegalArgumentException: Unable to update configuration property
> 'timeline.metrics.service.webapp.address' with topology information.
> Component 'METRICS_COLLECTOR' is mapped to an invalid number of hosts '2'.
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$SingleHostTopologyUpdater.updateForClusterCreate(BlueprintConfigurationProcessor.java:1350)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$6.updateForClusterCreate(BlueprintConfigurationProcessor.java:2630)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForClusterCreate(BlueprintConfigurationProcessor.java:271)
> at
> org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:153)
> at
> org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:780)
> at
> org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:754)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> 03 Jun 2016 04:18:49,553 INFO [pool-3-thread-1] AsyncCallableService:111 -
> Exception during task execution:
> java.util.concurrent.ExecutionException: java.lang.Exception:
> java.lang.IllegalArgumentException: Unable to update configuration property
> 'timeline.metrics.service.webapp.address' with topology information.
> Component 'METRICS_COLLECTOR' is mapped to an invalid number of hosts '2'.
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:202)
> at
> org.apache.ambari.server.topology.AsyncCallableService.taskCompleted(AsyncCallableService.java:103)
> at
> org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:74)
> at
> org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:37)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-10908) Usability: ability to perform bulk delete host
[ https://issues.apache.org/jira/browse/AMBARI-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-10908: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk bd58a5038032445831996a33ae52a08f387a2335 > Usability: ability to perform bulk delete host > -- > > Key: AMBARI-10908 > URL: https://issues.apache.org/jira/browse/AMBARI-10908 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Jeff Sposetti >Assignee: Zhe (Joe) Wang > Fix For: 3.0.0 > > Attachments: AMBARI-10908.v0.patch, AMBARI-10908.v1.patch > > > On Hosts page, provide ability to delete hosts in bulk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17076) Hive view 2.0.0 Instance has issues connecting to database in secure mode
[ https://issues.apache.org/jira/browse/AMBARI-17076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-17076: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2.4. > Hive view 2.0.0 Instance has issues connecting to database in secure mode > - > > Key: AMBARI-17076 > URL: https://issues.apache.org/jira/browse/AMBARI-17076 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.0 > > Attachments: AMBARI-17076.trunk.2.patch, AMBARI-17076.trunk.4.patch, > AMBARI-17076.trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-13979) Host action menu should be extensible by services
[ https://issues.apache.org/jira/browse/AMBARI-13979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj resolved AMBARI-13979. --- Resolution: Duplicate Based on the fix for Ambari-15443, now the services can be added to host level actions menu, this will require making changes in the metainfo.xml > Host action menu should be extensible by services > - > > Key: AMBARI-13979 > URL: https://issues.apache.org/jira/browse/AMBARI-13979 > Project: Ambari > Issue Type: Improvement > Components: ambari-views >Affects Versions: 2.1.0 >Reporter: Tuong Truong > Labels: extensibility > > Currently, in host view, the "Actions" menu items are hard coded for > specific services. Services should be able to add their own action into > this menu. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16017) Update Moment.js to latest stable version 2.13.0
[ https://issues.apache.org/jira/browse/AMBARI-16017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-16017: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Update Moment.js to latest stable version 2.13.0 > > > Key: AMBARI-16017 > URL: https://issues.apache.org/jira/browse/AMBARI-16017 > Project: Ambari > Issue Type: Task > Components: ambari-views, ambari-web >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Labels: patch > Fix For: trunk > > Attachments: AMBARI-16017_0602.patch > > > The latest stable version of Moment.js is 2.13.0. > This task is for updating the version of Moment.js used in > contrib/views/slider/src/main/resources/ui/vendor/scripts/common/ > ambari-web/vendor/scripts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
