[jira] [Updated] (AMBARI-20245) Setup tez ats related parameters
[ https://issues.apache.org/jira/browse/AMBARI-20245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated AMBARI-20245: Attachment: AMBARI-20245.modified.02.patch Uploaded a copy of Sumit's previous patch with the fix. > Setup tez ats related parameters > > > Key: AMBARI-20245 > URL: https://issues.apache.org/jira/browse/AMBARI-20245 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Siddharth Seth >Assignee: Sumit Mohanty >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20245.modified.02.patch, > AMBARI-20245.modified.patch, AMBARI-20245.patch > > > Dags per group needs to be set to 5. > TASK_ATTEMPT events to be ignored needs to be set to > |tez-interactive-site|tez.history.logging.timeline.num-dags-per-group|5| > |tez-site|tez.history.logging.timeline-cache-plugin.old-num-dags-per-group|5| > |tez-intearactive-site|tez.history.logging.taskattempt-filters|EXECUTOR_BUSY,EXTERNAL_PREEMPTION| -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20245) Setup tez ats related parameters
[ https://issues.apache.org/jira/browse/AMBARI-20245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893870#comment-15893870 ] Siddharth Seth commented on AMBARI-20245: - Provided incorrect info. EXECUTOR_BUSY,EXTERNAL_PREEMPTION was supposed to be SERVICE,EXTERNAL_PREEMPTION Sorry about that. > Setup tez ats related parameters > > > Key: AMBARI-20245 > URL: https://issues.apache.org/jira/browse/AMBARI-20245 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Siddharth Seth >Assignee: Sumit Mohanty >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20245.modified.patch, AMBARI-20245.patch > > > Dags per group needs to be set to 5. > TASK_ATTEMPT events to be ignored needs to be set to > |tez-interactive-site|tez.history.logging.timeline.num-dags-per-group|5| > |tez-site|tez.history.logging.timeline-cache-plugin.old-num-dags-per-group|5| > |tez-intearactive-site|tez.history.logging.taskattempt-filters|EXECUTOR_BUSY,EXTERNAL_PREEMPTION| -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20287) Filter in Customize Services Page doesn't bring up all properties that matches
[ https://issues.apache.org/jira/browse/AMBARI-20287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20287: -- Attachment: AMBARI-20287.patch > Filter in Customize Services Page doesn't bring up all properties that matches > -- > > Key: AMBARI-20287 > URL: https://issues.apache.org/jira/browse/AMBARI-20287 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran > Fix For: 2.5.0 > > Attachments: AMBARI-20287.patch > > > - Navigate to Add Service Wizard to Add Ranger > - At Customize Services page, change Sync Source to LDAP/AD > - try to filter out few properties like: > - Enable Group Sync, Incremental Sync etc > They are not getting filtered out. As there are multiple tabs and tabs inside > first level tabs, its not easy to find the values of these properties without > the help of filter -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20247) Show full error while importing the workflow from encrypted file
[ https://issues.apache.org/jira/browse/AMBARI-20247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M Madhan Mohan Reddy updated AMBARI-20247: -- Status: Patch Available (was: In Progress) > Show full error while importing the workflow from encrypted file > > > Key: AMBARI-20247 > URL: https://issues.apache.org/jira/browse/AMBARI-20247 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20247_trunk.patch > > > Live cluster : > https://172.22.98.248:8443/#/main/views/WORKFLOW_MANAGER/1.0.0/WFM > Facing issue while importing workflow where api > /api/v1/views/WORKFLOW_MANAGER/versions/1.0.0/instances/WFM/resources/proxy/readWorkflow?workflowPath=/user/hrt_qa/test_WfKillSubwf1/workflow.xml=WORKFLOW > is failing with 500 status code. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20247) Show full error while importing the workflow from encrypted file
[ https://issues.apache.org/jira/browse/AMBARI-20247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M Madhan Mohan Reddy updated AMBARI-20247: -- Attachment: AMBARI-20247_trunk.patch > Show full error while importing the workflow from encrypted file > > > Key: AMBARI-20247 > URL: https://issues.apache.org/jira/browse/AMBARI-20247 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20247_trunk.patch > > > Live cluster : > https://172.22.98.248:8443/#/main/views/WORKFLOW_MANAGER/1.0.0/WFM > Facing issue while importing workflow where api > /api/v1/views/WORKFLOW_MANAGER/versions/1.0.0/instances/WFM/resources/proxy/readWorkflow?workflowPath=/user/hrt_qa/test_WfKillSubwf1/workflow.xml=WORKFLOW > is failing with 500 status code. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20291) Script-Based Alert Dispathers support passing more parameters to script
[ https://issues.apache.org/jira/browse/AMBARI-20291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-20291: - Affects Version/s: trunk Status: Patch Available (was: Open) > Script-Based Alert Dispathers support passing more parameters to script > --- > > Key: AMBARI-20291 > URL: https://issues.apache.org/jira/browse/AMBARI-20291 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Yao Lei >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20291.patch > > > Script-Based Alert Dispatcher now pass five parameters to script,including > alert definition name, definition label,service name, alert state, and alert > text. > But if script can receive other two parameters from dispather,it will be > better. > 1.hostname. > Because hostname the alert for is not always included in alert text,although > it may be null like aggregate alerts. > With it we can more quick to find the related host that occured alert. > 2.alert timestamp. > We may need to know the alert occurrence time ( state change time) more > exactly. After the alert happened,it will spend some time to schedule the > script to run. > Without it,we can only regard the script start time as the alert occurrence > time. > We now use this feature to send alert information to mobile phone and suggest > also passing hostname and alert timestamp. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20291) Script-Based Alert Dispathers support passing more parameters to script
[ https://issues.apache.org/jira/browse/AMBARI-20291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-20291: - Attachment: AMBARI-20291.patch > Script-Based Alert Dispathers support passing more parameters to script > --- > > Key: AMBARI-20291 > URL: https://issues.apache.org/jira/browse/AMBARI-20291 > Project: Ambari > Issue Type: Improvement >Reporter: Yao Lei >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20291.patch > > > Script-Based Alert Dispatcher now pass five parameters to script,including > alert definition name, definition label,service name, alert state, and alert > text. > But if script can receive other two parameters from dispather,it will be > better. > 1.hostname. > Because hostname the alert for is not always included in alert text,although > it may be null like aggregate alerts. > With it we can more quick to find the related host that occured alert. > 2.alert timestamp. > We may need to know the alert occurrence time ( state change time) more > exactly. After the alert happened,it will spend some time to schedule the > script to run. > Without it,we can only regard the script start time as the alert occurrence > time. > We now use this feature to send alert information to mobile phone and suggest > also passing hostname and alert timestamp. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20208) Atlas kafka servers should be configured using kafka listeners.
[ https://issues.apache.org/jira/browse/AMBARI-20208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893795#comment-15893795 ] Hudson commented on AMBARI-20208: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6928 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6928/]) AMBARI-20208 Atlas kafka servers should be configured using kafka (mugdha: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=56af5741fa0fb7398438fe5bac2cb207c0f93df5]) * (edit) ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py * (edit) ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/application-properties.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py > Atlas kafka servers should be configured using kafka listeners. > --- > > Key: AMBARI-20208 > URL: https://issues.apache.org/jira/browse/AMBARI-20208 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-20208_1.patch, AMBARI-20208.2.patch, > AMBARI-20208.patch > > > Atlas kafka listeners should be configured to use the port value configured > in kafka-broker listeners, instead of the port property. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20208) Atlas kafka servers should be configured using kafka listeners.
[ https://issues.apache.org/jira/browse/AMBARI-20208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893788#comment-15893788 ] Hudson commented on AMBARI-20208: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1167 (See [https://builds.apache.org/job/Ambari-branch-2.5/1167/]) AMBARI-20208 Atlas kafka servers should be configured using kafka (mugdha: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=caaa6acba5d2d3ae0451ab115bc8955e774c3277]) * (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 * (edit) ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/application-properties.xml > Atlas kafka servers should be configured using kafka listeners. > --- > > Key: AMBARI-20208 > URL: https://issues.apache.org/jira/browse/AMBARI-20208 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-20208_1.patch, AMBARI-20208.2.patch, > AMBARI-20208.patch > > > Atlas kafka listeners should be configured to use the port value configured > in kafka-broker listeners, instead of the port property. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20292) Workflow manager view is not loading
Supreeth Sharma created AMBARI-20292:
Summary: Workflow manager view is not loading
Key: AMBARI-20292
URL: https://issues.apache.org/jira/browse/AMBARI-20292
Project: Ambari
Issue Type: Bug
Components: ambari-views
Affects Versions: 2.5.0
Reporter: Supreeth Sharma
Priority: Blocker
Fix For: 2.5.0
Workflow manager is not loading and I am seeing below error in UI console log
{code}
Uncaught SyntaxError: Illegal break statement
at vendor-1b1cf83….js:56
at vendor-1b1cf83….js:56
(anonymous) @ vendor-1b1cf83….js:56
(anonymous) @ vendor-1b1cf83….js:56
vendor-1b1cf83….js:1 Uncaught Error: Could not find module `ember-resolver`
imported from `oozie-designer/resolver`
at o (vendor-1b1cf83….js:1)
at a (vendor-1b1cf83….js:1)
at r.findDeps (vendor-1b1cf83….js:1)
at a (vendor-1b1cf83….js:1)
at r.findDeps (vendor-1b1cf83….js:1)
at a (vendor-1b1cf83….js:1)
at requireModule (vendor-1b1cf83….js:1)
at oozie-designer-3f49278….js:58
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20208) Atlas kafka servers should be configured using kafka listeners.
[ https://issues.apache.org/jira/browse/AMBARI-20208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-20208: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to [trunk|https://github.com/apache/ambari/commit/56af5741fa0fb7398438fe5bac2cb207c0f93df5] and [branch-2.5|https://github.com/apache/ambari/commit/caaa6acba5d2d3ae0451ab115bc8955e774c3277] > Atlas kafka servers should be configured using kafka listeners. > --- > > Key: AMBARI-20208 > URL: https://issues.apache.org/jira/browse/AMBARI-20208 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-20208_1.patch, AMBARI-20208.2.patch, > AMBARI-20208.patch > > > Atlas kafka listeners should be configured to use the port value configured > in kafka-broker listeners, instead of the port property. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20249) Stopping spark2 doesn't generate any alerts
[ https://issues.apache.org/jira/browse/AMBARI-20249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893752#comment-15893752 ] Hudson commented on AMBARI-20249: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1166 (See [https://builds.apache.org/job/Ambari-branch-2.5/1166/]) AMBARI-20249 - Stopping spark2 doesn't generate any alerts (Mingjie Tang (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=55a2ed0b02359be0c8eaca787887b2cf8741103b]) * (edit) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/alerts.json > Stopping spark2 doesn't generate any alerts > --- > > Key: AMBARI-20249 > URL: https://issues.apache.org/jira/browse/AMBARI-20249 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Shreya Bhat >Assignee: Mingjie Tang > Labels: system_test > Fix For: 2.5.0 > > Attachments: AMBARI-20249.diff > > > STR : > 1. Create cluster with spark2 > 2. Stop spark2 > Expected : An alert to signify stop of a service > Actual : No alert -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20249) Stopping spark2 doesn't generate any alerts
[ https://issues.apache.org/jira/browse/AMBARI-20249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893750#comment-15893750 ] Hudson commented on AMBARI-20249: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6927 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6927/]) AMBARI-20249 - Stopping spark2 doesn't generate any alerts (Mingjie Tang (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=69816f91037d4bc0d8e369e3a943340128df6e01]) * (edit) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/alerts.json > Stopping spark2 doesn't generate any alerts > --- > > Key: AMBARI-20249 > URL: https://issues.apache.org/jira/browse/AMBARI-20249 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Shreya Bhat >Assignee: Mingjie Tang > Labels: system_test > Fix For: 2.5.0 > > Attachments: AMBARI-20249.diff > > > STR : > 1. Create cluster with spark2 > 2. Stop spark2 > Expected : An alert to signify stop of a service > Actual : No alert -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20290) null in heapmap page
[
https://issues.apache.org/jira/browse/AMBARI-20290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893730#comment-15893730
]
Hadoop QA commented on AMBARI-20290:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12855766/screenshot-2.png
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10863//console
This message is automatically generated.
> null in heapmap page
>
>
> Key: AMBARI-20290
> URL: https://issues.apache.org/jira/browse/AMBARI-20290
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: zhangxiaolu
> Fix For: trunk
>
> Attachments: AMBARI-20290.patch, screenshot-1.png, screenshot-2.png
>
>
> drawWidget: function () {
> if (this.get('isLoaded')) {
> var hostToValueMap = this.calculateValues();
> var hostNames = [];
> if (this.get('racks').everyProperty('isLoaded', true)) {
> this.get('racks').forEach(function (rack) {
> hostNames = hostNames.concat(rack.hosts.mapProperty('hostName'));
> });
> }
> var metricObject = App.MainChartHeatmapMetric.create({
> name: this.get('content.displayName'),
> units: this.get('content.properties.display_unit'),
> maximumValue: this.get('controller.inputMaximum'),
> hostNames: hostNames,
> hostToValueMap: hostToValueMap
> });
> this.set('controller.selectedMetric', metricObject);
> App.loadTimer.finish('Heatmaps Page');
> App.loadTimer.finish('Service Heatmaps Page');
> }
> }.observes('racks.@each.isLoaded'),
> as loaded like top:
> this.get('content.displayName') is always null
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20291) Script-Based Alert Dispathers support passing more parameters to script
[ https://issues.apache.org/jira/browse/AMBARI-20291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-20291: - Summary: Script-Based Alert Dispathers support passing more parameters to script (was: Script-Based Alert Dispathers support passing more parameters to script.) > Script-Based Alert Dispathers support passing more parameters to script > --- > > Key: AMBARI-20291 > URL: https://issues.apache.org/jira/browse/AMBARI-20291 > Project: Ambari > Issue Type: Improvement >Reporter: Yao Lei >Priority: Minor > Fix For: trunk > > > Script-Based Alert Dispatcher now pass five parameters to script,including > alert definition name, definition label,service name, alert state, and alert > text. > But if script can receive other two parameters from dispather,it will be > better. > 1.hostname. > Because hostname the alert for is not always included in alert text,although > it may be null like aggregate alerts. > With it we can more quick to find the related host that occured alert. > 2.alert timestamp. > We may need to know the alert occurrence time ( state change time) more > exactly. After the alert happened,it will spend some time to schedule the > script to run. > Without it,we can only regard the script start time as the alert occurrence > time. > We now use this feature to send alert information to mobile phone and suggest > also passing hostname and alert timestamp. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20291) Script-Based Alert Dispathers support passing more parameters to script.
Yao Lei created AMBARI-20291: Summary: Script-Based Alert Dispathers support passing more parameters to script. Key: AMBARI-20291 URL: https://issues.apache.org/jira/browse/AMBARI-20291 Project: Ambari Issue Type: Improvement Reporter: Yao Lei Priority: Minor Fix For: trunk Script-Based Alert Dispatcher now pass five parameters to script,including alert definition name, definition label,service name, alert state, and alert text. But if script can receive other two parameters from dispather,it will be better. 1.hostname. Because hostname the alert for is not always included in alert text,although it may be null like aggregate alerts. With it we can more quick to find the related host that occured alert. 2.alert timestamp. We may need to know the alert occurrence time ( state change time) more exactly. After the alert happened,it will spend some time to schedule the script to run. Without it,we can only regard the script start time as the alert occurrence time. We now use this feature to send alert information to mobile phone and suggest also passing hostname and alert timestamp. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20282) Set tez task listener thread count to 1 by default for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-20282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893720#comment-15893720 ] Hudson commented on AMBARI-20282: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1165 (See [https://builds.apache.org/job/Ambari-branch-2.5/1165/]) AMBARI-20282. Set tez task listener thread count to 1 by default for (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=85f991e18ee25af5d701a89bd4e350db2def91e7]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/tez-interactive-site.xml > Set tez task listener thread count to 1 by default for hive interactive in > HDP 2.6 stack > > > Key: AMBARI-20282 > URL: https://issues.apache.org/jira/browse/AMBARI-20282 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Zhiyuan Yang >Assignee: Zhiyuan Yang > Fix For: 2.5.0 > > Attachments: AMBARI-20282.1.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20249) Stopping spark2 doesn't generate any alerts
[ https://issues.apache.org/jira/browse/AMBARI-20249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-20249: - Status: Patch Available (was: Open) > Stopping spark2 doesn't generate any alerts > --- > > Key: AMBARI-20249 > URL: https://issues.apache.org/jira/browse/AMBARI-20249 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Shreya Bhat >Assignee: Mingjie Tang > Labels: system_test > Fix For: 2.5.0 > > Attachments: AMBARI-20249.diff > > > STR : > 1. Create cluster with spark2 > 2. Stop spark2 > Expected : An alert to signify stop of a service > Actual : No alert -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20249) Stopping spark2 doesn't generate any alerts
[ https://issues.apache.org/jira/browse/AMBARI-20249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-20249: - Attachment: AMBARI-20249.diff > Stopping spark2 doesn't generate any alerts > --- > > Key: AMBARI-20249 > URL: https://issues.apache.org/jira/browse/AMBARI-20249 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Shreya Bhat >Assignee: Mingjie Tang > Labels: system_test > Fix For: 2.5.0 > > Attachments: AMBARI-20249.diff > > > STR : > 1. Create cluster with spark2 > 2. Stop spark2 > Expected : An alert to signify stop of a service > Actual : No alert -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20249) Stopping spark2 doesn't generate any alerts
[ https://issues.apache.org/jira/browse/AMBARI-20249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-20249: - Resolution: Fixed Status: Resolved (was: Patch Available) > Stopping spark2 doesn't generate any alerts > --- > > Key: AMBARI-20249 > URL: https://issues.apache.org/jira/browse/AMBARI-20249 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Shreya Bhat >Assignee: Mingjie Tang > Labels: system_test > Fix For: 2.5.0 > > Attachments: AMBARI-20249.diff > > > STR : > 1. Create cluster with spark2 > 2. Stop spark2 > Expected : An alert to signify stop of a service > Actual : No alert -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20249) Stopping spark2 doesn't generate any alerts
[ https://issues.apache.org/jira/browse/AMBARI-20249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley reassigned AMBARI-20249: Assignee: Mingjie Tang > Stopping spark2 doesn't generate any alerts > --- > > Key: AMBARI-20249 > URL: https://issues.apache.org/jira/browse/AMBARI-20249 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Shreya Bhat >Assignee: Mingjie Tang > Labels: system_test > Fix For: 2.5.0 > > > STR : > 1. Create cluster with spark2 > 2. Stop spark2 > Expected : An alert to signify stop of a service > Actual : No alert -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20282) Set tez task listener thread count to 1 by default for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-20282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893710#comment-15893710 ] Hudson commented on AMBARI-20282: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6926 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6926/]) AMBARI-20282. Set tez task listener thread count to 1 by default for (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4667e5fde179719e336ef68cd9283425cf0cea85]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/tez-interactive-site.xml > Set tez task listener thread count to 1 by default for hive interactive in > HDP 2.6 stack > > > Key: AMBARI-20282 > URL: https://issues.apache.org/jira/browse/AMBARI-20282 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Zhiyuan Yang >Assignee: Zhiyuan Yang > Fix For: 2.5.0 > > Attachments: AMBARI-20282.1.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20285) Spark2 Thrift Server stopped due to incompletely uploaded tar.gz
[
https://issues.apache.org/jira/browse/AMBARI-20285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893677#comment-15893677
]
Hadoop QA commented on AMBARI-20285:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12855722/AMBARI-20285.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/10862//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10862//console
This message is automatically generated.
> Spark2 Thrift Server stopped due to incompletely uploaded tar.gz
>
>
> Key: AMBARI-20285
> URL: https://issues.apache.org/jira/browse/AMBARI-20285
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20285.patch
>
>
> Case found by [~akhalymon].
> STR:
> # Setup ambari-agent to run as non-root user with its own group
> # Set umask=027 for ambari-agent's user
> # Deploy cluster with Spark2, including Thrift Server
> Result: Spark2 Thrift Server stops soon after being started
> This is happens because spark2-hdp-yarn-archive.tar.gz is uploaded to HDFS as
> empty file due to incorrect permissions on local source file.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20282) Set tez task listener thread count to 1 by default for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-20282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893671#comment-15893671 ] Sumit Mohanty commented on AMBARI-20282: LGTM, +1 > Set tez task listener thread count to 1 by default for hive interactive in > HDP 2.6 stack > > > Key: AMBARI-20282 > URL: https://issues.apache.org/jira/browse/AMBARI-20282 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Zhiyuan Yang >Assignee: Zhiyuan Yang > Fix For: 2.5.0 > > Attachments: AMBARI-20282.1.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20290) null in heapmap page
[
https://issues.apache.org/jira/browse/AMBARI-20290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu updated AMBARI-20290:
-
Attachment: screenshot-2.png
> null in heapmap page
>
>
> Key: AMBARI-20290
> URL: https://issues.apache.org/jira/browse/AMBARI-20290
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: zhangxiaolu
> Fix For: trunk
>
> Attachments: AMBARI-20290.patch, screenshot-1.png, screenshot-2.png
>
>
> drawWidget: function () {
> if (this.get('isLoaded')) {
> var hostToValueMap = this.calculateValues();
> var hostNames = [];
> if (this.get('racks').everyProperty('isLoaded', true)) {
> this.get('racks').forEach(function (rack) {
> hostNames = hostNames.concat(rack.hosts.mapProperty('hostName'));
> });
> }
> var metricObject = App.MainChartHeatmapMetric.create({
> name: this.get('content.displayName'),
> units: this.get('content.properties.display_unit'),
> maximumValue: this.get('controller.inputMaximum'),
> hostNames: hostNames,
> hostToValueMap: hostToValueMap
> });
> this.set('controller.selectedMetric', metricObject);
> App.loadTimer.finish('Heatmaps Page');
> App.loadTimer.finish('Service Heatmaps Page');
> }
> }.observes('racks.@each.isLoaded'),
> as loaded like top:
> this.get('content.displayName') is always null
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20290) null in heapmap page
[
https://issues.apache.org/jira/browse/AMBARI-20290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu updated AMBARI-20290:
-
Attachment: screenshot-1.png
> null in heapmap page
>
>
> Key: AMBARI-20290
> URL: https://issues.apache.org/jira/browse/AMBARI-20290
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: zhangxiaolu
> Fix For: trunk
>
> Attachments: AMBARI-20290.patch, screenshot-1.png
>
>
> drawWidget: function () {
> if (this.get('isLoaded')) {
> var hostToValueMap = this.calculateValues();
> var hostNames = [];
> if (this.get('racks').everyProperty('isLoaded', true)) {
> this.get('racks').forEach(function (rack) {
> hostNames = hostNames.concat(rack.hosts.mapProperty('hostName'));
> });
> }
> var metricObject = App.MainChartHeatmapMetric.create({
> name: this.get('content.displayName'),
> units: this.get('content.properties.display_unit'),
> maximumValue: this.get('controller.inputMaximum'),
> hostNames: hostNames,
> hostToValueMap: hostToValueMap
> });
> this.set('controller.selectedMetric', metricObject);
> App.loadTimer.finish('Heatmaps Page');
> App.loadTimer.finish('Service Heatmaps Page');
> }
> }.observes('racks.@each.isLoaded'),
> as loaded like top:
> this.get('content.displayName') is always null
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20290) null in heapmap page
[
https://issues.apache.org/jira/browse/AMBARI-20290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu updated AMBARI-20290:
-
Status: Patch Available (was: Open)
> null in heapmap page
>
>
> Key: AMBARI-20290
> URL: https://issues.apache.org/jira/browse/AMBARI-20290
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: zhangxiaolu
> Fix For: trunk
>
> Attachments: AMBARI-20290.patch
>
>
> drawWidget: function () {
> if (this.get('isLoaded')) {
> var hostToValueMap = this.calculateValues();
> var hostNames = [];
> if (this.get('racks').everyProperty('isLoaded', true)) {
> this.get('racks').forEach(function (rack) {
> hostNames = hostNames.concat(rack.hosts.mapProperty('hostName'));
> });
> }
> var metricObject = App.MainChartHeatmapMetric.create({
> name: this.get('content.displayName'),
> units: this.get('content.properties.display_unit'),
> maximumValue: this.get('controller.inputMaximum'),
> hostNames: hostNames,
> hostToValueMap: hostToValueMap
> });
> this.set('controller.selectedMetric', metricObject);
> App.loadTimer.finish('Heatmaps Page');
> App.loadTimer.finish('Service Heatmaps Page');
> }
> }.observes('racks.@each.isLoaded'),
> as loaded like top:
> this.get('content.displayName') is always null
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20290) null in heapmap page
[
https://issues.apache.org/jira/browse/AMBARI-20290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu updated AMBARI-20290:
-
Attachment: AMBARI-20290.patch
> null in heapmap page
>
>
> Key: AMBARI-20290
> URL: https://issues.apache.org/jira/browse/AMBARI-20290
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: zhangxiaolu
> Fix For: trunk
>
> Attachments: AMBARI-20290.patch
>
>
> drawWidget: function () {
> if (this.get('isLoaded')) {
> var hostToValueMap = this.calculateValues();
> var hostNames = [];
> if (this.get('racks').everyProperty('isLoaded', true)) {
> this.get('racks').forEach(function (rack) {
> hostNames = hostNames.concat(rack.hosts.mapProperty('hostName'));
> });
> }
> var metricObject = App.MainChartHeatmapMetric.create({
> name: this.get('content.displayName'),
> units: this.get('content.properties.display_unit'),
> maximumValue: this.get('controller.inputMaximum'),
> hostNames: hostNames,
> hostToValueMap: hostToValueMap
> });
> this.set('controller.selectedMetric', metricObject);
> App.loadTimer.finish('Heatmaps Page');
> App.loadTimer.finish('Service Heatmaps Page');
> }
> }.observes('racks.@each.isLoaded'),
> as loaded like top:
> this.get('content.displayName') is always null
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20290) null in heapmap page
zhangxiaolu created AMBARI-20290:
Summary: null in heapmap page
Key: AMBARI-20290
URL: https://issues.apache.org/jira/browse/AMBARI-20290
Project: Ambari
Issue Type: Bug
Affects Versions: trunk
Reporter: zhangxiaolu
Fix For: trunk
drawWidget: function () {
if (this.get('isLoaded')) {
var hostToValueMap = this.calculateValues();
var hostNames = [];
if (this.get('racks').everyProperty('isLoaded', true)) {
this.get('racks').forEach(function (rack) {
hostNames = hostNames.concat(rack.hosts.mapProperty('hostName'));
});
}
var metricObject = App.MainChartHeatmapMetric.create({
name: this.get('content.displayName'),
units: this.get('content.properties.display_unit'),
maximumValue: this.get('controller.inputMaximum'),
hostNames: hostNames,
hostToValueMap: hostToValueMap
});
this.set('controller.selectedMetric', metricObject);
App.loadTimer.finish('Heatmaps Page');
App.loadTimer.finish('Service Heatmaps Page');
}
}.observes('racks.@each.isLoaded'),
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20290) null in heapmap page
[
https://issues.apache.org/jira/browse/AMBARI-20290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu updated AMBARI-20290:
-
Description:
drawWidget: function () {
if (this.get('isLoaded')) {
var hostToValueMap = this.calculateValues();
var hostNames = [];
if (this.get('racks').everyProperty('isLoaded', true)) {
this.get('racks').forEach(function (rack) {
hostNames = hostNames.concat(rack.hosts.mapProperty('hostName'));
});
}
var metricObject = App.MainChartHeatmapMetric.create({
name: this.get('content.displayName'),
units: this.get('content.properties.display_unit'),
maximumValue: this.get('controller.inputMaximum'),
hostNames: hostNames,
hostToValueMap: hostToValueMap
});
this.set('controller.selectedMetric', metricObject);
App.loadTimer.finish('Heatmaps Page');
App.loadTimer.finish('Service Heatmaps Page');
}
}.observes('racks.@each.isLoaded'),
as loaded like top:
this.get('content.displayName') is always null
was:
drawWidget: function () {
if (this.get('isLoaded')) {
var hostToValueMap = this.calculateValues();
var hostNames = [];
if (this.get('racks').everyProperty('isLoaded', true)) {
this.get('racks').forEach(function (rack) {
hostNames = hostNames.concat(rack.hosts.mapProperty('hostName'));
});
}
var metricObject = App.MainChartHeatmapMetric.create({
name: this.get('content.displayName'),
units: this.get('content.properties.display_unit'),
maximumValue: this.get('controller.inputMaximum'),
hostNames: hostNames,
hostToValueMap: hostToValueMap
});
this.set('controller.selectedMetric', metricObject);
App.loadTimer.finish('Heatmaps Page');
App.loadTimer.finish('Service Heatmaps Page');
}
}.observes('racks.@each.isLoaded'),
> null in heapmap page
>
>
> Key: AMBARI-20290
> URL: https://issues.apache.org/jira/browse/AMBARI-20290
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: zhangxiaolu
> Fix For: trunk
>
>
> drawWidget: function () {
> if (this.get('isLoaded')) {
> var hostToValueMap = this.calculateValues();
> var hostNames = [];
> if (this.get('racks').everyProperty('isLoaded', true)) {
> this.get('racks').forEach(function (rack) {
> hostNames = hostNames.concat(rack.hosts.mapProperty('hostName'));
> });
> }
> var metricObject = App.MainChartHeatmapMetric.create({
> name: this.get('content.displayName'),
> units: this.get('content.properties.display_unit'),
> maximumValue: this.get('controller.inputMaximum'),
> hostNames: hostNames,
> hostToValueMap: hostToValueMap
> });
> this.set('controller.selectedMetric', metricObject);
> App.loadTimer.finish('Heatmaps Page');
> App.loadTimer.finish('Service Heatmaps Page');
> }
> }.observes('racks.@each.isLoaded'),
> as loaded like top:
> this.get('content.displayName') is always null
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20180) HDFS SecurityLogger messages are logged twice
[
https://issues.apache.org/jira/browse/AMBARI-20180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893634#comment-15893634
]
Hadoop QA commented on AMBARI-20180:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12855723/AMBARI-20180.01.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/10861//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10861//console
This message is automatically generated.
> HDFS SecurityLogger messages are logged twice
> -
>
> Key: AMBARI-20180
> URL: https://issues.apache.org/jira/browse/AMBARI-20180
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.0
>Reporter: Arpit Agarwal
>Assignee: Arpit Agarwal
> Fix For: 2.5.0
>
> Attachments: AMBARI-20180.01.patch
>
>
> HDFS SecurityLogger messages are logged twice, once each in the
> SecurityAuth.audit log and the NameNode service log.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20151) Add extra Tez logging configs for Hive
[ https://issues.apache.org/jira/browse/AMBARI-20151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893626#comment-15893626 ] Hudson commented on AMBARI-20151: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6925 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6925/]) AMBARI-20151. Add extra Tez logging configs for Hive (Sergey Shelukhin (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5aae5d0276a7d4d54922794acaed2828049a446c]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/llap-daemon-log4j.xml > Add extra Tez logging configs for Hive > -- > > Key: AMBARI-20151 > URL: https://issues.apache.org/jira/browse/AMBARI-20151 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 2.5.0 > > Attachments: AMBARI-20151.01.patch, AMBARI-20151.02.patch, > AMBARI-20151.03.patch, AMBARI-20151.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20151) Add extra Tez logging configs for Hive
[ https://issues.apache.org/jira/browse/AMBARI-20151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893625#comment-15893625 ] Sergey Shelukhin commented on AMBARI-20151: --- Thanks! > Add extra Tez logging configs for Hive > -- > > Key: AMBARI-20151 > URL: https://issues.apache.org/jira/browse/AMBARI-20151 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 2.5.0 > > Attachments: AMBARI-20151.01.patch, AMBARI-20151.02.patch, > AMBARI-20151.03.patch, AMBARI-20151.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20151) Add extra Tez logging configs for Hive
[ https://issues.apache.org/jira/browse/AMBARI-20151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893615#comment-15893615 ] Hudson commented on AMBARI-20151: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1164 (See [https://builds.apache.org/job/Ambari-branch-2.5/1164/]) AMBARI-20151. Add extra Tez logging configs for Hive (Sergey Shelukhin (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=acd8aef9137cacaa5f8021815df4661a11d8f2f3]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/llap-daemon-log4j.xml > Add extra Tez logging configs for Hive > -- > > Key: AMBARI-20151 > URL: https://issues.apache.org/jira/browse/AMBARI-20151 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 2.5.0 > > Attachments: AMBARI-20151.01.patch, AMBARI-20151.02.patch, > AMBARI-20151.03.patch, AMBARI-20151.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20288) Cluster deployment using blueprint with empty configuration doesn't work with stack advisor enabled
[
https://issues.apache.org/jira/browse/AMBARI-20288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893599#comment-15893599
]
Hadoop QA commented on AMBARI-20288:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12855745/AMBARI-20288.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10859//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10859//console
This message is automatically generated.
> Cluster deployment using blueprint with empty configuration doesn't work with
> stack advisor enabled
> ---
>
> Key: AMBARI-20288
> URL: https://issues.apache.org/jira/browse/AMBARI-20288
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, blueprints
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-20288.patch
>
>
> When a blueprint deployment is made with empty configuration for a particular
> config-type and when stack advisor is returning a ValueAttributeInfo for for
> that config-type with a property marked "true" for "Delete" flag
> Cluster deployment gets stuck at TOPOLOGY_RESOLUTION phase showing message
> Config type not resolved yet, Blueprint deployment will wait until
> configuration update is completed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20279) HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only if it exists in hive-interactive-site.
[ https://issues.apache.org/jira/browse/AMBARI-20279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893585#comment-15893585 ] Hudson commented on AMBARI-20279: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6924 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6924/]) AMBARI-20279. HiveServerInteractive. Set value for (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1142b526195feced7b42c82119220e065d56e24b]) * (edit) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/service_advisor.py * (edit) ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py > HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only > if it exists in hive-interactive-site. > -- > > Key: AMBARI-20279 > URL: https://issues.apache.org/jira/browse/AMBARI-20279 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20279.branch-2.5.patch, > AMBARI-20279.trunk.01.patch > > > Given that "num_llap_nodes_for_llap_daemons" only exists in 2.6 HDP stack, > there can be a scenario where "num_llap_nodes_for_llap_daemons" doesnt exist > in hive-interactive-site. This can happen if we upgrade from Ambari 2.4 (with > HDP 2.5) to Ambari 2.5. > *Fix:* Set this config in SA only if it present in hive-interactive-env. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20279) HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only if it exists in hive-interactive-site.
[ https://issues.apache.org/jira/browse/AMBARI-20279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893576#comment-15893576 ] Hudson commented on AMBARI-20279: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1163 (See [https://builds.apache.org/job/Ambari-branch-2.5/1163/]) AMBARI-20279. HiveServerInteractive. Set value for (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6ef4707077f20ae068ed1c94106a5242006d9f10]) * (edit) ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py > HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only > if it exists in hive-interactive-site. > -- > > Key: AMBARI-20279 > URL: https://issues.apache.org/jira/browse/AMBARI-20279 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20279.branch-2.5.patch, > AMBARI-20279.trunk.01.patch > > > Given that "num_llap_nodes_for_llap_daemons" only exists in 2.6 HDP stack, > there can be a scenario where "num_llap_nodes_for_llap_daemons" doesnt exist > in hive-interactive-site. This can happen if we upgrade from Ambari 2.4 (with > HDP 2.5) to Ambari 2.5. > *Fix:* Set this config in SA only if it present in hive-interactive-env. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20289) Optional host_group can interfere with blueprint deployment
[
https://issues.apache.org/jira/browse/AMBARI-20289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang updated AMBARI-20289:
---
Summary: Optional host_group can interfere with blueprint deployment (was:
Optional host_group can interfere with actual deployment)
> Optional host_group can interfere with blueprint deployment
> ---
>
> Key: AMBARI-20289
> URL: https://issues.apache.org/jira/browse/AMBARI-20289
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: 2.4.2
>Reporter: Eric Yang
>
> User defines a blueprint that contains 4 host groups. Edge group, management
> group 1 and 2, and worker group. For management group 1, include a single
> knox server. In edge group, also define Knox server. When edge group
> includes one or more hosts, they will be used for Knox Server HA. Without
> edge group, management group 1 will be used as a single Knox server.
> When edge group does not contain any host, Ambari throws a weird exception:
> {code}
> 26 Feb 2017 19:14:55,108 WARN [pool-16-thread-1]
> BlueprintConfigurationProcessor:1403 - The property
> 'dfs.namenode.secondary.http-address' is associated with the component
> 'SECONDARY_NAMENODE' which isn't mapped to any host group. This may affect
> configuration topology resolution.
> 26 Feb 2017 19:14:55,129 INFO [pool-3-thread-1] AsyncCallableService:111 -
> Exception during task execution:
> java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at
> org.apache.ambari.server.topology.AsyncCallableService.taskCompleted(AsyncCallableService.java:103)
> at
> org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:74)
> at
> org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:37)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException:
> TopologyManager.ConfigureClusterTask - prerequisites for config request
> processing not yet satisfied
> at
> org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:908)
> at
> org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:889)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> ... 3 more
> {code}
> HDFS does not get formatted. There is a 30 minutes delay between submit
> cluster construction REST request, and Ambari start to install the cluster.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20289) Optional host_group can interfere with actual deployment
Eric Yang created AMBARI-20289:
--
Summary: Optional host_group can interfere with actual deployment
Key: AMBARI-20289
URL: https://issues.apache.org/jira/browse/AMBARI-20289
Project: Ambari
Issue Type: Improvement
Affects Versions: 2.4.2
Reporter: Eric Yang
User defines a blueprint that contains 4 host groups. Edge group, management
group 1 and 2, and worker group. For management group 1, include a single knox
server. In edge group, also define Knox server. When edge group includes one
or more hosts, they will be used for Knox Server HA. Without edge group,
management group 1 will be used as a single Knox server.
When edge group does not contain any host, Ambari throws a weird exception:
{code}
26 Feb 2017 19:14:55,108 WARN [pool-16-thread-1]
BlueprintConfigurationProcessor:1403 - The property
'dfs.namenode.secondary.http-address' is associated with the component
'SECONDARY_NAMENODE' which isn't mapped to any host group. This may affect
configuration topology resolution.
26 Feb 2017 19:14:55,129 INFO [pool-3-thread-1] AsyncCallableService:111 -
Exception during task execution:
java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException:
TopologyManager.ConfigureClusterTask - prerequisites for config request
processing not yet satisfied
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:206)
at
org.apache.ambari.server.topology.AsyncCallableService.taskCompleted(AsyncCallableService.java:103)
at
org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:74)
at
org.apache.ambari.server.topology.AsyncCallableService.call(AsyncCallableService.java:37)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException:
TopologyManager.ConfigureClusterTask - prerequisites for config request
processing not yet satisfied
at
org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:908)
at
org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:889)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
... 3 more
{code}
HDFS does not get formatted. There is a 30 minutes delay between submit
cluster construction REST request, and Ambari start to install the cluster.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20151) Add extra Tez logging configs for Hive
[ https://issues.apache.org/jira/browse/AMBARI-20151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20151: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 with patch "AMBARI-20151.03.patch" > Add extra Tez logging configs for Hive > -- > > Key: AMBARI-20151 > URL: https://issues.apache.org/jira/browse/AMBARI-20151 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 2.5.0 > > Attachments: AMBARI-20151.01.patch, AMBARI-20151.02.patch, > AMBARI-20151.03.patch, AMBARI-20151.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20151) Add extra Tez logging configs for Hive
[ https://issues.apache.org/jira/browse/AMBARI-20151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20151: --- Summary: Add extra Tez logging configs for Hive (was: add extra Tez logging configs for Hive) > Add extra Tez logging configs for Hive > -- > > Key: AMBARI-20151 > URL: https://issues.apache.org/jira/browse/AMBARI-20151 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 2.5.0 > > Attachments: AMBARI-20151.01.patch, AMBARI-20151.02.patch, > AMBARI-20151.03.patch, AMBARI-20151.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20284) Fix values of ATS config params for HDP stack
[
https://issues.apache.org/jira/browse/AMBARI-20284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-20284:
---
Attachment: AMBARI-20284.patch
> Fix values of ATS config params for HDP stack
> -
>
> Key: AMBARI-20284
> URL: https://issues.apache.org/jira/browse/AMBARI-20284
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.0
>Reporter: Siddharth Seth
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20284.patch
>
>
> * Add {{yarn.timeline-service.entity-group-fs-store.app-cache-size}} and
> {{yarn.timeline-service.client.fd-flush-interval-secs}} to HDP-2.6. This will
> also automatically add them during HDP upgrade as these are new
> * Change
> {{yarn.timeline-service.entity-group-fs-store.scan-interval-seconds}} to 15
> as well as add a upgrade pack change to set it to 15 if it is 60 (previous
> default)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20257) Log Search upgrade to 2.5 should handle renamed properties safely
[ https://issues.apache.org/jira/browse/AMBARI-20257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893535#comment-15893535 ] Hudson commented on AMBARI-20257: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6923 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6923/]) AMBARI-20257 Log Search upgrade to 2.5 should handle renamed properties (mgergely: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7e2eb293def46ee172c05471bc7fc6954eafd98b]) * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-properties.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java > Log Search upgrade to 2.5 should handle renamed properties safely > - > > Key: AMBARI-20257 > URL: https://issues.apache.org/jira/browse/AMBARI-20257 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-20257.patch > > > Log Search upgrade to 2.5 renames some variables. If for some reason the > upgrade is repeated, it tries to rename them again, which causes some > problem, as the original variables are not present anymore. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20284) Fix values of ATS config params for HDP stack
[
https://issues.apache.org/jira/browse/AMBARI-20284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-20284:
---
Summary: Fix values of ATS config params for HDP stack (was: Fix values of
ATS config params in Ambari)
> Fix values of ATS config params for HDP stack
> -
>
> Key: AMBARI-20284
> URL: https://issues.apache.org/jira/browse/AMBARI-20284
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.0
>Reporter: Siddharth Seth
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
>
> * Add {{yarn.timeline-service.entity-group-fs-store.app-cache-size}} and
> {{yarn.timeline-service.client.fd-flush-interval-secs}} to HDP-2.6. This will
> also automatically add them during HDP upgrade as these are new
> * Change
> {{yarn.timeline-service.entity-group-fs-store.scan-interval-seconds}} to 15
> as well as add a upgrade pack change to set it to 15 if it is 60 (previous
> default)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20284) Fix values of ATS config params in Ambari
[
https://issues.apache.org/jira/browse/AMBARI-20284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-20284:
---
Description:
* Add {{yarn.timeline-service.entity-group-fs-store.app-cache-size}} and
{{yarn.timeline-service.client.fd-flush-interval-secs}} to HDP-2.6. This will
also automatically add them during HDP upgrade as these are new
* Change {{yarn.timeline-service.entity-group-fs-store.scan-interval-seconds}}
to 15 as well as add a upgrade pack change to set it to 15 if it is 60
(previous default)
was:
* Add {{yarn.timeline-service.entity-group-fs-store.app-cache-size}} and
{{yarn.timeline-service.client.fd-flush-interval-secs}} to HDP-2.6. This will
also automatically add them during HDP upgrade as these are new
* Change {{yarn.timeline-service.entity-group-fs-store.scan-interval-seconds}}
to 15 as well as add a upgrade pack change to set it to 15 if it is 60
> Fix values of ATS config params in Ambari
> -
>
> Key: AMBARI-20284
> URL: https://issues.apache.org/jira/browse/AMBARI-20284
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.0
>Reporter: Siddharth Seth
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
>
> * Add {{yarn.timeline-service.entity-group-fs-store.app-cache-size}} and
> {{yarn.timeline-service.client.fd-flush-interval-secs}} to HDP-2.6. This will
> also automatically add them during HDP upgrade as these are new
> * Change
> {{yarn.timeline-service.entity-group-fs-store.scan-interval-seconds}} to 15
> as well as add a upgrade pack change to set it to 15 if it is 60 (previous
> default)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20257) Log Search upgrade to 2.5 should handle renamed properties safely
[ https://issues.apache.org/jira/browse/AMBARI-20257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893528#comment-15893528 ] Hudson commented on AMBARI-20257: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1162 (See [https://builds.apache.org/job/Ambari-branch-2.5/1162/]) AMBARI-20257 Log Search upgrade to 2.5 should handle renamed properties (mgergely: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=de227f6d1f99212bfd131af6ce44dff6c2ce59b6]) * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-properties.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java > Log Search upgrade to 2.5 should handle renamed properties safely > - > > Key: AMBARI-20257 > URL: https://issues.apache.org/jira/browse/AMBARI-20257 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-20257.patch > > > Log Search upgrade to 2.5 renames some variables. If for some reason the > upgrade is repeated, it tries to rename them again, which causes some > problem, as the original variables are not present anymore. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20279) HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only if it exists in hive-interactive-site.
[
https://issues.apache.org/jira/browse/AMBARI-20279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893525#comment-15893525
]
Swapan Shridhar commented on AMBARI-20279:
--
commit
branch-2.5:
{code}
commit 6ef4707077f20ae068ed1c94106a5242006d9f10
Author: Swapan Shridhar
Date: Thu Mar 2 14:27:33 2017 -0800
AMBARI-20279. HiveServerInteractive. Set value for
num_llap_nodes_for_llap_daemons only if it exists in hive-interactive-site.
{code}
trunk:
{code}
commit 1142b526195feced7b42c82119220e065d56e24b
Author: Swapan Shridhar
Date: Thu Mar 2 14:25:12 2017 -0800
AMBARI-20279. HiveServerInteractive. Set value for
num_llap_nodes_for_llap_daemons only if it exists in hive-interactive-site.
{code}
> HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only
> if it exists in hive-interactive-site.
> --
>
> Key: AMBARI-20279
> URL: https://issues.apache.org/jira/browse/AMBARI-20279
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20279.branch-2.5.patch,
> AMBARI-20279.trunk.01.patch
>
>
> Given that "num_llap_nodes_for_llap_daemons" only exists in 2.6 HDP stack,
> there can be a scenario where "num_llap_nodes_for_llap_daemons" doesnt exist
> in hive-interactive-site. This can happen if we upgrade from Ambari 2.4 (with
> HDP 2.5) to Ambari 2.5.
> *Fix:* Set this config in SA only if it present in hive-interactive-env.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20279) HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only if it exists in hive-interactive-site.
[ https://issues.apache.org/jira/browse/AMBARI-20279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20279: - Resolution: Fixed Status: Resolved (was: Patch Available) > HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only > if it exists in hive-interactive-site. > -- > > Key: AMBARI-20279 > URL: https://issues.apache.org/jira/browse/AMBARI-20279 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20279.branch-2.5.patch, > AMBARI-20279.trunk.01.patch > > > Given that "num_llap_nodes_for_llap_daemons" only exists in 2.6 HDP stack, > there can be a scenario where "num_llap_nodes_for_llap_daemons" doesnt exist > in hive-interactive-site. This can happen if we upgrade from Ambari 2.4 (with > HDP 2.5) to Ambari 2.5. > *Fix:* Set this config in SA only if it present in hive-interactive-env. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20282) Set tez task listener thread count to 1 by default for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-20282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiyuan Yang updated AMBARI-20282: -- Fix Version/s: 2.5.0 > Set tez task listener thread count to 1 by default for hive interactive in > HDP 2.6 stack > > > Key: AMBARI-20282 > URL: https://issues.apache.org/jira/browse/AMBARI-20282 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Zhiyuan Yang >Assignee: Zhiyuan Yang > Fix For: 2.5.0 > > Attachments: AMBARI-20282.1.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20282) Set tez task listener thread count to 1 by default for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-20282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiyuan Yang updated AMBARI-20282: -- Issue Type: Task (was: Bug) > Set tez task listener thread count to 1 by default for hive interactive in > HDP 2.6 stack > > > Key: AMBARI-20282 > URL: https://issues.apache.org/jira/browse/AMBARI-20282 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Zhiyuan Yang >Assignee: Zhiyuan Yang > Fix For: 2.5.0 > > Attachments: AMBARI-20282.1.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20257) Log Search upgrade to 2.5 should handle renamed properties safely
[
https://issues.apache.org/jira/browse/AMBARI-20257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893397#comment-15893397
]
Miklos Gergely commented on AMBARI-20257:
-
committed to trunk:
{code:java}
commit 7e2eb293def46ee172c05471bc7fc6954eafd98b
Author: Miklos Gergely
Date: Fri Mar 3 01:38:11 2017 +0100
AMBARI-20257 Log Search upgrade to 2.5 should handle renamed properties
safely (mgergely)
Change-Id: I162e210a02e9c56575f682cb6d65074c18efd8b9
{code}
committed to branch-2.5:
{code:java}
commit de227f6d1f99212bfd131af6ce44dff6c2ce59b6
Author: Miklos Gergely
Date: Fri Mar 3 01:39:28 2017 +0100
AMBARI-20257 Log Search upgrade to 2.5 should handle renamed properties
safely (mgergely)
Change-Id: I35385a0bf3d596bea864767a04ea8d930404e7de
{code}
> Log Search upgrade to 2.5 should handle renamed properties safely
> -
>
> Key: AMBARI-20257
> URL: https://issues.apache.org/jira/browse/AMBARI-20257
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-20257.patch
>
>
> Log Search upgrade to 2.5 renames some variables. If for some reason the
> upgrade is repeated, it tries to rename them again, which causes some
> problem, as the original variables are not present anymore.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20257) Log Search upgrade to 2.5 should handle renamed properties safely
[ https://issues.apache.org/jira/browse/AMBARI-20257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-20257: Resolution: Fixed Status: Resolved (was: Patch Available) > Log Search upgrade to 2.5 should handle renamed properties safely > - > > Key: AMBARI-20257 > URL: https://issues.apache.org/jira/browse/AMBARI-20257 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-20257.patch > > > Log Search upgrade to 2.5 renames some variables. If for some reason the > upgrade is repeated, it tries to rename them again, which causes some > problem, as the original variables are not present anymore. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20288) Cluster deployment using blueprint with empty configuration doesn't work with stack advisor enabled
[ https://issues.apache.org/jira/browse/AMBARI-20288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20288: --- Fix Version/s: trunk Status: Patch Available (was: In Progress) > Cluster deployment using blueprint with empty configuration doesn't work with > stack advisor enabled > --- > > Key: AMBARI-20288 > URL: https://issues.apache.org/jira/browse/AMBARI-20288 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20288.patch > > > When a blueprint deployment is made with empty configuration for a particular > config-type and when stack advisor is returning a ValueAttributeInfo for for > that config-type with a property marked "true" for "Delete" flag > Cluster deployment gets stuck at TOPOLOGY_RESOLUTION phase showing message > Config type not resolved yet, Blueprint deployment will wait until > configuration update is completed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20288) Cluster deployment using blueprint with empty configuration doesn't work with stack advisor enabled
[ https://issues.apache.org/jira/browse/AMBARI-20288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20288: --- Attachment: AMBARI-20288.patch > Cluster deployment using blueprint with empty configuration doesn't work with > stack advisor enabled > --- > > Key: AMBARI-20288 > URL: https://issues.apache.org/jira/browse/AMBARI-20288 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Attachments: AMBARI-20288.patch > > > When a blueprint deployment is made with empty configuration for a particular > config-type and when stack advisor is returning a ValueAttributeInfo for for > that config-type with a property marked "true" for "Delete" flag > Cluster deployment gets stuck at TOPOLOGY_RESOLUTION phase showing message > Config type not resolved yet, Blueprint deployment will wait until > configuration update is completed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20288) Cluster deployment using blueprint with empty configuration doesn't work with stack advisor enabled
Amruta Borkar created AMBARI-20288: -- Summary: Cluster deployment using blueprint with empty configuration doesn't work with stack advisor enabled Key: AMBARI-20288 URL: https://issues.apache.org/jira/browse/AMBARI-20288 Project: Ambari Issue Type: Bug Components: ambari-server, blueprints Reporter: Amruta Borkar Assignee: Amruta Borkar When a blueprint deployment is made with empty configuration for a particular config-type and when stack advisor is returning a ValueAttributeInfo for for that config-type with a property marked "true" for "Delete" flag Cluster deployment gets stuck at TOPOLOGY_RESOLUTION phase showing message Config type not resolved yet, Blueprint deployment will wait until configuration update is completed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20287) Filter in Customize Services Page doesn't bring up all properties that matches
Dhanya Balasundaran created AMBARI-20287: Summary: Filter in Customize Services Page doesn't bring up all properties that matches Key: AMBARI-20287 URL: https://issues.apache.org/jira/browse/AMBARI-20287 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Dhanya Balasundaran Fix For: 2.5.0 - Navigate to Add Service Wizard to Add Ranger - At Customize Services page, change Sync Source to LDAP/AD - try to filter out few properties like: - Enable Group Sync, Incremental Sync etc They are not getting filtered out. As there are multiple tabs and tabs inside first level tabs, its not easy to find the values of these properties without the help of filter -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20151) add extra Tez logging configs for Hive
[ https://issues.apache.org/jira/browse/AMBARI-20151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated AMBARI-20151: -- Attachment: AMBARI-20151.03.patch Updated again > add extra Tez logging configs for Hive > -- > > Key: AMBARI-20151 > URL: https://issues.apache.org/jira/browse/AMBARI-20151 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 2.5.0 > > Attachments: AMBARI-20151.01.patch, AMBARI-20151.02.patch, > AMBARI-20151.03.patch, AMBARI-20151.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20180) HDFS SecurityLogger messages are logged twice
[ https://issues.apache.org/jira/browse/AMBARI-20180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893275#comment-15893275 ] Alejandro Fernandez commented on AMBARI-20180: -- [~arpitagarwal], +1 for [^AMBARI-20180.01.patch] > HDFS SecurityLogger messages are logged twice > - > > Key: AMBARI-20180 > URL: https://issues.apache.org/jira/browse/AMBARI-20180 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Arpit Agarwal >Assignee: Arpit Agarwal > Fix For: 2.5.0 > > Attachments: AMBARI-20180.01.patch > > > HDFS SecurityLogger messages are logged twice, once each in the > SecurityAuth.audit log and the NameNode service log. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20180) HDFS SecurityLogger messages are logged twice
[ https://issues.apache.org/jira/browse/AMBARI-20180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-20180: - Affects Version/s: 2.5.0 > HDFS SecurityLogger messages are logged twice > - > > Key: AMBARI-20180 > URL: https://issues.apache.org/jira/browse/AMBARI-20180 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Arpit Agarwal >Assignee: Arpit Agarwal > Fix For: 2.5.0 > > Attachments: AMBARI-20180.01.patch > > > HDFS SecurityLogger messages are logged twice, once each in the > SecurityAuth.audit log and the NameNode service log. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20180) HDFS SecurityLogger messages are logged twice
[ https://issues.apache.org/jira/browse/AMBARI-20180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-20180: - Component/s: stacks > HDFS SecurityLogger messages are logged twice > - > > Key: AMBARI-20180 > URL: https://issues.apache.org/jira/browse/AMBARI-20180 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Arpit Agarwal >Assignee: Arpit Agarwal > Fix For: 2.5.0 > > Attachments: AMBARI-20180.01.patch > > > HDFS SecurityLogger messages are logged twice, once each in the > SecurityAuth.audit log and the NameNode service log. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20280) Pre-Upgrade check message for disabling Auto Start is difficult to understand and take action on
[ https://issues.apache.org/jira/browse/AMBARI-20280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893274#comment-15893274 ] Hudson commented on AMBARI-20280: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6922 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6922/]) AMBARI-20280. Pre-Upgrade check message for disabling Auto Start is (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=74d33276c9e1672b70edd2ba18bfaa668ba2c88d]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/checks/AutoStartDisabledCheckTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/CheckDescription.java > Pre-Upgrade check message for disabling Auto Start is difficult to understand > and take action on > > > Key: AMBARI-20280 > URL: https://issues.apache.org/jira/browse/AMBARI-20280 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20280.patch > > > Change the text for the prereq check to: > "Auto Start must be disabled before performing an Upgrade. To disable Auto > Start, navigate to Admin > Service Auto Start. Turn the toggle switch off to > Disabled and hit Save." -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (AMBARI-20180) HDFS SecurityLogger messages are logged twice
[
https://issues.apache.org/jira/browse/AMBARI-20180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893233#comment-15893233
]
Arpit Agarwal edited comment on AMBARI-20180 at 3/2/17 11:29 PM:
-
Patch for trunk. This adds the following line to the HDFS log4j.properties file:
{code}
log4j.additivity.SecurityLogger=false
{code}
For upgrades from \[2.3, 2.4, 2.5\] => 2.6, we will add the setting by
replacing the following string in log4j.properties
{code}
hadoop.security.log.file=SecurityAuth.audit
{code}
with
{code}
hadoop.security.log.file=SecurityAuth.audit
log4j.additivity.SecurityLogger=false
{code}
Thank you [~afernandez] for the offline help.
was (Author: arpitagarwal):
Patch for trunk. This adds the following line to the HDFS log4j.properties file:
{code}
log4j.additivity.SecurityLogger=false
{code}
For upgrades from \[2.3, 2.4, 2.5\] => 2.6, we will add the setting by
replacing the following string in log4j.properties
{code}
hadoop.security.log.file=SecurityAuth.audit
{code}
with
{code}
log4j.additivity.SecurityLogger=false
{code}
Thank you [~afernandez] for the offline help.
> HDFS SecurityLogger messages are logged twice
> -
>
> Key: AMBARI-20180
> URL: https://issues.apache.org/jira/browse/AMBARI-20180
> Project: Ambari
> Issue Type: Bug
>Reporter: Arpit Agarwal
>Assignee: Arpit Agarwal
> Fix For: 2.5.0
>
> Attachments: AMBARI-20180.01.patch
>
>
> HDFS SecurityLogger messages are logged twice, once each in the
> SecurityAuth.audit log and the NameNode service log.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20180) HDFS SecurityLogger messages are logged twice
[
https://issues.apache.org/jira/browse/AMBARI-20180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Agarwal updated AMBARI-20180:
---
Attachment: AMBARI-20180.01.patch
Patch for trunk. This adds the following line to the HDFS log4j.properties file:
{code}
log4j.additivity.SecurityLogger=false
{code}
For upgrades from \[2.3, 2.4, 2.5\] => 2.6, we will add the setting by
replacing the following string in log4j.properties
{code}
hadoop.security.log.file=SecurityAuth.audit
{code}
with
{code}
log4j.additivity.SecurityLogger=false
{code}
Thank you [~afernandez] for the offline help.
> HDFS SecurityLogger messages are logged twice
> -
>
> Key: AMBARI-20180
> URL: https://issues.apache.org/jira/browse/AMBARI-20180
> Project: Ambari
> Issue Type: Bug
>Reporter: Arpit Agarwal
>Assignee: Arpit Agarwal
> Fix For: 2.5.0
>
> Attachments: AMBARI-20180.01.patch
>
>
> HDFS SecurityLogger messages are logged twice, once each in the
> SecurityAuth.audit log and the NameNode service log.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20180) HDFS SecurityLogger messages are logged twice
[ https://issues.apache.org/jira/browse/AMBARI-20180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated AMBARI-20180: --- Status: Patch Available (was: Open) > HDFS SecurityLogger messages are logged twice > - > > Key: AMBARI-20180 > URL: https://issues.apache.org/jira/browse/AMBARI-20180 > Project: Ambari > Issue Type: Bug >Reporter: Arpit Agarwal >Assignee: Arpit Agarwal > Fix For: 2.5.0 > > Attachments: AMBARI-20180.01.patch > > > HDFS SecurityLogger messages are logged twice, once each in the > SecurityAuth.audit log and the NameNode service log. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20286) While Comparing versions, value in latest version is not shown for custom property
Dhanya Balasundaran created AMBARI-20286: Summary: While Comparing versions, value in latest version is not shown for custom property Key: AMBARI-20286 URL: https://issues.apache.org/jira/browse/AMBARI-20286 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Dhanya Balasundaran Fix For: 2.5.0 Difftool which shows the comparison between 2versions doesnt show custom properties added to a service -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20285) Spark2 Thrift Server stopped due to incompletely uploaded tar.gz
[ https://issues.apache.org/jira/browse/AMBARI-20285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-20285: --- Status: Patch Available (was: Open) > Spark2 Thrift Server stopped due to incompletely uploaded tar.gz > > > Key: AMBARI-20285 > URL: https://issues.apache.org/jira/browse/AMBARI-20285 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20285.patch > > > Case found by [~akhalymon]. > STR: > # Setup ambari-agent to run as non-root user with its own group > # Set umask=027 for ambari-agent's user > # Deploy cluster with Spark2, including Thrift Server > Result: Spark2 Thrift Server stops soon after being started > This is happens because spark2-hdp-yarn-archive.tar.gz is uploaded to HDFS as > empty file due to incorrect permissions on local source file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20285) Spark2 Thrift Server stopped due to incompletely uploaded tar.gz
[ https://issues.apache.org/jira/browse/AMBARI-20285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-20285: --- Attachment: AMBARI-20285.patch > Spark2 Thrift Server stopped due to incompletely uploaded tar.gz > > > Key: AMBARI-20285 > URL: https://issues.apache.org/jira/browse/AMBARI-20285 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20285.patch > > > Case found by [~akhalymon]. > STR: > # Setup ambari-agent to run as non-root user with its own group > # Set umask=027 for ambari-agent's user > # Deploy cluster with Spark2, including Thrift Server > Result: Spark2 Thrift Server stops soon after being started > This is happens because spark2-hdp-yarn-archive.tar.gz is uploaded to HDFS as > empty file due to incorrect permissions on local source file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20285) Spark2 Thrift Server stopped due to incompletely uploaded tar.gz
Doroszlai, Attila created AMBARI-20285: -- Summary: Spark2 Thrift Server stopped due to incompletely uploaded tar.gz Key: AMBARI-20285 URL: https://issues.apache.org/jira/browse/AMBARI-20285 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Doroszlai, Attila Assignee: Doroszlai, Attila Priority: Critical Fix For: 2.5.0 Case found by [~akhalymon]. STR: # Setup ambari-agent to run as non-root user with its own group # Set umask=027 for ambari-agent's user # Deploy cluster with Spark2, including Thrift Server Result: Spark2 Thrift Server stops soon after being started This is happens because spark2-hdp-yarn-archive.tar.gz is uploaded to HDFS as empty file due to incorrect permissions on local source file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20281) Porting changes made in 2.5/stack_advisor to 3.0/YARN/service_advisor for LLAP.
[ https://issues.apache.org/jira/browse/AMBARI-20281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893188#comment-15893188 ] Hudson commented on AMBARI-20281: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6921 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6921/]) AMBARI-20281. Porting changes made in 2.5/stack_advisor to (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fc8128b0de0a97c3c8ef9e7064776a5f0030ae6a]) * (edit) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/service_advisor.py > Porting changes made in 2.5/stack_advisor to 3.0/YARN/service_advisor for > LLAP. > --- > > Key: AMBARI-20281 > URL: https://issues.apache.org/jira/browse/AMBARI-20281 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: trunk > > Attachments: AMBARI-20281.trunk.patch > > > Porting changes made in 2.5/stack_advisor to 3.0/YARN/service_advisor for > LLAP from following bugs: > 1. AMBARI-19827 > 2. AMBARI-19760 > 3. AMBARI-19686 > 4. AMBARI-19814 > 5. AMBARI-19971 > 6. AMBARI-19760 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20282) Set tez task listener thread count to 1 by default for hive interactive in HDP 2.6 stack
[
https://issues.apache.org/jira/browse/AMBARI-20282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893185#comment-15893185
]
Hadoop QA commented on AMBARI-20282:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12855711/AMBARI-20282.1.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10857//console
This message is automatically generated.
> Set tez task listener thread count to 1 by default for hive interactive in
> HDP 2.6 stack
>
>
> Key: AMBARI-20282
> URL: https://issues.apache.org/jira/browse/AMBARI-20282
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Reporter: Zhiyuan Yang
>Assignee: Zhiyuan Yang
> Attachments: AMBARI-20282.1.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20280) Pre-Upgrade check message for disabling Auto Start is difficult to understand and take action on
[ https://issues.apache.org/jira/browse/AMBARI-20280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893176#comment-15893176 ] Hudson commented on AMBARI-20280: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1161 (See [https://builds.apache.org/job/Ambari-branch-2.5/1161/]) AMBARI-20280. Pre-Upgrade check message for disabling Auto Start is (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c4f071be2e75936fc059358afe418e1faa2fcf2a]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/checks/AutoStartDisabledCheckTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/CheckDescription.java > Pre-Upgrade check message for disabling Auto Start is difficult to understand > and take action on > > > Key: AMBARI-20280 > URL: https://issues.apache.org/jira/browse/AMBARI-20280 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20280.patch > > > Change the text for the prereq check to: > "Auto Start must be disabled before performing an Upgrade. To disable Auto > Start, navigate to Admin > Service Auto Start. Turn the toggle switch off to > Disabled and hit Save." -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20279) HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only if it exists in hive-interactive-site.
[ https://issues.apache.org/jira/browse/AMBARI-20279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20279: - Attachment: AMBARI-20279.trunk.01.patch > HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only > if it exists in hive-interactive-site. > -- > > Key: AMBARI-20279 > URL: https://issues.apache.org/jira/browse/AMBARI-20279 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20279.branch-2.5.patch, > AMBARI-20279.trunk.01.patch > > > Given that "num_llap_nodes_for_llap_daemons" only exists in 2.6 HDP stack, > there can be a scenario where "num_llap_nodes_for_llap_daemons" doesnt exist > in hive-interactive-site. This can happen if we upgrade from Ambari 2.4 (with > HDP 2.5) to Ambari 2.5. > *Fix:* Set this config in SA only if it present in hive-interactive-env. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20265) Blueprint deployment with auto-restart settings enabled, auto-restart UI is incomplete.
[
https://issues.apache.org/jira/browse/AMBARI-20265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zang updated AMBARI-20265:
--
Resolution: Invalid
Status: Resolved (was: Patch Available)
> Blueprint deployment with auto-restart settings enabled, auto-restart UI is
> incomplete.
> ---
>
> Key: AMBARI-20265
> URL: https://issues.apache.org/jira/browse/AMBARI-20265
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.5.0
>
>
> Attached screenshot of UI post blueprint deployment.
> Attached blueprint used for deployment.
> Here is a snipped of blueprint to enable the auto-restart feature:
> {noformat}
> "settings" : [
> {
> "recovery_settings" : [
> {
> "recovery_enabled" : "true"
> }
> ]
> },
> {
> "service_settings" : [
> {
> "recovery_enabled" : "true",
> "name" : "YARN"
> }
> ]
> },
> {
> "component_settings" : [
> {
> "recovery_enabled" : "true",
> "name" : "APP_TIMELINE_SERVER"
> }
> ]
> }
> ],
> {noformat}
> The expectation is that only the YARN App_timeline_server should be
> auto-restart enabled. The overall property would also show enabled.
> {noformat}
> {
> "blueprint": "bugbash",
> "default_password": "password",
> "config_recommendation_strategy":
> "ALWAYS_APPLY_DONT_OVERRIDE_CUSTOM_VALUES",
> "host_groups": [
> {
> "name": "host_group_1",
> "hosts": [
> {
> "fqdn": "c6401.apache.ambari.org",
> "ip": "192.168.64.101"
> }
> ]
> },
> {
> "name": "host_group_2",
> "hosts": [
> {
> "fqdn": "c6402.apache.ambari.org",
> "ip": "192.168.64.102"
> }
> ]
> },
> {
> "name": "host_group_3",
> "hosts": [
> {
> "fqdn": "c6403.apache.ambari.org",
> "ip": "192.168.64.103"
> }
> ]
> }
> ]
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20265) Blueprint deployment with auto-restart settings enabled, auto-restart UI is incomplete.
[
https://issues.apache.org/jira/browse/AMBARI-20265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zang updated AMBARI-20265:
--
Attachment: (was: AMBARI-20265.patch)
> Blueprint deployment with auto-restart settings enabled, auto-restart UI is
> incomplete.
> ---
>
> Key: AMBARI-20265
> URL: https://issues.apache.org/jira/browse/AMBARI-20265
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.5.0
>
>
> Attached screenshot of UI post blueprint deployment.
> Attached blueprint used for deployment.
> Here is a snipped of blueprint to enable the auto-restart feature:
> {noformat}
> "settings" : [
> {
> "recovery_settings" : [
> {
> "recovery_enabled" : "true"
> }
> ]
> },
> {
> "service_settings" : [
> {
> "recovery_enabled" : "true",
> "name" : "YARN"
> }
> ]
> },
> {
> "component_settings" : [
> {
> "recovery_enabled" : "true",
> "name" : "APP_TIMELINE_SERVER"
> }
> ]
> }
> ],
> {noformat}
> The expectation is that only the YARN App_timeline_server should be
> auto-restart enabled. The overall property would also show enabled.
> {noformat}
> {
> "blueprint": "bugbash",
> "default_password": "password",
> "config_recommendation_strategy":
> "ALWAYS_APPLY_DONT_OVERRIDE_CUSTOM_VALUES",
> "host_groups": [
> {
> "name": "host_group_1",
> "hosts": [
> {
> "fqdn": "c6401.apache.ambari.org",
> "ip": "192.168.64.101"
> }
> ]
> },
> {
> "name": "host_group_2",
> "hosts": [
> {
> "fqdn": "c6402.apache.ambari.org",
> "ip": "192.168.64.102"
> }
> ]
> },
> {
> "name": "host_group_3",
> "hosts": [
> {
> "fqdn": "c6403.apache.ambari.org",
> "ip": "192.168.64.103"
> }
> ]
> }
> ]
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20279) HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only if it exists in hive-interactive-site.
[ https://issues.apache.org/jira/browse/AMBARI-20279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20279: - Status: Patch Available (was: Open) > HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only > if it exists in hive-interactive-site. > -- > > Key: AMBARI-20279 > URL: https://issues.apache.org/jira/browse/AMBARI-20279 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20279.branch-2.5.patch, > AMBARI-20279.trunk.01.patch > > > Given that "num_llap_nodes_for_llap_daemons" only exists in 2.6 HDP stack, > there can be a scenario where "num_llap_nodes_for_llap_daemons" doesnt exist > in hive-interactive-site. This can happen if we upgrade from Ambari 2.4 (with > HDP 2.5) to Ambari 2.5. > *Fix:* Set this config in SA only if it present in hive-interactive-env. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20279) HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only if it exists in hive-interactive-site.
[ https://issues.apache.org/jira/browse/AMBARI-20279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20279: - Attachment: AMBARI-20279.branch-2.5.patch > HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only > if it exists in hive-interactive-site. > -- > > Key: AMBARI-20279 > URL: https://issues.apache.org/jira/browse/AMBARI-20279 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20279.branch-2.5.patch > > > Given that "num_llap_nodes_for_llap_daemons" only exists in 2.6 HDP stack, > there can be a scenario where "num_llap_nodes_for_llap_daemons" doesnt exist > in hive-interactive-site. This can happen if we upgrade from Ambari 2.4 (with > HDP 2.5) to Ambari 2.5. > *Fix:* Set this config in SA only if it present in hive-interactive-env. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20284) Fix values of ATS config params in Ambari
Sumit Mohanty created AMBARI-20284:
--
Summary: Fix values of ATS config params in Ambari
Key: AMBARI-20284
URL: https://issues.apache.org/jira/browse/AMBARI-20284
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 2.5.0
Reporter: Siddharth Seth
Assignee: Sumit Mohanty
Priority: Critical
Fix For: 2.5.0
* Add {{yarn.timeline-service.entity-group-fs-store.app-cache-size}} and
{{yarn.timeline-service.client.fd-flush-interval-secs}} to HDP-2.6. This will
also automatically add them during HDP upgrade as these are new
* Change {{yarn.timeline-service.entity-group-fs-store.scan-interval-seconds}}
to 15 as well as add a upgrade pack change to set it to 15 if it is 60
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20279) HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only if it exists in hive-interactive-site.
[ https://issues.apache.org/jira/browse/AMBARI-20279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20279: - Attachment: (was: AMBARI-20279.trunk.01.patch) > HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only > if it exists in hive-interactive-site. > -- > > Key: AMBARI-20279 > URL: https://issues.apache.org/jira/browse/AMBARI-20279 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.0 > > > Given that "num_llap_nodes_for_llap_daemons" only exists in 2.6 HDP stack, > there can be a scenario where "num_llap_nodes_for_llap_daemons" doesnt exist > in hive-interactive-site. This can happen if we upgrade from Ambari 2.4 (with > HDP 2.5) to Ambari 2.5. > *Fix:* Set this config in SA only if it present in hive-interactive-env. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20282) Set tez task listener thread count to 1 by default for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-20282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiyuan Yang updated AMBARI-20282: -- Status: Patch Available (was: Open) > Set tez task listener thread count to 1 by default for hive interactive in > HDP 2.6 stack > > > Key: AMBARI-20282 > URL: https://issues.apache.org/jira/browse/AMBARI-20282 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Zhiyuan Yang >Assignee: Zhiyuan Yang > Attachments: AMBARI-20282.1.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20279) HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only if it exists in hive-interactive-site.
[ https://issues.apache.org/jira/browse/AMBARI-20279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20279: - Attachment: AMBARI-20279.trunk.01.patch > HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only > if it exists in hive-interactive-site. > -- > > Key: AMBARI-20279 > URL: https://issues.apache.org/jira/browse/AMBARI-20279 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20279.trunk.01.patch > > > Given that "num_llap_nodes_for_llap_daemons" only exists in 2.6 HDP stack, > there can be a scenario where "num_llap_nodes_for_llap_daemons" doesnt exist > in hive-interactive-site. This can happen if we upgrade from Ambari 2.4 (with > HDP 2.5) to Ambari 2.5. > *Fix:* Set this config in SA only if it present in hive-interactive-env. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20279) HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only if it exists in hive-interactive-site.
[ https://issues.apache.org/jira/browse/AMBARI-20279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20279: - Description: Given that "num_llap_nodes_for_llap_daemons" only exists in 2.6 HDP stack, there can be a scenario where "num_llap_nodes_for_llap_daemons" doesnt exist in hive-interactive-site. This can happen if we upgrade from Ambari 2.4 (with HDP 2.5) to Ambari 2.5. *Fix:* Set this config in SA only if it present in hive-interactive-env. > HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only > if it exists in hive-interactive-site. > -- > > Key: AMBARI-20279 > URL: https://issues.apache.org/jira/browse/AMBARI-20279 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.0 > > > Given that "num_llap_nodes_for_llap_daemons" only exists in 2.6 HDP stack, > there can be a scenario where "num_llap_nodes_for_llap_daemons" doesnt exist > in hive-interactive-site. This can happen if we upgrade from Ambari 2.4 (with > HDP 2.5) to Ambari 2.5. > *Fix:* Set this config in SA only if it present in hive-interactive-env. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20282) Set tez task listener thread count to 1 by default for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-20282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiyuan Yang updated AMBARI-20282: -- Attachment: AMBARI-20282.1.patch > Set tez task listener thread count to 1 by default for hive interactive in > HDP 2.6 stack > > > Key: AMBARI-20282 > URL: https://issues.apache.org/jira/browse/AMBARI-20282 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Zhiyuan Yang >Assignee: Zhiyuan Yang > Attachments: AMBARI-20282.1.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20282) Set tez task listener thread count to 1 by default for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-20282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiyuan Yang updated AMBARI-20282: -- Fix Version/s: 2.5.0 > Set tez task listener thread count to 1 by default for hive interactive in > HDP 2.6 stack > > > Key: AMBARI-20282 > URL: https://issues.apache.org/jira/browse/AMBARI-20282 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Zhiyuan Yang >Assignee: Zhiyuan Yang > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20282) Set tez task listener thread count to 1 by default for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-20282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiyuan Yang updated AMBARI-20282: -- Fix Version/s: (was: 2.5.0) > Set tez task listener thread count to 1 by default for hive interactive in > HDP 2.6 stack > > > Key: AMBARI-20282 > URL: https://issues.apache.org/jira/browse/AMBARI-20282 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Zhiyuan Yang >Assignee: Zhiyuan Yang > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20280) Pre-Upgrade check message for disabling Auto Start is difficult to understand and take action on
[ https://issues.apache.org/jira/browse/AMBARI-20280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-20280: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Pre-Upgrade check message for disabling Auto Start is difficult to understand > and take action on > > > Key: AMBARI-20280 > URL: https://issues.apache.org/jira/browse/AMBARI-20280 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20280.patch > > > Change the text for the prereq check to: > "Auto Start must be disabled before performing an Upgrade. To disable Auto > Start, navigate to Admin > Service Auto Start. Turn the toggle switch off to > Disabled and hit Save." -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20275) Credential Store should be enabled by default on fresh installs
[ https://issues.apache.org/jira/browse/AMBARI-20275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893088#comment-15893088 ] Hudson commented on AMBARI-20275: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6920 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6920/]) AMBARI-20275. Credential Store should be enabled by default on fresh (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8e6c3212a4f1c874083c6c803afe253eaa4a07e1]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/OOZIE/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/metainfo.xml > Credential Store should be enabled by default on fresh installs > --- > > Key: AMBARI-20275 > URL: https://issues.apache.org/jira/browse/AMBARI-20275 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-20275.patch > > > For fresh installs, enable credential store by default. For upgrades, user > can enable credential store per service using the API. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20281) Porting changes made in 2.5/stack_advisor to 3.0/YARN/service_advisor for LLAP.
[ https://issues.apache.org/jira/browse/AMBARI-20281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20281: - Resolution: Fixed Status: Resolved (was: Patch Available) > Porting changes made in 2.5/stack_advisor to 3.0/YARN/service_advisor for > LLAP. > --- > > Key: AMBARI-20281 > URL: https://issues.apache.org/jira/browse/AMBARI-20281 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: trunk > > Attachments: AMBARI-20281.trunk.patch > > > Porting changes made in 2.5/stack_advisor to 3.0/YARN/service_advisor for > LLAP from following bugs: > 1. AMBARI-19827 > 2. AMBARI-19760 > 3. AMBARI-19686 > 4. AMBARI-19814 > 5. AMBARI-19971 > 6. AMBARI-19760 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20281) Porting changes made in 2.5/stack_advisor to 3.0/YARN/service_advisor for LLAP.
[
https://issues.apache.org/jira/browse/AMBARI-20281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893079#comment-15893079
]
Swapan Shridhar commented on AMBARI-20281:
--
commit
trunk:
{code}
commit fc8128b0de0a97c3c8ef9e7064776a5f0030ae6a
Author: Swapan Shridhar
Date: Thu Mar 2 12:56:54 2017 -0800
AMBARI-20281. Porting changes made in 2.5/stack_advisor to
3.0/YARN/service_advisor for LLAP.
{code}
> Porting changes made in 2.5/stack_advisor to 3.0/YARN/service_advisor for
> LLAP.
> ---
>
> Key: AMBARI-20281
> URL: https://issues.apache.org/jira/browse/AMBARI-20281
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk
>
> Attachments: AMBARI-20281.trunk.patch
>
>
> Porting changes made in 2.5/stack_advisor to 3.0/YARN/service_advisor for
> LLAP from following bugs:
> 1. AMBARI-19827
> 2. AMBARI-19760
> 3. AMBARI-19686
> 4. AMBARI-19814
> 5. AMBARI-19971
> 6. AMBARI-19760
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20279) HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only if it exists in hive-interactive-site.
[
https://issues.apache.org/jira/browse/AMBARI-20279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893075#comment-15893075
]
Swapan Shridhar commented on AMBARI-20279:
--
commit
trunk:
{code}
commit fc8128b0de0a97c3c8ef9e7064776a5f0030ae6a
Author: Swapan Shridhar
Date: Thu Mar 2 12:56:54 2017 -0800
AMBARI-20281. Porting changes made in 2.5/stack_advisor to
3.0/YARN/service_advisor for LLAP.
{code}
> HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only
> if it exists in hive-interactive-site.
> --
>
> Key: AMBARI-20279
> URL: https://issues.apache.org/jira/browse/AMBARI-20279
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk, 2.5.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Issue Comment Deleted] (AMBARI-20279) HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only if it exists in hive-interactive-site.
[
https://issues.apache.org/jira/browse/AMBARI-20279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-20279:
-
Comment: was deleted
(was: commit
trunk:
{code}
commit fc8128b0de0a97c3c8ef9e7064776a5f0030ae6a
Author: Swapan Shridhar
Date: Thu Mar 2 12:56:54 2017 -0800
AMBARI-20281. Porting changes made in 2.5/stack_advisor to
3.0/YARN/service_advisor for LLAP.
{code})
> HiveServerInteractive. Set value for "num_llap_nodes_for_llap_daemons" only
> if it exists in hive-interactive-site.
> --
>
> Key: AMBARI-20279
> URL: https://issues.apache.org/jira/browse/AMBARI-20279
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk, 2.5.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20276) Perf: AMS scale test for 3000 node cluster
[ https://issues.apache.org/jira/browse/AMBARI-20276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-20276: --- Status: Patch Available (was: Open) > Perf: AMS scale test for 3000 node cluster > -- > > Key: AMBARI-20276 > URL: https://issues.apache.org/jira/browse/AMBARI-20276 > 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-20276.patch > > > This Jira tracks effort of AMS load simulation testing and end goal is to > capture the tuning required to get AMS and Grafana working on a 3K node load > simulated metrics system. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20276) Perf: AMS scale test for 3000 node cluster
[ https://issues.apache.org/jira/browse/AMBARI-20276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-20276: --- Attachment: AMBARI-20276.patch > Perf: AMS scale test for 3000 node cluster > -- > > Key: AMBARI-20276 > URL: https://issues.apache.org/jira/browse/AMBARI-20276 > 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-20276.patch > > > This Jira tracks effort of AMS load simulation testing and end goal is to > capture the tuning required to get AMS and Grafana working on a 3K node load > simulated metrics system. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20283) Consolidate metric list used for load simulation and split points calculation.
Aravindan Vijayan created AMBARI-20283: -- Summary: Consolidate metric list used for load simulation and split points calculation. Key: AMBARI-20283 URL: https://issues.apache.org/jira/browse/AMBARI-20283 Project: Ambari Issue Type: Task Components: ambari-metrics Affects Versions: 3.0.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20281) Porting changes made in 2.5/stack_advisor to 3.0/YARN/service_advisor for LLAP.
[ https://issues.apache.org/jira/browse/AMBARI-20281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20281: - Description: Porting changes made in 2.5/stack_advisor to 3.0/YARN/service_advisor for LLAP from following bugs: 1. AMBARI-19827 2. AMBARI-19760 3. AMBARI-19686 4. AMBARI-19814 5. AMBARI-19971 6. AMBARI-19760 was: Porting changes made 2.5/stack_advisor to 3.0/YARN/service_advisor for LLAP. from following bugs: 1. AMBARI-19827 2. AMBARI-19760 3. AMBARI-19686 4. AMBARI-19814 5. AMBARI-19971 6. AMBARI-19760 > Porting changes made in 2.5/stack_advisor to 3.0/YARN/service_advisor for > LLAP. > --- > > Key: AMBARI-20281 > URL: https://issues.apache.org/jira/browse/AMBARI-20281 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: trunk > > Attachments: AMBARI-20281.trunk.patch > > > Porting changes made in 2.5/stack_advisor to 3.0/YARN/service_advisor for > LLAP from following bugs: > 1. AMBARI-19827 > 2. AMBARI-19760 > 3. AMBARI-19686 > 4. AMBARI-19814 > 5. AMBARI-19971 > 6. AMBARI-19760 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20281) Porting changes made in 2.5/stack_advisor to 3.0/YARN/service_advisor for LLAP.
[ https://issues.apache.org/jira/browse/AMBARI-20281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20281: - Status: Patch Available (was: Open) > Porting changes made in 2.5/stack_advisor to 3.0/YARN/service_advisor for > LLAP. > --- > > Key: AMBARI-20281 > URL: https://issues.apache.org/jira/browse/AMBARI-20281 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: trunk > > Attachments: AMBARI-20281.trunk.patch > > > Porting changes made in 2.5/stack_advisor to 3.0/YARN/service_advisor for > LLAP from following bugs: > 1. AMBARI-19827 > 2. AMBARI-19760 > 3. AMBARI-19686 > 4. AMBARI-19814 > 5. AMBARI-19971 > 6. AMBARI-19760 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20281) Porting changes made in 2.5/stack_advisor to 3.0/YARN/service_advisor for LLAP.
[ https://issues.apache.org/jira/browse/AMBARI-20281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20281: - Attachment: AMBARI-20281.trunk.patch > Porting changes made in 2.5/stack_advisor to 3.0/YARN/service_advisor for > LLAP. > --- > > Key: AMBARI-20281 > URL: https://issues.apache.org/jira/browse/AMBARI-20281 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: trunk > > Attachments: AMBARI-20281.trunk.patch > > > Porting changes made in 2.5/stack_advisor to 3.0/YARN/service_advisor for > LLAP from following bugs: > 1. AMBARI-19827 > 2. AMBARI-19760 > 3. AMBARI-19686 > 4. AMBARI-19814 > 5. AMBARI-19971 > 6. AMBARI-19760 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20281) Porting changes made in 2.5/stack_advisor to 3.0/YARN/service_advisor for LLAP.
[ https://issues.apache.org/jira/browse/AMBARI-20281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20281: - Description: Porting changes made 2.5/stack_advisor to 3.0/YARN/service_advisor for LLAP. from following bugs: 1. AMBARI-19827 2. AMBARI-19760 3. AMBARI-19686 4. AMBARI-19814 5. AMBARI-19971 6. AMBARI-19760 > Porting changes made in 2.5/stack_advisor to 3.0/YARN/service_advisor for > LLAP. > --- > > Key: AMBARI-20281 > URL: https://issues.apache.org/jira/browse/AMBARI-20281 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: trunk > > > Porting changes made 2.5/stack_advisor to 3.0/YARN/service_advisor for LLAP. > from following bugs: > 1. AMBARI-19827 > 2. AMBARI-19760 > 3. AMBARI-19686 > 4. AMBARI-19814 > 5. AMBARI-19971 > 6. AMBARI-19760 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20275) Credential Store should be enabled by default on fresh installs
[ https://issues.apache.org/jira/browse/AMBARI-20275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893047#comment-15893047 ] Hudson commented on AMBARI-20275: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1160 (See [https://builds.apache.org/job/Ambari-branch-2.5/1160/]) AMBARI-20275. Credential Store should be enabled by default on fresh (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9ce7d709e26b3d598c1d21b5bf84e345eaf50d98]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/OOZIE/metainfo.xml > Credential Store should be enabled by default on fresh installs > --- > > Key: AMBARI-20275 > URL: https://issues.apache.org/jira/browse/AMBARI-20275 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-20275.patch > > > For fresh installs, enable credential store by default. For upgrades, user > can enable credential store per service using the API. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20282) Set tez task listener thread count to 1 by default for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-20282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiyuan Yang updated AMBARI-20282: -- Component/s: stacks > Set tez task listener thread count to 1 by default for hive interactive in > HDP 2.6 stack > > > Key: AMBARI-20282 > URL: https://issues.apache.org/jira/browse/AMBARI-20282 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Zhiyuan Yang >Assignee: Zhiyuan Yang > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20282) Set tez task listener thread count to 1 by default for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-20282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiyuan Yang updated AMBARI-20282: -- Summary: Set tez task listener thread count to 1 by default for hive interactive in HDP 2.6 stack (was: Set AM task listener thread count to 1 for LLAP) > Set tez task listener thread count to 1 by default for hive interactive in > HDP 2.6 stack > > > Key: AMBARI-20282 > URL: https://issues.apache.org/jira/browse/AMBARI-20282 > Project: Ambari > Issue Type: Bug >Reporter: Zhiyuan Yang >Assignee: Zhiyuan Yang > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
