[jira] [Commented] (AMBARI-17396) Performance issues with ambari metrics (and Metrics Collector keeps going down)
[ https://issues.apache.org/jira/browse/AMBARI-17396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347757#comment-15347757 ] Dmytro Sen commented on AMBARI-17396: - Test failures aren't related to this patch. > Performance issues with ambari metrics (and Metrics Collector keeps going > down) > --- > > Key: AMBARI-17396 > URL: https://issues.apache.org/jira/browse/AMBARI-17396 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17396_1.patch > > > Metrics widgets are taking a long time to load. Dashboard page widgets take > nearly 30 secs to completely load. > Even after progress bar indicator is stopped, it takes a couple of > secs(15-20) for actual data to show up. Attaching the screenshot. > Same kind of delay is observed in service as well as host widgets. > AMS periodically crashes with SQLTimeoutException or CallTimeoutException -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-17392) Add llap-*log4j config dependency for hive server interactive component
[ https://issues.apache.org/jira/browse/AMBARI-17392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajit Kumar resolved AMBARI-17392. - Resolution: Fixed Push to trunk and branch-2.4 > Add llap-*log4j config dependency for hive server interactive component > --- > > Key: AMBARI-17392 > URL: https://issues.apache.org/jira/browse/AMBARI-17392 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Ajit Kumar >Assignee: Ajit Kumar > Fix For: 2.4.0 > > Attachments: rb49134.patch > > > Add llap-*log4j config dependency for hive server interactive component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17392) Add llap-*log4j config dependency for hive server interactive component
[ https://issues.apache.org/jira/browse/AMBARI-17392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajit Kumar updated AMBARI-17392: Attachment: rb49134.patch > Add llap-*log4j config dependency for hive server interactive component > --- > > Key: AMBARI-17392 > URL: https://issues.apache.org/jira/browse/AMBARI-17392 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Ajit Kumar >Assignee: Ajit Kumar > Fix For: 2.4.0 > > Attachments: rb49134.patch > > > Add llap-*log4j config dependency for hive server interactive component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17418) Fix for LLAP calculation to happen on invocation by Blueprints and HIVE SERVER INTERACTIVE is ON (1st invocation to Stack Advisor). Also, reverts AMBARI-17283.
Swapan Shridhar created AMBARI-17418: Summary: Fix for LLAP calculation to happen on invocation by Blueprints and HIVE SERVER INTERACTIVE is ON (1st invocation to Stack Advisor). Also, reverts AMBARI-17283. Key: AMBARI-17418 URL: https://issues.apache.org/jira/browse/AMBARI-17418 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Swapan Shridhar Assignee: Swapan Shridhar Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17186) Tez View: Improve proxy logging
[ https://issues.apache.org/jira/browse/AMBARI-17186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated AMBARI-17186: Attachment: AMBARI-17186.7.patch Corrected white-spaces in the exception message. > Tez View: Improve proxy logging > --- > > Key: AMBARI-17186 > URL: https://issues.apache.org/jira/browse/AMBARI-17186 > Project: Ambari > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17186.1.patch, AMBARI-17186.2.patch, > AMBARI-17186.3.patch, AMBARI-17186.4.patch, AMBARI-17186.5.patch, > AMBARI-17186.6.patch, AMBARI-17186.7.patch > > > More log messages would help us to debug EARs faster. > # Add error log when configuration fetch fails. > # Add debug log when request proxying / redirection succeed > # Add error log when request proxying / redirection fails > With effect from AMBARI-14084, each view would have separate log file. > - For Tez view that is /var/log/ambari-server/tez-view/tez-view.log. > - Debug log would be logged only when the debug mode is enabled. (Set > log4j.logger.org.apache.ambari.view.tez=DEBUG,tezView in > view.log4j.properties for the same) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-10982) Ambari support for NameNode Federation
[ https://issues.apache.org/jira/browse/AMBARI-10982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347665#comment-15347665 ] Masahiro Tanaka commented on AMBARI-10982: -- Any updates on this? > Ambari support for NameNode Federation > -- > > Key: AMBARI-10982 > URL: https://issues.apache.org/jira/browse/AMBARI-10982 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.0.0 >Reporter: Jeff Sposetti > Labels: hdp > > Ambari needs to be able to deploy, manage and monitor HDFS Federation - with > 2 or more Federated namespaces. > *Hdfs configuration* > Each hdfs federated namespace has a namenode, and for each namespace namenode > ha can be set up - allowing for multiple journal nodes and active/standby > namenode for the namespace. When kerberizing, managing (start/stop/configure) > , and monitoring, each namenode needs to be treated as a separate master. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17383) User names should be case insensitive
[ https://issues.apache.org/jira/browse/AMBARI-17383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17383: --- Status: Patch Available (was: Open) > User names should be case insensitive > - > > Key: AMBARI-17383 > URL: https://issues.apache.org/jira/browse/AMBARI-17383 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram >Priority: Critical > Fix For: 2.4.0 > > Attachments: rb49119 (1).patch > > > User names should be case insensitive. The following usernames are the same: > VIEWUSER > viewUser > viewuser > Before adding a new user, a case sensitive search is made. Change this to > case insensitive. Additionally, store user names in the DB in lower case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17383) User names should be case insensitive
[ https://issues.apache.org/jira/browse/AMBARI-17383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17383: --- Attachment: rb49119 (1).patch > User names should be case insensitive > - > > Key: AMBARI-17383 > URL: https://issues.apache.org/jira/browse/AMBARI-17383 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram >Priority: Critical > Fix For: 2.4.0 > > Attachments: rb49119 (1).patch > > > User names should be case insensitive. The following usernames are the same: > VIEWUSER > viewUser > viewuser > Before adding a new user, a case sensitive search is made. Change this to > case insensitive. Additionally, store user names in the DB in lower case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17383) User names should be case insensitive
[ https://issues.apache.org/jira/browse/AMBARI-17383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17383: --- Attachment: (was: rb49119.patch) > User names should be case insensitive > - > > Key: AMBARI-17383 > URL: https://issues.apache.org/jira/browse/AMBARI-17383 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram >Priority: Critical > Fix For: 2.4.0 > > Attachments: rb49119 (1).patch > > > User names should be case insensitive. The following usernames are the same: > VIEWUSER > viewUser > viewuser > Before adding a new user, a case sensitive search is made. Change this to > case insensitive. Additionally, store user names in the DB in lower case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17409) Ranger has error count while adding Ranger KMS
[ https://issues.apache.org/jira/browse/AMBARI-17409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347539#comment-15347539 ] Hudson commented on AMBARI-17409: - FAILURE: Integrated in Ambari-trunk-Commit #5150 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5150/]) AMBARI-17409. Ranger has error count while adding Ranger KMS (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=485a69dd80aaa21338552e2aaab7b4b42a013e73]) * ambari-web/app/models/configs/objects/service_config.js > Ranger has error count while adding Ranger KMS > -- > > Key: AMBARI-17409 > URL: https://issues.apache.org/jira/browse/AMBARI-17409 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-17409.patch, Screen Shot 2016-06-23 at 2.00.20 > PM.png > > > Go to add service on cluster with installer ranger, add RAnger KMS > Go to customize service page > Expected: > No error counts on installed services > Actual > Ranger has 1 error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17416) AMS-Grafana: show 'alias' when there's no datapoint available
[ https://issues.apache.org/jira/browse/AMBARI-17416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated AMBARI-17416: -- Attachment: AMBARI-17416-v1.patch Attaching patch. It is a tiny patch so I think it will pass the review process unless there's specific intention to not using alias. > AMS-Grafana: show 'alias' when there's no datapoint available > - > > Key: AMBARI-17416 > URL: https://issues.apache.org/jira/browse/AMBARI-17416 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim >Priority: Minor > Attachments: AMBARI-17416-v1.patch > > > When there's no datapoint available, AMS Grafana plugin just ignores alias > and shows metric name instead. It seems to be not consistent in point of > view, and not good UX I think. > It'd be great AMS Grafana shows alias whenever there're datapoints available > or not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17416) AMS-Grafana: show 'alias' when there's no datapoint available
[ https://issues.apache.org/jira/browse/AMBARI-17416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated AMBARI-17416: -- Status: Patch Available (was: Open) > AMS-Grafana: show 'alias' when there's no datapoint available > - > > Key: AMBARI-17416 > URL: https://issues.apache.org/jira/browse/AMBARI-17416 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim >Priority: Minor > Attachments: AMBARI-17416-v1.patch > > > When there's no datapoint available, AMS Grafana plugin just ignores alias > and shows metric name instead. It seems to be not consistent in point of > view, and not good UX I think. > It'd be great AMS Grafana shows alias whenever there're datapoints available > or not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17416) AMS-Grafana: show 'alias' when there's no datapoint available
Jungtaek Lim created AMBARI-17416: - Summary: AMS-Grafana: show 'alias' when there's no datapoint available Key: AMBARI-17416 URL: https://issues.apache.org/jira/browse/AMBARI-17416 Project: Ambari Issue Type: Improvement Components: ambari-metrics Affects Versions: 2.4.0 Reporter: Jungtaek Lim Priority: Minor When there's no datapoint available, AMS Grafana plugin just ignores alias and shows metric name instead. It seems to be not consistent in point of view, and not good UX I think. It'd be great AMS Grafana shows alias whenever there're datapoints available or not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17415) Ambari configuration for ranger-tagsync needs to support property for atlas keystore filename
Abhay Kulkarni created AMBARI-17415: --- Summary: Ambari configuration for ranger-tagsync needs to support property for atlas keystore filename Key: AMBARI-17415 URL: https://issues.apache.org/jira/browse/AMBARI-17415 Project: Ambari Issue Type: Bug Affects Versions: 2.4.0 Reporter: Abhay Kulkarni Fix For: 2.4.0 Ranger-Tagsync configuration with Ambari needs to : 1. Provide reasonable defaults for Atlas Endpoint (from Atlas URL) and Atlas-source-download-interval (6) when Atlasrest is selected as tag-source. 2. Support property ranger.tagsync.source.atlasrest.keystore.filename in the Advanced ranger-tagsync-site tab with default value of /usr/hdp/current/ranger-tagsync/conf/atlasuser.jceks. Without this property, updatetagadminpassword.py script fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17414) Inconsistent behavior of Spark thrift server and Livy server in Summary page
Yesha Vora created AMBARI-17414: --- Summary: Inconsistent behavior of Spark thrift server and Livy server in Summary page Key: AMBARI-17414 URL: https://issues.apache.org/jira/browse/AMBARI-17414 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Yesha Vora Steps to reproduce: * Install Spark1 (Install with Spark-thriftserver and do not Install Livy server) * Install Spark2 (Do not install spark-thriftserver) In spark1, Livy server is not installed. In spark1 summary tab, ambari shows spark-client, spark-history-server and spark-thrift server In spark2, spark-thriftserver is not installed. But ambari shows spark-thriftserver on summary tab. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17410) Incorrect error message for invalid category in Host Combo Search Box
[
https://issues.apache.org/jira/browse/AMBARI-17410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347403#comment-15347403
]
Hadoop QA commented on AMBARI-17410:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12812938/ErrorMessageWithFix.jpg
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7523//console
This message is automatically generated.
> Incorrect error message for invalid category in Host Combo Search Box
> -
>
> Key: AMBARI-17410
> URL: https://issues.apache.org/jira/browse/AMBARI-17410
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: trunk
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-17410.patch, ErrorMessage.jpg,
> ErrorMessageWithFix.jpg
>
>
> 1. In the host combo box, if an invalid category is entered, an error is
> displayed
> [object Object] is not a valid category.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17186) Tez View: Improve proxy logging
[
https://issues.apache.org/jira/browse/AMBARI-17186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347400#comment-15347400
]
Hadoop QA commented on AMBARI-17186:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12812944/AMBARI-17186.6.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
contrib/views/tez.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7522//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7522//console
This message is automatically generated.
> Tez View: Improve proxy logging
> ---
>
> Key: AMBARI-17186
> URL: https://issues.apache.org/jira/browse/AMBARI-17186
> Project: Ambari
> Issue Type: Bug
>Reporter: Sreenath Somarajapuram
>Assignee: Sreenath Somarajapuram
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17186.1.patch, AMBARI-17186.2.patch,
> AMBARI-17186.3.patch, AMBARI-17186.4.patch, AMBARI-17186.5.patch,
> AMBARI-17186.6.patch
>
>
> More log messages would help us to debug EARs faster.
> # Add error log when configuration fetch fails.
> # Add debug log when request proxying / redirection succeed
> # Add error log when request proxying / redirection fails
> With effect from AMBARI-14084, each view would have separate log file.
> - For Tez view that is /var/log/ambari-server/tez-view/tez-view.log.
> - Debug log would be logged only when the debug mode is enabled. (Set
> log4j.logger.org.apache.ambari.view.tez=DEBUG,tezView in
> view.log4j.properties for the same)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-17413) Spark2 History server QuickLink redirects to wrong port
[ https://issues.apache.org/jira/browse/AMBARI-17413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yesha Vora resolved AMBARI-17413. - Resolution: Duplicate > Spark2 History server QuickLink redirects to wrong port > --- > > Key: AMBARI-17413 > URL: https://issues.apache.org/jira/browse/AMBARI-17413 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Yesha Vora > > Steps to reproduce: > * Install spark1 and spark2 > * Click on spark2 component > * Click on "Quick Links" tab, it will hover "Spark2 History server UI" > * Click on Spark2 History server UI > Spark2 history server Quick Link redirects to wrong ui. > Expected url : http://: > Actual url : http://: > The Quick link for Spark2 History server is using spark1 history server port > instead spark2 history server port. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17382) Migrate AMS queries to use ROW_TIMESTAMP instead of native timerange hint
[
https://issues.apache.org/jira/browse/AMBARI-17382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347382#comment-15347382
]
Hadoop QA commented on AMBARI-17382:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12812953/AMBARI-17382.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 patch failed these unit tests in
ambari-metrics/ambari-metrics-timelineservice:
org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.discovery.TestMetadataManager
org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.availability.MetricCollectorHAControllerTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7521//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7521//console
This message is automatically generated.
> Migrate AMS queries to use ROW_TIMESTAMP instead of native timerange hint
> -
>
> Key: AMBARI-17382
> URL: https://issues.apache.org/jira/browse/AMBARI-17382
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Labels: ambari-metrics
> Fix For: 2.4.0
>
> Attachments: AMBARI-17382.patch
>
>
> With PHOENIX-914, there is a change in implementation , As earlier, timestamp
> range was passed as a hint to the query to get advantage of native timerange
> optimization in hbase but with new implementation we can mark the timestamp
> column in the schema as a ROW_TIMESTAMP and pass timestamp range with “where”
> clause only to achieve equivalent performance and better accuracy.
> For eq:-
> With earlier implementation , AMS forms query like this:-
> SELECT /*+ NATIVE_TIME_RANGE(1448029523000) */ METRIC_NAME, APP_ID,
> INSTANCE_ID, SERVER_TIME, UNITS, METRIC_SUM, HOSTS_COUNT, METRIC_MAX,
> METRIC_MIN FROM METRIC_AGGREGATE WHERE (METRIC_NAME IN
> ('regionserver.Server.totalRequestCount',
> 'regionserver.Server.blockCacheCountHitPercent',
> 'regionserver.Server.regionCount',
> 'regionserver.Server.compactionQueueLength',
> 'regionserver.Server.storeFileCount', 'master.Server.averageLoad')) AND
> APP_ID = 'ams-hbase' AND SERVER_TIME >= 1448029643000 AND SERVER_TIME <
> 1448033243 ORDER BY METRIC_NAME, SERVER_TIME LIMIT 11520
> But with PHOENIX-914 :-
> Declare SERVER_TIME as ROW_TIMESTAMP in schema:-
> CREATE TABLE DESTINATION_METRICS_TABLE (SERVER_TIME DATE not null, METRIC_ID
> CHAR(15) not null, METRIC_VALUE bigint … CONSTRAINT PK PRIMARY
> KEY(CREATED_DATE ROW_TIMESTAMP, METRIC_ID…)) …;
> And remove hint from the query:-
> SELECT METRIC_NAME, APP_ID, INSTANCE_ID, SERVER_TIME, UNITS, METRIC_SUM,
> HOSTS_COUNT, METRIC_MAX, METRIC_MIN FROM METRIC_AGGREGATE WHERE (METRIC_NAME
> IN ('regionserver.Server.totalRequestCount',
> 'regionserver.Server.blockCacheCountHitPercent',
> 'regionserver.Server.regionCount',
> 'regionserver.Server.compactionQueueLength',
> 'regionserver.Server.storeFileCount', 'master.Server.averageLoad')) AND
> APP_ID = 'ams-hbase' AND SERVER_TIME >= 1448029643000 AND SERVER_TIME <
> 1448033243 ORDER BY METRIC_NAME, SERVER_TIME LIMIT 11520
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17413) Spark2 History server QuickLink redirects to wrong port
Yesha Vora created AMBARI-17413: --- Summary: Spark2 History server QuickLink redirects to wrong port Key: AMBARI-17413 URL: https://issues.apache.org/jira/browse/AMBARI-17413 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Yesha Vora Steps to reproduce: * Install spark1 and spark2 * Click on spark2 component * Click on "Quick Links" tab, it will hover "Spark2 History server UI" * Click on Spark2 History server UI Spark2 history server Quick Link redirects to wrong ui. Expected url : http://: Actual url : http://: The Quick link for Spark2 History server is using spark1 history server port instead spark2 history server port. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17412) Add service wizard page fails to load correctly if its open in new browser window
[ https://issues.apache.org/jira/browse/AMBARI-17412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yesha Vora updated AMBARI-17412: Attachment: Screen Shot 2016-06-23 at 2.57.42 PM.png > Add service wizard page fails to load correctly if its open in new browser > window > - > > Key: AMBARI-17412 > URL: https://issues.apache.org/jira/browse/AMBARI-17412 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Yesha Vora > Attachments: Screen Shot 2016-06-23 at 2.57.42 PM.png > > > Steps to reproduce. > * open ambari ui in chrome. > * to add services and choose spark2 for installation > * Finish step1 and step2 ( Choose service and assign master. ) > * Step3 is Assign slaves and clients. Go to Step3 > (http://xx.xx.xx.xx:8080/#/main/service/add/step3) > At this stage, open new browser (ex: safari ) > * copy http://xx.xx.xx.xx:8080/#/main/service/add/step3 in browser > * It will redirect to login page. > * After logging in, ambari is redirected to > http://xx.xx.xx.xx:8080/#/main/service/add/step3 > At this point page fails to load completely. Find ui errors in attached > screenshots. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17412) Add service wizard page fails to load correctly if its open in new browser window
Yesha Vora created AMBARI-17412: --- Summary: Add service wizard page fails to load correctly if its open in new browser window Key: AMBARI-17412 URL: https://issues.apache.org/jira/browse/AMBARI-17412 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Yesha Vora Steps to reproduce. * open ambari ui in chrome. * to add services and choose spark2 for installation * Finish step1 and step2 ( Choose service and assign master. ) * Step3 is Assign slaves and clients. Go to Step3 (http://xx.xx.xx.xx:8080/#/main/service/add/step3) At this stage, open new browser (ex: safari ) * copy http://xx.xx.xx.xx:8080/#/main/service/add/step3 in browser * It will redirect to login page. * After logging in, ambari is redirected to http://xx.xx.xx.xx:8080/#/main/service/add/step3 At this point page fails to load completely. Find ui errors in attached screenshots. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17382) Migrate AMS queries to use ROW_TIMESTAMP instead of native timerange hint
[
https://issues.apache.org/jira/browse/AMBARI-17382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-17382:
---
Attachment: AMBARI-17382.patch
> Migrate AMS queries to use ROW_TIMESTAMP instead of native timerange hint
> -
>
> Key: AMBARI-17382
> URL: https://issues.apache.org/jira/browse/AMBARI-17382
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Labels: ambari-metrics
> Fix For: 2.4.0
>
> Attachments: AMBARI-17382.patch
>
>
> With PHOENIX-914, there is a change in implementation , As earlier, timestamp
> range was passed as a hint to the query to get advantage of native timerange
> optimization in hbase but with new implementation we can mark the timestamp
> column in the schema as a ROW_TIMESTAMP and pass timestamp range with “where”
> clause only to achieve equivalent performance and better accuracy.
> For eq:-
> With earlier implementation , AMS forms query like this:-
> SELECT /*+ NATIVE_TIME_RANGE(1448029523000) */ METRIC_NAME, APP_ID,
> INSTANCE_ID, SERVER_TIME, UNITS, METRIC_SUM, HOSTS_COUNT, METRIC_MAX,
> METRIC_MIN FROM METRIC_AGGREGATE WHERE (METRIC_NAME IN
> ('regionserver.Server.totalRequestCount',
> 'regionserver.Server.blockCacheCountHitPercent',
> 'regionserver.Server.regionCount',
> 'regionserver.Server.compactionQueueLength',
> 'regionserver.Server.storeFileCount', 'master.Server.averageLoad')) AND
> APP_ID = 'ams-hbase' AND SERVER_TIME >= 1448029643000 AND SERVER_TIME <
> 1448033243 ORDER BY METRIC_NAME, SERVER_TIME LIMIT 11520
> But with PHOENIX-914 :-
> Declare SERVER_TIME as ROW_TIMESTAMP in schema:-
> CREATE TABLE DESTINATION_METRICS_TABLE (SERVER_TIME DATE not null, METRIC_ID
> CHAR(15) not null, METRIC_VALUE bigint … CONSTRAINT PK PRIMARY
> KEY(CREATED_DATE ROW_TIMESTAMP, METRIC_ID…)) …;
> And remove hint from the query:-
> SELECT METRIC_NAME, APP_ID, INSTANCE_ID, SERVER_TIME, UNITS, METRIC_SUM,
> HOSTS_COUNT, METRIC_MAX, METRIC_MIN FROM METRIC_AGGREGATE WHERE (METRIC_NAME
> IN ('regionserver.Server.totalRequestCount',
> 'regionserver.Server.blockCacheCountHitPercent',
> 'regionserver.Server.regionCount',
> 'regionserver.Server.compactionQueueLength',
> 'regionserver.Server.storeFileCount', 'master.Server.averageLoad')) AND
> APP_ID = 'ams-hbase' AND SERVER_TIME >= 1448029643000 AND SERVER_TIME <
> 1448033243 ORDER BY METRIC_NAME, SERVER_TIME LIMIT 11520
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17382) Migrate AMS queries to use ROW_TIMESTAMP instead of native timerange hint
[
https://issues.apache.org/jira/browse/AMBARI-17382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347303#comment-15347303
]
Aravindan Vijayan commented on AMBARI-17382:
The plan is to go ahead with support for both the old and the new phoenix
native timestamp support, and retire the native time range hint support in the
future in both Phoenix and AMS.
> Migrate AMS queries to use ROW_TIMESTAMP instead of native timerange hint
> -
>
> Key: AMBARI-17382
> URL: https://issues.apache.org/jira/browse/AMBARI-17382
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Labels: ambari-metrics
> Fix For: 2.4.0
>
> Attachments: AMBARI-17382.patch
>
>
> With PHOENIX-914, there is a change in implementation , As earlier, timestamp
> range was passed as a hint to the query to get advantage of native timerange
> optimization in hbase but with new implementation we can mark the timestamp
> column in the schema as a ROW_TIMESTAMP and pass timestamp range with “where”
> clause only to achieve equivalent performance and better accuracy.
> For eq:-
> With earlier implementation , AMS forms query like this:-
> SELECT /*+ NATIVE_TIME_RANGE(1448029523000) */ METRIC_NAME, APP_ID,
> INSTANCE_ID, SERVER_TIME, UNITS, METRIC_SUM, HOSTS_COUNT, METRIC_MAX,
> METRIC_MIN FROM METRIC_AGGREGATE WHERE (METRIC_NAME IN
> ('regionserver.Server.totalRequestCount',
> 'regionserver.Server.blockCacheCountHitPercent',
> 'regionserver.Server.regionCount',
> 'regionserver.Server.compactionQueueLength',
> 'regionserver.Server.storeFileCount', 'master.Server.averageLoad')) AND
> APP_ID = 'ams-hbase' AND SERVER_TIME >= 1448029643000 AND SERVER_TIME <
> 1448033243 ORDER BY METRIC_NAME, SERVER_TIME LIMIT 11520
> But with PHOENIX-914 :-
> Declare SERVER_TIME as ROW_TIMESTAMP in schema:-
> CREATE TABLE DESTINATION_METRICS_TABLE (SERVER_TIME DATE not null, METRIC_ID
> CHAR(15) not null, METRIC_VALUE bigint … CONSTRAINT PK PRIMARY
> KEY(CREATED_DATE ROW_TIMESTAMP, METRIC_ID…)) …;
> And remove hint from the query:-
> SELECT METRIC_NAME, APP_ID, INSTANCE_ID, SERVER_TIME, UNITS, METRIC_SUM,
> HOSTS_COUNT, METRIC_MAX, METRIC_MIN FROM METRIC_AGGREGATE WHERE (METRIC_NAME
> IN ('regionserver.Server.totalRequestCount',
> 'regionserver.Server.blockCacheCountHitPercent',
> 'regionserver.Server.regionCount',
> 'regionserver.Server.compactionQueueLength',
> 'regionserver.Server.storeFileCount', 'master.Server.averageLoad')) AND
> APP_ID = 'ams-hbase' AND SERVER_TIME >= 1448029643000 AND SERVER_TIME <
> 1448033243 ORDER BY METRIC_NAME, SERVER_TIME LIMIT 11520
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17382) Migrate AMS queries to use ROW_TIMESTAMP instead of native timerange hint
[
https://issues.apache.org/jira/browse/AMBARI-17382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-17382:
---
Description:
With PHOENIX-914, there is a change in implementation , As earlier, timestamp
range was passed as a hint to the query to get advantage of native timerange
optimization in hbase but with new implementation we can mark the timestamp
column in the schema as a ROW_TIMESTAMP and pass timestamp range with “where”
clause only to achieve equivalent performance and better accuracy.
For eq:-
With earlier implementation , AMS forms query like this:-
SELECT /*+ NATIVE_TIME_RANGE(1448029523000) */ METRIC_NAME, APP_ID,
INSTANCE_ID, SERVER_TIME, UNITS, METRIC_SUM, HOSTS_COUNT, METRIC_MAX,
METRIC_MIN FROM METRIC_AGGREGATE WHERE (METRIC_NAME IN
('regionserver.Server.totalRequestCount',
'regionserver.Server.blockCacheCountHitPercent',
'regionserver.Server.regionCount', 'regionserver.Server.compactionQueueLength',
'regionserver.Server.storeFileCount', 'master.Server.averageLoad')) AND APP_ID
= 'ams-hbase' AND SERVER_TIME >= 1448029643000 AND SERVER_TIME < 1448033243
ORDER BY METRIC_NAME, SERVER_TIME LIMIT 11520
But with PHOENIX-914 :-
Declare SERVER_TIME as ROW_TIMESTAMP in schema:-
CREATE TABLE DESTINATION_METRICS_TABLE (SERVER_TIME DATE not null, METRIC_ID
CHAR(15) not null, METRIC_VALUE bigint … CONSTRAINT PK PRIMARY KEY(CREATED_DATE
ROW_TIMESTAMP, METRIC_ID…)) …;
And remove hint from the query:-
SELECT METRIC_NAME, APP_ID, INSTANCE_ID, SERVER_TIME, UNITS, METRIC_SUM,
HOSTS_COUNT, METRIC_MAX, METRIC_MIN FROM METRIC_AGGREGATE WHERE (METRIC_NAME IN
('regionserver.Server.totalRequestCount',
'regionserver.Server.blockCacheCountHitPercent',
'regionserver.Server.regionCount', 'regionserver.Server.compactionQueueLength',
'regionserver.Server.storeFileCount', 'master.Server.averageLoad')) AND APP_ID
= 'ams-hbase' AND SERVER_TIME >= 1448029643000 AND SERVER_TIME < 1448033243
ORDER BY METRIC_NAME, SERVER_TIME LIMIT 11520
was:
With PHOENIX-914, there is a change in implementation , As earlier, timestamp
range was passed as a hint to the query to get advantage of native timerange
optimization in hbase but with new implementation we can mark the timestamp
column in the schema as a ROW_TIMESTAMP and pass timestamp range with “where”
clause only to achieve equivalent performance and better accuracy.
For eq:-
With earlier implementation , AMS forms query like this:-
SELECT /*+ NATIVE_TIME_RANGE(1448029523000) */ METRIC_NAME, APP_ID,
INSTANCE_ID, SERVER_TIME, UNITS, METRIC_SUM, HOSTS_COUNT, METRIC_MAX,
METRIC_MIN FROM METRIC_AGGREGATE WHERE (METRIC_NAME IN
('regionserver.Server.totalRequestCount',
'regionserver.Server.blockCacheCountHitPercent',
'regionserver.Server.regionCount', 'regionserver.Server.compactionQueueLength',
'regionserver.Server.storeFileCount', 'master.Server.averageLoad')) AND APP_ID
= 'ams-hbase' AND SERVER_TIME >= 1448029643000 AND SERVER_TIME < 1448033243
ORDER BY METRIC_NAME, SERVER_TIME LIMIT 11520
But with PHOENIX-914 :-
Declare SERVER_TIME as ROW_TIMESTAMP in schema:-
CREATE TABLE DESTINATION_METRICS_TABLE (SERVER_TIME DATE not null, METRIC_ID
CHAR(15) not null, METRIC_VALUE bigint … CONSTRAINT PK PRIMARY KEY(CREATED_DATE
ROW_TIMESTAMP, METRIC_ID…)) …;
And remove hint from the query:-
SELECT METRIC_NAME, APP_ID, INSTANCE_ID, SERVER_TIME, UNITS, METRIC_SUM,
HOSTS_COUNT, METRIC_MAX, METRIC_MIN FROM METRIC_AGGREGATE WHERE (METRIC_NAME IN
('regionserver.Server.totalRequestCount',
'regionserver.Server.blockCacheCountHitPercent',
'regionserver.Server.regionCount', 'regionserver.Server.compactionQueueLength',
'regionserver.Server.storeFileCount', 'master.Server.averageLoad')) AND APP_ID
= 'ams-hbase' AND SERVER_TIME >= 1448029643000 AND SERVER_TIME < 1448033243
ORDER BY METRIC_NAME, SERVER_TIME LIMIT 11520
The plan is to go ahead with support for both the old and the new phoenix
native timestamp support and toggle based on whether the AMS tables were
created using ROW_TIMESTAMP or not.
> Migrate AMS queries to use ROW_TIMESTAMP instead of native timerange hint
> -
>
> Key: AMBARI-17382
> URL: https://issues.apache.org/jira/browse/AMBARI-17382
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Labels: ambari-metrics
> Fix For: 2.4.0
>
>
> With PHOENIX-914, there is a change in implementation , As earlier, timestamp
> range was passed as a hint to the query to get advantage of native timerange
> optimization in hbase but with new implementation we can mark the timestamp
> column in the schema as a ROW_TIMESTAMP and pass timestamp range with “where”
>
[jira] [Updated] (AMBARI-17409) Ranger has error count while adding Ranger KMS
[ https://issues.apache.org/jira/browse/AMBARI-17409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-17409: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and brunch-2.4 > Ranger has error count while adding Ranger KMS > -- > > Key: AMBARI-17409 > URL: https://issues.apache.org/jira/browse/AMBARI-17409 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-17409.patch, Screen Shot 2016-06-23 at 2.00.20 > PM.png > > > Go to add service on cluster with installer ranger, add RAnger KMS > Go to customize service page > Expected: > No error counts on installed services > Actual > Ranger has 1 error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17186) Tez View: Improve proxy logging
[ https://issues.apache.org/jira/browse/AMBARI-17186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347254#comment-15347254 ] Sreenath Somarajapuram commented on AMBARI-17186: - Attaching patch 6 with the extra space removed. > Tez View: Improve proxy logging > --- > > Key: AMBARI-17186 > URL: https://issues.apache.org/jira/browse/AMBARI-17186 > Project: Ambari > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17186.1.patch, AMBARI-17186.2.patch, > AMBARI-17186.3.patch, AMBARI-17186.4.patch, AMBARI-17186.5.patch, > AMBARI-17186.6.patch > > > More log messages would help us to debug EARs faster. > # Add error log when configuration fetch fails. > # Add debug log when request proxying / redirection succeed > # Add error log when request proxying / redirection fails > With effect from AMBARI-14084, each view would have separate log file. > - For Tez view that is /var/log/ambari-server/tez-view/tez-view.log. > - Debug log would be logged only when the debug mode is enabled. (Set > log4j.logger.org.apache.ambari.view.tez=DEBUG,tezView in > view.log4j.properties for the same) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17186) Tez View: Improve proxy logging
[ https://issues.apache.org/jira/browse/AMBARI-17186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated AMBARI-17186: Attachment: AMBARI-17186.6.patch > Tez View: Improve proxy logging > --- > > Key: AMBARI-17186 > URL: https://issues.apache.org/jira/browse/AMBARI-17186 > Project: Ambari > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17186.1.patch, AMBARI-17186.2.patch, > AMBARI-17186.3.patch, AMBARI-17186.4.patch, AMBARI-17186.5.patch, > AMBARI-17186.6.patch > > > More log messages would help us to debug EARs faster. > # Add error log when configuration fetch fails. > # Add debug log when request proxying / redirection succeed > # Add error log when request proxying / redirection fails > With effect from AMBARI-14084, each view would have separate log file. > - For Tez view that is /var/log/ambari-server/tez-view/tez-view.log. > - Debug log would be logged only when the debug mode is enabled. (Set > log4j.logger.org.apache.ambari.view.tez=DEBUG,tezView in > view.log4j.properties for the same) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-17074) Expose Spark daemon memory in Spark2
[ https://issues.apache.org/jira/browse/AMBARI-17074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srimanth Gunturi resolved AMBARI-17074. --- Resolution: Fixed Committed to branch-2.4 and trunk > Expose Spark daemon memory in Spark2 > > > Key: AMBARI-17074 > URL: https://issues.apache.org/jira/browse/AMBARI-17074 > Project: Ambari > Issue Type: Improvement >Reporter: Weiqing Yang >Assignee: Weiqing Yang > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-17074.v1.patch, AMBARI-17074_v2.patch, > AMBARI-17074_v3.patch, AMBARI-17074_v4.patch > > > Expose Spark daemon memory in Spark2, so that the user can modify its size on > ambari web UI easily. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17386) Misc fixes for Atlas, write correct conf files for server and client, use PLAINTEXTSASL, and remove atlas from HADOOP_CLASSPATH in Hive
[ https://issues.apache.org/jira/browse/AMBARI-17386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347245#comment-15347245 ] Hudson commented on AMBARI-17386: - FAILURE: Integrated in Ambari-trunk-Commit #5148 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5148/]) AMBARI-17386. Misc fixes for Atlas, write correct conf files for server (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8b0b903b2c7be50689e9bab30e118e9f61739306]) * ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-env.xml * ambari-server/src/main/resources/stacks/HDP/2.5/services/ATLAS/kerberos.json * ambari-server/src/test/python/stacks/2.3/ATLAS/test_metadata_server.py * 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/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-env.xml * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/hive-env.xml * ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py > Misc fixes for Atlas, write correct conf files for server and client, use > PLAINTEXTSASL, and remove atlas from HADOOP_CLASSPATH in Hive > --- > > Key: AMBARI-17386 > URL: https://issues.apache.org/jira/browse/AMBARI-17386 > 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-17386.branch-2.4.patch, AMBARI-17386.trunk.patch > > > Misc fixes for Atlas > * Today, the same config files and directories get written out for both > server and client, which is incorrect. > * When kerberizing Atlas, change atlas.kafka.security.protocol to > PLAINTEXTSASL > * In hive-env, remove all atlas paths from HADOOP_CLASSPATH -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17226) When requesting a Kerberos Descriptor via the REST API, 'when' clauses should optionally be processed
[
https://issues.apache.org/jira/browse/AMBARI-17226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347244#comment-15347244
]
Hudson commented on AMBARI-17226:
-
FAILURE: Integrated in Ambari-trunk-Commit #5148 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5148/])
AMBARI-17226. When requesting a Kerberos Descriptor via the REST API, (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=628f81922cc099d5fa7ca8299d860176486f07c4])
*
ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosDescriptorType.java
*
ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterKerberosDescriptorResourceProvider.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelper.java
*
ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosDescriptorTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosComponentDescriptor.java
*
ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosComponentDescriptorTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosDescriptor.java
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterKerberosDescriptorResourceProviderTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosServiceDescriptor.java
*
ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosServiceDescriptorTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/api/resources/ResourceInstanceFactoryImpl.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/KerberosIdentityDescriptor.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/AbstractKerberosDescriptorContainer.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/kerberos/AbstractKerberosDescriptor.java
> When requesting a Kerberos Descriptor via the REST API, 'when' clauses should
> optionally be processed
> -
>
> Key: AMBARI-17226
> URL: https://issues.apache.org/jira/browse/AMBARI-17226
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Fix For: 2.4.0
>
> Attachments: AMBARI-17226_branch-2.4_01.patch,
> AMBARI-17226_branch-2.4_02.patch, AMBARI-17226_branch-2.4_03.patch,
> AMBARI-17226_trunk_01.patch, AMBARI-17226_trunk_02.patch,
> AMBARI-17226_trunk_03.patch
>
>
> When requesting a Kerberos Descriptor via the REST API, 'when' clauses should
> optionally be processed. If elected to be processed, identities that contain
> {{when}} clauses will be included or excluded from the resulting descriptor
> based on the result of the evaluation.
> In the event of an _add service_ scenario, the services being added should be
> able to be specified so that they can be included in the data used for
> {{when}}-clause evaluation.
> *Solution*
> Add _{{GET}} directives_ to specify whether {{when}} clauses are to be
> evaluated (or not) while building the Kerberos Descriptor using the following
> API call:
> {noformat}
> GET
> /api/v1/clusters/CLUSTER_NAME/kerberos_descriptors/COMPOSITE?evaluate_when=true
> {noformat}
> If new services are being added, the {{additional_services}} directive should
> be added to the request so the evaluation can be preformed on the _future_
> set of services, which may evaluate differently then the _current_ set of
> services.
> {noformat}
> GET
> /api/v1/clusters/CLUSTER_NAME/kerberos_descriptors/COMPOSITE?evaluate_when=true@additional_services=HIVE,TEZ,PIG
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17409) Ranger has error count while adding Ranger KMS
[
https://issues.apache.org/jira/browse/AMBARI-17409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347242#comment-15347242
]
Hadoop QA commented on AMBARI-17409:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12812930/AMBARI-17409.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/7520//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7520//console
This message is automatically generated.
> Ranger has error count while adding Ranger KMS
> --
>
> Key: AMBARI-17409
> URL: https://issues.apache.org/jira/browse/AMBARI-17409
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-17409.patch, Screen Shot 2016-06-23 at 2.00.20
> PM.png
>
>
> Go to add service on cluster with installer ranger, add RAnger KMS
> Go to customize service page
> Expected:
> No error counts on installed services
> Actual
> Ranger has 1 error
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17376) Recommendations request execution takes too long time
[ https://issues.apache.org/jira/browse/AMBARI-17376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srimanth Gunturi updated AMBARI-17376: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed change to branch-2.4 and trunk > Recommendations request execution takes too long time > - > > Key: AMBARI-17376 > URL: https://issues.apache.org/jira/browse/AMBARI-17376 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Srimanth Gunturi >Assignee: Srimanth Gunturi >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17376.patch, RecommendationsBreakdown.png > > > /api/v1/stacks/HDP/versions/2.5/recommendations GET request is executed for a > long time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17376) Recommendations request execution takes too long time
[ https://issues.apache.org/jira/browse/AMBARI-17376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srimanth Gunturi updated AMBARI-17376: -- Attachment: AMBARI-17376.patch > Recommendations request execution takes too long time > - > > Key: AMBARI-17376 > URL: https://issues.apache.org/jira/browse/AMBARI-17376 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Srimanth Gunturi >Assignee: Srimanth Gunturi >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17376.patch, RecommendationsBreakdown.png > > > /api/v1/stacks/HDP/versions/2.5/recommendations GET request is executed for a > long time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17376) Recommendations request execution takes too long time
[ https://issues.apache.org/jira/browse/AMBARI-17376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srimanth Gunturi updated AMBARI-17376: -- Attachment: (was: AMBARI-17376.patch) > Recommendations request execution takes too long time > - > > Key: AMBARI-17376 > URL: https://issues.apache.org/jira/browse/AMBARI-17376 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Srimanth Gunturi >Assignee: Srimanth Gunturi >Priority: Critical > Fix For: 2.4.0 > > Attachments: RecommendationsBreakdown.png > > > /api/v1/stacks/HDP/versions/2.5/recommendations GET request is executed for a > long time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17389) Read 'yarn.nodemanager.resource.memory-mb' and 'yarn.scheduler.minimum-allocation-mb' from 'configurations' if 'changed-configurations' is empty and config is there in
[ https://issues.apache.org/jira/browse/AMBARI-17389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated AMBARI-17389: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Read 'yarn.nodemanager.resource.memory-mb' and > 'yarn.scheduler.minimum-allocation-mb' from 'configurations' if > 'changed-configurations' is empty and config is there in 'configurations', > else from 'services'. > > > Key: AMBARI-17389 > URL: https://issues.apache.org/jira/browse/AMBARI-17389 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > Attachments: AMBARI-17389.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17411) Spark thriftserver link redirects wrong url
Yesha Vora created AMBARI-17411: --- Summary: Spark thriftserver link redirects wrong url Key: AMBARI-17411 URL: https://issues.apache.org/jira/browse/AMBARI-17411 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Yesha Vora Spark-thriftserver link redirects to wrong url. * Go to http://:8080/#/main/services/SPARK/summary * click on spark-thriftserver This link redirects to "http://:8080/#/main/hosts" instead of "http://:8080/#/main/hosts//summary" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17410) Incorrect error message for invalid category in Host Combo Search Box
[ https://issues.apache.org/jira/browse/AMBARI-17410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-17410: Attachment: ErrorMessageWithFix.jpg > Incorrect error message for invalid category in Host Combo Search Box > - > > Key: AMBARI-17410 > URL: https://issues.apache.org/jira/browse/AMBARI-17410 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17410.patch, ErrorMessage.jpg, > ErrorMessageWithFix.jpg > > > 1. In the host combo box, if an invalid category is entered, an error is > displayed > [object Object] is not a valid category. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17407) Wizard in progress for other users after Move Wizard
[ https://issues.apache.org/jira/browse/AMBARI-17407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-17407: - Resolution: Fixed Status: Resolved (was: Patch Available) > Wizard in progress for other users after Move Wizard > > > Key: AMBARI-17407 > URL: https://issues.apache.org/jira/browse/AMBARI-17407 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17407.patch > > > STR: > 1. Run Move Wizard for some component with 4 steps (some components have 6 or > 7 steps). > 2. Complete Move Wizard. > 3. Login with other ambari admin user. > As a result message about running wizard will appear and all actions will be > disabled (actually wizard was completed). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17410) Incorrect error message for invalid category in Host Combo Search Box
[ https://issues.apache.org/jira/browse/AMBARI-17410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-17410: Fix Version/s: trunk Status: Patch Available (was: In Progress) > Incorrect error message for invalid category in Host Combo Search Box > - > > Key: AMBARI-17410 > URL: https://issues.apache.org/jira/browse/AMBARI-17410 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17410.patch, ErrorMessage.jpg > > > 1. In the host combo box, if an invalid category is entered, an error is > displayed > [object Object] is not a valid category. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17407) Wizard in progress for other users after Move Wizard
[ https://issues.apache.org/jira/browse/AMBARI-17407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347221#comment-15347221 ] Aleksandr Kovalenko commented on AMBARI-17407: -- committed to trunk and brunch-2.4 > Wizard in progress for other users after Move Wizard > > > Key: AMBARI-17407 > URL: https://issues.apache.org/jira/browse/AMBARI-17407 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17407.patch > > > STR: > 1. Run Move Wizard for some component with 4 steps (some components have 6 or > 7 steps). > 2. Complete Move Wizard. > 3. Login with other ambari admin user. > As a result message about running wizard will appear and all actions will be > disabled (actually wizard was completed). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17410) Incorrect error message for invalid category in Host Combo Search Box
[ https://issues.apache.org/jira/browse/AMBARI-17410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-17410: Attachment: AMBARI-17410.patch > Incorrect error message for invalid category in Host Combo Search Box > - > > Key: AMBARI-17410 > URL: https://issues.apache.org/jira/browse/AMBARI-17410 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Attachments: AMBARI-17410.patch, ErrorMessage.jpg > > > 1. In the host combo box, if an invalid category is entered, an error is > displayed > [object Object] is not a valid category. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17410) Incorrect error message for invalid category in Host Combo Search Box
[ https://issues.apache.org/jira/browse/AMBARI-17410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-17410: Attachment: ErrorMessage.jpg > Incorrect error message for invalid category in Host Combo Search Box > - > > Key: AMBARI-17410 > URL: https://issues.apache.org/jira/browse/AMBARI-17410 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Attachments: AMBARI-17410.patch, ErrorMessage.jpg > > > 1. In the host combo box, if an invalid category is entered, an error is > displayed > [object Object] is not a valid category. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17407) Wizard in progress for other users after Move Wizard
[ https://issues.apache.org/jira/browse/AMBARI-17407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347213#comment-15347213 ] Aleksandr Kovalenko commented on AMBARI-17407: -- changed logic in application router can not be covered with unit tests, tested manually > Wizard in progress for other users after Move Wizard > > > Key: AMBARI-17407 > URL: https://issues.apache.org/jira/browse/AMBARI-17407 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17407.patch > > > STR: > 1. Run Move Wizard for some component with 4 steps (some components have 6 or > 7 steps). > 2. Complete Move Wizard. > 3. Login with other ambari admin user. > As a result message about running wizard will appear and all actions will be > disabled (actually wizard was completed). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17409) Ranger has error count while adding Ranger KMS
[ https://issues.apache.org/jira/browse/AMBARI-17409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347209#comment-15347209 ] Aleksandr Kovalenko commented on AMBARI-17409: -- +1 for the patch > Ranger has error count while adding Ranger KMS > -- > > Key: AMBARI-17409 > URL: https://issues.apache.org/jira/browse/AMBARI-17409 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-17409.patch, Screen Shot 2016-06-23 at 2.00.20 > PM.png > > > Go to add service on cluster with installer ranger, add RAnger KMS > Go to customize service page > Expected: > No error counts on installed services > Actual > Ranger has 1 error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17186) Tez View: Improve proxy logging
[ https://issues.apache.org/jira/browse/AMBARI-17186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated AMBARI-17186: Attachment: AMBARI-17186.5.patch Attaching a patch with the comments addressed. > Tez View: Improve proxy logging > --- > > Key: AMBARI-17186 > URL: https://issues.apache.org/jira/browse/AMBARI-17186 > Project: Ambari > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17186.1.patch, AMBARI-17186.2.patch, > AMBARI-17186.3.patch, AMBARI-17186.4.patch, AMBARI-17186.5.patch > > > More log messages would help us to debug EARs faster. > # Add error log when configuration fetch fails. > # Add debug log when request proxying / redirection succeed > # Add error log when request proxying / redirection fails > With effect from AMBARI-14084, each view would have separate log file. > - For Tez view that is /var/log/ambari-server/tez-view/tez-view.log. > - Debug log would be logged only when the debug mode is enabled. (Set > log4j.logger.org.apache.ambari.view.tez=DEBUG,tezView in > view.log4j.properties for the same) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17409) Ranger has error count while adding Ranger KMS
[ https://issues.apache.org/jira/browse/AMBARI-17409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-17409: - Attachment: AMBARI-17409.patch > Ranger has error count while adding Ranger KMS > -- > > Key: AMBARI-17409 > URL: https://issues.apache.org/jira/browse/AMBARI-17409 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-17409.patch, Screen Shot 2016-06-23 at 2.00.20 > PM.png > > > Go to add service on cluster with installer ranger, add RAnger KMS > Go to customize service page > Expected: > No error counts on installed services > Actual > Ranger has 1 error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17410) Incorrect error message for invalid category in Host Combo Search Box
Sangeeta Ravindran created AMBARI-17410: --- Summary: Incorrect error message for invalid category in Host Combo Search Box Key: AMBARI-17410 URL: https://issues.apache.org/jira/browse/AMBARI-17410 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: trunk Reporter: Sangeeta Ravindran Assignee: Sangeeta Ravindran Priority: Minor 1. In the host combo box, if an invalid category is entered, an error is displayed [object Object] is not a valid category. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17407) Wizard in progress for other users after Move Wizard
[ https://issues.apache.org/jira/browse/AMBARI-17407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347206#comment-15347206 ] Antonenko Alexander commented on AMBARI-17407: -- +1 for the patch > Wizard in progress for other users after Move Wizard > > > Key: AMBARI-17407 > URL: https://issues.apache.org/jira/browse/AMBARI-17407 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17407.patch > > > STR: > 1. Run Move Wizard for some component with 4 steps (some components have 6 or > 7 steps). > 2. Complete Move Wizard. > 3. Login with other ambari admin user. > As a result message about running wizard will appear and all actions will be > disabled (actually wizard was completed). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17407) Wizard in progress for other users after Move Wizard
[
https://issues.apache.org/jira/browse/AMBARI-17407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347199#comment-15347199
]
Hadoop QA commented on AMBARI-17407:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12812907/AMBARI-17407.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/7518//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7518//console
This message is automatically generated.
> Wizard in progress for other users after Move Wizard
>
>
> Key: AMBARI-17407
> URL: https://issues.apache.org/jira/browse/AMBARI-17407
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17407.patch
>
>
> STR:
> 1. Run Move Wizard for some component with 4 steps (some components have 6 or
> 7 steps).
> 2. Complete Move Wizard.
> 3. Login with other ambari admin user.
> As a result message about running wizard will appear and all actions will be
> disabled (actually wizard was completed).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17409) Ranger has error count while adding Ranger KMS
Antonenko Alexander created AMBARI-17409: Summary: Ranger has error count while adding Ranger KMS Key: AMBARI-17409 URL: https://issues.apache.org/jira/browse/AMBARI-17409 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Fix For: 2.4.0 Attachments: Screen Shot 2016-06-23 at 2.00.20 PM.png Go to add service on cluster with installer ranger, add RAnger KMS Go to customize service page Expected: No error counts on installed services Actual Ranger has 1 error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17409) Ranger has error count while adding Ranger KMS
[ https://issues.apache.org/jira/browse/AMBARI-17409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-17409: - Status: Patch Available (was: Open) > Ranger has error count while adding Ranger KMS > -- > > Key: AMBARI-17409 > URL: https://issues.apache.org/jira/browse/AMBARI-17409 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-17409.patch, Screen Shot 2016-06-23 at 2.00.20 > PM.png > > > Go to add service on cluster with installer ranger, add RAnger KMS > Go to customize service page > Expected: > No error counts on installed services > Actual > Ranger has 1 error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17409) Ranger has error count while adding Ranger KMS
[ https://issues.apache.org/jira/browse/AMBARI-17409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-17409: - Attachment: Screen Shot 2016-06-23 at 2.00.20 PM.png > Ranger has error count while adding Ranger KMS > -- > > Key: AMBARI-17409 > URL: https://issues.apache.org/jira/browse/AMBARI-17409 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: Screen Shot 2016-06-23 at 2.00.20 PM.png > > > Go to add service on cluster with installer ranger, add RAnger KMS > Go to customize service page > Expected: > No error counts on installed services > Actual > Ranger has 1 error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17343) Blueprint attribute provision_action=INSTALL_ONLY loses its value after server restart
[
https://issues.apache.org/jira/browse/AMBARI-17343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347166#comment-15347166
]
Hadoop QA commented on AMBARI-17343:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12812865/AMBARI-17343.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7517//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7517//console
This message is automatically generated.
> Blueprint attribute provision_action=INSTALL_ONLY loses its value after
> server restart
> --
>
> Key: AMBARI-17343
> URL: https://issues.apache.org/jira/browse/AMBARI-17343
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17343.patch
>
>
> We created a cluster via blueprints where we did not want components to be
> started by Ambari (background - this was a takeover of existing cluster where
> services were already installed and started. We did not want STARTs to be
> done as they would overwrite existing configs). Towards this goal we set
> {{"provision_action" : "INSTALL_ONLY"}} so that when agents register with
> Ambari they will only do the install and not start.
> {code}
> {
> "blueprint" : "blueprint",
> "default_password" : "ambari",
> "provision_action" : "INSTALL_ONLY",
> "host_groups" : [
> ...
> ]
> }
> {code}
> This flag did its job as long as ambari-server was not restarted. After
> restart however, new agents would install and start the host-components.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17186) Tez View: Improve proxy logging
[ https://issues.apache.org/jira/browse/AMBARI-17186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347098#comment-15347098 ] Hitesh Shah commented on AMBARI-17186: -- Updated with review comments > Tez View: Improve proxy logging > --- > > Key: AMBARI-17186 > URL: https://issues.apache.org/jira/browse/AMBARI-17186 > Project: Ambari > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17186.1.patch, AMBARI-17186.2.patch, > AMBARI-17186.3.patch, AMBARI-17186.4.patch > > > More log messages would help us to debug EARs faster. > # Add error log when configuration fetch fails. > # Add debug log when request proxying / redirection succeed > # Add error log when request proxying / redirection fails > With effect from AMBARI-14084, each view would have separate log file. > - For Tez view that is /var/log/ambari-server/tez-view/tez-view.log. > - Debug log would be logged only when the debug mode is enabled. (Set > log4j.logger.org.apache.ambari.view.tez=DEBUG,tezView in > view.log4j.properties for the same) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17186) Tez View: Improve proxy logging
[ https://issues.apache.org/jira/browse/AMBARI-17186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated AMBARI-17186: Attachment: AMBARI-17186.4.patch [~hitesh] Attaching a fresh patch with the exception implementation refactored. Now we use a single class "TezWebAppException" with overloaded constructors for various kinds of exceptions. Please help in reviewing. > Tez View: Improve proxy logging > --- > > Key: AMBARI-17186 > URL: https://issues.apache.org/jira/browse/AMBARI-17186 > Project: Ambari > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17186.1.patch, AMBARI-17186.2.patch, > AMBARI-17186.3.patch, AMBARI-17186.4.patch > > > More log messages would help us to debug EARs faster. > # Add error log when configuration fetch fails. > # Add debug log when request proxying / redirection succeed > # Add error log when request proxying / redirection fails > With effect from AMBARI-14084, each view would have separate log file. > - For Tez view that is /var/log/ambari-server/tez-view/tez-view.log. > - Debug log would be logged only when the debug mode is enabled. (Set > log4j.logger.org.apache.ambari.view.tez=DEBUG,tezView in > view.log4j.properties for the same) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17408) Use the correct config for slider AM size 'slider_am_container_mb' to set its value during LLAP config calculations.
[ https://issues.apache.org/jira/browse/AMBARI-17408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-17408: - Attachment: AMBARI-17408.patch > Use the correct config for slider AM size 'slider_am_container_mb' to set its > value during LLAP config calculations. > > > Key: AMBARI-17408 > URL: https://issues.apache.org/jira/browse/AMBARI-17408 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > Attachments: AMBARI-17408.patch > > > - Currently, it uses config 'slider_am_container_size' which doesn't exist. > - use correct config name 'slider_am_container_mb' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17408) Use the correct config for slider AM size 'slider_am_container_mb' to set its value during LLAP config calculations.
[ https://issues.apache.org/jira/browse/AMBARI-17408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-17408: - Resolution: Fixed Status: Resolved (was: Patch Available) > Use the correct config for slider AM size 'slider_am_container_mb' to set its > value during LLAP config calculations. > > > Key: AMBARI-17408 > URL: https://issues.apache.org/jira/browse/AMBARI-17408 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > Attachments: AMBARI-17408.patch > > > - Currently, it uses config 'slider_am_container_size' which doesn't exist. > - use correct config name 'slider_am_container_mb' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17408) Use the correct config for slider AM size 'slider_am_container_mb' to set its value during LLAP config calculations.
[ https://issues.apache.org/jira/browse/AMBARI-17408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-17408: - Status: Patch Available (was: Open) > Use the correct config for slider AM size 'slider_am_container_mb' to set its > value during LLAP config calculations. > > > Key: AMBARI-17408 > URL: https://issues.apache.org/jira/browse/AMBARI-17408 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > Attachments: AMBARI-17408.patch > > > - Currently, it uses config 'slider_am_container_size' which doesn't exist. > - use correct config name 'slider_am_container_mb' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17408) Use the correct config for slider AM size 'slider_am_container_mb' to set its value during LLAP config calculations.
Swapan Shridhar created AMBARI-17408: Summary: Use the correct config for slider AM size 'slider_am_container_mb' to set its value during LLAP config calculations. Key: AMBARI-17408 URL: https://issues.apache.org/jira/browse/AMBARI-17408 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Swapan Shridhar Assignee: Swapan Shridhar Fix For: 2.4.0 - Currently, it uses config 'slider_am_container_size' which doesn't exist. - use correct config name 'slider_am_container_mb' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17183) client.properties for Falcon should be configurable via Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347047#comment-15347047 ] Hudson commented on AMBARI-17183: - FAILURE: Integrated in Ambari-trunk-Commit #5147 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5147/]) AMBARI-17183: client.properties for Falcon should be configurable via (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4a3fb6ef1db5ef15c0caca958a7a72786b0fafd3]) * ambari-server/src/test/python/stacks/2.2/configs/falcon-upgrade.json * ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/FALCON/package/scripts/falcon.py * ambari-server/src/test/python/stacks/2.1/configs/default.json * ambari-server/src/test/python/stacks/2.1/FALCON/test_falcon_client.py * ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/params_linux.py * ambari-server/src/test/python/stacks/2.1/FALCON/test_falcon_server.py * ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/falcon.py > client.properties for Falcon should be configurable via Ambari > -- > > Key: AMBARI-17183 > URL: https://issues.apache.org/jira/browse/AMBARI-17183 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan > Fix For: 2.4.0 > > Attachments: AMBARI-17183-2.patch, AMBARI-17183.patch.2 > > > Everytime Falcon is restarted using Ambari, the client.properties under > /usr/hdp/current/falcon-client/conf/client.properties gets overwritten by > default properties. But there are scenarios where a Falcon user might wish to > change the falcon.url in client.properties, or add custom client.properties. > Ambari should provide a way to do this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17226) When requesting a Kerberos Descriptor via the REST API, 'when' clauses should optionally be processed
[
https://issues.apache.org/jira/browse/AMBARI-17226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-17226:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit 628f81922cc099d5fa7ca8299d860176486f07c4
Author: Robert Levas
Date: Thu Jun 23 15:31:06 2016 -0400
{noformat}
Committed to branch-2.4
{noformat}
commit 77a9ce8ce5bf6062de3cb937aad98964b0527c5a
Author: Robert Levas
Date: Thu Jun 23 15:32:04 2016 -0400
{noformat}
> When requesting a Kerberos Descriptor via the REST API, 'when' clauses should
> optionally be processed
> -
>
> Key: AMBARI-17226
> URL: https://issues.apache.org/jira/browse/AMBARI-17226
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Fix For: 2.4.0
>
> Attachments: AMBARI-17226_branch-2.4_01.patch,
> AMBARI-17226_branch-2.4_02.patch, AMBARI-17226_branch-2.4_03.patch,
> AMBARI-17226_trunk_01.patch, AMBARI-17226_trunk_02.patch,
> AMBARI-17226_trunk_03.patch
>
>
> When requesting a Kerberos Descriptor via the REST API, 'when' clauses should
> optionally be processed. If elected to be processed, identities that contain
> {{when}} clauses will be included or excluded from the resulting descriptor
> based on the result of the evaluation.
> In the event of an _add service_ scenario, the services being added should be
> able to be specified so that they can be included in the data used for
> {{when}}-clause evaluation.
> *Solution*
> Add _{{GET}} directives_ to specify whether {{when}} clauses are to be
> evaluated (or not) while building the Kerberos Descriptor using the following
> API call:
> {noformat}
> GET
> /api/v1/clusters/CLUSTER_NAME/kerberos_descriptors/COMPOSITE?evaluate_when=true
> {noformat}
> If new services are being added, the {{additional_services}} directive should
> be added to the request so the evaluation can be preformed on the _future_
> set of services, which may evaluate differently then the _current_ set of
> services.
> {noformat}
> GET
> /api/v1/clusters/CLUSTER_NAME/kerberos_descriptors/COMPOSITE?evaluate_when=true@additional_services=HIVE,TEZ,PIG
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17407) Wizard in progress for other users after Move Wizard
Aleksandr Kovalenko created AMBARI-17407: Summary: Wizard in progress for other users after Move Wizard Key: AMBARI-17407 URL: https://issues.apache.org/jira/browse/AMBARI-17407 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Priority: Critical Fix For: 2.4.0 STR: 1. Run Move Wizard for some component with 4 steps (some components have 6 or 7 steps). 2. Complete Move Wizard. 3. Login with other ambari admin user. As a result message about running wizard will appear and all actions will be disabled (actually wizard was completed). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17406) Update Zeppelin service definition
[ https://issues.apache.org/jira/browse/AMBARI-17406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith Kamath updated AMBARI-17406: Status: Patch Available (was: Open) > Update Zeppelin service definition > -- > > Key: AMBARI-17406 > URL: https://issues.apache.org/jira/browse/AMBARI-17406 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Renjith Kamath >Assignee: Renjith Kamath > Fix For: 2.4.0 > > > - comment session manager config in shiro.ini > - fix default value for zeppelin kerberos properties > - extract kerberos config update to a new function > - prevent overwriting interpreter config > - set default value for spark and livy master -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17406) Update Zeppelin service definition
Renjith Kamath created AMBARI-17406: --- Summary: Update Zeppelin service definition Key: AMBARI-17406 URL: https://issues.apache.org/jira/browse/AMBARI-17406 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Renjith Kamath Assignee: Renjith Kamath Fix For: 2.4.0 - comment session manager config in shiro.ini - fix default value for zeppelin kerberos properties - extract kerberos config update to a new function - prevent overwriting interpreter config - set default value for spark and livy master -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-17183) client.properties for Falcon should be configurable via Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez resolved AMBARI-17183. -- Resolution: Fixed Pushed to trunk, commit 4a3fb6ef1db5ef15c0caca958a7a72786b0fafd3 branch-2.4, commit 16d63dabf41f2dcb58a51d537ec9262e7f4a4f79 > client.properties for Falcon should be configurable via Ambari > -- > > Key: AMBARI-17183 > URL: https://issues.apache.org/jira/browse/AMBARI-17183 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan > Fix For: 2.4.0 > > Attachments: AMBARI-17183-2.patch, AMBARI-17183.patch.2 > > > Everytime Falcon is restarted using Ambari, the client.properties under > /usr/hdp/current/falcon-client/conf/client.properties gets overwritten by > default properties. But there are scenarios where a Falcon user might wish to > change the falcon.url in client.properties, or add custom client.properties. > Ambari should provide a way to do this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17405) Rename Hive View version 2.0.0 to version 1.5.0 to reduce confusion
[ https://issues.apache.org/jira/browse/AMBARI-17405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-17405: --- Status: Patch Available (was: Open) > Rename Hive View version 2.0.0 to version 1.5.0 to reduce confusion > --- > > Key: AMBARI-17405 > URL: https://issues.apache.org/jira/browse/AMBARI-17405 > 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-17405.trunk.patch > > Original Estimate: 0.5h > Remaining Estimate: 0.5h > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17405) Rename Hive View version 2.0.0 to version 1.5.0 to reduce confusion
[ https://issues.apache.org/jira/browse/AMBARI-17405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-17405: --- Attachment: AMBARI-17405.trunk.patch > Rename Hive View version 2.0.0 to version 1.5.0 to reduce confusion > --- > > Key: AMBARI-17405 > URL: https://issues.apache.org/jira/browse/AMBARI-17405 > 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-17405.trunk.patch > > Original Estimate: 0.5h > Remaining Estimate: 0.5h > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17405) Rename Hive View version 2.0.0 to version 1.5.0 to reduce confusion
Ashwin Rajeev created AMBARI-17405: -- Summary: Rename Hive View version 2.0.0 to version 1.5.0 to reduce confusion Key: AMBARI-17405 URL: https://issues.apache.org/jira/browse/AMBARI-17405 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] [Commented] (AMBARI-17377) Rolling Upgrade process is blocked after ambari-server/ambari-agent restart
[
https://issues.apache.org/jira/browse/AMBARI-17377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346763#comment-15346763
]
Hudson commented on AMBARI-17377:
-
FAILURE: Integrated in Ambari-trunk-Commit #5146 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5146/])
AMBARI-17377. Rolling Upgrade process is blocked after (mpapyrkovskyy:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7d317cc29dd4189dd19fdba3cbf44b70232d538e])
* ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml
* ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml
*
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionDBAccessorImpl.java
*
ambari-server/src/test/java/org/apache/ambari/server/actionmanager/TestActionScheduler.java
*
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/HostRoleStatus.java
*
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionScheduler.java
* ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.2.xml
* ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.5.xml
* ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.4.xml
* ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.4.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/upgrade-2.3.xml
* ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.4.xml
> Rolling Upgrade process is blocked after ambari-server/ambari-agent restart
> ---
>
> Key: AMBARI-17377
> URL: https://issues.apache.org/jira/browse/AMBARI-17377
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17377.patch
>
>
> Steps to reproduce:
> # Start Rolling Upgrade.
> # Restart ambari-server or ambari-agent.
> Result: operation running during restart will be moved to skipped_failed
> status, all next - to aborted. After that it is impossible to execute retry
> or ignore and proceed:
> {code}
> {
> "status" : 400,
> "message" : "java.lang.IllegalArgumentException: Can not transition a stage
> from ABORTED to PENDING"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17381) AuthorizationHelperTest.testAuthName may fail due to residual SecurityContext from previously executed test cases.
[
https://issues.apache.org/jira/browse/AMBARI-17381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346765#comment-15346765
]
Hudson commented on AMBARI-17381:
-
FAILURE: Integrated in Ambari-trunk-Commit #5146 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5146/])
AMBARI-17381. AuthorizationHelperTest.testAuthName may fail due to (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=80abd6ca68977035d40f4dea942423223beecb9d])
*
ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AuthorizationHelperTest.java
> AuthorizationHelperTest.testAuthName may fail due to residual SecurityContext
> from previously executed test cases.
> ---
>
> Key: AMBARI-17381
> URL: https://issues.apache.org/jira/browse/AMBARI-17381
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17381_branch-2.4_01.patch,
> AMBARI-17381_trunk_01.patch
>
>
> {{org.apache.ambari.server.security.authorization.AuthorizationHelperTest#testAuthName}}
> may fail due to residual SecurityContext from previously executed test
> cases. The SecurityContext should be cleared before (and after) each test in
> the suite.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17402) Add new configuration property to enable skipping of INSTALL tasks for Blueprint deployments
[ https://issues.apache.org/jira/browse/AMBARI-17402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346766#comment-15346766 ] Hudson commented on AMBARI-17402: - FAILURE: Integrated in Ambari-trunk-Commit #5146 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5146/]) AMBARI-17402. Add new configuration property to enable skipping of (smagyari: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5e11d0366747182987825ab5bfb3e68d5e2807d9]) * ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterInstallWithoutStartTest.java * ambari-server/src/main/java/org/apache/ambari/server/topology/AmbariContext.java * ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterDeployWithHostsSyspreppedTest.java * ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java * ambari-server/src/main/java/org/apache/ambari/server/topology/HostRequest.java > Add new configuration property to enable skipping of INSTALL tasks for > Blueprint deployments > > > Key: AMBARI-17402 > URL: https://issues.apache.org/jira/browse/AMBARI-17402 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Sandor Magyari >Assignee: Sandor Magyari >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17402.patch > > > Add new configuration property to ambari.properties: > 'blueprint.skip_install_tasks' to control skipping of INSTALL tasks for > Blueprint deployments. INSTALL tasks will be skipped for non-client > components in case packages.pre.installed & blueprint.skip_install_tasks are > both set to true. By default blueprint.skip_install_tasks should be set to > false. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17183) client.properties for Falcon should be configurable via Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Ranganathan updated AMBARI-17183: Attachment: AMBARI-17183-2.patch > client.properties for Falcon should be configurable via Ambari > -- > > Key: AMBARI-17183 > URL: https://issues.apache.org/jira/browse/AMBARI-17183 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan > Fix For: 2.4.0 > > Attachments: AMBARI-17183-2.patch, AMBARI-17183.patch.2 > > > Everytime Falcon is restarted using Ambari, the client.properties under > /usr/hdp/current/falcon-client/conf/client.properties gets overwritten by > default properties. But there are scenarios where a Falcon user might wish to > change the falcon.url in client.properties, or add custom client.properties. > Ambari should provide a way to do this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17183) client.properties for Falcon should be configurable via Ambari
[ https://issues.apache.org/jira/browse/AMBARI-17183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346746#comment-15346746 ] Venkat Ranganathan commented on AMBARI-17183: - Uploaded latest patch > client.properties for Falcon should be configurable via Ambari > -- > > Key: AMBARI-17183 > URL: https://issues.apache.org/jira/browse/AMBARI-17183 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan > Fix For: 2.4.0 > > Attachments: AMBARI-17183-2.patch, AMBARI-17183.patch.2 > > > Everytime Falcon is restarted using Ambari, the client.properties under > /usr/hdp/current/falcon-client/conf/client.properties gets overwritten by > default properties. But there are scenarios where a Falcon user might wish to > change the falcon.url in client.properties, or add custom client.properties. > Ambari should provide a way to do this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17311) Modify HTTP headers to follow best security practices
[
https://issues.apache.org/jira/browse/AMBARI-17311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346738#comment-15346738
]
Hadoop QA commented on AMBARI-17311:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12812833/AMBARI-17311.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7514//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7514//console
This message is automatically generated.
> Modify HTTP headers to follow best security practices
> -
>
> Key: AMBARI-17311
> URL: https://issues.apache.org/jira/browse/AMBARI-17311
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: trunk
>
> Attachments: AMBARI-17311.patch
>
>
> Add the following HTTP headers to follow security best practices.
> X-Content-Type-Options: nosniff
> Cache-control: no-store
> Pragma: no-cache
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17358) After switching to external database in hive, user should be allowed to delete mysql server
[ https://issues.apache.org/jira/browse/AMBARI-17358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-17358: -- Attachment: AMBARI-17358.patch > After switching to external database in hive, user should be allowed to > delete mysql server > --- > > Key: AMBARI-17358 > URL: https://issues.apache.org/jira/browse/AMBARI-17358 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17358.patch > > > When user switches from MySQL to Existing database in hive and stop the MySQL > Server > 1) Ambari UI > Hive > Service Actions > Stop becomes unavailable, so Hive > can't be stopped anymore > 2) Hive status is showing up as red Triangle indicating there is a problem > with Hive > Providing an option to delete MySQL server when an existing database is used > in Hive would help in overcoming the issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17358) After switching to external database in hive, user should be allowed to delete mysql server
[ https://issues.apache.org/jira/browse/AMBARI-17358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-17358: -- Fix Version/s: trunk Status: Patch Available (was: Open) > After switching to external database in hive, user should be allowed to > delete mysql server > --- > > Key: AMBARI-17358 > URL: https://issues.apache.org/jira/browse/AMBARI-17358 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17358.patch > > > When user switches from MySQL to Existing database in hive and stop the MySQL > Server > 1) Ambari UI > Hive > Service Actions > Stop becomes unavailable, so Hive > can't be stopped anymore > 2) Hive status is showing up as red Triangle indicating there is a problem > with Hive > Providing an option to delete MySQL server when an existing database is used > in Hive would help in overcoming the issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17358) After switching to external database in hive, user should be allowed to delete mysql server
[ https://issues.apache.org/jira/browse/AMBARI-17358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-17358: -- Affects Version/s: trunk > After switching to external database in hive, user should be allowed to > delete mysql server > --- > > Key: AMBARI-17358 > URL: https://issues.apache.org/jira/browse/AMBARI-17358 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > > When user switches from MySQL to Existing database in hive and stop the MySQL > Server > 1) Ambari UI > Hive > Service Actions > Stop becomes unavailable, so Hive > can't be stopped anymore > 2) Hive status is showing up as red Triangle indicating there is a problem > with Hive > Providing an option to delete MySQL server when an existing database is used > in Hive would help in overcoming the issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17358) After switching to external database in hive, user should be allowed to delete mysql server
[ https://issues.apache.org/jira/browse/AMBARI-17358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-17358: -- Component/s: ambari-web > After switching to external database in hive, user should be allowed to > delete mysql server > --- > > Key: AMBARI-17358 > URL: https://issues.apache.org/jira/browse/AMBARI-17358 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > > When user switches from MySQL to Existing database in hive and stop the MySQL > Server > 1) Ambari UI > Hive > Service Actions > Stop becomes unavailable, so Hive > can't be stopped anymore > 2) Hive status is showing up as red Triangle indicating there is a problem > with Hive > Providing an option to delete MySQL server when an existing database is used > in Hive would help in overcoming the issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17402) Add new configuration property to enable skipping of INSTALL tasks for Blueprint deployments
[ https://issues.apache.org/jira/browse/AMBARI-17402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-17402: Resolution: Fixed Status: Resolved (was: Patch Available) > Add new configuration property to enable skipping of INSTALL tasks for > Blueprint deployments > > > Key: AMBARI-17402 > URL: https://issues.apache.org/jira/browse/AMBARI-17402 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Sandor Magyari >Assignee: Sandor Magyari >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17402.patch > > > Add new configuration property to ambari.properties: > 'blueprint.skip_install_tasks' to control skipping of INSTALL tasks for > Blueprint deployments. INSTALL tasks will be skipped for non-client > components in case packages.pre.installed & blueprint.skip_install_tasks are > both set to true. By default blueprint.skip_install_tasks should be set to > false. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17343) Blueprint attribute provision_action=INSTALL_ONLY loses its value after server restart
[
https://issues.apache.org/jira/browse/AMBARI-17343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Magyari updated AMBARI-17343:
Status: Patch Available (was: Open)
> Blueprint attribute provision_action=INSTALL_ONLY loses its value after
> server restart
> --
>
> Key: AMBARI-17343
> URL: https://issues.apache.org/jira/browse/AMBARI-17343
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17343.patch
>
>
> We created a cluster via blueprints where we did not want components to be
> started by Ambari (background - this was a takeover of existing cluster where
> services were already installed and started. We did not want STARTs to be
> done as they would overwrite existing configs). Towards this goal we set
> {{"provision_action" : "INSTALL_ONLY"}} so that when agents register with
> Ambari they will only do the install and not start.
> {code}
> {
> "blueprint" : "blueprint",
> "default_password" : "ambari",
> "provision_action" : "INSTALL_ONLY",
> "host_groups" : [
> ...
> ]
> }
> {code}
> This flag did its job as long as ambari-server was not restarted. After
> restart however, new agents would install and start the host-components.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17343) Blueprint attribute provision_action=INSTALL_ONLY loses its value after server restart
[
https://issues.apache.org/jira/browse/AMBARI-17343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Magyari updated AMBARI-17343:
Attachment: AMBARI-17343.patch
> Blueprint attribute provision_action=INSTALL_ONLY loses its value after
> server restart
> --
>
> Key: AMBARI-17343
> URL: https://issues.apache.org/jira/browse/AMBARI-17343
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17343.patch
>
>
> We created a cluster via blueprints where we did not want components to be
> started by Ambari (background - this was a takeover of existing cluster where
> services were already installed and started. We did not want STARTs to be
> done as they would overwrite existing configs). Towards this goal we set
> {{"provision_action" : "INSTALL_ONLY"}} so that when agents register with
> Ambari they will only do the install and not start.
> {code}
> {
> "blueprint" : "blueprint",
> "default_password" : "ambari",
> "provision_action" : "INSTALL_ONLY",
> "host_groups" : [
> ...
> ]
> }
> {code}
> This flag did its job as long as ambari-server was not restarted. After
> restart however, new agents would install and start the host-components.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17404) RU/EU Install packages fails on non-root
[
https://issues.apache.org/jira/browse/AMBARI-17404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346626#comment-15346626
]
Hudson commented on AMBARI-17404:
-
FAILURE: Integrated in Ambari-trunk-Commit #5145 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5145/])
AMBARI-17404. RU/EU Install packages fails on non-root (aonishuk) (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=bfc904b204ea962392b2be19984a60661d0cd3a0])
*
ambari-common/src/main/python/resource_management/libraries/functions/packages_analyzer.py
> RU/EU Install packages fails on non-root
>
>
> Key: AMBARI-17404
> URL: https://issues.apache.org/jira/browse/AMBARI-17404
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17404.patch
>
>
> 2016-06-23 13:39:05,672 - Could not install packages. Error: Execution of
> '/usr/bin/apt-get -qq check' returned 100. E: Could not open lock file
> /var/lib/dpkg/lock - open (13: Permission denied)
> E: Unable to lock the administration directory (/var/lib/dpkg/), are you
> root?
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 166, in actionexecute
> ret_code = self.install_packages(package_list)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 400, in install_packages
> if not verifyDependencies():
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/packages_analyzer.py",
> line 309, in verifyDependencies
> code, out = rmf_shell.checked_call(cmd)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 71, in inner
> result = function(command, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 294, in _call
> raise Fail(err_msg)
> Fail: Execution of '/usr/bin/apt-get -qq check' returned 100. E: Could
> not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
> E: Unable to lock the administration directory (/var/lib/dpkg/), are you
> root?
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 469, in
> InstallPackages().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 179, in actionexecute
> raise Fail("Failed to distribute repositories/install packages")
> resource_management.core.exceptions.Fail: Failed to distribute
> repositories/install packages
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17356) Add the ability to perform interactive shell commands from Ambari server side actions
[ https://issues.apache.org/jira/browse/AMBARI-17356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346624#comment-15346624 ] Hudson commented on AMBARI-17356: - FAILURE: Integrated in Ambari-trunk-Commit #5145 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5145/]) AMBARI-17356. Add the ability to perform interactive shell commands from (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1125bb8af8d29e677fdff741c6169f33637cd7be]) * ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/KerberosOperationHandler.java * ambari-server/src/main/java/org/apache/ambari/server/utils/ShellCommandUtil.java * ambari-server/src/test/java/org/apache/ambari/server/serveraction/kerberos/MITKerberosOperationHandlerTest.java * ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/MITKerberosOperationHandler.java * ambari-server/src/test/java/org/apache/ambari/server/utils/TestShellCommandUtil.java AMBARI-17356. Add the ability to perform interactive shell commands from (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5dab212708198c544725d3747d200e7c299d36f7]) * ambari-server/src/test/resources/interactive_shell_test.sh > Add the ability to perform interactive shell commands from Ambari server side > actions > - > > Key: AMBARI-17356 > URL: https://issues.apache.org/jira/browse/AMBARI-17356 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.0.0 >Reporter: Robert Levas >Assignee: Robert Levas > Fix For: 2.4.0 > > Attachments: AMBARI-17356_branch-2.4_01.patch, > AMBARI-17356_trunk_01.patch > > > Add the ability to perform interactive shell commands from Ambari server side > actions. This will allow sensitive data, like passwords, to be sent to shell > commands via STDIN rather than on the command line. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17399) Hive llap principals are shown on Configure Identity even when Hive is not deployed
[
https://issues.apache.org/jira/browse/AMBARI-17399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346627#comment-15346627
]
Hudson commented on AMBARI-17399:
-
FAILURE: Integrated in Ambari-trunk-Commit #5145 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5145/])
AMBARI-17399. Hive llap principals are shown on Configure Identity even
(hiveww:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b83b3e274850fefcba22f330c15617375b04a325])
* ambari-web/app/utils/ajax/ajax.js
* ambari-web/app/mixins/wizard/addSecurityConfigs.js
* ambari-web/test/controllers/main/admin/kerberos/step4_controller_test.js
* ambari-web/app/controllers/main/admin/kerberos/step4_controller.js
* ambari-web/app/controllers/main/admin/kerberos.js
> Hive llap principals are shown on Configure Identity even when Hive is not
> deployed
> ---
>
> Key: AMBARI-17399
> URL: https://issues.apache.org/jira/browse/AMBARI-17399
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17399.patch,
> hive_llap_principal_and_Keytab_present_unconditionally.png
>
>
> 1. Deploy ambari cluster with YARN, HDFS, ZOOKEEPER and HBASE
> 2. enable security (AD)
> Expected: On ConfigureIdentities page hive.llap.zk.sm.principal and
> hive.llap.zk.sm.keytab.file
> should not be present if hive is not deployed on cluster.
> Actual: These 2 properties are showing under Ambari Principals panel even
> when Hive is not deployed on the cluster.
> Attached screenshot for reference.
> *Cause*
> This is caused when identities that have _when_ clauses are not filtered out
> if the when clause evaluates to {{false}} when the UI queries for the
> (composite) Kerberos Descriptor.
> *Solution*
> Use the {{evaluate_when}} and (optionally) the {{additional_services}}
> _{{GET}} directives_ to have {{when}} Kerberos descriptor identitiy {{when}}
> clauses evaluated when requesting Kerberos descriptors.
> {noformat:title=Get composite Kerberos descriptor when enabling Kerberos}
> GET
> /api/v1/clusters/CLUSTER_NAME/kerberos_descriptors/COMPOSITE?evaluate_when=true
> {noformat}
> {noformat:title=Get composite Kerberos descriptor when adding services (HIVE,
> PIG, and TEZ)}
> GET
> /api/v1/clusters/CLUSTER_NAME/kerberos_descriptors/COMPOSITE?evaluate_when=true_services=HIVE,TEZ,PIG
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17400) Ambari could not detect the spark-client that is dependency of livy
[ https://issues.apache.org/jira/browse/AMBARI-17400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346625#comment-15346625 ] Hudson commented on AMBARI-17400: - FAILURE: Integrated in Ambari-trunk-Commit #5145 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5145/]) AMBARI-17400. Ambari could not detect the spark-client that is (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=28ecf734ca1e8ac7e56801f4610956a2cd33b288]) * ambari-web/app/controllers/wizard/step8_controller.js > Ambari could not detect the spark-client that is dependency of livy > --- > > Key: AMBARI-17400 > URL: https://issues.apache.org/jira/browse/AMBARI-17400 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17400.patch > > > I install livy on machine-1, but spark-client on machine-2. Since > spark-client is dependency of livy with host scope, so it would be installed > on machine-1 too. And after installation, I do see spark-client is installed > on machine-1, but the ambari ui only show it is installed on machine-2. It > might be a bug of ambari -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17401) Service actions are available via firepath even if not visible on UI (RBAC)
[ https://issues.apache.org/jira/browse/AMBARI-17401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346628#comment-15346628 ] Hudson commented on AMBARI-17401: - FAILURE: Integrated in Ambari-trunk-Commit #5145 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5145/]) AMBARI-17401. Service actions are available via firepath even if not (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b6f022d80603567706c149b7c2b73c0bb0c23df6]) * ambari-web/app/templates/main/service/item.hbs > Service actions are available via firepath even if not visible on UI (RBAC) > --- > > Key: AMBARI-17401 > URL: https://issues.apache.org/jira/browse/AMBARI-17401 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17401.patch > > > Login as a service operator. (He is not allowed to move components) > Move to services tab, move to MapReduce service. Now with firepath search for > xpath : //a[text()='Move History Server']. Even though it is not visible, it > is accessible via UI elements. Anyone with this knowledge can run a script to > do move components to different hosts (My selenium test successfully ran for > service operator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17396) Performance issues with ambari metrics (and Metrics Collector keeps going down)
[ https://issues.apache.org/jira/browse/AMBARI-17396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-17396: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 > Performance issues with ambari metrics (and Metrics Collector keeps going > down) > --- > > Key: AMBARI-17396 > URL: https://issues.apache.org/jira/browse/AMBARI-17396 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17396_1.patch > > > Metrics widgets are taking a long time to load. Dashboard page widgets take > nearly 30 secs to completely load. > Even after progress bar indicator is stopped, it takes a couple of > secs(15-20) for actual data to show up. Attaching the screenshot. > Same kind of delay is observed in service as well as host widgets. > AMS periodically crashes with SQLTimeoutException or CallTimeoutException -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17377) Rolling Upgrade process is blocked after ambari-server/ambari-agent restart
[
https://issues.apache.org/jira/browse/AMBARI-17377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myroslav Papirkovskyi updated AMBARI-17377:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Unit test failures are unrelated.
Pushed to trunk and branch-2.4
> Rolling Upgrade process is blocked after ambari-server/ambari-agent restart
> ---
>
> Key: AMBARI-17377
> URL: https://issues.apache.org/jira/browse/AMBARI-17377
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17377.patch
>
>
> Steps to reproduce:
> # Start Rolling Upgrade.
> # Restart ambari-server or ambari-agent.
> Result: operation running during restart will be moved to skipped_failed
> status, all next - to aborted. After that it is impossible to execute retry
> or ignore and proceed:
> {code}
> {
> "status" : 400,
> "message" : "java.lang.IllegalArgumentException: Can not transition a stage
> from ABORTED to PENDING"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17402) Add new configuration property to enable skipping of INSTALL tasks for Blueprint deployments
[
https://issues.apache.org/jira/browse/AMBARI-17402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346555#comment-15346555
]
Hadoop QA commented on AMBARI-17402:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12812813/AMBARI-17402.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7512//console
This message is automatically generated.
> Add new configuration property to enable skipping of INSTALL tasks for
> Blueprint deployments
>
>
> Key: AMBARI-17402
> URL: https://issues.apache.org/jira/browse/AMBARI-17402
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17402.patch
>
>
> Add new configuration property to ambari.properties:
> 'blueprint.skip_install_tasks' to control skipping of INSTALL tasks for
> Blueprint deployments. INSTALL tasks will be skipped for non-client
> components in case packages.pre.installed & blueprint.skip_install_tasks are
> both set to true. By default blueprint.skip_install_tasks should be set to
> false.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17396) Performance issues with ambari metrics (and Metrics Collector keeps going down)
[
https://issues.apache.org/jira/browse/AMBARI-17396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346546#comment-15346546
]
Hadoop QA commented on AMBARI-17396:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12812774/AMBARI-17396_1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7510//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7510//console
This message is automatically generated.
> Performance issues with ambari metrics (and Metrics Collector keeps going
> down)
> ---
>
> Key: AMBARI-17396
> URL: https://issues.apache.org/jira/browse/AMBARI-17396
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17396_1.patch
>
>
> Metrics widgets are taking a long time to load. Dashboard page widgets take
> nearly 30 secs to completely load.
> Even after progress bar indicator is stopped, it takes a couple of
> secs(15-20) for actual data to show up. Attaching the screenshot.
> Same kind of delay is observed in service as well as host widgets.
> AMS periodically crashes with SQLTimeoutException or CallTimeoutException
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17381) AuthorizationHelperTest.testAuthName may fail due to residual SecurityContext from previously executed test cases.
[
https://issues.apache.org/jira/browse/AMBARI-17381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-17381:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit 80abd6ca68977035d40f4dea942423223beecb9d
Author: Robert Levas
Date: Thu Jun 23 10:35:20 2016 -0400
{noformat}
Committed to branch-2.4
{noformat}
commit c4efb1abf93bfa1922e928f7c7be99eee6ab596a
Author: Robert Levas
Date: Thu Jun 23 10:36:07 2016 -0400
{noformat}
> AuthorizationHelperTest.testAuthName may fail due to residual SecurityContext
> from previously executed test cases.
> ---
>
> Key: AMBARI-17381
> URL: https://issues.apache.org/jira/browse/AMBARI-17381
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17381_branch-2.4_01.patch,
> AMBARI-17381_trunk_01.patch
>
>
> {{org.apache.ambari.server.security.authorization.AuthorizationHelperTest#testAuthName}}
> may fail due to residual SecurityContext from previously executed test
> cases. The SecurityContext should be cleared before (and after) each test in
> the suite.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17311) Modify HTTP headers to follow best security practices
[ https://issues.apache.org/jira/browse/AMBARI-17311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-17311: Status: Patch Available (was: In Progress) > Modify HTTP headers to follow best security practices > - > > Key: AMBARI-17311 > URL: https://issues.apache.org/jira/browse/AMBARI-17311 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: trunk > > Attachments: AMBARI-17311.patch > > > Add the following HTTP headers to follow security best practices. > X-Content-Type-Options: nosniff > Cache-control: no-store > Pragma: no-cache -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17311) Modify HTTP headers to follow best security practices
[ https://issues.apache.org/jira/browse/AMBARI-17311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-17311: Attachment: AMBARI-17311.patch > Modify HTTP headers to follow best security practices > - > > Key: AMBARI-17311 > URL: https://issues.apache.org/jira/browse/AMBARI-17311 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: trunk > > Attachments: AMBARI-17311.patch > > > Add the following HTTP headers to follow security best practices. > X-Content-Type-Options: nosniff > Cache-control: no-store > Pragma: no-cache -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17311) Modify HTTP headers to follow best security practices
[ https://issues.apache.org/jira/browse/AMBARI-17311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-17311: Status: Open (was: Patch Available) > Modify HTTP headers to follow best security practices > - > > Key: AMBARI-17311 > URL: https://issues.apache.org/jira/browse/AMBARI-17311 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: trunk > > > Add the following HTTP headers to follow security best practices. > X-Content-Type-Options: nosniff > Cache-control: no-store > Pragma: no-cache -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17311) Modify HTTP headers to follow best security practices
[ https://issues.apache.org/jira/browse/AMBARI-17311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-17311: Attachment: (was: AMBARI-17311.patch) > Modify HTTP headers to follow best security practices > - > > Key: AMBARI-17311 > URL: https://issues.apache.org/jira/browse/AMBARI-17311 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: trunk > > > Add the following HTTP headers to follow security best practices. > X-Content-Type-Options: nosniff > Cache-control: no-store > Pragma: no-cache -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17404) RU/EU Install packages fails on non-root
[
https://issues.apache.org/jira/browse/AMBARI-17404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-17404:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.4
> RU/EU Install packages fails on non-root
>
>
> Key: AMBARI-17404
> URL: https://issues.apache.org/jira/browse/AMBARI-17404
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17404.patch
>
>
> 2016-06-23 13:39:05,672 - Could not install packages. Error: Execution of
> '/usr/bin/apt-get -qq check' returned 100. E: Could not open lock file
> /var/lib/dpkg/lock - open (13: Permission denied)
> E: Unable to lock the administration directory (/var/lib/dpkg/), are you
> root?
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 166, in actionexecute
> ret_code = self.install_packages(package_list)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 400, in install_packages
> if not verifyDependencies():
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/packages_analyzer.py",
> line 309, in verifyDependencies
> code, out = rmf_shell.checked_call(cmd)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 71, in inner
> result = function(command, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 294, in _call
> raise Fail(err_msg)
> Fail: Execution of '/usr/bin/apt-get -qq check' returned 100. E: Could
> not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
> E: Unable to lock the administration directory (/var/lib/dpkg/), are you
> root?
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 469, in
> InstallPackages().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 179, in actionexecute
> raise Fail("Failed to distribute repositories/install packages")
> resource_management.core.exceptions.Fail: Failed to distribute
> repositories/install packages
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17375) [RU/EU] According to Atlas run-book, implement upgrade for Atlas component
[ https://issues.apache.org/jira/browse/AMBARI-17375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346481#comment-15346481 ] Hudson commented on AMBARI-17375: - FAILURE: Integrated in Ambari-trunk-Commit #5144 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5144/]) AMBARI-17375. [RU/EU] According to Atlas run-book, implement upgrade for (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4ed6a3d22f832e73941102a4eb4a64bb404e0746]) * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml * ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/atlas_client.py * ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_features.json * ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.4.xml * ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py * ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.4.xml * ambari-common/src/main/python/resource_management/libraries/functions/constants.py * ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.5.xml * ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.5.xml * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml > [RU/EU] According to Atlas run-book, implement upgrade for Atlas component > -- > > Key: AMBARI-17375 > URL: https://issues.apache.org/jira/browse/AMBARI-17375 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Dmytro Grinenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17375.patch > > > We should implement upgrade for this component according to runbook from > Atlas team. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17397) Ambari-server start failed
[ https://issues.apache.org/jira/browse/AMBARI-17397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346483#comment-15346483 ] Hudson commented on AMBARI-17397: - FAILURE: Integrated in Ambari-trunk-Commit #5144 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5144/]) AMBARI-17397. Ambari-server start failed (aonishuk) (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=04de79c0888f9f0fa6914f13a2d5a49be238d765]) * ambari-server/src/main/resources/common-services/OOZIE/4.2.0.2.5/metainfo.xml * ambari-server/src/main/resources/stacks/HDP/2.5/services/OOZIE/metainfo.xml AMBARI-17397. Ambari-server start failed (aonishuk) (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=49a10f14b5fee88dd60973a1c93521370a4a4e96]) * ambari-server/src/main/resources/common-services/OOZIE/4.2.0.2.5/configuration/oozie-site.xml > Ambari-server start failed > -- > > Key: AMBARI-17397 > URL: https://issues.apache.org/jira/browse/AMBARI-17397 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-17397.patch > > > Error injecting constructor, org.apache.ambari.server.AmbariException: > Stack Definition Service at > '/var/lib/ambari-server/resources/common-services/OOZIE/4.2.0.2.5/metainfo.xml' > doesn't contain a metainfo.xml file > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17395) Capacity Scheduler View: Javascript error causing new queue creation failed in Yarn Capacity Scheduler
[ https://issues.apache.org/jira/browse/AMBARI-17395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346482#comment-15346482 ] Hudson commented on AMBARI-17395: - FAILURE: Integrated in Ambari-trunk-Commit #5144 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5144/]) AMBARI-17395. Capacity Scheduler View: Javascript error causing new (pallav.kul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cd972f01a8ee49efbcf195fd42b2ccde51de7ce0]) * contrib/views/capacity-scheduler/src/main/resources/ui/app/components/totalCapacity.js > Capacity Scheduler View: Javascript error causing new queue creation failed > in Yarn Capacity Scheduler > -- > > Key: AMBARI-17395 > URL: https://issues.apache.org/jira/browse/AMBARI-17395 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Akhil PB > Fix For: 2.4.0 > > Attachments: AMBARI-17395.1.patch > > > Steps > 1. Open the Yarn Capacity Scheduler view. > 2. Create a new queue. > The action is not complete. We are getting the Javascript error in console. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
