[jira] [Updated] (AMBARI-19914) Hive View 2.0: Go to Table manager and click on statistics, the panel does not come up
[ https://issues.apache.org/jira/browse/AMBARI-19914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-19914: -- Status: Patch Available (was: Open) > Hive View 2.0: Go to Table manager and click on statistics, the panel does > not come up > -- > > Key: AMBARI-19914 > URL: https://issues.apache.org/jira/browse/AMBARI-19914 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.0 > > Attachments: AMBARI-19914.branch-2.5.patch > > > Go to Table manager and click on statistics, the panel does not come up. > Steps to reproduce : > 1) Go to Hive view. > 2) Select table > 3) Try to view the statistics and panel does not come up. > Attaching the script used to create table. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19914) Hive View 2.0: Go to Table manager and click on statistics, the panel does not come up
[ https://issues.apache.org/jira/browse/AMBARI-19914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-19914: -- Attachment: AMBARI-19914.branch-2.5.patch > Hive View 2.0: Go to Table manager and click on statistics, the panel does > not come up > -- > > Key: AMBARI-19914 > URL: https://issues.apache.org/jira/browse/AMBARI-19914 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.0 > > Attachments: AMBARI-19914.branch-2.5.patch > > > Go to Table manager and click on statistics, the panel does not come up. > Steps to reproduce : > 1) Go to Hive view. > 2) Select table > 3) Try to view the statistics and panel does not come up. > Attaching the script used to create table. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19914) Hive View 2.0: Go to Table manager and click on statistics, the panel does not come up
DIPAYAN BHOWMICK created AMBARI-19914: - Summary: Hive View 2.0: Go to Table manager and click on statistics, the panel does not come up Key: AMBARI-19914 URL: https://issues.apache.org/jira/browse/AMBARI-19914 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: DIPAYAN BHOWMICK Assignee: DIPAYAN BHOWMICK Fix For: 2.5.0 Go to Table manager and click on statistics, the panel does not come up. Steps to reproduce : 1) Go to Hive view. 2) Select table 3) Try to view the statistics and panel does not come up. Attaching the script used to create table. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19883) Hive2 view UDF tab is blank always
[ https://issues.apache.org/jira/browse/AMBARI-19883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-19883: - Attachment: AMBARI-19883_trunk.patch > Hive2 view UDF tab is blank always > -- > > Key: AMBARI-19883 > URL: https://issues.apache.org/jira/browse/AMBARI-19883 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19883_trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19883) Hive2 view UDF tab is blank always
[ https://issues.apache.org/jira/browse/AMBARI-19883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-19883: - Attachment: (was: AMBARI-19883_trunk-v3.patch) > Hive2 view UDF tab is blank always > -- > > Key: AMBARI-19883 > URL: https://issues.apache.org/jira/browse/AMBARI-19883 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19883_trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19913) incorrect imports in hive-next view
[ https://issues.apache.org/jira/browse/AMBARI-19913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-19913: --- Status: Patch Available (was: Open) > incorrect imports in hive-next view > --- > > Key: AMBARI-19913 > URL: https://issues.apache.org/jira/browse/AMBARI-19913 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > Attachments: AMBARI-19913_branch-2.5.patch > > > due to commit in AMBARI-17501 there were 2 incorrect imports and package > declarations introduced in hive-next view. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19913) incorrect imports in hive-next view
[ https://issues.apache.org/jira/browse/AMBARI-19913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-19913: --- Attachment: AMBARI-19913_branch-2.5.patch > incorrect imports in hive-next view > --- > > Key: AMBARI-19913 > URL: https://issues.apache.org/jira/browse/AMBARI-19913 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > Attachments: AMBARI-19913_branch-2.5.patch > > > due to commit in AMBARI-17501 there were 2 incorrect imports and package > declarations introduced in hive-next view. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19913) incorrect imports in hive-next view
[ https://issues.apache.org/jira/browse/AMBARI-19913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-19913: --- Fix Version/s: 2.5.0 > incorrect imports in hive-next view > --- > > Key: AMBARI-19913 > URL: https://issues.apache.org/jira/browse/AMBARI-19913 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > > due to commit in AMBARI-17501 there were 2 incorrect imports and package > declarations introduced in hive-next view. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19913) incorrect imports in hive-next view
[ https://issues.apache.org/jira/browse/AMBARI-19913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-19913: --- Affects Version/s: 2.4.0 > incorrect imports in hive-next view > --- > > Key: AMBARI-19913 > URL: https://issues.apache.org/jira/browse/AMBARI-19913 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > > due to commit in AMBARI-17501 there were 2 incorrect imports and package > declarations introduced in hive-next view. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19913) incorrect imports in hive-next view
[ https://issues.apache.org/jira/browse/AMBARI-19913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-19913: --- Summary: incorrect imports in hive-next view (was: compilation error in hive-next view import statements) > incorrect imports in hive-next view > --- > > Key: AMBARI-19913 > URL: https://issues.apache.org/jira/browse/AMBARI-19913 > Project: Ambari > Issue Type: Bug >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > > due to commit in AMBARI-17501 there were 2 incorrect imports and package > declarations introduced in hive-next view. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19913) compilation error in hive-next view import statements
Nitiraj Singh Rathore created AMBARI-19913: -- Summary: compilation error in hive-next view import statements Key: AMBARI-19913 URL: https://issues.apache.org/jira/browse/AMBARI-19913 Project: Ambari Issue Type: Bug Reporter: Nitiraj Singh Rathore Assignee: Nitiraj Singh Rathore due to commit in AMBARI-17501 there were 2 incorrect imports and package declarations introduced in hive-next view. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19906) Ambari Log Search – Single Click Log Collection and Download.
[ https://issues.apache.org/jira/browse/AMBARI-19906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857463#comment-15857463 ] George Mathew commented on AMBARI-19906: [~afernandez] Yes the log messages are collected,organized and then compressed to a single file before moving it to HDFS > Ambari Log Search – Single Click Log Collection and Download. > - > > Key: AMBARI-19906 > URL: https://issues.apache.org/jira/browse/AMBARI-19906 > Project: Ambari > Issue Type: Story > Components: ambari-logsearch, logsearch >Affects Versions: 2.4.0, 2.4.2 >Reporter: George Mathew >Assignee: Juanjo Marron > Fix For: trunk > > Attachments: Proposal.docx, Proposal.pdf > > > Ambari Log Search can be used to download log messages for further analysis. > It lets you download log messages generated by a specific service in a > specific node in the cluster. > The challenge comes when troubleshooting several services spanning several > nodes and you want to collect all the logs, there is no simple way to click > and collect them at once. I am proposing a solution that would simplify the > current actions needed to collect logs by clicking a button. The proposed > download button will collect all the logs in the search criteria, organize > them by service, place them on HDFS and offer a download link -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-19906) Ambari Log Search – Single Click Log Collection and Download.
[ https://issues.apache.org/jira/browse/AMBARI-19906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] George Mathew reassigned AMBARI-19906: -- Assignee: George Mathew (was: Juanjo Marron) > Ambari Log Search – Single Click Log Collection and Download. > - > > Key: AMBARI-19906 > URL: https://issues.apache.org/jira/browse/AMBARI-19906 > Project: Ambari > Issue Type: Story > Components: ambari-logsearch, logsearch >Affects Versions: 2.4.0, 2.4.2 >Reporter: George Mathew >Assignee: George Mathew > Fix For: trunk > > Attachments: Proposal.docx, Proposal.pdf > > > Ambari Log Search can be used to download log messages for further analysis. > It lets you download log messages generated by a specific service in a > specific node in the cluster. > The challenge comes when troubleshooting several services spanning several > nodes and you want to collect all the logs, there is no simple way to click > and collect them at once. I am proposing a solution that would simplify the > current actions needed to collect logs by clicking a button. The proposed > download button will collect all the logs in the search criteria, organize > them by service, place them on HDFS and offer a download link -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19906) Ambari Log Search – Single Click Log Collection and Download.
[ https://issues.apache.org/jira/browse/AMBARI-19906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] George Mathew updated AMBARI-19906: --- Attachment: Proposal.pdf > Ambari Log Search – Single Click Log Collection and Download. > - > > Key: AMBARI-19906 > URL: https://issues.apache.org/jira/browse/AMBARI-19906 > Project: Ambari > Issue Type: Story > Components: ambari-logsearch, logsearch >Affects Versions: 2.4.0, 2.4.2 >Reporter: George Mathew >Assignee: Juanjo Marron > Fix For: trunk > > Attachments: Proposal.docx, Proposal.pdf > > > Ambari Log Search can be used to download log messages for further analysis. > It lets you download log messages generated by a specific service in a > specific node in the cluster. > The challenge comes when troubleshooting several services spanning several > nodes and you want to collect all the logs, there is no simple way to click > and collect them at once. I am proposing a solution that would simplify the > current actions needed to collect logs by clicking a button. The proposed > download button will collect all the logs in the search criteria, organize > them by service, place them on HDFS and offer a download link -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19906) Ambari Log Search – Single Click Log Collection and Download.
[ https://issues.apache.org/jira/browse/AMBARI-19906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857458#comment-15857458 ] Sebastian Toader commented on AMBARI-19906: --- cc [~mgergely] [~oleewere] [~rnettleton] > Ambari Log Search – Single Click Log Collection and Download. > - > > Key: AMBARI-19906 > URL: https://issues.apache.org/jira/browse/AMBARI-19906 > Project: Ambari > Issue Type: Story > Components: ambari-logsearch, logsearch >Affects Versions: 2.4.0, 2.4.2 >Reporter: George Mathew >Assignee: Juanjo Marron > Fix For: trunk > > Attachments: Proposal.docx > > > Ambari Log Search can be used to download log messages for further analysis. > It lets you download log messages generated by a specific service in a > specific node in the cluster. > The challenge comes when troubleshooting several services spanning several > nodes and you want to collect all the logs, there is no simple way to click > and collect them at once. I am proposing a solution that would simplify the > current actions needed to collect logs by clicking a button. The proposed > download button will collect all the logs in the search criteria, organize > them by service, place them on HDFS and offer a download link -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19894) HiveView2.0 : View migration not working for new hive view
[ https://issues.apache.org/jira/browse/AMBARI-19894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857425#comment-15857425 ] Hudson commented on AMBARI-19894: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #923 (See [https://builds.apache.org/job/Ambari-branch-2.5/923/]) AMBARI-19894. HiveView2.0 : View migration not working for new hive (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=24f4aa737b2620fab89873f11cecc1b9a46db23c]) * (edit) contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/DataMigrator.java * (edit) contrib/views/hive20/src/main/resources/view.xml > HiveView2.0 : View migration not working for new hive view > -- > > Key: AMBARI-19894 > URL: https://issues.apache.org/jira/browse/AMBARI-19894 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-19894_branch-2.5.patch > > > View migration not supported from Hive View 1.5.0 to 2.0.0. and 2.0.0. to > another instance of 2.0.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19908) Deploy job fails intermittent due to ambari metrics service check failure
[ https://issues.apache.org/jira/browse/AMBARI-19908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857426#comment-15857426 ] Hudson commented on AMBARI-19908: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #923 (See [https://builds.apache.org/job/Ambari-branch-2.5/923/]) AMBARI-19908 : Deploy job fails intermittent due to ambari metrics (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=69ef28cf89ee7ba61390e6a4b1d874b5eac6db2c]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py * (edit) ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_collector.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/service_check.py * (edit) ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_grafana.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py > Deploy job fails intermittent due to ambari metrics service check failure > - > > Key: AMBARI-19908 > URL: https://issues.apache.org/jira/browse/AMBARI-19908 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19908.patch > > > PROBLEM > Service check for AMS fails intermittently. > BUG > Service check was trying to use certificate file from collector conf dir even > though it can be run on any host on the cluster. Hence, file not found > exceptions were seen. > FIX > Service check will look for certificate file in Monitor conf dir since > monitors are deployed on all hosts. > Grafana script will look for certificate file in Grafana conf dir rather than > collector conf (Bug) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19894) HiveView2.0 : View migration not working for new hive view
[ https://issues.apache.org/jira/browse/AMBARI-19894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857410#comment-15857410 ] Hudson commented on AMBARI-19894: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6667 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6667/]) AMBARI-19894. HiveView2.0 : View migration not working for new hive (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1e583a8f458f961cd56c5a6d934c263bf33a098e]) * (edit) contrib/views/hive20/src/main/resources/view.xml * (edit) contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/DataMigrator.java > HiveView2.0 : View migration not working for new hive view > -- > > Key: AMBARI-19894 > URL: https://issues.apache.org/jira/browse/AMBARI-19894 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-19894_branch-2.5.patch > > > View migration not supported from Hive View 1.5.0 to 2.0.0. and 2.0.0. to > another instance of 2.0.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19908) Deploy job fails intermittent due to ambari metrics service check failure
[ https://issues.apache.org/jira/browse/AMBARI-19908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857411#comment-15857411 ] Hudson commented on AMBARI-19908: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6667 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6667/]) AMBARI-19908 : Deploy job fails intermittent due to ambari metrics (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b6d5c19892efbd63ce0bf2a2a3da906e41520342]) * (edit) ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_collector.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py * (edit) ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_grafana.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/service_check.py > Deploy job fails intermittent due to ambari metrics service check failure > - > > Key: AMBARI-19908 > URL: https://issues.apache.org/jira/browse/AMBARI-19908 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19908.patch > > > PROBLEM > Service check for AMS fails intermittently. > BUG > Service check was trying to use certificate file from collector conf dir even > though it can be run on any host on the cluster. Hence, file not found > exceptions were seen. > FIX > Service check will look for certificate file in Monitor conf dir since > monitors are deployed on all hosts. > Grafana script will look for certificate file in Grafana conf dir rather than > collector conf (Bug) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19886) Update ambari managed llap queue to set preemption policy
[
https://issues.apache.org/jira/browse/AMBARI-19886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857405#comment-15857405
]
Hadoop QA commented on AMBARI-19886:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12851443/AMBARI-19886.02.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10449//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10449//console
This message is automatically generated.
> Update ambari managed llap queue to set preemption policy
> -
>
> Key: AMBARI-19886
> URL: https://issues.apache.org/jira/browse/AMBARI-19886
> Project: Ambari
> Issue Type: Task
> Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-19886.01.patch, AMBARI-19886.02.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19912) Manage Config Group host list is not sorted
[ https://issues.apache.org/jira/browse/AMBARI-19912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19912: -- Status: Patch Available (was: Open) > Manage Config Group host list is not sorted > > > Key: AMBARI-19912 > URL: https://issues.apache.org/jira/browse/AMBARI-19912 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-19912.patch > > > The host list in the Manage Config Group popup is not sorted so it is very > difficult to see which hosts are in the group when you have a large number of > hosts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19912) Manage Config Group host list is not sorted
[ https://issues.apache.org/jira/browse/AMBARI-19912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19912: -- Attachment: AMBARI-19912.patch > Manage Config Group host list is not sorted > > > Key: AMBARI-19912 > URL: https://issues.apache.org/jira/browse/AMBARI-19912 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-19912.patch > > > The host list in the Manage Config Group popup is not sorted so it is very > difficult to see which hosts are in the group when you have a large number of > hosts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19912) Manage Config Group host list is not sorted
Richard Zang created AMBARI-19912: - Summary: Manage Config Group host list is not sorted Key: AMBARI-19912 URL: https://issues.apache.org/jira/browse/AMBARI-19912 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Richard Zang Assignee: Richard Zang Fix For: 2.5.0 The host list in the Manage Config Group popup is not sorted so it is very difficult to see which hosts are in the group when you have a large number of hosts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19894) HiveView2.0 : View migration not working for new hive view
[ https://issues.apache.org/jira/browse/AMBARI-19894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-19894: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > HiveView2.0 : View migration not working for new hive view > -- > > Key: AMBARI-19894 > URL: https://issues.apache.org/jira/browse/AMBARI-19894 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-19894_branch-2.5.patch > > > View migration not supported from Hive View 1.5.0 to 2.0.0. and 2.0.0. to > another instance of 2.0.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19911) When yarn-site.xml is changed, MapReduce related components should be required to restart
[ https://issues.apache.org/jira/browse/AMBARI-19911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuanbo Liu updated AMBARI-19911: Attachment: AMBARI-19911.001.patch > When yarn-site.xml is changed, MapReduce related components should be > required to restart > - > > Key: AMBARI-19911 > URL: https://issues.apache.org/jira/browse/AMBARI-19911 > Project: Ambari > Issue Type: Bug >Reporter: Yuanbo Liu > Attachments: AMBARI-19911.001.patch > > > Some properties in yarn-site.xml are used by MR components, such as > "yarn.admin.acl", it's a good practice to have MR restart when yarn-site.xml > is modified. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19911) When yarn-site.xml is changed, MapReduce related components should be required to restart
Yuanbo Liu created AMBARI-19911: --- Summary: When yarn-site.xml is changed, MapReduce related components should be required to restart Key: AMBARI-19911 URL: https://issues.apache.org/jira/browse/AMBARI-19911 Project: Ambari Issue Type: Bug Reporter: Yuanbo Liu Some properties in yarn-site.xml are used by MR components, such as "yarn.admin.acl", it's a good practice to have MR restart when yarn-site.xml is modified. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19905) Restrict hive interactive Tez session pool to be used for interactive execution mode
[ https://issues.apache.org/jira/browse/AMBARI-19905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857285#comment-15857285 ] Hudson commented on AMBARI-19905: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #922 (See [https://builds.apache.org/job/Ambari-branch-2.5/922/]) AMBARI-19905. Restrict hive interactive Tez session pool to be used for (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=afd70d018881e1a3bb748c310cbde22c14f2aed1]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/hive-interactive-site.xml > Restrict hive interactive Tez session pool to be used for interactive > execution mode > > > Key: AMBARI-19905 > URL: https://issues.apache.org/jira/browse/AMBARI-19905 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19905.01.patch, AMBARI-19905.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19908) Deploy job fails intermittent due to ambari metrics service check failure
[ https://issues.apache.org/jira/browse/AMBARI-19908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19908: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-2.5 and trunk. > Deploy job fails intermittent due to ambari metrics service check failure > - > > Key: AMBARI-19908 > URL: https://issues.apache.org/jira/browse/AMBARI-19908 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19908.patch > > > PROBLEM > Service check for AMS fails intermittently. > BUG > Service check was trying to use certificate file from collector conf dir even > though it can be run on any host on the cluster. Hence, file not found > exceptions were seen. > FIX > Service check will look for certificate file in Monitor conf dir since > monitors are deployed on all hosts. > Grafana script will look for certificate file in Grafana conf dir rather than > collector conf (Bug) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19902) Ambari scripts have 777 permission which is a major security concern (change came from 2.4.x)
[
https://issues.apache.org/jira/browse/AMBARI-19902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857254#comment-15857254
]
Hadoop QA commented on AMBARI-19902:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12851467/AMBARI-19902.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-agent ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10448//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10448//console
This message is automatically generated.
> Ambari scripts have 777 permission which is a major security concern (change
> came from 2.4.x)
> -
>
> Key: AMBARI-19902
> URL: https://issues.apache.org/jira/browse/AMBARI-19902
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19902.patch
>
>
> If we look at the below output these files have 777 perms :
> {code}
> [root@h1 ~]# ll /usr/lib/python2.6/site-packages/ambari_agent/HostCleanup.py
> -rwxrwxrwx. 1 root root 22471 Nov 23 07:40
> /usr/lib/python2.6/site-packages/ambari_agent/HostCleanup.py
> [root@h1 ~]# ll /var/lib/ambari-server/resources/scripts/configs.sh
> -rwxrwxrwx. 1 root root 9801 Nov 23 07:27
> /var/lib/ambari-server/resources/scripts/configs.sh
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19907) On certain actions, there's no feedback from the UI when API takes a long time to respond - not reassuring and the user is encouraged to keep triggering the same heavy
[ https://issues.apache.org/jira/browse/AMBARI-19907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19907: Status: Patch Available (was: In Progress) > On certain actions, there's no feedback from the UI when API takes a long > time to respond - not reassuring and the user is encouraged to keep > triggering the same heavy action to make the problem worse > > > Key: AMBARI-19907 > URL: https://issues.apache.org/jira/browse/AMBARI-19907 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19907.v0.branch-2.5.patch > > > On a big cluster, it takes the server a long time to process the API request > for certain operations, like "Stop All", "Start All", etc. > On a small cluster, the "background operations" popup appears within a few > seconds to acknowledge to the user that the server is working on handling the > request. > However, when the cluster gets bigger and the request API takes the server > much longer (e.g., on a 1000-node cluster, it took ~35 seconds), there's no > indication on the UI that the server received the request. This is not > reassuring to the user and the user is tempted to keep re-triggering the > action and overwhelming the server. > This problem is not just for "Start All", "Stop All". This problem actually > happens for "Stop" and "Start" of a single service as well (and likely other > places, like Hosts / Host Detail pages.) On the 1000-node cluster, this > takes about 6-7 seconds, enough to make the user wonder if the request got to > the server or not. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19893) Mark Druid as Technical Preview
[ https://issues.apache.org/jira/browse/AMBARI-19893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857237#comment-15857237 ] Hudson commented on AMBARI-19893: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit # (See [https://builds.apache.org/job/Ambari-trunk-Commit//]) AMBARI-19893. Mark Druid as Technical Preview. (Nishant Bangarwa via (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=de56092a4a46d88b0a785b0a27c74b563d9cd5a1]) * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/metainfo.xml > Mark Druid as Technical Preview > --- > > Key: AMBARI-19893 > URL: https://issues.apache.org/jira/browse/AMBARI-19893 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: ambari-19893.patch > > > Mark Druid as Technical Preview. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19378) Druid db connection check fails if user uploads connector jar manually in extension folder
[ https://issues.apache.org/jira/browse/AMBARI-19378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857235#comment-15857235 ] Hudson commented on AMBARI-19378: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit # (See [https://builds.apache.org/job/Ambari-trunk-Commit//]) AMBARI-19378. Druid db connection check fails if user uploads connector (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c99ca1254fb48a207a6759b3ba113aa859a6b0ba]) * (edit) ambari-server/src/test/python/stacks/2.6/DRUID/test_druid.py * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/druid_node.py > Druid db connection check fails if user uploads connector jar manually in > extension folder > -- > > Key: AMBARI-19378 > URL: https://issues.apache.org/jira/browse/AMBARI-19378 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19378.patch > > > If the user uploads mysql connector jar manually in druid extensions folder > with a file name different than the expected one, db connection verification > fails. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19905) Restrict hive interactive Tez session pool to be used for interactive execution mode
[ https://issues.apache.org/jira/browse/AMBARI-19905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857236#comment-15857236 ] Hudson commented on AMBARI-19905: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit # (See [https://builds.apache.org/job/Ambari-trunk-Commit//]) AMBARI-19905. Restrict hive interactive Tez session pool to be used for (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b3f63395b009f0d5c1b492ea666f61aad910da0f]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/hive-interactive-site.xml > Restrict hive interactive Tez session pool to be used for interactive > execution mode > > > Key: AMBARI-19905 > URL: https://issues.apache.org/jira/browse/AMBARI-19905 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19905.01.patch, AMBARI-19905.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19907) On certain actions, there's no feedback from the UI when API takes a long time to respond - not reassuring and the user is encouraged to keep triggering the same heavy
[ https://issues.apache.org/jira/browse/AMBARI-19907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19907: Attachment: AMBARI-19907.v0.branch-2.5.patch > On certain actions, there's no feedback from the UI when API takes a long > time to respond - not reassuring and the user is encouraged to keep > triggering the same heavy action to make the problem worse > > > Key: AMBARI-19907 > URL: https://issues.apache.org/jira/browse/AMBARI-19907 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19907.v0.branch-2.5.patch > > > On a big cluster, it takes the server a long time to process the API request > for certain operations, like "Stop All", "Start All", etc. > On a small cluster, the "background operations" popup appears within a few > seconds to acknowledge to the user that the server is working on handling the > request. > However, when the cluster gets bigger and the request API takes the server > much longer (e.g., on a 1000-node cluster, it took ~35 seconds), there's no > indication on the UI that the server received the request. This is not > reassuring to the user and the user is tempted to keep re-triggering the > action and overwhelming the server. > This problem is not just for "Start All", "Stop All". This problem actually > happens for "Stop" and "Start" of a single service as well (and likely other > places, like Hosts / Host Detail pages.) On the 1000-node cluster, this > takes about 6-7 seconds, enough to make the user wonder if the request got to > the server or not. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19910) Cannot change user passwords
Sangeeta Ravindran created AMBARI-19910: --- Summary: Cannot change user passwords Key: AMBARI-19910 URL: https://issues.apache.org/jira/browse/AMBARI-19910 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk, 2.5.0 Reporter: Sangeeta Ravindran Assignee: Sangeeta Ravindran 1. Create a user and set a password (that does not match the admin password). 2. Click on Change Password and enter the old and new passwords. 3. Click on OK. An error is displayed and you cannot change password although the current password is correct. Cannot change password org.apache.ambari.server.controller.spi.SystemException: An internal system exception occurred: Wrong current password provided This seems to happen because in modifyPassword method in Users.java we compare the current password passed in with the password of the logged in user (admin). passwordEncoder.matches(currentUserPassword, currentUserEntity.getUserPassword()) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19884) Set a higher value of num aggregated files per container - HDP stack, YARN
[ https://issues.apache.org/jira/browse/AMBARI-19884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857216#comment-15857216 ] Siddharth Seth commented on AMBARI-19884: - Yes. > Set a higher value of num aggregated files per container - HDP stack, YARN > -- > > Key: AMBARI-19884 > URL: https://issues.apache.org/jira/browse/AMBARI-19884 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19884.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19378) Druid db connection check fails if user uploads connector jar manually in extension folder
[ https://issues.apache.org/jira/browse/AMBARI-19378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857187#comment-15857187 ] Hudson commented on AMBARI-19378: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #921 (See [https://builds.apache.org/job/Ambari-branch-2.5/921/]) AMBARI-19378. Druid db connection check fails if user uploads connector (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ebec24e88baece2fd35097925c500a9d8780ea87]) * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/druid_node.py * (edit) ambari-server/src/test/python/stacks/2.6/DRUID/test_druid.py > Druid db connection check fails if user uploads connector jar manually in > extension folder > -- > > Key: AMBARI-19378 > URL: https://issues.apache.org/jira/browse/AMBARI-19378 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19378.patch > > > If the user uploads mysql connector jar manually in druid extensions folder > with a file name different than the expected one, db connection verification > fails. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19827) HiveServer2 Interactive won't start in clusters with less memory
[
https://issues.apache.org/jira/browse/AMBARI-19827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857188#comment-15857188
]
Hudson commented on AMBARI-19827:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #921 (See
[https://builds.apache.org/job/Ambari-branch-2.5/921/])
AMBARI-19827. HiveServer2 Interactive won't start in clusters with less
(sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=868b2a88455957f36cc498b94956e816d9868674])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
* (edit) ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py
> HiveServer2 Interactive won't start in clusters with less memory
>
>
> Key: AMBARI-19827
> URL: https://issues.apache.org/jira/browse/AMBARI-19827
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19827.patch
>
>
> HS2 Interactive in a 3 node local cluster with 3.5G memory in each node. The
> task fails due to this exception:
> {code:java}
> WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns
> does not exist
> WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT
> type value
> Failed: null
> java.lang.IllegalArgumentException
> at
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1307)
> at
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1230)
> at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151)
> at
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:197)
> at
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:112)
> INFO cli.LlapServiceDriver: LLAP service driver finished
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19895) Firewall check during ambari-server setup fails on CentOS7
[
https://issues.apache.org/jira/browse/AMBARI-19895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857186#comment-15857186
]
Hudson commented on AMBARI-19895:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #921 (See
[https://builds.apache.org/job/Ambari-branch-2.5/921/])
AMBARI-19895. Firewall check during ambari-server setup fails on CentOS7
(smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=383901fdec7acd9a0be1c42c97438048f7031272])
* (edit) ambari-common/src/main/python/resource_management/core/shell.py
* (edit) ambari-common/src/main/python/resource_management/core/logger.py
* (edit) ambari-common/src/main/python/ambari_commons/firewall.py
> Firewall check during ambari-server setup fails on CentOS7
> --
>
> Key: AMBARI-19895
> URL: https://issues.apache.org/jira/browse/AMBARI-19895
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
> Environment: CentOS7
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19895.patch
>
>
> {noformat:title=ambari-server setup -s}
> Using python /usr/bin/python
> Setup ambari-server
> Checking SELinux...
> SELinux status is 'disabled'
> Customize user account for ambari-server daemon [y/n] (n)?
> Adjusting ambari-server permissions and ownership...
> Checking firewall status...
> WARNING: Unable to check firewall status: 'NoneType' object has no attribute
> 'isEnabledFor'
> ERROR: Unexpected AttributeError: 'NoneType' object has no attribute 'split'
> For more info run ambari-server with -v or --verbose option
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19903) In UpgradeCatalog250.java, (1). Fix value for config "hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for config 'hive.llap.execution.mode'.
[
https://issues.apache.org/jira/browse/AMBARI-19903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857189#comment-15857189
]
Hudson commented on AMBARI-19903:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #921 (See
[https://builds.apache.org/job/Ambari-branch-2.5/921/])
AMBARI-19903. In UpgradeCatalog250.java, (1). Fix value for config (sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c25187fa6e78cb8ba5929cf805c75ad7775c0fab])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
> In UpgradeCatalog250.java, (1). Fix value for config
> "hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for
> config 'hive.llap.execution.mode'.
> ---
>
> Key: AMBARI-19903
> URL: https://issues.apache.org/jira/browse/AMBARI-19903
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19903.01.patch
>
>
> From llap-daemon logs:
> {code}
> 2017-02-07T19:59:39,800 INFO [main ()] org.apache.hadoop.hive.conf.HiveConf:
> Found configuration file
> file:/grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004/container_e10_1486481006089_0004_01_07/app/install/conf/hive-site.xml
> 2017-02-07T19:59:40,392 INFO [main ()] org.apache.hadoop.hive.llap.LlapUtil:
> Using local dirs from environment:
> /grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004
> 2017-02-07T19:59:40,394 WARN [main ()]
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon: Failed to start LLAP
> Daemon with exception
> java.lang.NumberFormatException: For input string: "only"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:492) ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:527) ~[?:1.7.0_67]
> at
> org.apache.hadoop.conf.Configuration.getInt(Configuration.java:1258)
> ~[hadoop-common-2.7.3.2.5.0.0-1245.jar:?]
> at org.apache.hadoop.hive.conf.HiveConf.getIntVar(HiveConf.java:3378)
> ~[hive-exec-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> at
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon.main(LlapDaemon.java:442)
> [hive-llap-server-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> {code}
> *Reason:* "hive.llap.daemon.rpc.port" has been updated as "only" as part of
> the upgrade code as part of fix in AMBARI-19719.
> *Fix:* Set the config value as "0".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19893) Mark Druid as Technical Preview
[ https://issues.apache.org/jira/browse/AMBARI-19893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857190#comment-15857190 ] Hudson commented on AMBARI-19893: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #921 (See [https://builds.apache.org/job/Ambari-branch-2.5/921/]) AMBARI-19893. Mark Druid as Technical Preview. (Nishant Bangarwa via (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e2cabfbfb6d95b6b4b340428d63fc6c90b04868c]) * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/metainfo.xml > Mark Druid as Technical Preview > --- > > Key: AMBARI-19893 > URL: https://issues.apache.org/jira/browse/AMBARI-19893 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: ambari-19893.patch > > > Mark Druid as Technical Preview. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19376) Support Simplified Chinese language for Ambari
[ https://issues.apache.org/jira/browse/AMBARI-19376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857185#comment-15857185 ] wuhui commented on AMBARI-19376: Hi，Did you translate the version of 2.4.0 from English to Chinese？ > Support Simplified Chinese language for Ambari > --- > > Key: AMBARI-19376 > URL: https://issues.apache.org/jira/browse/AMBARI-19376 > Project: Ambari > Issue Type: Task > Components: ambari-admin, ambari-web >Affects Versions: trunk, 2.2.1 >Reporter: xlsong > Fix For: 2.2.1 > > Attachments: AMBARI-19376-admin.patch, AMBARI-19376-web.patch, > chinesization.tar.gz > > > Translate web pages from English to Chinese for Ambari in branch-2.2.1.I do > the chinesizing work in the files of ambari-web/app/messages.js, > ambari-admin/src/main/resources/ui/admin-web/app/index.html and the > leftNavbar.html with the main.html file in the path of > ambari-admin/src/main/resources/ui/admin-web/app/views. > About more,please visit > http://www.redoop.org/apache/patch/src/master/AMBARI-19376 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19906) Ambari Log Search – Single Click Log Collection and Download.
[ https://issues.apache.org/jira/browse/AMBARI-19906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857175#comment-15857175 ] Alejandro Fernandez commented on AMBARI-19906: -- [~jmarron], this is a very useful feature. Will the tar file also be compressed? > Ambari Log Search – Single Click Log Collection and Download. > - > > Key: AMBARI-19906 > URL: https://issues.apache.org/jira/browse/AMBARI-19906 > Project: Ambari > Issue Type: Story > Components: ambari-logsearch, logsearch >Affects Versions: 2.4.0, 2.4.2 >Reporter: George Mathew >Assignee: Juanjo Marron > Fix For: trunk > > Attachments: Proposal.docx > > > Ambari Log Search can be used to download log messages for further analysis. > It lets you download log messages generated by a specific service in a > specific node in the cluster. > The challenge comes when troubleshooting several services spanning several > nodes and you want to collect all the logs, there is no simple way to click > and collect them at once. I am proposing a solution that would simplify the > current actions needed to collect logs by clicking a button. The proposed > download button will collect all the logs in the search criteria, organize > them by service, place them on HDFS and offer a download link -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19906) Ambari Log Search – Single Click Log Collection and Download.
[ https://issues.apache.org/jira/browse/AMBARI-19906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857171#comment-15857171 ] Alejandro Fernandez commented on AMBARI-19906: -- cc [~stoader], [~sumitmohanty] for input > Ambari Log Search – Single Click Log Collection and Download. > - > > Key: AMBARI-19906 > URL: https://issues.apache.org/jira/browse/AMBARI-19906 > Project: Ambari > Issue Type: Story > Components: ambari-logsearch, logsearch >Affects Versions: 2.4.0, 2.4.2 >Reporter: George Mathew >Assignee: Juanjo Marron > Fix For: trunk > > Attachments: Proposal.docx > > > Ambari Log Search can be used to download log messages for further analysis. > It lets you download log messages generated by a specific service in a > specific node in the cluster. > The challenge comes when troubleshooting several services spanning several > nodes and you want to collect all the logs, there is no simple way to click > and collect them at once. I am proposing a solution that would simplify the > current actions needed to collect logs by clicking a button. The proposed > download button will collect all the logs in the search criteria, organize > them by service, place them on HDFS and offer a download link -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19884) Set a higher value of num aggregated files per container - HDP stack, YARN
[ https://issues.apache.org/jira/browse/AMBARI-19884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857147#comment-15857147 ] Swapan Shridhar commented on AMBARI-19884: -- [~sseth] Confirming. We need this change for Ambari upgrade from 2.4 to 2.5? > Set a higher value of num aggregated files per container - HDP stack, YARN > -- > > Key: AMBARI-19884 > URL: https://issues.apache.org/jira/browse/AMBARI-19884 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19884.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19886) Update ambari managed llap queue to set preemption policy
[ https://issues.apache.org/jira/browse/AMBARI-19886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857145#comment-15857145 ] Swapan Shridhar commented on AMBARI-19886: -- Run time issue at stack-advisor.py:1638 -> elif block but no line to execute. Python UT's also fail. Please fix. [~sseth] > Update ambari managed llap queue to set preemption policy > - > > Key: AMBARI-19886 > URL: https://issues.apache.org/jira/browse/AMBARI-19886 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19886.01.patch, AMBARI-19886.02.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19905) Restrict hive interactive Tez session pool to be used for interactive execution mode
[ https://issues.apache.org/jira/browse/AMBARI-19905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19905: - Resolution: Fixed Status: Resolved (was: Patch Available) > Restrict hive interactive Tez session pool to be used for interactive > execution mode > > > Key: AMBARI-19905 > URL: https://issues.apache.org/jira/browse/AMBARI-19905 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19905.01.patch, AMBARI-19905.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19905) Restrict hive interactive Tez session pool to be used for interactive execution mode
[ https://issues.apache.org/jira/browse/AMBARI-19905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19905: - Fix Version/s: trunk Status: Patch Available (was: Reopened) > Restrict hive interactive Tez session pool to be used for interactive > execution mode > > > Key: AMBARI-19905 > URL: https://issues.apache.org/jira/browse/AMBARI-19905 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19905.01.patch, AMBARI-19905.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (AMBARI-19905) Restrict hive interactive Tez session pool to be used for interactive execution mode
[ https://issues.apache.org/jira/browse/AMBARI-19905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar reopened AMBARI-19905: -- > Restrict hive interactive Tez session pool to be used for interactive > execution mode > > > Key: AMBARI-19905 > URL: https://issues.apache.org/jira/browse/AMBARI-19905 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 2.5.0 > > Attachments: AMBARI-19905.01.patch, AMBARI-19905.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19905) Restrict hive interactive Tez session pool to be used for interactive execution mode
[ https://issues.apache.org/jira/browse/AMBARI-19905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19905: - Resolution: Fixed Status: Resolved (was: Patch Available) > Restrict hive interactive Tez session pool to be used for interactive > execution mode > > > Key: AMBARI-19905 > URL: https://issues.apache.org/jira/browse/AMBARI-19905 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 2.5.0 > > Attachments: AMBARI-19905.01.patch, AMBARI-19905.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19905) Restrict hive interactive Tez session pool to be used for interactive execution mode
[
https://issues.apache.org/jira/browse/AMBARI-19905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857133#comment-15857133
]
Swapan Shridhar commented on AMBARI-19905:
--
commit
trunk
{code}
commit b3f63395b009f0d5c1b492ea666f61aad910da0f
Author: Swapan Shridhar
Date: Tue Feb 7 16:46:13 2017 -0800
AMBARI-19905. Restrict hive interactive Tez session pool to be used for
interactive execution mode. (Sergey Shelukhin via Swapan Shridhar).
{code}
branch-2.5:
{code}
commit afd70d018881e1a3bb748c310cbde22c14f2aed1
Author: Swapan Shridhar
Date: Tue Feb 7 16:46:13 2017 -0800
AMBARI-19905. Restrict hive interactive Tez session pool to be used for
interactive execution mode. (Sergey Shelukhin via Swapan Shridhar).
{code}
> Restrict hive interactive Tez session pool to be used for interactive
> execution mode
>
>
> Key: AMBARI-19905
> URL: https://issues.apache.org/jira/browse/AMBARI-19905
> Project: Ambari
> Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Fix For: 2.5.0
>
> Attachments: AMBARI-19905.01.patch, AMBARI-19905.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19905) Restrict hive interactive Tez session pool to be used for interactive execution mode
[ https://issues.apache.org/jira/browse/AMBARI-19905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19905: - Summary: Restrict hive interactive Tez session pool to be used for interactive execution mode (was: restrict hive interactive Tez session pool to be used for interactive execution mode) > Restrict hive interactive Tez session pool to be used for interactive > execution mode > > > Key: AMBARI-19905 > URL: https://issues.apache.org/jira/browse/AMBARI-19905 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 2.5.0 > > Attachments: AMBARI-19905.01.patch, AMBARI-19905.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19905) restrict hive interactive Tez session pool to be used for interactive execution mode
[ https://issues.apache.org/jira/browse/AMBARI-19905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857124#comment-15857124 ] Swapan Shridhar commented on AMBARI-19905: -- +1 for [^AMBARI-19905.01.patch] > restrict hive interactive Tez session pool to be used for interactive > execution mode > > > Key: AMBARI-19905 > URL: https://issues.apache.org/jira/browse/AMBARI-19905 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 2.5.0 > > Attachments: AMBARI-19905.01.patch, AMBARI-19905.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19909) Export Blueprints does not contain the settings object and hence the credential store values
Madhuvanthi Radhakrishnan created AMBARI-19909: -- Summary: Export Blueprints does not contain the settings object and hence the credential store values Key: AMBARI-19909 URL: https://issues.apache.org/jira/browse/AMBARI-19909 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Madhuvanthi Radhakrishnan Assignee: Madhuvanthi Radhakrishnan Fix For: 2.5.0 Settings object is missing in Cluster blueprint -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19905) restrict hive interactive Tez session pool to be used for interactive execution mode
[ https://issues.apache.org/jira/browse/AMBARI-19905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated AMBARI-19905: -- Attachment: AMBARI-19905.01.patch Updated the patch based on [~swapanshridhar]'s feedback > restrict hive interactive Tez session pool to be used for interactive > execution mode > > > Key: AMBARI-19905 > URL: https://issues.apache.org/jira/browse/AMBARI-19905 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 2.5.0 > > Attachments: AMBARI-19905.01.patch, AMBARI-19905.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19908) Deploy job fails intermittent due to ambari metrics service check failure
[ https://issues.apache.org/jira/browse/AMBARI-19908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19908: --- Attachment: (was: AMBARI-19908.patch) > Deploy job fails intermittent due to ambari metrics service check failure > - > > Key: AMBARI-19908 > URL: https://issues.apache.org/jira/browse/AMBARI-19908 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19908.patch > > > PROBLEM > Service check for AMS fails intermittently. > BUG > Service check was trying to use certificate file from collector conf dir even > though it can be run on any host on the cluster. Hence, file not found > exceptions were seen. > FIX > Service check will look for certificate file in Monitor conf dir since > monitors are deployed on all hosts. > Grafana script will look for certificate file in Grafana conf dir rather than > collector conf (Bug) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19903) In UpgradeCatalog250.java, (1). Fix value for config "hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for config 'hive.llap.execution.mode'.
[
https://issues.apache.org/jira/browse/AMBARI-19903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857072#comment-15857072
]
Hudson commented on AMBARI-19903:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6665 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6665/])
AMBARI-19903. In UpgradeCatalog250.java, (1). Fix value for config (sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=14738859ccdffa64ba5d66a5cdf3757723826736])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
> In UpgradeCatalog250.java, (1). Fix value for config
> "hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for
> config 'hive.llap.execution.mode'.
> ---
>
> Key: AMBARI-19903
> URL: https://issues.apache.org/jira/browse/AMBARI-19903
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19903.01.patch
>
>
> From llap-daemon logs:
> {code}
> 2017-02-07T19:59:39,800 INFO [main ()] org.apache.hadoop.hive.conf.HiveConf:
> Found configuration file
> file:/grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004/container_e10_1486481006089_0004_01_07/app/install/conf/hive-site.xml
> 2017-02-07T19:59:40,392 INFO [main ()] org.apache.hadoop.hive.llap.LlapUtil:
> Using local dirs from environment:
> /grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004
> 2017-02-07T19:59:40,394 WARN [main ()]
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon: Failed to start LLAP
> Daemon with exception
> java.lang.NumberFormatException: For input string: "only"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:492) ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:527) ~[?:1.7.0_67]
> at
> org.apache.hadoop.conf.Configuration.getInt(Configuration.java:1258)
> ~[hadoop-common-2.7.3.2.5.0.0-1245.jar:?]
> at org.apache.hadoop.hive.conf.HiveConf.getIntVar(HiveConf.java:3378)
> ~[hive-exec-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> at
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon.main(LlapDaemon.java:442)
> [hive-llap-server-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> {code}
> *Reason:* "hive.llap.daemon.rpc.port" has been updated as "only" as part of
> the upgrade code as part of fix in AMBARI-19719.
> *Fix:* Set the config value as "0".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19895) Firewall check during ambari-server setup fails on CentOS7
[
https://issues.apache.org/jira/browse/AMBARI-19895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857070#comment-15857070
]
Hudson commented on AMBARI-19895:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6665 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6665/])
AMBARI-19895. Firewall check during ambari-server setup fails on CentOS7
(smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fb4fb888e6345e7ab03ea0e85325c53f1ef560d9])
* (edit) ambari-common/src/main/python/ambari_commons/firewall.py
* (edit) ambari-common/src/main/python/resource_management/core/logger.py
* (edit) ambari-common/src/main/python/resource_management/core/shell.py
> Firewall check during ambari-server setup fails on CentOS7
> --
>
> Key: AMBARI-19895
> URL: https://issues.apache.org/jira/browse/AMBARI-19895
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
> Environment: CentOS7
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19895.patch
>
>
> {noformat:title=ambari-server setup -s}
> Using python /usr/bin/python
> Setup ambari-server
> Checking SELinux...
> SELinux status is 'disabled'
> Customize user account for ambari-server daemon [y/n] (n)?
> Adjusting ambari-server permissions and ownership...
> Checking firewall status...
> WARNING: Unable to check firewall status: 'NoneType' object has no attribute
> 'isEnabledFor'
> ERROR: Unexpected AttributeError: 'NoneType' object has no attribute 'split'
> For more info run ambari-server with -v or --verbose option
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19827) HiveServer2 Interactive won't start in clusters with less memory
[
https://issues.apache.org/jira/browse/AMBARI-19827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857071#comment-15857071
]
Hudson commented on AMBARI-19827:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6665 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6665/])
AMBARI-19827. HiveServer2 Interactive won't start in clusters with less
(sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=63b68260817214285267923ed08ee9970affad30])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
* (edit) ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py
> HiveServer2 Interactive won't start in clusters with less memory
>
>
> Key: AMBARI-19827
> URL: https://issues.apache.org/jira/browse/AMBARI-19827
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19827.patch
>
>
> HS2 Interactive in a 3 node local cluster with 3.5G memory in each node. The
> task fails due to this exception:
> {code:java}
> WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns
> does not exist
> WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT
> type value
> Failed: null
> java.lang.IllegalArgumentException
> at
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1307)
> at
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1230)
> at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151)
> at
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:197)
> at
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:112)
> INFO cli.LlapServiceDriver: LLAP service driver finished
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19908) Deploy job fails intermittent due to ambari metrics service check failure
[ https://issues.apache.org/jira/browse/AMBARI-19908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19908: --- Attachment: AMBARI-19908.patch > Deploy job fails intermittent due to ambari metrics service check failure > - > > Key: AMBARI-19908 > URL: https://issues.apache.org/jira/browse/AMBARI-19908 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19908.patch > > > PROBLEM > Service check for AMS fails intermittently. > BUG > Service check was trying to use certificate file from collector conf dir even > though it can be run on any host on the cluster. Hence, file not found > exceptions were seen. > FIX > Service check will look for certificate file in Monitor conf dir since > monitors are deployed on all hosts. > Grafana script will look for certificate file in Grafana conf dir rather than > collector conf (Bug) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19908) Deploy job fails intermittent due to ambari metrics service check failure
[ https://issues.apache.org/jira/browse/AMBARI-19908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19908: --- Status: Patch Available (was: Open) > Deploy job fails intermittent due to ambari metrics service check failure > - > > Key: AMBARI-19908 > URL: https://issues.apache.org/jira/browse/AMBARI-19908 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19908.patch > > > PROBLEM > Service check for AMS fails intermittently. > BUG > Service check was trying to use certificate file from collector conf dir even > though it can be run on any host on the cluster. Hence, file not found > exceptions were seen. > FIX > Service check will look for certificate file in Monitor conf dir since > monitors are deployed on all hosts. > Grafana script will look for certificate file in Grafana conf dir rather than > collector conf (Bug) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19906) Ambari Log Search – Single Click Log Collection and Download.
[ https://issues.apache.org/jira/browse/AMBARI-19906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857062#comment-15857062 ] George Mathew commented on AMBARI-19906: I worked with [~ddimatos] , [~jmarron], [~tctruong213] and [~dili] to come up with this proposal. It will be great if [~mgergely], [~oleewere] and [~afernandez] could take a look at this document and let me know what you think. > Ambari Log Search – Single Click Log Collection and Download. > - > > Key: AMBARI-19906 > URL: https://issues.apache.org/jira/browse/AMBARI-19906 > Project: Ambari > Issue Type: Story > Components: ambari-logsearch, logsearch >Affects Versions: 2.4.0, 2.4.2 >Reporter: George Mathew >Assignee: Juanjo Marron > Fix For: trunk > > Attachments: Proposal.docx > > > Ambari Log Search can be used to download log messages for further analysis. > It lets you download log messages generated by a specific service in a > specific node in the cluster. > The challenge comes when troubleshooting several services spanning several > nodes and you want to collect all the logs, there is no simple way to click > and collect them at once. I am proposing a solution that would simplify the > current actions needed to collect logs by clicking a button. The proposed > download button will collect all the logs in the search criteria, organize > them by service, place them on HDFS and offer a download link -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19908) Deploy job fails intermittent due to ambari metrics service check failure
[ https://issues.apache.org/jira/browse/AMBARI-19908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19908: --- Attachment: AMBARI-19908.patch > Deploy job fails intermittent due to ambari metrics service check failure > - > > Key: AMBARI-19908 > URL: https://issues.apache.org/jira/browse/AMBARI-19908 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19908.patch > > > PROBLEM > Service check for AMS fails intermittently. > BUG > Service check was trying to use certificate file from collector conf dir even > though it can be run on any host on the cluster. Hence, file not found > exceptions were seen. > FIX > Service check will look for certificate file in Monitor conf dir since > monitors are deployed on all hosts. > Grafana script will look for certificate file in Grafana conf dir rather than > collector conf (Bug) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19906) Ambari Log Search – Single Click Log Collection and Download.
[ https://issues.apache.org/jira/browse/AMBARI-19906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] George Mathew updated AMBARI-19906: --- Attachment: Proposal.docx Document Explaining the architecture of the proposed functionality > Ambari Log Search – Single Click Log Collection and Download. > - > > Key: AMBARI-19906 > URL: https://issues.apache.org/jira/browse/AMBARI-19906 > Project: Ambari > Issue Type: Story > Components: ambari-logsearch, logsearch >Affects Versions: 2.4.0, 2.4.2 >Reporter: George Mathew >Assignee: Juanjo Marron > Fix For: trunk > > Attachments: Proposal.docx > > > Ambari Log Search can be used to download log messages for further analysis. > It lets you download log messages generated by a specific service in a > specific node in the cluster. > The challenge comes when troubleshooting several services spanning several > nodes and you want to collect all the logs, there is no simple way to click > and collect them at once. I am proposing a solution that would simplify the > current actions needed to collect logs by clicking a button. The proposed > download button will collect all the logs in the search criteria, organize > them by service, place them on HDFS and offer a download link -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19906) Ambari Log Search – Single Click Log Collection and Download.
[ https://issues.apache.org/jira/browse/AMBARI-19906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] George Mathew updated AMBARI-19906: --- Description: Ambari Log Search can be used to download log messages for further analysis. It lets you download log messages generated by a specific service in a specific node in the cluster. The challenge comes when troubleshooting several services spanning several nodes and you want to collect all the logs, there is no simple way to click and collect them at once. I am proposing a solution that would simplify the current actions needed to collect logs by clicking a button. The proposed download button will collect all the logs in the search criteria, organize them by service, place them on HDFS and offer a download link > Ambari Log Search – Single Click Log Collection and Download. > - > > Key: AMBARI-19906 > URL: https://issues.apache.org/jira/browse/AMBARI-19906 > Project: Ambari > Issue Type: Story > Components: ambari-logsearch, logsearch >Affects Versions: 2.4.0, 2.4.2 >Reporter: George Mathew >Assignee: Juanjo Marron > Fix For: trunk > > > Ambari Log Search can be used to download log messages for further analysis. > It lets you download log messages generated by a specific service in a > specific node in the cluster. > The challenge comes when troubleshooting several services spanning several > nodes and you want to collect all the logs, there is no simple way to click > and collect them at once. I am proposing a solution that would simplify the > current actions needed to collect logs by clicking a button. The proposed > download button will collect all the logs in the search criteria, organize > them by service, place them on HDFS and offer a download link -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19378) Druid db connection check fails if user uploads connector jar manually in extension folder
[ https://issues.apache.org/jira/browse/AMBARI-19378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19378: - Resolution: Fixed Status: Resolved (was: Patch Available) > Druid db connection check fails if user uploads connector jar manually in > extension folder > -- > > Key: AMBARI-19378 > URL: https://issues.apache.org/jira/browse/AMBARI-19378 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19378.patch > > > If the user uploads mysql connector jar manually in druid extensions folder > with a file name different than the expected one, db connection verification > fails. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19378) Druid db connection check fails if user uploads connector jar manually in extension folder
[
https://issues.apache.org/jira/browse/AMBARI-19378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857045#comment-15857045
]
Swapan Shridhar commented on AMBARI-19378:
--
commit
trunk
{code}
commit c99ca1254fb48a207a6759b3ba113aa859a6b0ba
Author: Swapan Shridhar
Date: Tue Feb 7 15:40:50 2017 -0800
AMBARI-19378. Druid db connection check fails if user uploads connector jar
manually in extension folder. ((Nishant Bangarwa via Swapan Shridhar).)
{code}
branch-2.5:
{code}
commit ebec24e88baece2fd35097925c500a9d8780ea87
Author: Swapan Shridhar
Date: Tue Feb 7 15:40:50 2017 -0800
AMBARI-19378. Druid db connection check fails if user uploads connector jar
manually in extension folder. (Nishant Bangarwa via Swapan Shridhar).
{code}
> Druid db connection check fails if user uploads connector jar manually in
> extension folder
> --
>
> Key: AMBARI-19378
> URL: https://issues.apache.org/jira/browse/AMBARI-19378
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19378.patch
>
>
> If the user uploads mysql connector jar manually in druid extensions folder
> with a file name different than the expected one, db connection verification
> fails.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19893) Mark Druid as Technical Preview
[
https://issues.apache.org/jira/browse/AMBARI-19893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857042#comment-15857042
]
Hadoop QA commented on AMBARI-19893:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12851401/ambari-19893.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10446//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10446//console
This message is automatically generated.
> Mark Druid as Technical Preview
> ---
>
> Key: AMBARI-19893
> URL: https://issues.apache.org/jira/browse/AMBARI-19893
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-19893.patch
>
>
> Mark Druid as Technical Preview.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-19908) Deploy job fails intermittent due to ambari metrics service check failure
Aravindan Vijayan created AMBARI-19908: -- Summary: Deploy job fails intermittent due to ambari metrics service check failure Key: AMBARI-19908 URL: https://issues.apache.org/jira/browse/AMBARI-19908 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.5.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Priority: Critical Fix For: 2.5.0 PROBLEM Service check for AMS fails intermittently. BUG Service check was trying to use certificate file from collector conf dir even though it can be run on any host on the cluster. Hence, file not found exceptions were seen. FIX Service check will look for certificate file in Monitor conf dir since monitors are deployed on all hosts. Grafana script will look for certificate file in Grafana conf dir rather than collector conf (Bug) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19905) restrict hive interactive Tez session pool to be used for interactive execution mode
[ https://issues.apache.org/jira/browse/AMBARI-19905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated AMBARI-19905: -- Status: Patch Available (was: Open) > restrict hive interactive Tez session pool to be used for interactive > execution mode > > > Key: AMBARI-19905 > URL: https://issues.apache.org/jira/browse/AMBARI-19905 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 2.5.0 > > Attachments: AMBARI-19905.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19905) restrict hive interactive Tez session pool to be used for interactive execution mode
[ https://issues.apache.org/jira/browse/AMBARI-19905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated AMBARI-19905: -- Attachment: AMBARI-19905.patch The patch. > restrict hive interactive Tez session pool to be used for interactive > execution mode > > > Key: AMBARI-19905 > URL: https://issues.apache.org/jira/browse/AMBARI-19905 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 2.5.0 > > Attachments: AMBARI-19905.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19907) On certain actions, there's no feedback from the UI when API takes a long time to respond - not reassuring and the user is encouraged to keep triggering the same heavy
Vivek Ratnavel Subramanian created AMBARI-19907: --- Summary: On certain actions, there's no feedback from the UI when API takes a long time to respond - not reassuring and the user is encouraged to keep triggering the same heavy action to make the problem worse Key: AMBARI-19907 URL: https://issues.apache.org/jira/browse/AMBARI-19907 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Priority: Critical Fix For: 2.5.0 On a big cluster, it takes the server a long time to process the API request for certain operations, like "Stop All", "Start All", etc. On a small cluster, the "background operations" popup appears within a few seconds to acknowledge to the user that the server is working on handling the request. However, when the cluster gets bigger and the request API takes the server much longer (e.g., on a 1000-node cluster, it took ~35 seconds), there's no indication on the UI that the server received the request. This is not reassuring to the user and the user is tempted to keep re-triggering the action and overwhelming the server. This problem is not just for "Start All", "Stop All". This problem actually happens for "Stop" and "Start" of a single service as well (and likely other places, like Hosts / Host Detail pages.) On the 1000-node cluster, this takes about 6-7 seconds, enough to make the user wonder if the request got to the server or not. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19893) Mark Druid as Technical Preview
[ https://issues.apache.org/jira/browse/AMBARI-19893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19893: - Resolution: Fixed Status: Resolved (was: Patch Available) > Mark Druid as Technical Preview > --- > > Key: AMBARI-19893 > URL: https://issues.apache.org/jira/browse/AMBARI-19893 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: ambari-19893.patch > > > Mark Druid as Technical Preview. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-19906) Ambari Log Search – Single Click Log Collection and Download.
[ https://issues.apache.org/jira/browse/AMBARI-19906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron reassigned AMBARI-19906: -- Assignee: Juanjo Marron > Ambari Log Search – Single Click Log Collection and Download. > - > > Key: AMBARI-19906 > URL: https://issues.apache.org/jira/browse/AMBARI-19906 > Project: Ambari > Issue Type: Story > Components: ambari-logsearch, logsearch >Affects Versions: 2.4.0, 2.4.2 >Reporter: George Mathew >Assignee: Juanjo Marron > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19893) Mark Druid as Technical Preview
[
https://issues.apache.org/jira/browse/AMBARI-19893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857031#comment-15857031
]
Swapan Shridhar commented on AMBARI-19893:
--
commit
trunk:
{code}
commit de56092a4a46d88b0a785b0a27c74b563d9cd5a1
Author: Swapan Shridhar
Date: Tue Feb 7 15:33:16 2017 -0800
AMBARI-19893. Mark Druid as Technical Preview. (Nishant Bangarwa via Swapan
Shridhar).
{code}
branch-2.5:
{code}
commit e2cabfbfb6d95b6b4b340428d63fc6c90b04868c
Author: Swapan Shridhar
Date: Tue Feb 7 15:33:16 2017 -0800
AMBARI-19893. Mark Druid as Technical Preview. (Nishant Bangarwa via Swapan
Shridhar).
{code}
> Mark Druid as Technical Preview
> ---
>
> Key: AMBARI-19893
> URL: https://issues.apache.org/jira/browse/AMBARI-19893
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-19893.patch
>
>
> Mark Druid as Technical Preview.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19893) Mark Druid as Technical Preview
[ https://issues.apache.org/jira/browse/AMBARI-19893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857026#comment-15857026 ] Swapan Shridhar commented on AMBARI-19893: -- +1 for the patch [^ambari-19893.patch] > Mark Druid as Technical Preview > --- > > Key: AMBARI-19893 > URL: https://issues.apache.org/jira/browse/AMBARI-19893 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: ambari-19893.patch > > > Mark Druid as Technical Preview. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-19905) restrict hive interactive Tez session pool to be used for interactive execution mode
[ https://issues.apache.org/jira/browse/AMBARI-19905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty reassigned AMBARI-19905: -- Assignee: Sergey Shelukhin > restrict hive interactive Tez session pool to be used for interactive > execution mode > > > Key: AMBARI-19905 > URL: https://issues.apache.org/jira/browse/AMBARI-19905 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19905) restrict hive interactive Tez session pool to be used for interactive execution mode
[ https://issues.apache.org/jira/browse/AMBARI-19905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19905: --- Fix Version/s: 2.5.0 > restrict hive interactive Tez session pool to be used for interactive > execution mode > > > Key: AMBARI-19905 > URL: https://issues.apache.org/jira/browse/AMBARI-19905 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19906) Ambari Log Search – Single Click Log Collection and Download.
George Mathew created AMBARI-19906: -- Summary: Ambari Log Search – Single Click Log Collection and Download. Key: AMBARI-19906 URL: https://issues.apache.org/jira/browse/AMBARI-19906 Project: Ambari Issue Type: Story Components: ambari-logsearch, logsearch Affects Versions: 2.4.0, 2.4.2 Reporter: George Mathew Fix For: trunk -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19905) restrict hive interactive Tez session pool to be used for interactive execution mode
[ https://issues.apache.org/jira/browse/AMBARI-19905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857017#comment-15857017 ] Sergey Shelukhin commented on AMBARI-19905: --- [~swapanshridhar] can you assign this to me? > restrict hive interactive Tez session pool to be used for interactive > execution mode > > > Key: AMBARI-19905 > URL: https://issues.apache.org/jira/browse/AMBARI-19905 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19905) restrict hive interactive Tez session pool to be used for interactive execution mode
Sergey Shelukhin created AMBARI-19905: - Summary: restrict hive interactive Tez session pool to be used for interactive execution mode Key: AMBARI-19905 URL: https://issues.apache.org/jira/browse/AMBARI-19905 Project: Ambari Issue Type: Bug Reporter: Sergey Shelukhin -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19895) Firewall check during ambari-server setup fails on CentOS7
[
https://issues.apache.org/jira/browse/AMBARI-19895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-19895:
---
Fix Version/s: (was: 3.0.0)
> Firewall check during ambari-server setup fails on CentOS7
> --
>
> Key: AMBARI-19895
> URL: https://issues.apache.org/jira/browse/AMBARI-19895
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
> Environment: CentOS7
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19895.patch
>
>
> {noformat:title=ambari-server setup -s}
> Using python /usr/bin/python
> Setup ambari-server
> Checking SELinux...
> SELinux status is 'disabled'
> Customize user account for ambari-server daemon [y/n] (n)?
> Adjusting ambari-server permissions and ownership...
> Checking firewall status...
> WARNING: Unable to check firewall status: 'NoneType' object has no attribute
> 'isEnabledFor'
> ERROR: Unexpected AttributeError: 'NoneType' object has no attribute 'split'
> For more info run ambari-server with -v or --verbose option
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19895) Firewall check during ambari-server setup fails on CentOS7
[
https://issues.apache.org/jira/browse/AMBARI-19895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-19895:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.5
> Firewall check during ambari-server setup fails on CentOS7
> --
>
> Key: AMBARI-19895
> URL: https://issues.apache.org/jira/browse/AMBARI-19895
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
> Environment: CentOS7
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19895.patch
>
>
> {noformat:title=ambari-server setup -s}
> Using python /usr/bin/python
> Setup ambari-server
> Checking SELinux...
> SELinux status is 'disabled'
> Customize user account for ambari-server daemon [y/n] (n)?
> Adjusting ambari-server permissions and ownership...
> Checking firewall status...
> WARNING: Unable to check firewall status: 'NoneType' object has no attribute
> 'isEnabledFor'
> ERROR: Unexpected AttributeError: 'NoneType' object has no attribute 'split'
> For more info run ambari-server with -v or --verbose option
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19827) HiveServer2 Interactive won't start in clusters with less memory
[
https://issues.apache.org/jira/browse/AMBARI-19827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856993#comment-15856993
]
Swapan Shridhar commented on AMBARI-19827:
--
commit
trunk
{code}
commit 63b68260817214285267923ed08ee9970affad30
Author: Swapan Shridhar
Date: Tue Feb 7 15:11:59 2017 -0800
AMBARI-19827. HiveServer2 Interactive won't start in clusters with less
memory.
{code}
branch-2.5:
{code}
commit 868b2a88455957f36cc498b94956e816d9868674
Author: Swapan Shridhar
Date: Tue Feb 7 15:11:59 2017 -0800
AMBARI-19827. HiveServer2 Interactive won't start in clusters with less
memory.
{code}
> HiveServer2 Interactive won't start in clusters with less memory
>
>
> Key: AMBARI-19827
> URL: https://issues.apache.org/jira/browse/AMBARI-19827
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19827.patch
>
>
> HS2 Interactive in a 3 node local cluster with 3.5G memory in each node. The
> task fails due to this exception:
> {code:java}
> WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns
> does not exist
> WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT
> type value
> Failed: null
> java.lang.IllegalArgumentException
> at
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1307)
> at
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1230)
> at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151)
> at
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:197)
> at
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:112)
> INFO cli.LlapServiceDriver: LLAP service driver finished
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19827) HiveServer2 Interactive won't start in clusters with less memory
[
https://issues.apache.org/jira/browse/AMBARI-19827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19827:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> HiveServer2 Interactive won't start in clusters with less memory
>
>
> Key: AMBARI-19827
> URL: https://issues.apache.org/jira/browse/AMBARI-19827
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19827.patch
>
>
> HS2 Interactive in a 3 node local cluster with 3.5G memory in each node. The
> task fails due to this exception:
> {code:java}
> WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns
> does not exist
> WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT
> type value
> Failed: null
> java.lang.IllegalArgumentException
> at
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1307)
> at
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1230)
> at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151)
> at
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:197)
> at
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:112)
> INFO cli.LlapServiceDriver: LLAP service driver finished
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19903) In UpgradeCatalog250.java, (1). Fix value for config "hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for config 'hive.llap.execution.mode'.
[
https://issues.apache.org/jira/browse/AMBARI-19903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19903:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> In UpgradeCatalog250.java, (1). Fix value for config
> "hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for
> config 'hive.llap.execution.mode'.
> ---
>
> Key: AMBARI-19903
> URL: https://issues.apache.org/jira/browse/AMBARI-19903
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19903.01.patch
>
>
> From llap-daemon logs:
> {code}
> 2017-02-07T19:59:39,800 INFO [main ()] org.apache.hadoop.hive.conf.HiveConf:
> Found configuration file
> file:/grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004/container_e10_1486481006089_0004_01_07/app/install/conf/hive-site.xml
> 2017-02-07T19:59:40,392 INFO [main ()] org.apache.hadoop.hive.llap.LlapUtil:
> Using local dirs from environment:
> /grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004
> 2017-02-07T19:59:40,394 WARN [main ()]
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon: Failed to start LLAP
> Daemon with exception
> java.lang.NumberFormatException: For input string: "only"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:492) ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:527) ~[?:1.7.0_67]
> at
> org.apache.hadoop.conf.Configuration.getInt(Configuration.java:1258)
> ~[hadoop-common-2.7.3.2.5.0.0-1245.jar:?]
> at org.apache.hadoop.hive.conf.HiveConf.getIntVar(HiveConf.java:3378)
> ~[hive-exec-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> at
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon.main(LlapDaemon.java:442)
> [hive-llap-server-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> {code}
> *Reason:* "hive.llap.daemon.rpc.port" has been updated as "only" as part of
> the upgrade code as part of fix in AMBARI-19719.
> *Fix:* Set the config value as "0".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19903) In UpgradeCatalog250.java, (1). Fix value for config "hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for config 'hive.llap.execution.mode'.
[
https://issues.apache.org/jira/browse/AMBARI-19903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856986#comment-15856986
]
Swapan Shridhar commented on AMBARI-19903:
--
commit
trunk:
{code}
commit 14738859ccdffa64ba5d66a5cdf3757723826736
Author: Swapan Shridhar
Date: Tue Feb 7 12:58:40 2017 -0800
AMBARI-19903. In UpgradeCatalog250.java, (1). Fix value for config
"hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for
config 'hive.llap.execution.mode'.
{code}
branch-2.5:
{code}
commit c25187fa6e78cb8ba5929cf805c75ad7775c0fab
Author: Swapan Shridhar
Date: Tue Feb 7 12:58:40 2017 -0800
AMBARI-19903. In UpgradeCatalog250.java, (1). Fix value for config
"hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for
config 'hive.llap.execution.mode'.
{code}
> In UpgradeCatalog250.java, (1). Fix value for config
> "hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for
> config 'hive.llap.execution.mode'.
> ---
>
> Key: AMBARI-19903
> URL: https://issues.apache.org/jira/browse/AMBARI-19903
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19903.01.patch
>
>
> From llap-daemon logs:
> {code}
> 2017-02-07T19:59:39,800 INFO [main ()] org.apache.hadoop.hive.conf.HiveConf:
> Found configuration file
> file:/grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004/container_e10_1486481006089_0004_01_07/app/install/conf/hive-site.xml
> 2017-02-07T19:59:40,392 INFO [main ()] org.apache.hadoop.hive.llap.LlapUtil:
> Using local dirs from environment:
> /grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004
> 2017-02-07T19:59:40,394 WARN [main ()]
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon: Failed to start LLAP
> Daemon with exception
> java.lang.NumberFormatException: For input string: "only"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:492) ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:527) ~[?:1.7.0_67]
> at
> org.apache.hadoop.conf.Configuration.getInt(Configuration.java:1258)
> ~[hadoop-common-2.7.3.2.5.0.0-1245.jar:?]
> at org.apache.hadoop.hive.conf.HiveConf.getIntVar(HiveConf.java:3378)
> ~[hive-exec-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> at
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon.main(LlapDaemon.java:442)
> [hive-llap-server-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> {code}
> *Reason:* "hive.llap.daemon.rpc.port" has been updated as "only" as part of
> the upgrade code as part of fix in AMBARI-19719.
> *Fix:* Set the config value as "0".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19831) HDP 3.0 TP - Support changed configs and scripts for YARN/MR
[ https://issues.apache.org/jira/browse/AMBARI-19831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19831: - Attachment: AMBARI-19831.patch > HDP 3.0 TP - Support changed configs and scripts for YARN/MR > > > Key: AMBARI-19831 > URL: https://issues.apache.org/jira/browse/AMBARI-19831 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > Attachments: AMBARI-19831.patch > > > In HDP 3.0, there are expected changes to configs and the startup scripts for > YARN/MR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19831) HDP 3.0 TP - Support changed configs and scripts for YARN/MR
[ https://issues.apache.org/jira/browse/AMBARI-19831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19831: - Status: Patch Available (was: Open) > HDP 3.0 TP - Support changed configs and scripts for YARN/MR > > > Key: AMBARI-19831 > URL: https://issues.apache.org/jira/browse/AMBARI-19831 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 3.0.0 > > Attachments: AMBARI-19831.patch > > > In HDP 3.0, there are expected changes to configs and the startup scripts for > YARN/MR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19894) HiveView2.0 : View migration not working for new hive view
[
https://issues.apache.org/jira/browse/AMBARI-19894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856946#comment-15856946
]
Hadoop QA commented on AMBARI-19894:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12851405/AMBARI-19894_branch-2.5.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
contrib/views/hive20
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10445//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10445//console
This message is automatically generated.
> HiveView2.0 : View migration not working for new hive view
> --
>
> Key: AMBARI-19894
> URL: https://issues.apache.org/jira/browse/AMBARI-19894
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19894_branch-2.5.patch
>
>
> View migration not supported from Hive View 1.5.0 to 2.0.0. and 2.0.0. to
> another instance of 2.0.0
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (AMBARI-17817) Storm Ambari View should use proxy for secure clusters
[ https://issues.apache.org/jira/browse/AMBARI-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani reassigned AMBARI-17817: --- Assignee: Sanket Shah (was: Sriharsha Chintalapani) > Storm Ambari View should use proxy for secure clusters > -- > > Key: AMBARI-17817 > URL: https://issues.apache.org/jira/browse/AMBARI-17817 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sanket Shah > Attachments: AMBARI-17817.patch > > > We observed that in secure cluster where ambari has SSL configured. Storm > Ambari view fails to make http calls to Storm REST API as it won't be allowed > to make calls from https origin to http destination. > When we used ambari proxy this issue resolved. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-18431) Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes.
[ https://issues.apache.org/jira/browse/AMBARI-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani reassigned AMBARI-18431: --- Assignee: Sanket Shah (was: Sriharsha Chintalapani) > Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes. > - > > Key: AMBARI-18431 > URL: https://issues.apache.org/jira/browse/AMBARI-18431 > Project: Ambari > Issue Type: Improvement >Reporter: Sriharsha Chintalapani >Assignee: Sanket Shah > Fix For: 2.5.0 > > Attachments: > 0001-Changed-topology-DAG-Fixed-Kafka-Spout-Lag-data-form.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19903) In UpgradeCatalog250.java, (1). Fix value for config "hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for config 'hive.llap.execution.mode'.
[
https://issues.apache.org/jira/browse/AMBARI-19903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856932#comment-15856932
]
Sumit Mohanty commented on AMBARI-19903:
LGTM, +1
> In UpgradeCatalog250.java, (1). Fix value for config
> "hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for
> config 'hive.llap.execution.mode'.
> ---
>
> Key: AMBARI-19903
> URL: https://issues.apache.org/jira/browse/AMBARI-19903
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19903.01.patch
>
>
> From llap-daemon logs:
> {code}
> 2017-02-07T19:59:39,800 INFO [main ()] org.apache.hadoop.hive.conf.HiveConf:
> Found configuration file
> file:/grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004/container_e10_1486481006089_0004_01_07/app/install/conf/hive-site.xml
> 2017-02-07T19:59:40,392 INFO [main ()] org.apache.hadoop.hive.llap.LlapUtil:
> Using local dirs from environment:
> /grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004
> 2017-02-07T19:59:40,394 WARN [main ()]
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon: Failed to start LLAP
> Daemon with exception
> java.lang.NumberFormatException: For input string: "only"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:492) ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:527) ~[?:1.7.0_67]
> at
> org.apache.hadoop.conf.Configuration.getInt(Configuration.java:1258)
> ~[hadoop-common-2.7.3.2.5.0.0-1245.jar:?]
> at org.apache.hadoop.hive.conf.HiveConf.getIntVar(HiveConf.java:3378)
> ~[hive-exec-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> at
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon.main(LlapDaemon.java:442)
> [hive-llap-server-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> {code}
> *Reason:* "hive.llap.daemon.rpc.port" has been updated as "only" as part of
> the upgrade code as part of fix in AMBARI-19719.
> *Fix:* Set the config value as "0".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19903) In UpgradeCatalog250.java, (1). Fix value for config "hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for config 'hive.llap.execution.mode'.
[
https://issues.apache.org/jira/browse/AMBARI-19903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856927#comment-15856927
]
Swapan Shridhar commented on AMBARI-19903:
--
Patch updated. Removed update for config "hive.llap.execution.mode" as well, as
this is for upgrade to 2.5.
CC [~sumitmohanty] | [~sseth]
> In UpgradeCatalog250.java, (1). Fix value for config
> "hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for
> config 'hive.llap.execution.mode'.
> ---
>
> Key: AMBARI-19903
> URL: https://issues.apache.org/jira/browse/AMBARI-19903
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19903.01.patch
>
>
> From llap-daemon logs:
> {code}
> 2017-02-07T19:59:39,800 INFO [main ()] org.apache.hadoop.hive.conf.HiveConf:
> Found configuration file
> file:/grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004/container_e10_1486481006089_0004_01_07/app/install/conf/hive-site.xml
> 2017-02-07T19:59:40,392 INFO [main ()] org.apache.hadoop.hive.llap.LlapUtil:
> Using local dirs from environment:
> /grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004
> 2017-02-07T19:59:40,394 WARN [main ()]
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon: Failed to start LLAP
> Daemon with exception
> java.lang.NumberFormatException: For input string: "only"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:492) ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:527) ~[?:1.7.0_67]
> at
> org.apache.hadoop.conf.Configuration.getInt(Configuration.java:1258)
> ~[hadoop-common-2.7.3.2.5.0.0-1245.jar:?]
> at org.apache.hadoop.hive.conf.HiveConf.getIntVar(HiveConf.java:3378)
> ~[hive-exec-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> at
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon.main(LlapDaemon.java:442)
> [hive-llap-server-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> {code}
> *Reason:* "hive.llap.daemon.rpc.port" has been updated as "only" as part of
> the upgrade code as part of fix in AMBARI-19719.
> *Fix:* Set the config value as "0".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19903) In UpgradeCatalog250.java, (1). Fix value for config "hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for config 'hive.llap.execution.mode'.
[
https://issues.apache.org/jira/browse/AMBARI-19903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19903:
-
Attachment: AMBARI-19903.01.patch
> In UpgradeCatalog250.java, (1). Fix value for config
> "hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for
> config 'hive.llap.execution.mode'.
> ---
>
> Key: AMBARI-19903
> URL: https://issues.apache.org/jira/browse/AMBARI-19903
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19903.01.patch
>
>
> From llap-daemon logs:
> {code}
> 2017-02-07T19:59:39,800 INFO [main ()] org.apache.hadoop.hive.conf.HiveConf:
> Found configuration file
> file:/grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004/container_e10_1486481006089_0004_01_07/app/install/conf/hive-site.xml
> 2017-02-07T19:59:40,392 INFO [main ()] org.apache.hadoop.hive.llap.LlapUtil:
> Using local dirs from environment:
> /grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004
> 2017-02-07T19:59:40,394 WARN [main ()]
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon: Failed to start LLAP
> Daemon with exception
> java.lang.NumberFormatException: For input string: "only"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:492) ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:527) ~[?:1.7.0_67]
> at
> org.apache.hadoop.conf.Configuration.getInt(Configuration.java:1258)
> ~[hadoop-common-2.7.3.2.5.0.0-1245.jar:?]
> at org.apache.hadoop.hive.conf.HiveConf.getIntVar(HiveConf.java:3378)
> ~[hive-exec-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> at
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon.main(LlapDaemon.java:442)
> [hive-llap-server-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> {code}
> *Reason:* "hive.llap.daemon.rpc.port" has been updated as "only" as part of
> the upgrade code as part of fix in AMBARI-19719.
> *Fix:* Set the config value as "0".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19903) In UpgradeCatalog250.java, (1). Fix value for config "hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for config 'hive.llap.execution.mode'.
[
https://issues.apache.org/jira/browse/AMBARI-19903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19903:
-
Status: Patch Available (was: Open)
> In UpgradeCatalog250.java, (1). Fix value for config
> "hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for
> config 'hive.llap.execution.mode'.
> ---
>
> Key: AMBARI-19903
> URL: https://issues.apache.org/jira/browse/AMBARI-19903
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19903.01.patch
>
>
> From llap-daemon logs:
> {code}
> 2017-02-07T19:59:39,800 INFO [main ()] org.apache.hadoop.hive.conf.HiveConf:
> Found configuration file
> file:/grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004/container_e10_1486481006089_0004_01_07/app/install/conf/hive-site.xml
> 2017-02-07T19:59:40,392 INFO [main ()] org.apache.hadoop.hive.llap.LlapUtil:
> Using local dirs from environment:
> /grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004
> 2017-02-07T19:59:40,394 WARN [main ()]
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon: Failed to start LLAP
> Daemon with exception
> java.lang.NumberFormatException: For input string: "only"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:492) ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:527) ~[?:1.7.0_67]
> at
> org.apache.hadoop.conf.Configuration.getInt(Configuration.java:1258)
> ~[hadoop-common-2.7.3.2.5.0.0-1245.jar:?]
> at org.apache.hadoop.hive.conf.HiveConf.getIntVar(HiveConf.java:3378)
> ~[hive-exec-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> at
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon.main(LlapDaemon.java:442)
> [hive-llap-server-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> {code}
> *Reason:* "hive.llap.daemon.rpc.port" has been updated as "only" as part of
> the upgrade code as part of fix in AMBARI-19719.
> *Fix:* Set the config value as "0".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19903) In UpgradeCatalog250.java, (1). Fix value for config "hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for config 'hive.llap.execution.mode'.
[
https://issues.apache.org/jira/browse/AMBARI-19903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19903:
-
Status: Open (was: Patch Available)
> In UpgradeCatalog250.java, (1). Fix value for config
> "hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for
> config 'hive.llap.execution.mode'.
> ---
>
> Key: AMBARI-19903
> URL: https://issues.apache.org/jira/browse/AMBARI-19903
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
>
> From llap-daemon logs:
> {code}
> 2017-02-07T19:59:39,800 INFO [main ()] org.apache.hadoop.hive.conf.HiveConf:
> Found configuration file
> file:/grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004/container_e10_1486481006089_0004_01_07/app/install/conf/hive-site.xml
> 2017-02-07T19:59:40,392 INFO [main ()] org.apache.hadoop.hive.llap.LlapUtil:
> Using local dirs from environment:
> /grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004
> 2017-02-07T19:59:40,394 WARN [main ()]
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon: Failed to start LLAP
> Daemon with exception
> java.lang.NumberFormatException: For input string: "only"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:492) ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:527) ~[?:1.7.0_67]
> at
> org.apache.hadoop.conf.Configuration.getInt(Configuration.java:1258)
> ~[hadoop-common-2.7.3.2.5.0.0-1245.jar:?]
> at org.apache.hadoop.hive.conf.HiveConf.getIntVar(HiveConf.java:3378)
> ~[hive-exec-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> at
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon.main(LlapDaemon.java:442)
> [hive-llap-server-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> {code}
> *Reason:* "hive.llap.daemon.rpc.port" has been updated as "only" as part of
> the upgrade code as part of fix in AMBARI-19719.
> *Fix:* Set the config value as "0".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19903) In UpgradeCatalog250.java, (1). Fix value for config "hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for config 'hive.llap.execution.mode'.
[
https://issues.apache.org/jira/browse/AMBARI-19903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19903:
-
Summary: In UpgradeCatalog250.java, (1). Fix value for config
"hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for
config 'hive.llap.execution.mode'. (was: Fix value for config
"hive.llap.daemon.rpc.port" to be updated as "0" in UpgradeCatalog250.java)
> In UpgradeCatalog250.java, (1). Fix value for config
> "hive.llap.daemon.rpc.port" to be updated as "0" and (2). Remove update for
> config 'hive.llap.execution.mode'.
> ---
>
> Key: AMBARI-19903
> URL: https://issues.apache.org/jira/browse/AMBARI-19903
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
>
> From llap-daemon logs:
> {code}
> 2017-02-07T19:59:39,800 INFO [main ()] org.apache.hadoop.hive.conf.HiveConf:
> Found configuration file
> file:/grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004/container_e10_1486481006089_0004_01_07/app/install/conf/hive-site.xml
> 2017-02-07T19:59:40,392 INFO [main ()] org.apache.hadoop.hive.llap.LlapUtil:
> Using local dirs from environment:
> /grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004
> 2017-02-07T19:59:40,394 WARN [main ()]
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon: Failed to start LLAP
> Daemon with exception
> java.lang.NumberFormatException: For input string: "only"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:492) ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:527) ~[?:1.7.0_67]
> at
> org.apache.hadoop.conf.Configuration.getInt(Configuration.java:1258)
> ~[hadoop-common-2.7.3.2.5.0.0-1245.jar:?]
> at org.apache.hadoop.hive.conf.HiveConf.getIntVar(HiveConf.java:3378)
> ~[hive-exec-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> at
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon.main(LlapDaemon.java:442)
> [hive-llap-server-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> {code}
> *Reason:* "hive.llap.daemon.rpc.port" has been updated as "only" as part of
> the upgrade code as part of fix in AMBARI-19719.
> *Fix:* Set the config value as "0".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19903) Fix value for config "hive.llap.daemon.rpc.port" to be updated as "0" in UpgradeCatalog250.java
[
https://issues.apache.org/jira/browse/AMBARI-19903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19903:
-
Attachment: (was: AMBARI-19903.01.patch)
> Fix value for config "hive.llap.daemon.rpc.port" to be updated as "0" in
> UpgradeCatalog250.java
> ---
>
> Key: AMBARI-19903
> URL: https://issues.apache.org/jira/browse/AMBARI-19903
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
>
> From llap-daemon logs:
> {code}
> 2017-02-07T19:59:39,800 INFO [main ()] org.apache.hadoop.hive.conf.HiveConf:
> Found configuration file
> file:/grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004/container_e10_1486481006089_0004_01_07/app/install/conf/hive-site.xml
> 2017-02-07T19:59:40,392 INFO [main ()] org.apache.hadoop.hive.llap.LlapUtil:
> Using local dirs from environment:
> /grid/0/hadoop/yarn/local/usercache/hive/appcache/application_1486481006089_0004
> 2017-02-07T19:59:40,394 WARN [main ()]
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon: Failed to start LLAP
> Daemon with exception
> java.lang.NumberFormatException: For input string: "only"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:492) ~[?:1.7.0_67]
> at java.lang.Integer.parseInt(Integer.java:527) ~[?:1.7.0_67]
> at
> org.apache.hadoop.conf.Configuration.getInt(Configuration.java:1258)
> ~[hadoop-common-2.7.3.2.5.0.0-1245.jar:?]
> at org.apache.hadoop.hive.conf.HiveConf.getIntVar(HiveConf.java:3378)
> ~[hive-exec-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> at
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon.main(LlapDaemon.java:442)
> [hive-llap-server-2.1.0.2.5.0.0-1245.jar:2.1.0.2.5.0.0-1245]
> {code}
> *Reason:* "hive.llap.daemon.rpc.port" has been updated as "only" as part of
> the upgrade code as part of fix in AMBARI-19719.
> *Fix:* Set the config value as "0".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19904) Upgrade: Package Install stuck in "Installing" state forever
[
https://issues.apache.org/jira/browse/AMBARI-19904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-19904:
--
Attachment: AMBARI-19904.v1.patch
> Upgrade: Package Install stuck in "Installing" state forever
>
>
> Key: AMBARI-19904
> URL: https://issues.apache.org/jira/browse/AMBARI-19904
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2, 2.4.1
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19904.v1.patch
>
>
> Install Packages part of the upgrade got stuck in the "Installing" state
> forever.
> Steps to reproduce:
> # Install Ambari 2.4.1 with HDP 2.4.0.0 on at least 3 hosts
># Register a repo for HDP 2.4+ or 2.5
># Modify the ambari properties "agent.package.parallel.commands.limit=1"
> and "agent.auto.cache.update=false"
># Modify
> _/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py_ such
> as the {{def install_packages}} method always returns with {{1}} on at least
> 2 agents. Also delete the
> _/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.pyo_
> file on these agents.
># Restart the agents to pick up the modified {{install_packages.py}}
># Restart ambari server
># Install bits for HDP 2.5
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
