[jira] [Commented] (AMBARI-19841) Add 'yarn.client.failover-proxy-provider' in yarn-site.xml by default for all HA enabled clusters

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849596#comment-15849596
 ] 

Hudson commented on AMBARI-19841:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #876 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/876/])
AMBARI-19841. Add yarn.client.failover-proxy-provider in yarn-site.xml 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7e11d79f9386b85e576056d239e3ecdab064f673])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/YARN/metainfo.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/YARN/configuration/yarn-site.xml


> Add 'yarn.client.failover-proxy-provider' in yarn-site.xml by default for all 
> HA enabled clusters
> -
>
> Key: AMBARI-19841
> URL: https://issues.apache.org/jira/browse/AMBARI-19841
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.0
>
>
> 
> When HA is enabled, the class to be used by Clients, AMs and
>   NMs to failover to the Active RM. It should extend
>   org.apache.hadoop.yarn.client.RMFailoverProxyProvider
> yarn.client.failover-proxy-provider
> 
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider
>   
> needs to be added to yarn-site.xml for HDP 2.6/fenton



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19817) Hive View 2.0: Introduce service checks

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849563#comment-15849563
 ] 

Hudson commented on AMBARI-19817:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6625 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6625/])
AMBARI-19817. Hive View 2.0: Introduce service checks. (dipayanb) 
(dipayan.bhowmick: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d1f26f98f5faf1d45035922c585c0c7bcebf154a])
* (add) 
contrib/views/hive20/src/main/resources/ui/app/templates/service-check.hbs
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/components/top-application-bar.js
* (add) 
contrib/views/hive20/src/main/resources/ui/app/controllers/service-check.js
* (edit) contrib/views/hive20/src/main/resources/ui/app/router.js
* (add) contrib/views/hive20/src/main/resources/ui/app/services/service-check.js
* (add) contrib/views/hive20/src/main/resources/ui/app/adapters/service-check.js
* (add) 
contrib/views/hive20/src/main/resources/ui/app/components/service-check-entry.js
* (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/application.js
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/templates/application.hbs
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/templates/components/top-application-bar.hbs
* (add) contrib/views/hive20/src/main/resources/ui/app/routes/service-check.js
* (add) 
contrib/views/hive20/src/main/resources/ui/app/configs/service-check-status.js
* (add) 
contrib/views/hive20/src/main/resources/ui/app/controllers/application.js
* (add) 
contrib/views/hive20/src/main/resources/ui/app/templates/components/service-check-entry.hbs
* (edit) contrib/views/hive20/src/main/resources/ui/app/routes/application.js


> Hive View 2.0: Introduce service checks
> ---
>
> Key: AMBARI-19817
> URL: https://issues.apache.org/jira/browse/AMBARI-19817
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.0
>
> Attachments: AMBARI-19817.branch-2.5.patch
>
>
> Service Checks should also be present in Hive View 2.0 as it was there in 
> Hive View 1.5



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19841) Add 'yarn.client.failover-proxy-provider' in yarn-site.xml by default for all HA enabled clusters

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849560#comment-15849560
 ] 

Hudson commented on AMBARI-19841:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6625 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6625/])
AMBARI-19841. Add yarn.client.failover-proxy-provider in yarn-site.xml 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=325dc20537b3328ce9cc6e4a3f5d0b111e353d94])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/YARN/metainfo.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/YARN/configuration/yarn-site.xml


> Add 'yarn.client.failover-proxy-provider' in yarn-site.xml by default for all 
> HA enabled clusters
> -
>
> Key: AMBARI-19841
> URL: https://issues.apache.org/jira/browse/AMBARI-19841
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.0
>
>
> 
> When HA is enabled, the class to be used by Clients, AMs and
>   NMs to failover to the Active RM. It should extend
>   org.apache.hadoop.yarn.client.RMFailoverProxyProvider
> yarn.client.failover-proxy-provider
> 
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider
>   
> needs to be added to yarn-site.xml for HDP 2.6/fenton



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19792) Hive View 2.0: Jobs page shows "Invalid date - Jan 24"

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849565#comment-15849565
 ] 

Hudson commented on AMBARI-19792:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6625 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6625/])
AMBARI-19792. Hive View 2.0: Jobs page shows 'Invalid date - Jan 24'. 
(dipayan.bhowmick: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=318f352252d31e97d9110f0fb5013d006dd0adab])
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/templates/components/jobs-browser.hbs
* (edit) contrib/views/hive20/src/main/resources/ui/app/routes/jobs.js
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/components/jobs-browser.js
* (edit) contrib/views/hive20/src/main/resources/ui/app/controllers/jobs.js
* (edit) contrib/views/hive20/src/main/resources/ui/config/environment.js
* (edit) contrib/views/hive20/src/main/resources/ui/app/app.js


> Hive View 2.0: Jobs page shows "Invalid date - Jan 24"
> --
>
> Key: AMBARI-19792
> URL: https://issues.apache.org/jira/browse/AMBARI-19792
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.0
>
> Attachments: AMBARI-19792.branch-2.5.patch
>
>
> Jobs page shows: "Invalid date - Jan 24" as well as the filter criteria does 
> not remain same through-out the life time of the application.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19798) Hive View 2.0: Tab switching on in table view broken

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849562#comment-15849562
 ] 

Hudson commented on AMBARI-19798:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6625 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6625/])
AMBARI-19798. Hive View 2.0: Tab switching on in table view broken. 
(dipayan.bhowmick: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1d17baf9f8cb6f89cc3b2c316b4a5603f1b111d5])
* (edit) contrib/views/hive20/src/main/resources/ui/app/components/tabs-item.js
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/styles/bootstrap-overrides.scss


> Hive View 2.0: Tab switching on in table view broken
> 
>
> Key: AMBARI-19798
> URL: https://issues.apache.org/jira/browse/AMBARI-19798
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.0
>
> Attachments: AMBARI-19798.branch-2.5.patch
>
>
> Active tab show different in when the application is in a route.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19819) Styling changes and spelling fixes

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849564#comment-15849564
 ] 

Hudson commented on AMBARI-19819:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6625 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6625/])
AMBARI-19819. Styling changes and spelling fixes (Madhan Mohan Reddy via 
(pallavkul: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a9ddb2fd2014954cb35821f8ad1f33faa3ae1d95])
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/workflow-job-details.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/shell-action.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/asset-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/asset-manager.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/archive-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/workflow-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/global-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/date-with-expr.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/hive-action.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/components/job-config.js
* (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/save-wf.js
* (edit) contrib/views/wfmanager/src/main/resources/ui/app/styles/app.less
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/designer-errors.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/designer-workspace.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/hive2-action.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/components/flow-designer.js
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/spark-action.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/coord-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/coord-job-details.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/sub-workflow.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/name-value-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/bundle-coord-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/help-icon.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/validators/operand-length.js
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/components/job-details.js
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/components/asset-config.js
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/file-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/prepare-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/components/bundle-config.js
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/asset-list.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/instance-list-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/pig-action.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/arg-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/job-row.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/workflow-action-editor.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/job-details.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/save-wf.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/prepare-config-fs.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/bundle-job-details.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/job-config.hbs


> Styling changes and spelling fixes 
> ---
>
> Key: AMBARI-19819
> URL: https://issues.apache.org/jira/browse/AMBARI-19819
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: M Madhan Mohan Reddy
>Assignee: M Madhan Mohan Reddy
>  Labels: WFD
> Fix For: 2.5.0
>
> Attachments: AMBARI-19819_trunk.patch
>
>
> Spelling fixes given by Beverley and minor coolor changes based on inputs 

[jira] [Commented] (AMBARI-19792) Hive View 2.0: Jobs page shows "Invalid date - Jan 24"

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849554#comment-15849554
 ] 

Hudson commented on AMBARI-19792:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #875 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/875/])
AMBARI-19792. Hive View 2.0: Jobs page shows 'Invalid date - Jan 24'. 
(dipayan.bhowmick: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3f41dbc80fcc1fe2a3620df8df5d1da58c5bb126])
* (edit) contrib/views/hive20/src/main/resources/ui/app/controllers/jobs.js
* (edit) contrib/views/hive20/src/main/resources/ui/app/app.js
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/components/jobs-browser.js
* (edit) contrib/views/hive20/src/main/resources/ui/app/routes/jobs.js
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/templates/components/jobs-browser.hbs
* (edit) contrib/views/hive20/src/main/resources/ui/config/environment.js


> Hive View 2.0: Jobs page shows "Invalid date - Jan 24"
> --
>
> Key: AMBARI-19792
> URL: https://issues.apache.org/jira/browse/AMBARI-19792
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.0
>
> Attachments: AMBARI-19792.branch-2.5.patch
>
>
> Jobs page shows: "Invalid date - Jan 24" as well as the filter criteria does 
> not remain same through-out the life time of the application.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19798) Hive View 2.0: Tab switching on in table view broken

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849551#comment-15849551
 ] 

Hudson commented on AMBARI-19798:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #875 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/875/])
AMBARI-19798. Hive View 2.0: Tab switching on in table view broken. 
(dipayan.bhowmick: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e29fa051c9481b016fdfc85236e25f2eaa672702])
* (edit) contrib/views/hive20/src/main/resources/ui/app/components/tabs-item.js
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/styles/bootstrap-overrides.scss


> Hive View 2.0: Tab switching on in table view broken
> 
>
> Key: AMBARI-19798
> URL: https://issues.apache.org/jira/browse/AMBARI-19798
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.0
>
> Attachments: AMBARI-19798.branch-2.5.patch
>
>
> Active tab show different in when the application is in a route.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19819) Styling changes and spelling fixes

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849553#comment-15849553
 ] 

Hudson commented on AMBARI-19819:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #875 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/875/])
AMBARI-19819. Styling changes and spelling fixes (Madhan Mohan Reddy via 
(pallavkul: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=952bf9de3d13c6cd5913d3c08e1f4c558d58599b])
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/bundle-job-details.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/coord-job-details.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/sub-workflow.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/date-with-expr.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/coord-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/prepare-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/global-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/file-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/prepare-config-fs.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/hive-action.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/arg-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/components/asset-config.js
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/components/flow-designer.js
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/instance-list-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/bundle-coord-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/designer-workspace.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/spark-action.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/asset-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/pig-action.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/save-wf.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/workflow-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/help-icon.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/archive-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/name-value-config.hbs
* (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/save-wf.js
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/job-details.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/asset-list.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/job-row.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/components/bundle-config.js
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/shell-action.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/job-config.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/hive2-action.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/components/job-details.js
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/workflow-action-editor.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/validators/operand-length.js
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/asset-manager.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/components/job-config.js
* (edit) contrib/views/wfmanager/src/main/resources/ui/app/styles/app.less
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/designer-errors.hbs
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/templates/components/workflow-job-details.hbs


> Styling changes and spelling fixes 
> ---
>
> Key: AMBARI-19819
> URL: https://issues.apache.org/jira/browse/AMBARI-19819
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: M Madhan Mohan Reddy
>Assignee: M Madhan Mohan Reddy
>  Labels: WFD
> Fix For: 2.5.0
>
> Attachments: AMBARI-19819_trunk.patch
>
>
> Spelling fixes given by Beverley and minor coolor changes based on inputs 
> 

[jira] [Commented] (AMBARI-19817) Hive View 2.0: Introduce service checks

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849552#comment-15849552
 ] 

Hudson commented on AMBARI-19817:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #875 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/875/])
AMBARI-19817. Hive View 2.0: Introduce service checks. (dipayanb) 
(dipayan.bhowmick: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d1c9c9174a86958ddbc0eb4d89d39d43c3928d58])
* (add) 
contrib/views/hive20/src/main/resources/ui/app/configs/service-check-status.js
* (add) 
contrib/views/hive20/src/main/resources/ui/app/components/service-check-entry.js
* (add) contrib/views/hive20/src/main/resources/ui/app/routes/service-check.js
* (edit) contrib/views/hive20/src/main/resources/ui/app/router.js
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/components/top-application-bar.js
* (add) 
contrib/views/hive20/src/main/resources/ui/app/controllers/service-check.js
* (add) contrib/views/hive20/src/main/resources/ui/app/adapters/service-check.js
* (add) 
contrib/views/hive20/src/main/resources/ui/app/templates/service-check.hbs
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/templates/application.hbs
* (add) 
contrib/views/hive20/src/main/resources/ui/app/templates/components/service-check-entry.hbs
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/templates/components/top-application-bar.hbs
* (edit) contrib/views/hive20/src/main/resources/ui/app/routes/application.js
* (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/application.js
* (add) 
contrib/views/hive20/src/main/resources/ui/app/controllers/application.js
* (add) contrib/views/hive20/src/main/resources/ui/app/services/service-check.js


> Hive View 2.0: Introduce service checks
> ---
>
> Key: AMBARI-19817
> URL: https://issues.apache.org/jira/browse/AMBARI-19817
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.0
>
> Attachments: AMBARI-19817.branch-2.5.patch
>
>
> Service Checks should also be present in Hive View 2.0 as it was there in 
> Hive View 1.5



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (AMBARI-19841) Add 'yarn.client.failover-proxy-provider' in yarn-site.xml by default for all HA enabled clusters

[Sumit Mohanty (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Mohanty resolved AMBARI-19841.

Resolution: Fixed

Committed to trunk and branch-2.5

> Add 'yarn.client.failover-proxy-provider' in yarn-site.xml by default for all 
> HA enabled clusters
> -
>
> Key: AMBARI-19841
> URL: https://issues.apache.org/jira/browse/AMBARI-19841
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.0
>
>
> 
> When HA is enabled, the class to be used by Clients, AMs and
>   NMs to failover to the Active RM. It should extend
>   org.apache.hadoop.yarn.client.RMFailoverProxyProvider
> yarn.client.failover-proxy-provider
> 
> org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider
>   
> needs to be added to yarn-site.xml for HDP 2.6/fenton



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19733) Regression in Spark2 keytab and {{stack_root}} for Livy2

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849522#comment-15849522
 ] 

Hudson commented on AMBARI-19733:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6624 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6624/])
AMBARI-19733: Regression in Spark2 keytab and {{stack_root}} for Livy2 
(jluniya: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b01438c7dc82ec9f0263eed8b6c1575491e78f6b])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/kerberos.json
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/configuration/livy2-env.xml


> Regression in Spark2 keytab and {{stack_root}} for Livy2
> 
>
> Key: AMBARI-19733
> URL: https://issues.apache.org/jira/browse/AMBARI-19733
> Project: Ambari
>  Issue Type: Bug
>Reporter: Bikas Saha
>Assignee: Bikas Saha
> Fix For: 2.5.0
>
> Attachments: AMBARI-19733.1.patch, AMBARI-19733.2.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19733) Regression in Spark2 keytab and {{stack_root}} for Livy2

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849519#comment-15849519
 ] 

Hudson commented on AMBARI-19733:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #874 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/874/])
AMBARI-19733: Regression in Spark2 keytab and {{stack_root}} for Livy2 
(jluniya: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2ccee3d2617f1e620dac49ced5414697d9928555])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/configuration/livy2-env.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/kerberos.json


> Regression in Spark2 keytab and {{stack_root}} for Livy2
> 
>
> Key: AMBARI-19733
> URL: https://issues.apache.org/jira/browse/AMBARI-19733
> Project: Ambari
>  Issue Type: Bug
>Reporter: Bikas Saha
>Assignee: Bikas Saha
> Fix For: 2.5.0
>
> Attachments: AMBARI-19733.1.patch, AMBARI-19733.2.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19842) Custom Action should be created without prompting for the action type

[Padma Priya Nagaraj (JIRA)]

Padma Priya Nagaraj created AMBARI-19842:


 Summary: Custom Action should be created without prompting for the 
action type
 Key: AMBARI-19842
 URL: https://issues.apache.org/jira/browse/AMBARI-19842
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Affects Versions: 2.5.0
Reporter: Padma Priya Nagaraj
Assignee: Padma Priya Nagaraj
 Fix For: 2.5.0


User is prompted to enter an action type before creating a custom action. It 
restricts user from changing the custom action type while creating the action. 
The user should be provided with a flexibility to create a custom action of any 
type while creating the action.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19817) Hive View 2.0: Introduce service checks

[DIPAYAN BHOWMICK (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

DIPAYAN BHOWMICK updated AMBARI-19817:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to branch-2.5, trunk.

> Hive View 2.0: Introduce service checks
> ---
>
> Key: AMBARI-19817
> URL: https://issues.apache.org/jira/browse/AMBARI-19817
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.0
>
> Attachments: AMBARI-19817.branch-2.5.patch
>
>
> Service Checks should also be present in Hive View 2.0 as it was there in 
> Hive View 1.5



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19792) Hive View 2.0: Jobs page shows "Invalid date - Jan 24"

[DIPAYAN BHOWMICK (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

DIPAYAN BHOWMICK updated AMBARI-19792:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to branch-2.5, trunk.

> Hive View 2.0: Jobs page shows "Invalid date - Jan 24"
> --
>
> Key: AMBARI-19792
> URL: https://issues.apache.org/jira/browse/AMBARI-19792
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.0
>
> Attachments: AMBARI-19792.branch-2.5.patch
>
>
> Jobs page shows: "Invalid date - Jan 24" as well as the filter criteria does 
> not remain same through-out the life time of the application.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19798) Hive View 2.0: Tab switching on in table view broken

[DIPAYAN BHOWMICK (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

DIPAYAN BHOWMICK updated AMBARI-19798:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to branch-2.5, trunk.

> Hive View 2.0: Tab switching on in table view broken
> 
>
> Key: AMBARI-19798
> URL: https://issues.apache.org/jira/browse/AMBARI-19798
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.0
>
> Attachments: AMBARI-19798.branch-2.5.patch
>
>
> Active tab show different in when the application is in a route.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-14671) Reevaluate the use of threadpools in Ambari code base

[Jayush Luniya (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-14671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayush Luniya updated AMBARI-14671:
---
Fix Version/s: (was: 2.5.0)
   3.0.0

> Reevaluate the use of threadpools in Ambari code base
> -
>
> Key: AMBARI-14671
> URL: https://issues.apache.org/jira/browse/AMBARI-14671
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 3.0.0
>
> Attachments: DynamicScaling.tgz
>
>
> As part of investigation for BUG-43981, noticed that in many places in the 
> Ambari code base, the way we use the threadpool is not quite correct.  We 
> will never scale up the number of threads on high load when we use unbounded 
> queues. This could lead to performance bottlenecks especially if we are 
> configure ThreadPoolExecutor with corePoolSize=0 and maxPoolSize=10, only one 
> thread will ever be spawned. See observations below
> Observations: 
> 1. When a ThreadPoolExecutor object is created, the pool size is 0 (i.e. no 
> new threads are created then) unless prestartAllCoreThreads() is called. Also 
> if we set allowCoreThreadTimeOut(true), idle core threads will also be 
> reclaimed.
> 2. In our code base, I observed that we create a threadpool using unlimited 
> queue. However the pool will never scale up from coreThreads -> maxThreads as 
> the request will always get queued. 
> {code:java}
> LinkedBlockingQueue queue = new LinkedBlockingQueue(); // 
> unlimited Queue
> ThreadPoolExecutor threadPoolExecutor =
> new ThreadPoolExecutor(
> THREAD_POOL_CORE_SIZE,
> THREAD_POOL_MAX_SIZE,
> THREAD_POOL_TIMEOUT_MILLIS,
> TimeUnit.MILLISECONDS,
> queue);
> {code}
> http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ThreadPoolExecutor.html
> {quote}
> Unbounded queues. Using an unbounded queue (for example a LinkedBlockingQueue 
> without a predefined capacity) will cause new tasks to wait in the queue when 
> all corePoolSize threads are busy. Thus, no more than corePoolSize threads 
> will ever be created. (And the value of the maximumPoolSize therefore doesn't 
> have any effect.) This may be appropriate when each task is completely 
> independent of others, so tasks cannot affect each others execution; for 
> example, in a web page server. While this style of queuing can be useful in 
> smoothing out transient bursts of requests, it admits the possibility of 
> unbounded work queue growth when commands continue to arrive on average 
> faster than they can be processed.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19733) Regression in Spark2 keytab and {{stack_root}} for Livy2

[Jayush Luniya (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayush Luniya updated AMBARI-19733:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Regression in Spark2 keytab and {{stack_root}} for Livy2
> 
>
> Key: AMBARI-19733
> URL: https://issues.apache.org/jira/browse/AMBARI-19733
> Project: Ambari
>  Issue Type: Bug
>Reporter: Bikas Saha
>Assignee: Bikas Saha
> Fix For: 2.5.0
>
> Attachments: AMBARI-19733.1.patch, AMBARI-19733.2.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19733) Regression in Spark2 keytab and {{stack_root}} for Livy2

[Jayush Luniya (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849481#comment-15849481
 ] 

Jayush Luniya commented on AMBARI-19733:


Trunk
commit b01438c7dc82ec9f0263eed8b6c1575491e78f6b
Author: Jayush Luniya 
Date:   Wed Feb 1 21:54:08 2017 -0800

AMBARI-19733: Regression in Spark2 keytab and {{stack_root}} for Livy2 
(Bikas Saha via jluniya)

Branch-2.5
commit 2ccee3d2617f1e620dac49ced5414697d9928555
Author: Jayush Luniya 
Date:   Wed Feb 1 21:54:08 2017 -0800

AMBARI-19733: Regression in Spark2 keytab and {{stack_root}} for Livy2 
(Bikas Saha via jluniya)


> Regression in Spark2 keytab and {{stack_root}} for Livy2
> 
>
> Key: AMBARI-19733
> URL: https://issues.apache.org/jira/browse/AMBARI-19733
> Project: Ambari
>  Issue Type: Bug
>Reporter: Bikas Saha
>Assignee: Bikas Saha
> Fix For: 2.5.0
>
> Attachments: AMBARI-19733.1.patch, AMBARI-19733.2.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19816) Agent heartbeat lost due to dead service check process

[Sumit Mohanty (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Mohanty updated AMBARI-19816:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to addendum patch to trunk and branch-2.5

> Agent heartbeat lost due to dead service check process
> --
>
> Key: AMBARI-19816
> URL: https://issues.apache.org/jira/browse/AMBARI-19816
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19816.2.patch, AMBARI-19816.patch
>
>
> Ambari Agent heartbeat loop can get stuck in getting service status via the 
> {{subprocess}} module. This can happen if the invoked process dies.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19825) Metrics data is not getting collected for different services when AMS HTTPS is enabled

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849448#comment-15849448
 ] 

Hadoop QA commented on AMBARI-19825:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12850522/AMBARI-19825-trunk.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-metrics/ambari-metrics-flume-sink 
ambari-metrics/ambari-metrics-hadoop-sink ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/10375//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/10375//console

This message is automatically generated.

> Metrics data is not getting collected for different services when AMS HTTPS 
> is enabled
> --
>
> Key: AMBARI-19825
> URL: https://issues.apache.org/jira/browse/AMBARI-19825
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19825-2.5.patch, AMBARI-19825-trunk.patch
>
>
> {code}
> org.apache.hadoop.metrics2.impl.MetricsConfigException: Error creating 
> plugin: org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink
> at 
> org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:203)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.newSink(MetricsSystemImpl.java:529)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configureSinks(MetricsSystemImpl.java:501)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configure(MetricsSystemImpl.java:480)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.start(MetricsSystemImpl.java:189)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.init(MetricsSystemImpl.java:164)
> at 
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.init(DefaultMetricsSystem.java:54)
> at 
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.initialize(DefaultMetricsSystem.java:50)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.makeInstance(DataNode.java:2530)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:2435)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.createDataNode(DataNode.java:2482)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.secureMain(DataNode.java:2622)
> at 
> org.apache.hadoop.hdfs.server.datanode.SecureDataNodeStarter.start(SecureDataNodeStarter.java:77)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243)
> Caused by: java.lang.IllegalArgumentException: no SSLSocketFactory specified
> at 
> javax.net.ssl.HttpsURLConnection.setSSLSocketFactory(HttpsURLConnection.java:357)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.getSSLConnection(AbstractTimelineMetricsSink.java:284)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findLiveCollectorHostsFromKnownCollector(AbstractTimelineMetricsSink.java:440)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.refreshCollectorsFromConfigured(AbstractTimelineMetricsSink.java:412)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:352)
> at 
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.init(HadoopTimelineMetricsSink.java:110)
> at 
> org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:199)
>

[jira] [Created] (AMBARI-19841) Add 'yarn.client.failover-proxy-provider' in yarn-site.xml by default for all HA enabled clusters

[Madhuvanthi Radhakrishnan (JIRA)]

Madhuvanthi Radhakrishnan created AMBARI-19841:
--

 Summary: Add 'yarn.client.failover-proxy-provider' in 
yarn-site.xml by default for all HA enabled clusters
 Key: AMBARI-19841
 URL: https://issues.apache.org/jira/browse/AMBARI-19841
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Reporter: Madhuvanthi Radhakrishnan
Assignee: Madhuvanthi Radhakrishnan
 Fix For: 2.5.0



When HA is enabled, the class to be used by Clients, AMs and
  NMs to failover to the Active RM. It should extend
  org.apache.hadoop.yarn.client.RMFailoverProxyProvider
yarn.client.failover-proxy-provider

org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider
  

needs to be added to yarn-site.xml for HDP 2.6/fenton



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19827) HiveServer2 Interactive won't start in clusters with less memory

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849420#comment-15849420
 ] 

Hadoop QA commented on AMBARI-19827:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12850523/AMBARI-19827.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/10374//console

This message is automatically generated.

> HiveServer2 Interactive won't start in clusters with less memory
> 
>
> Key: AMBARI-19827
> URL: https://issues.apache.org/jira/browse/AMBARI-19827
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19827.patch
>
>
> HS2 Interactive in a 3 node local cluster with 3.5G memory in each node. The 
> task fails due to this exception:
> {code:java}
> WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns 
> does not exist
> WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT 
> type value
> Failed: null
> java.lang.IllegalArgumentException
>   at 
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1307)
>   at 
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1230)
>   at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151)
>   at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:197)
>   at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:112)
> INFO cli.LlapServiceDriver: LLAP service driver finished
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19830) HDP 3.0 TP - Support changed configs and scripts for HDFS

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849382#comment-15849382
 ] 

Hadoop QA commented on AMBARI-19830:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12850527/AMBARI-19830.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/10373//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/10373//console

This message is automatically generated.

> HDP 3.0 TP - Support changed configs and scripts for HDFS
> -
>
> Key: AMBARI-19830
> URL: https://issues.apache.org/jira/browse/AMBARI-19830
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19830.patch
>
>
> In HDP 3.0, there are expected changes to configs and the startup scripts for 
> HDFS.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19816) Agent heartbeat lost due to dead service check process

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849350#comment-15849350
 ] 

Hadoop QA commented on AMBARI-19816:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12850498/AMBARI-19816.2.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/10372//console

This message is automatically generated.

> Agent heartbeat lost due to dead service check process
> --
>
> Key: AMBARI-19816
> URL: https://issues.apache.org/jira/browse/AMBARI-19816
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19816.2.patch, AMBARI-19816.patch
>
>
> Ambari Agent heartbeat loop can get stuck in getting service status via the 
> {{subprocess}} module. This can happen if the invoked process dies.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19829) Several HDFS/YARN widgets on Heatmaps show N/A

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849349#comment-15849349
 ] 

Hadoop QA commented on AMBARI-19829:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12850507/AMBARI-19829.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/10371//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/10371//console

This message is automatically generated.

> Several HDFS/YARN widgets on Heatmaps show N/A
> --
>
> Key: AMBARI-19829
> URL: https://issues.apache.org/jira/browse/AMBARI-19829
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-19829.patch
>
>
> The following HDFS/YARN widgets on Heatmaps show N/A:
> 1. HDFS - HDFS Bytes Written, HDFS Bytes Read, DataNode Process Disk I/O 
> Utilization, and DataNode Process Network I/O Utilization
> 2. YARN - Container Failures
> The issue was introduced by AMBARI-15835 "Rate metrics requesting widgets do 
> not show up on Ambari" which introduced rate metrics and applied rate metrics 
> to several HBASE/HDFS/YARN widgets on Summary pages  as well as Heatmap 
> pages. Rate metrics work fine on Summary pages but they don't work on Heatmap 
> pages because current Heatmap design can only show point-in-time metrics and 
> rate metrics need a time range.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19809) HDP 3.0 TP - failed to deploy YARN configs because yarn-site creates conflicts since should not belong to MAPREDUCE2

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849289#comment-15849289
 ] 

Hudson commented on AMBARI-19809:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6623 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6623/])
AMBARI-19809. HDP 3.0 TP - failed to deploy YARN configs because (afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c744cac60ebe0ae4046278f7ef78fe20d0872b0e])
* (edit) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/metainfo.xml
* (edit) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/service_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/metainfo.xml


> HDP 3.0 TP - failed to deploy YARN configs because yarn-site creates 
> conflicts since should not belong to MAPREDUCE2
> 
>
> Key: AMBARI-19809
> URL: https://issues.apache.org/jira/browse/AMBARI-19809
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19809.patch
>
>
> STR:
> * Install Ambari trunk
> * Install HDP 3.0, e.g., centos6: 
> http://s3.amazonaws.com/dev.hortonworks.com/HDP/centos6/3.x/BUILDS/3.0.0.0-30
> * Select ZK, HDFS, YARN
> * During deployment, will see the following error in the ambari-server log
> {noformat}
> 26 Jan 2017 20:01:48,119 ERROR [ambari-client-thread-26] ClusterImpl:2662 - 
> Updating configs for multiple services by a single API request isn't 
> supported. Conflicting services YARN and MAPREDUCE2 for yarn-site, config 
> version not created for YARN
> {noformat}
> This is because yarn-site is marked right now as belonging to both YARN and 
> MAPREDUCE2, which is incorrect since it should not belong to MAPREDUCE2.
> The fix update the HDP 3.0 service definition for MAPREDUCE2 to use the 
> correct configuration directory.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19813) findLatestServiceConfigsByStack query returns deleted config group

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849286#comment-15849286
 ] 

Hadoop QA commented on AMBARI-19813:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12850509/AMBARI-19813.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 patch failed these unit tests in 
ambari-server:

  org.apache.ambari.server.agent.HeartbeatProcessorTest
  
org.apache.ambari.server.serveraction.upgrades.UpgradeActionTest

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/10370//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/10370//console

This message is automatically generated.

> findLatestServiceConfigsByStack query returns deleted config group
> --
>
> Key: AMBARI-19813
> URL: https://issues.apache.org/jira/browse/AMBARI-19813
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-19813.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19814) 'num_llap_nodes' should show up as non-editable property when non-ambari managed queue is selected

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849288#comment-15849288
 ] 

Hudson commented on AMBARI-19814:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6623 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6623/])
ADDENDUM. AMBARI-19814. Backend path for 'num_llap_nodes' should show up 
(sshridhar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e406234a7dcc1f11f9f13c8e40fd64187e20eaf8])
* (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


> 'num_llap_nodes' should show up as non-editable property when non-ambari 
> managed queue is selected
> --
>
> Key: AMBARI-19814
> URL: https://issues.apache.org/jira/browse/AMBARI-19814
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
>  Labels: llap
> Fix For: 2.5.0
>
> Attachments: AMBARI-19814.backend.01.patch, AMBARI-19814.patch
>
>
> - 'num_llap_nodes' as of now is shown as a slider and comes only when we have 
> selected 'llap' named queue and is a child of root level. It is shown because 
> 'num_llap_nodes' visible attribute is set as True by SA.
> - For any other queue, 'num_llap_nodes' is set as visible=false by SA call 
> and is not shown on UI.
> *Expected:*
> A way to show 'num_llap_nodes' node on UI for user, irrespective of the queue 
> selected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19814) 'num_llap_nodes' should show up as non-editable property when non-ambari managed queue is selected

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849285#comment-15849285
 ] 

Hudson commented on AMBARI-19814:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #873 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/873/])
ADDENDUM. AMBARI-19814. Backend path for 'num_llap_nodes' should show up 
(sshridhar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0b5f375db8744e47a009a52a74ae3d2dfe7749ab])
* (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


> 'num_llap_nodes' should show up as non-editable property when non-ambari 
> managed queue is selected
> --
>
> Key: AMBARI-19814
> URL: https://issues.apache.org/jira/browse/AMBARI-19814
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
>  Labels: llap
> Fix For: 2.5.0
>
> Attachments: AMBARI-19814.backend.01.patch, AMBARI-19814.patch
>
>
> - 'num_llap_nodes' as of now is shown as a slider and comes only when we have 
> selected 'llap' named queue and is a child of root level. It is shown because 
> 'num_llap_nodes' visible attribute is set as True by SA.
> - For any other queue, 'num_llap_nodes' is set as visible=false by SA call 
> and is not shown on UI.
> *Expected:*
> A way to show 'num_llap_nodes' node on UI for user, irrespective of the queue 
> selected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19840) Atlas Metadata Server Fails to start

[Vivek Rathod (JIRA)]

Vivek Rathod created AMBARI-19840:
-

 Summary: Atlas Metadata Server Fails to start
 Key: AMBARI-19840
 URL: https://issues.apache.org/jira/browse/AMBARI-19840
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.5.0
Reporter: Vivek Rathod
 Fix For: 2.5.0


Atlas Metadata Server Fails to start after deleting and adding back atlas.
STR:
1) Delete the following services from the cluster: Smartsense, Atlas, Hbase, 
Sqoop, Storm, Knox, Flume and AMS
2) Add back the deleted services using Add service Wizard
Atlas Metadata Server fails with

{code}
ERROR Java::OrgApacheHadoopHbaseIpc::RemoteWithExtrasException: 
org.apache.hadoop.hbase.coprocessor.CoprocessorException: SSLContext must not 
be null
at 
org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor.grant(RangerAuthorizationCoprocessor.java:1180)
at 
org.apache.hadoop.hbase.protobuf.generated.AccessControlProtos$AccessControlService$1.grant(AccessControlProtos.java:9933)
at 
org.apache.hadoop.hbase.protobuf.generated.AccessControlProtos$AccessControlService.callMethod(AccessControlProtos.java:10097)
at 
org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:7832)
at 
org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1961)
at 
org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1943)
at 
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:32389)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2141)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:112)
at 
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:187)
at 
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:167)
{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19816) Agent heartbeat lost due to dead service check process

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849222#comment-15849222
 ] 

Hudson commented on AMBARI-19816:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #872 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/872/])
AMBARI-19816. Agent heartbeat lost due to dead service check process - 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8832146e96be59ea117e155b46936b4d28e1d7e0])
* (edit) ambari-agent/src/test/python/ambari_agent/TestHardware.py
* (edit) ambari-agent/src/main/python/ambari_agent/Hardware.py


> Agent heartbeat lost due to dead service check process
> --
>
> Key: AMBARI-19816
> URL: https://issues.apache.org/jira/browse/AMBARI-19816
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19816.2.patch, AMBARI-19816.patch
>
>
> Ambari Agent heartbeat loop can get stuck in getting service status via the 
> {{subprocess}} module. This can happen if the invoked process dies.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19816) Agent heartbeat lost due to dead service check process

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849217#comment-15849217
 ] 

Hudson commented on AMBARI-19816:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6622 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6622/])
AMBARI-19816. Agent heartbeat lost due to dead service check process - 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c10fcc8f3682e7e4a2924e8a58fa895920fef908])
* (edit) ambari-agent/src/main/python/ambari_agent/Hardware.py
* (edit) ambari-agent/src/test/python/ambari_agent/TestHardware.py


> Agent heartbeat lost due to dead service check process
> --
>
> Key: AMBARI-19816
> URL: https://issues.apache.org/jira/browse/AMBARI-19816
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19816.2.patch, AMBARI-19816.patch
>
>
> Ambari Agent heartbeat loop can get stuck in getting service status via the 
> {{subprocess}} module. This can happen if the invoked process dies.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19809) HDP 3.0 TP - failed to deploy YARN configs because yarn-site creates conflicts since should not belong to MAPREDUCE2

[Alejandro Fernandez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-19809:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Pushed to trunk, commit c744cac60ebe0ae4046278f7ef78fe20d0872b0e

> HDP 3.0 TP - failed to deploy YARN configs because yarn-site creates 
> conflicts since should not belong to MAPREDUCE2
> 
>
> Key: AMBARI-19809
> URL: https://issues.apache.org/jira/browse/AMBARI-19809
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19809.patch
>
>
> STR:
> * Install Ambari trunk
> * Install HDP 3.0, e.g., centos6: 
> http://s3.amazonaws.com/dev.hortonworks.com/HDP/centos6/3.x/BUILDS/3.0.0.0-30
> * Select ZK, HDFS, YARN
> * During deployment, will see the following error in the ambari-server log
> {noformat}
> 26 Jan 2017 20:01:48,119 ERROR [ambari-client-thread-26] ClusterImpl:2662 - 
> Updating configs for multiple services by a single API request isn't 
> supported. Conflicting services YARN and MAPREDUCE2 for yarn-site, config 
> version not created for YARN
> {noformat}
> This is because yarn-site is marked right now as belonging to both YARN and 
> MAPREDUCE2, which is incorrect since it should not belong to MAPREDUCE2.
> The fix update the HDP 3.0 service definition for MAPREDUCE2 to use the 
> correct configuration directory.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19814) 'num_llap_nodes' should show up as non-editable property when non-ambari managed queue is selected

[Swapan Shridhar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapan Shridhar updated AMBARI-19814:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> 'num_llap_nodes' should show up as non-editable property when non-ambari 
> managed queue is selected
> --
>
> Key: AMBARI-19814
> URL: https://issues.apache.org/jira/browse/AMBARI-19814
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
>  Labels: llap
> Fix For: 2.5.0
>
> Attachments: AMBARI-19814.backend.01.patch, AMBARI-19814.patch
>
>
> - 'num_llap_nodes' as of now is shown as a slider and comes only when we have 
> selected 'llap' named queue and is a child of root level. It is shown because 
> 'num_llap_nodes' visible attribute is set as True by SA.
> - For any other queue, 'num_llap_nodes' is set as visible=false by SA call 
> and is not shown on UI.
> *Expected:*
> A way to show 'num_llap_nodes' node on UI for user, irrespective of the queue 
> selected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19814) 'num_llap_nodes' should show up as non-editable property when non-ambari managed queue is selected

[Swapan Shridhar (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849210#comment-15849210
 ] 

Swapan Shridhar commented on AMBARI-19814:
--

commit for patch [^AMBARI-19814.backend.01.patch]


branch-2.5:

{code}
commit 0b5f375db8744e47a009a52a74ae3d2dfe7749ab
Author: Swapan Shridhar 
Date:   Wed Feb 1 17:08:41 2017 -0800

ADDENDUM. AMBARI-19814. Backend path for 'num_llap_nodes' should show up as 
non-editable property when non-ambari managed queue is selected.
{code}

trunk

{code}
commit e406234a7dcc1f11f9f13c8e40fd64187e20eaf8
Author: Swapan Shridhar 
Date:   Wed Feb 1 17:08:41 2017 -0800

ADDENDUM. AMBARI-19814. Backend path for 'num_llap_nodes' should show up as 
non-editable property when non-ambari managed queue is selected.
{code}

> 'num_llap_nodes' should show up as non-editable property when non-ambari 
> managed queue is selected
> --
>
> Key: AMBARI-19814
> URL: https://issues.apache.org/jira/browse/AMBARI-19814
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
>  Labels: llap
> Fix For: 2.5.0
>
> Attachments: AMBARI-19814.backend.01.patch, AMBARI-19814.patch
>
>
> - 'num_llap_nodes' as of now is shown as a slider and comes only when we have 
> selected 'llap' named queue and is a child of root level. It is shown because 
> 'num_llap_nodes' visible attribute is set as True by SA.
> - For any other queue, 'num_llap_nodes' is set as visible=false by SA call 
> and is not shown on UI.
> *Expected:*
> A way to show 'num_llap_nodes' node on UI for user, irrespective of the queue 
> selected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19830) HDP 3.0 TP - Support changed configs and scripts for HDFS

[Alejandro Fernandez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-19830:
-
Attachment: AMBARI-19830.patch

> HDP 3.0 TP - Support changed configs and scripts for HDFS
> -
>
> Key: AMBARI-19830
> URL: https://issues.apache.org/jira/browse/AMBARI-19830
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19830.patch
>
>
> In HDP 3.0, there are expected changes to configs and the startup scripts for 
> HDFS.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19830) HDP 3.0 TP - Support changed configs and scripts for HDFS

[Alejandro Fernandez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-19830:
-
Status: Patch Available  (was: Open)

> HDP 3.0 TP - Support changed configs and scripts for HDFS
> -
>
> Key: AMBARI-19830
> URL: https://issues.apache.org/jira/browse/AMBARI-19830
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19830.patch
>
>
> In HDP 3.0, there are expected changes to configs and the startup scripts for 
> HDFS.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19814) 'num_llap_nodes' should show up as non-editable property when non-ambari managed queue is selected

[Swapan Shridhar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapan Shridhar updated AMBARI-19814:
-
Attachment: AMBARI-19814.backend.01.patch

> 'num_llap_nodes' should show up as non-editable property when non-ambari 
> managed queue is selected
> --
>
> Key: AMBARI-19814
> URL: https://issues.apache.org/jira/browse/AMBARI-19814
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
>  Labels: llap
> Fix For: 2.5.0
>
> Attachments: AMBARI-19814.backend.01.patch, AMBARI-19814.patch
>
>
> - 'num_llap_nodes' as of now is shown as a slider and comes only when we have 
> selected 'llap' named queue and is a child of root level. It is shown because 
> 'num_llap_nodes' visible attribute is set as True by SA.
> - For any other queue, 'num_llap_nodes' is set as visible=false by SA call 
> and is not shown on UI.
> *Expected:*
> A way to show 'num_llap_nodes' node on UI for user, irrespective of the queue 
> selected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19814) 'num_llap_nodes' should show up as non-editable property when non-ambari managed queue is selected

[Swapan Shridhar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapan Shridhar updated AMBARI-19814:
-
Attachment: (was: AMBARI-19814.backend.patch)

> 'num_llap_nodes' should show up as non-editable property when non-ambari 
> managed queue is selected
> --
>
> Key: AMBARI-19814
> URL: https://issues.apache.org/jira/browse/AMBARI-19814
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
>  Labels: llap
> Fix For: 2.5.0
>
> Attachments: AMBARI-19814.patch
>
>
> - 'num_llap_nodes' as of now is shown as a slider and comes only when we have 
> selected 'llap' named queue and is a child of root level. It is shown because 
> 'num_llap_nodes' visible attribute is set as True by SA.
> - For any other queue, 'num_llap_nodes' is set as visible=false by SA call 
> and is not shown on UI.
> *Expected:*
> A way to show 'num_llap_nodes' node on UI for user, irrespective of the queue 
> selected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19828) UI changes to resolve discrepancies between what the stack vs Ambari reports as "live" for NodeManagers

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849191#comment-15849191
 ] 

Hadoop QA commented on AMBARI-19828:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12850515/AMBARI-19828.v0.trunk.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 2 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/10369//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/10369//console

This message is automatically generated.

> UI changes to resolve discrepancies between what the stack vs Ambari reports 
> as "live" for NodeManagers
> ---
>
> Key: AMBARI-19828
> URL: https://issues.apache.org/jira/browse/AMBARI-19828
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-19828.v0.branch-2.5.patch, 
> AMBARI-19828.v0.trunk.patch
>
>
> Looks like the changes in https://issues.apache.org/jira/browse/AMBARI-9418 
> was meant to be applied to YARN summary / NodeManagers as well, but that is 
> not happening.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19838) HDP 3.0 TP - Support changed configs and scripts for Spark

[Alejandro Fernandez (JIRA)]

Alejandro Fernandez created AMBARI-19838:


 Summary: HDP 3.0 TP - Support changed configs and scripts for Spark
 Key: AMBARI-19838
 URL: https://issues.apache.org/jira/browse/AMBARI-19838
 Project: Ambari
  Issue Type: Story
  Components: stacks
Affects Versions: 3.0.0
Reporter: Alejandro Fernandez
 Fix For: 3.0.0


In HDP 3.0, there are expected changes to configs and the startup scripts for 
Spark.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19836) HDP 3.0 TP - Support changed configs and scripts for Hive

[Alejandro Fernandez (JIRA)]

Alejandro Fernandez created AMBARI-19836:


 Summary: HDP 3.0 TP - Support changed configs and scripts for Hive
 Key: AMBARI-19836
 URL: https://issues.apache.org/jira/browse/AMBARI-19836
 Project: Ambari
  Issue Type: Story
  Components: stacks
Affects Versions: 3.0.0
Reporter: Alejandro Fernandez
 Fix For: 3.0.0


In HDP 3.0, there are expected changes to configs and the startup scripts for 
Hive.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19837) HDP 3.0 TP - Support changed configs and scripts for Tez

[Alejandro Fernandez (JIRA)]

Alejandro Fernandez created AMBARI-19837:


 Summary: HDP 3.0 TP - Support changed configs and scripts for Tez
 Key: AMBARI-19837
 URL: https://issues.apache.org/jira/browse/AMBARI-19837
 Project: Ambari
  Issue Type: Story
  Components: stacks
Affects Versions: 3.0.0
Reporter: Alejandro Fernandez
 Fix For: 3.0.0


In HDP 3.0, there are expected changes to configs and the startup scripts for 
Tez.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19839) HDP 3.0 TP - Support changed configs and scripts for Slider

[Alejandro Fernandez (JIRA)]

Alejandro Fernandez created AMBARI-19839:


 Summary: HDP 3.0 TP - Support changed configs and scripts for 
Slider
 Key: AMBARI-19839
 URL: https://issues.apache.org/jira/browse/AMBARI-19839
 Project: Ambari
  Issue Type: Story
  Components: stacks
Affects Versions: 3.0.0
Reporter: Alejandro Fernandez
 Fix For: 3.0.0


In HDP 3.0, there are expected changes to configs and the startup scripts for 
Slider.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19834) HDP 3.0 support for Spark with configs, kerberos, widgets, metrics, quicklinks, and themes

[Alejandro Fernandez (JIRA)]

Alejandro Fernandez created AMBARI-19834:


 Summary: HDP 3.0 support for Spark with configs, kerberos, 
widgets, metrics, quicklinks, and themes
 Key: AMBARI-19834
 URL: https://issues.apache.org/jira/browse/AMBARI-19834
 Project: Ambari
  Issue Type: Story
  Components: stacks
Affects Versions: 3.0.0
Reporter: Alejandro Fernandez
 Fix For: 3.0.0


HDP 3.0 support for Spark with configs, kerberos, widgets, metrics, quicklinks, 
and themes
Flatten from HDP 2.0.6 - 2.6 into common-services, and reference in HDP 3.0
IMPORTANT: In HDP 3.0, Spark1 is being removed, and Spark2 is being rebranded 
as "Spark"
In HDP 3.0, we have created a new stack definition that does not inherit from 
other stacks, in order to reduce the complexity of having to analyze older 
stacks.
This means that we need to create a service definition (metainfo.xml, configs, 
kerberos, widgets, metrics, quicklinks, and themes) that is equivalent to what 
is inherit and deleted from all of the previous stacks.
A merge needs to account for additions, overrides, and deletions.
metainfo.xml and configs perform a merge of older versions
kerberos.json always seems to override the previous file
Because the bits for this service may not yet be available in the HDP 3.0 repo, 
the task is to ensure that /api/v1/stacks/HDP/versions/2.6/services/SPARK2 
(which uses inheritance) is equivalent to the flattening of 
/api/v1/stacks/HDP/versions/3.0/services/SPARK .
Please take a look at how this was done for ZK, HDFS, and YARN/MR.
This means that you will not be able to actually install the service for now, 
but can still perform validation during the Install Wizard that the correct 
components and configs show up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19835) HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, quicklinks, and themes

[Alejandro Fernandez (JIRA)]

Alejandro Fernandez created AMBARI-19835:


 Summary: HDP 3.0 support for Slider with configs, kerberos, 
widgets, metrics, quicklinks, and themes
 Key: AMBARI-19835
 URL: https://issues.apache.org/jira/browse/AMBARI-19835
 Project: Ambari
  Issue Type: Story
  Components: stacks
Affects Versions: 3.0.0
Reporter: Alejandro Fernandez
 Fix For: 3.0.0


HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, 
quicklinks, and themes
Flatten from HDP 2.0.6 - 2.6 into common-services, and reference in HDP 3.0
In HDP 3.0, we have created a new stack definition that does not inherit from 
other stacks, in order to reduce the complexity of having to analyze older 
stacks.
This means that we need to create a service definition (metainfo.xml, configs, 
kerberos, widgets, metrics, quicklinks, and themes) that is equivalent to what 
is inherit and deleted from all of the previous stacks.
A merge needs to account for additions, overrides, and deletions.
metainfo.xml and configs perform a merge of older versions
kerberos.json always seems to override the previous file
Because the bits for this service may not yet be available in the HDP 3.0 repo, 
the task is to ensure that /api/v1/stacks/HDP/versions/2.6/services/SLIDER 
(which uses inheritance) is equivalent to the flattening of 
/api/v1/stacks/HDP/versions/3.0/services/SLIDER .
Please take a look at how this was done for ZK, HDFS, and YARN/MR.
This means that you will not be able to actually install the service for now, 
but can still perform validation during the Install Wizard that the correct 
components and configs show up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19833) HDP 3.0 support for Tez with configs, kerberos, widgets, metrics, quicklinks, and themes

[Alejandro Fernandez (JIRA)]

Alejandro Fernandez created AMBARI-19833:


 Summary: HDP 3.0 support for Tez with configs, kerberos, widgets, 
metrics, quicklinks, and themes
 Key: AMBARI-19833
 URL: https://issues.apache.org/jira/browse/AMBARI-19833
 Project: Ambari
  Issue Type: Story
  Components: stacks
Affects Versions: 3.0.0
Reporter: Alejandro Fernandez
 Fix For: 3.0.0


HDP 3.0 support for Tez with configs, kerberos, widgets, metrics, quicklinks, 
and themes
Flatten from HDP 2.0.6 - 2.6 into common-services, and reference in HDP 3.0
In HDP 3.0, we have created a new stack definition that does not inherit from 
other stacks, in order to reduce the complexity of having to analyze older 
stacks.
This means that we need to create a service definition (metainfo.xml, configs, 
kerberos, widgets, metrics, quicklinks, and themes) that is equivalent to what 
is inherit and deleted from all of the previous stacks.
A merge needs to account for additions, overrides, and deletions.
metainfo.xml and configs perform a merge of older versions
kerberos.json always seems to override the previous file
Because the bits for this service may not yet be available in the HDP 3.0 repo, 
the task is to ensure that /api/v1/stacks/HDP/versions/2.6/services/TEZ (which 
uses inheritance) is equivalent to the flattening of 
/api/v1/stacks/HDP/versions/3.0/services/TEZ .
Please take a look at how this was done for ZK, HDFS, and YARN/MR.
This means that you will not be able to actually install the service for now, 
but can still perform validation during the Install Wizard that the correct 
components and configs show up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19832) HDP 3.0 support for Hive with configs, kerberos, widgets, metrics, quicklinks, and themes

[Alejandro Fernandez (JIRA)]

Alejandro Fernandez created AMBARI-19832:


 Summary: HDP 3.0 support for Hive with configs, kerberos, widgets, 
metrics, quicklinks, and themes
 Key: AMBARI-19832
 URL: https://issues.apache.org/jira/browse/AMBARI-19832
 Project: Ambari
  Issue Type: Story
  Components: stacks
Affects Versions: 3.0.0
Reporter: Alejandro Fernandez
 Fix For: 3.0.0


HDP 3.0 support for Hive with configs, kerberos, widgets, metrics, quicklinks, 
and themes
Flatten from HDP 2.0.6 - 2.6 into common-services, and reference in HDP 3.0

In HDP 3.0, we have created a new stack definition that does not inherit from 
other stacks, in order to reduce the complexity of having to analyze older 
stacks.
This means that we need to create a service definition (metainfo.xml, configs, 
kerberos, widgets, metrics, quicklinks, and themes) that is equivalent to what 
is inherit and deleted from all of the previous stacks.
A merge needs to account for additions, overrides, and deletions.
metainfo.xml and configs perform a merge of older versions
kerberos.json always seems to override the previous file

Because the bits for this service may not yet be available in the HDP 3.0 repo, 
the task is to ensure that /api/v1/stacks/HDP/versions/2.6/services/HIVE (which 
uses inheritance) is equivalent to the flattening of 
/api/v1/stacks/HDP/versions/3.0/services/HIVE .
Please take a look at how this was done for ZK, HDFS, and YARN/MR.

This means that you will not be able to actually install the service for now, 
but can still perform validation during the Install Wizard that the correct 
components and configs show up.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19806) After setting up hadoop credential, cannot start Hive Metastore

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849183#comment-15849183
 ] 

Hudson commented on AMBARI-19806:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6621 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6621/])
AMBARI-19806: After setting up hadoop credential, cannot start Hive 
(nsomasundaram: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d340fe93b51b82dc380ad7783cd63b7e76b72224])
* (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
* (edit) ambari-server/pom.xml
* (add) 
ambari-server/src/test/java/org/apache/ambari/server/credentialapi/CredentialUtilTest.java
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/credentialapi/CredentialUtil.java


> After setting up hadoop credential, cannot start Hive Metastore
> ---
>
> Key: AMBARI-19806
> URL: https://issues.apache.org/jira/browse/AMBARI-19806
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: rb56142.patch
>
>
> In HIVE, after javax.jdo.option.ConnectionPassword property and value is 
> moved  into a JCEKS file using hadoop credential store, hive-site.xml looks 
> like this:
> {quote} 
> hadoop.security.credential.provider.path
> jceks://file/usr/lib/hive/conf/hive.jceks
>   {quote}
> instead of:
> {quote} 
> javax.jdo.option.ConnectionPassword
> MyHiveConnectionPassword
>   {quote}
> However, after the above change, HIVE fails to start. This is an Ambari 
> deployed cluster.
> {quote}Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
>  line 259, in 
> HiveMetastore().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 287, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
>  line 59, in start
> self.configure(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
>  line 73, in configure
> hive(name = 'metastore')
>   File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
> line 89, in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
>  line 326, in hive
> create_schema_cmd = format("export HIVE_CONF_DIR={hive_server_conf_dir} ; 
> "
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 62, in format
> result_unprotected = self.vformat(format_string, args, all_params)
>   File "/usr/lib64/python2.6/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
>   File "/usr/lib64/python2.6/string.py", line 575, in _vformat
> obj = self.convert_field(obj, conversion)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 70, in convert_field_unprotected
> return self._convert_field(value, conversion, False)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 85, in _convert_field
> return utils.PASSWORDS_HIDE_STRING if is_protected else 
> self._convert_field(value, 'e', is_protected)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 81, in _convert_field
> return quote_bash_args(unicode(value))
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
>  line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in 
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'javax.jdo.option.ConnectionPassword' was not found in configurations 
> dictionary!{quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19831) HDP 3.0 TP - Support changed configs and scripts for YARN/MR

[Alejandro Fernandez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-19831:
-
Summary: HDP 3.0 TP - Support changed configs and scripts for YARN/MR  
(was: Support changed configs and scripts for YARN/MR)

> HDP 3.0 TP - Support changed configs and scripts for YARN/MR
> 
>
> Key: AMBARI-19831
> URL: https://issues.apache.org/jira/browse/AMBARI-19831
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
>
> In HDP 3.0, there are expected changes to configs and the startup scripts for 
> YARN/MR.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19831) Support changed configs and scripts for YARN/MR

[Alejandro Fernandez (JIRA)]

Alejandro Fernandez created AMBARI-19831:


 Summary: Support changed configs and scripts for YARN/MR
 Key: AMBARI-19831
 URL: https://issues.apache.org/jira/browse/AMBARI-19831
 Project: Ambari
  Issue Type: Story
  Components: stacks
Affects Versions: 3.0.0
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
 Fix For: 3.0.0


In HDP 3.0, there are expected changes to configs and the startup scripts for 
YARN/MR.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19827) HiveServer2 Interactive won't start in clusters with less memory

[Swapan Shridhar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapan Shridhar updated AMBARI-19827:
-
Status: Patch Available  (was: Open)

> HiveServer2 Interactive won't start in clusters with less memory
> 
>
> Key: AMBARI-19827
> URL: https://issues.apache.org/jira/browse/AMBARI-19827
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19827.patch
>
>
> HS2 Interactive in a 3 node local cluster with 3.5G memory in each node. The 
> task fails due to this exception:
> {code:java}
> WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns 
> does not exist
> WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT 
> type value
> Failed: null
> java.lang.IllegalArgumentException
>   at 
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1307)
>   at 
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1230)
>   at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151)
>   at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:197)
>   at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:112)
> INFO cli.LlapServiceDriver: LLAP service driver finished
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19830) HDP 3.0 TP - Support changed configs and scripts for HDFS

[Alejandro Fernandez (JIRA)]

Alejandro Fernandez created AMBARI-19830:


 Summary: HDP 3.0 TP - Support changed configs and scripts for HDFS
 Key: AMBARI-19830
 URL: https://issues.apache.org/jira/browse/AMBARI-19830
 Project: Ambari
  Issue Type: Story
  Components: stacks
Affects Versions: 3.0.0
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
 Fix For: 3.0.0


In HDP 3.0, there are expected changes to configs and the startup scripts for 
HDFS.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19827) HiveServer2 Interactive won't start in clusters with less memory

[Swapan Shridhar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapan Shridhar updated AMBARI-19827:
-
Status: Patch Available  (was: Open)

> HiveServer2 Interactive won't start in clusters with less memory
> 
>
> Key: AMBARI-19827
> URL: https://issues.apache.org/jira/browse/AMBARI-19827
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19827.patch
>
>
> HS2 Interactive in a 3 node local cluster with 3.5G memory in each node. The 
> task fails due to this exception:
> {code:java}
> WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns 
> does not exist
> WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT 
> type value
> Failed: null
> java.lang.IllegalArgumentException
>   at 
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1307)
>   at 
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1230)
>   at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151)
>   at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:197)
>   at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:112)
> INFO cli.LlapServiceDriver: LLAP service driver finished
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19827) HiveServer2 Interactive won't start in clusters with less memory

[Swapan Shridhar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapan Shridhar updated AMBARI-19827:
-
Status: Open  (was: Patch Available)

> HiveServer2 Interactive won't start in clusters with less memory
> 
>
> Key: AMBARI-19827
> URL: https://issues.apache.org/jira/browse/AMBARI-19827
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19827.patch
>
>
> HS2 Interactive in a 3 node local cluster with 3.5G memory in each node. The 
> task fails due to this exception:
> {code:java}
> WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns 
> does not exist
> WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT 
> type value
> Failed: null
> java.lang.IllegalArgumentException
>   at 
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1307)
>   at 
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1230)
>   at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151)
>   at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:197)
>   at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:112)
> INFO cli.LlapServiceDriver: LLAP service driver finished
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19827) HiveServer2 Interactive won't start in clusters with less memory

[Swapan Shridhar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapan Shridhar updated AMBARI-19827:
-
Attachment: AMBARI-19827.patch

> HiveServer2 Interactive won't start in clusters with less memory
> 
>
> Key: AMBARI-19827
> URL: https://issues.apache.org/jira/browse/AMBARI-19827
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19827.patch
>
>
> HS2 Interactive in a 3 node local cluster with 3.5G memory in each node. The 
> task fails due to this exception:
> {code:java}
> WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns 
> does not exist
> WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT 
> type value
> Failed: null
> java.lang.IllegalArgumentException
>   at 
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1307)
>   at 
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1230)
>   at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151)
>   at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:197)
>   at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:112)
> INFO cli.LlapServiceDriver: LLAP service driver finished
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19827) HiveServer2 Interactive won't start in clusters with less memory

[Swapan Shridhar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapan Shridhar updated AMBARI-19827:
-
Fix Version/s: trunk

> HiveServer2 Interactive won't start in clusters with less memory
> 
>
> Key: AMBARI-19827
> URL: https://issues.apache.org/jira/browse/AMBARI-19827
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19827.patch
>
>
> HS2 Interactive in a 3 node local cluster with 3.5G memory in each node. The 
> task fails due to this exception:
> {code:java}
> WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns 
> does not exist
> WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT 
> type value
> Failed: null
> java.lang.IllegalArgumentException
>   at 
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1307)
>   at 
> java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1230)
>   at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151)
>   at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:197)
>   at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:112)
> INFO cli.LlapServiceDriver: LLAP service driver finished
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19805) Add outputFormat attribute to all PXF Hive-related profiles

[Alexander Denissov (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849175#comment-15849175
 ] 

Alexander Denissov commented on AMBARI-19805:
-

[~odiachenko] -- ( is / does it need to be ) the addition of extra parameter 
backward-compatible to previous PXF releases ?

> Add outputFormat attribute to all PXF Hive-related profiles
> ---
>
> Key: AMBARI-19805
> URL: https://issues.apache.org/jira/browse/AMBARI-19805
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
>Priority: Minor
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19805.patch
>
>
> There was new attribute outputFormat introduced in 
> https://issues.apache.org/jira/browse/HAWQ-1228, which needs to be reflected 
> in PXF as a common service.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19825) Metrics data is not getting collected for different services when AMS HTTPS is enabled

[Aravindan Vijayan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aravindan Vijayan updated AMBARI-19825:
---
Attachment: AMBARI-19825-trunk.patch
AMBARI-19825-2.5.patch

> Metrics data is not getting collected for different services when AMS HTTPS 
> is enabled
> --
>
> Key: AMBARI-19825
> URL: https://issues.apache.org/jira/browse/AMBARI-19825
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19825-2.5.patch, AMBARI-19825-trunk.patch
>
>
> {code}
> org.apache.hadoop.metrics2.impl.MetricsConfigException: Error creating 
> plugin: org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink
> at 
> org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:203)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.newSink(MetricsSystemImpl.java:529)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configureSinks(MetricsSystemImpl.java:501)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configure(MetricsSystemImpl.java:480)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.start(MetricsSystemImpl.java:189)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.init(MetricsSystemImpl.java:164)
> at 
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.init(DefaultMetricsSystem.java:54)
> at 
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.initialize(DefaultMetricsSystem.java:50)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.makeInstance(DataNode.java:2530)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:2435)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.createDataNode(DataNode.java:2482)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.secureMain(DataNode.java:2622)
> at 
> org.apache.hadoop.hdfs.server.datanode.SecureDataNodeStarter.start(SecureDataNodeStarter.java:77)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243)
> Caused by: java.lang.IllegalArgumentException: no SSLSocketFactory specified
> at 
> javax.net.ssl.HttpsURLConnection.setSSLSocketFactory(HttpsURLConnection.java:357)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.getSSLConnection(AbstractTimelineMetricsSink.java:284)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findLiveCollectorHostsFromKnownCollector(AbstractTimelineMetricsSink.java:440)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.refreshCollectorsFromConfigured(AbstractTimelineMetricsSink.java:412)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:352)
> at 
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.init(HadoopTimelineMetricsSink.java:110)
> at 
> org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:199)
> ... 17 more
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19825) Metrics data is not getting collected for different services when AMS HTTPS is enabled

[Aravindan Vijayan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aravindan Vijayan updated AMBARI-19825:
---
Status: Open  (was: Patch Available)

> Metrics data is not getting collected for different services when AMS HTTPS 
> is enabled
> --
>
> Key: AMBARI-19825
> URL: https://issues.apache.org/jira/browse/AMBARI-19825
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19825-2.5.patch, AMBARI-19825-trunk.patch
>
>
> {code}
> org.apache.hadoop.metrics2.impl.MetricsConfigException: Error creating 
> plugin: org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink
> at 
> org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:203)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.newSink(MetricsSystemImpl.java:529)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configureSinks(MetricsSystemImpl.java:501)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configure(MetricsSystemImpl.java:480)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.start(MetricsSystemImpl.java:189)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.init(MetricsSystemImpl.java:164)
> at 
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.init(DefaultMetricsSystem.java:54)
> at 
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.initialize(DefaultMetricsSystem.java:50)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.makeInstance(DataNode.java:2530)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:2435)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.createDataNode(DataNode.java:2482)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.secureMain(DataNode.java:2622)
> at 
> org.apache.hadoop.hdfs.server.datanode.SecureDataNodeStarter.start(SecureDataNodeStarter.java:77)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243)
> Caused by: java.lang.IllegalArgumentException: no SSLSocketFactory specified
> at 
> javax.net.ssl.HttpsURLConnection.setSSLSocketFactory(HttpsURLConnection.java:357)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.getSSLConnection(AbstractTimelineMetricsSink.java:284)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findLiveCollectorHostsFromKnownCollector(AbstractTimelineMetricsSink.java:440)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.refreshCollectorsFromConfigured(AbstractTimelineMetricsSink.java:412)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:352)
> at 
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.init(HadoopTimelineMetricsSink.java:110)
> at 
> org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:199)
> ... 17 more
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19825) Metrics data is not getting collected for different services when AMS HTTPS is enabled

[Aravindan Vijayan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aravindan Vijayan updated AMBARI-19825:
---
Status: Patch Available  (was: Open)

> Metrics data is not getting collected for different services when AMS HTTPS 
> is enabled
> --
>
> Key: AMBARI-19825
> URL: https://issues.apache.org/jira/browse/AMBARI-19825
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19825-2.5.patch, AMBARI-19825-trunk.patch
>
>
> {code}
> org.apache.hadoop.metrics2.impl.MetricsConfigException: Error creating 
> plugin: org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink
> at 
> org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:203)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.newSink(MetricsSystemImpl.java:529)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configureSinks(MetricsSystemImpl.java:501)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configure(MetricsSystemImpl.java:480)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.start(MetricsSystemImpl.java:189)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.init(MetricsSystemImpl.java:164)
> at 
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.init(DefaultMetricsSystem.java:54)
> at 
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.initialize(DefaultMetricsSystem.java:50)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.makeInstance(DataNode.java:2530)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:2435)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.createDataNode(DataNode.java:2482)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.secureMain(DataNode.java:2622)
> at 
> org.apache.hadoop.hdfs.server.datanode.SecureDataNodeStarter.start(SecureDataNodeStarter.java:77)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243)
> Caused by: java.lang.IllegalArgumentException: no SSLSocketFactory specified
> at 
> javax.net.ssl.HttpsURLConnection.setSSLSocketFactory(HttpsURLConnection.java:357)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.getSSLConnection(AbstractTimelineMetricsSink.java:284)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findLiveCollectorHostsFromKnownCollector(AbstractTimelineMetricsSink.java:440)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.refreshCollectorsFromConfigured(AbstractTimelineMetricsSink.java:412)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:352)
> at 
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.init(HadoopTimelineMetricsSink.java:110)
> at 
> org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:199)
> ... 17 more
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19825) Metrics data is not getting collected for different services when AMS HTTPS is enabled

[Aravindan Vijayan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aravindan Vijayan updated AMBARI-19825:
---
Attachment: (was: AMBARI-19825.patch)

> Metrics data is not getting collected for different services when AMS HTTPS 
> is enabled
> --
>
> Key: AMBARI-19825
> URL: https://issues.apache.org/jira/browse/AMBARI-19825
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
>
> {code}
> org.apache.hadoop.metrics2.impl.MetricsConfigException: Error creating 
> plugin: org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink
> at 
> org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:203)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.newSink(MetricsSystemImpl.java:529)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configureSinks(MetricsSystemImpl.java:501)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configure(MetricsSystemImpl.java:480)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.start(MetricsSystemImpl.java:189)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.init(MetricsSystemImpl.java:164)
> at 
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.init(DefaultMetricsSystem.java:54)
> at 
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.initialize(DefaultMetricsSystem.java:50)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.makeInstance(DataNode.java:2530)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:2435)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.createDataNode(DataNode.java:2482)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.secureMain(DataNode.java:2622)
> at 
> org.apache.hadoop.hdfs.server.datanode.SecureDataNodeStarter.start(SecureDataNodeStarter.java:77)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243)
> Caused by: java.lang.IllegalArgumentException: no SSLSocketFactory specified
> at 
> javax.net.ssl.HttpsURLConnection.setSSLSocketFactory(HttpsURLConnection.java:357)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.getSSLConnection(AbstractTimelineMetricsSink.java:284)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findLiveCollectorHostsFromKnownCollector(AbstractTimelineMetricsSink.java:440)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.refreshCollectorsFromConfigured(AbstractTimelineMetricsSink.java:412)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:352)
> at 
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.init(HadoopTimelineMetricsSink.java:110)
> at 
> org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:199)
> ... 17 more
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19816) Agent heartbeat lost due to dead service check process

[Sumit Mohanty (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849165#comment-15849165
 ] 

Sumit Mohanty commented on AMBARI-19816:


LGTM, +1 for AMBARI-19816.2.patch

> Agent heartbeat lost due to dead service check process
> --
>
> Key: AMBARI-19816
> URL: https://issues.apache.org/jira/browse/AMBARI-19816
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19816.2.patch, AMBARI-19816.patch
>
>
> Ambari Agent heartbeat loop can get stuck in getting service status via the 
> {{subprocess}} module. This can happen if the invoked process dies.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19805) Add outputFormat attribute to all PXF Hive-related profiles

[Oleksandr Diachenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleksandr Diachenko updated AMBARI-19805:
-
Fix Version/s: trunk

> Add outputFormat attribute to all PXF Hive-related profiles
> ---
>
> Key: AMBARI-19805
> URL: https://issues.apache.org/jira/browse/AMBARI-19805
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
>Priority: Minor
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19805.patch
>
>
> There was new attribute outputFormat introduced in 
> https://issues.apache.org/jira/browse/HAWQ-1228, which needs to be reflected 
> in PXF as a common service.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19825) Metrics data is not getting collected for different services when AMS HTTPS is enabled

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849153#comment-15849153
 ] 

Hadoop QA commented on AMBARI-19825:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12850471/AMBARI-19825.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/10368//console

This message is automatically generated.

> Metrics data is not getting collected for different services when AMS HTTPS 
> is enabled
> --
>
> Key: AMBARI-19825
> URL: https://issues.apache.org/jira/browse/AMBARI-19825
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19825.patch
>
>
> {code}
> org.apache.hadoop.metrics2.impl.MetricsConfigException: Error creating 
> plugin: org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink
> at 
> org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:203)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.newSink(MetricsSystemImpl.java:529)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configureSinks(MetricsSystemImpl.java:501)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configure(MetricsSystemImpl.java:480)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.start(MetricsSystemImpl.java:189)
> at 
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.init(MetricsSystemImpl.java:164)
> at 
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.init(DefaultMetricsSystem.java:54)
> at 
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.initialize(DefaultMetricsSystem.java:50)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.makeInstance(DataNode.java:2530)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:2435)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.createDataNode(DataNode.java:2482)
> at 
> org.apache.hadoop.hdfs.server.datanode.DataNode.secureMain(DataNode.java:2622)
> at 
> org.apache.hadoop.hdfs.server.datanode.SecureDataNodeStarter.start(SecureDataNodeStarter.java:77)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243)
> Caused by: java.lang.IllegalArgumentException: no SSLSocketFactory specified
> at 
> javax.net.ssl.HttpsURLConnection.setSSLSocketFactory(HttpsURLConnection.java:357)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.getSSLConnection(AbstractTimelineMetricsSink.java:284)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findLiveCollectorHostsFromKnownCollector(AbstractTimelineMetricsSink.java:440)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.refreshCollectorsFromConfigured(AbstractTimelineMetricsSink.java:412)
> at 
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:352)
> at 
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.init(HadoopTimelineMetricsSink.java:110)
> at 
> org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:199)
> ... 17 more
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19828) UI changes to resolve discrepancies between what the stack vs Ambari reports as "live" for NodeManagers

[Vivek Ratnavel Subramanian (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vivek Ratnavel Subramanian updated AMBARI-19828:

Attachment: AMBARI-19828.v0.trunk.patch

> UI changes to resolve discrepancies between what the stack vs Ambari reports 
> as "live" for NodeManagers
> ---
>
> Key: AMBARI-19828
> URL: https://issues.apache.org/jira/browse/AMBARI-19828
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-19828.v0.branch-2.5.patch, 
> AMBARI-19828.v0.trunk.patch
>
>
> Looks like the changes in https://issues.apache.org/jira/browse/AMBARI-9418 
> was meant to be applied to YARN summary / NodeManagers as well, but that is 
> not happening.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19828) UI changes to resolve discrepancies between what the stack vs Ambari reports as "live" for NodeManagers

[Vivek Ratnavel Subramanian (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vivek Ratnavel Subramanian updated AMBARI-19828:

Status: Patch Available  (was: In Progress)

> UI changes to resolve discrepancies between what the stack vs Ambari reports 
> as "live" for NodeManagers
> ---
>
> Key: AMBARI-19828
> URL: https://issues.apache.org/jira/browse/AMBARI-19828
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-19828.v0.branch-2.5.patch, 
> AMBARI-19828.v0.trunk.patch
>
>
> Looks like the changes in https://issues.apache.org/jira/browse/AMBARI-9418 
> was meant to be applied to YARN summary / NodeManagers as well, but that is 
> not happening.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19828) UI changes to resolve discrepancies between what the stack vs Ambari reports as "live" for NodeManagers

[Vivek Ratnavel Subramanian (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vivek Ratnavel Subramanian updated AMBARI-19828:

Attachment: AMBARI-19828.v0.branch-2.5.patch

> UI changes to resolve discrepancies between what the stack vs Ambari reports 
> as "live" for NodeManagers
> ---
>
> Key: AMBARI-19828
> URL: https://issues.apache.org/jira/browse/AMBARI-19828
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-19828.v0.branch-2.5.patch
>
>
> Looks like the changes in https://issues.apache.org/jira/browse/AMBARI-9418 
> was meant to be applied to YARN summary / NodeManagers as well, but that is 
> not happening.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19813) findLatestServiceConfigsByStack query returns deleted config group

[Amruta Borkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amruta Borkar updated AMBARI-19813:
---
Attachment: AMBARI-19813.patch

> findLatestServiceConfigsByStack query returns deleted config group
> --
>
> Key: AMBARI-19813
> URL: https://issues.apache.org/jira/browse/AMBARI-19813
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-19813.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19813) findLatestServiceConfigsByStack query returns deleted config group

[Amruta Borkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amruta Borkar updated AMBARI-19813:
---
Attachment: (was: AMBARI-158442.patch)

> findLatestServiceConfigsByStack query returns deleted config group
> --
>
> Key: AMBARI-19813
> URL: https://issues.apache.org/jira/browse/AMBARI-19813
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-19813.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19813) findLatestServiceConfigsByStack query returns deleted config group

[Amruta Borkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amruta Borkar updated AMBARI-19813:
---
Status: Patch Available  (was: In Progress)

> findLatestServiceConfigsByStack query returns deleted config group
> --
>
> Key: AMBARI-19813
> URL: https://issues.apache.org/jira/browse/AMBARI-19813
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-19813.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19813) findLatestServiceConfigsByStack query returns deleted config group

[Amruta Borkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amruta Borkar updated AMBARI-19813:
---
Status: Open  (was: Patch Available)

> findLatestServiceConfigsByStack query returns deleted config group
> --
>
> Key: AMBARI-19813
> URL: https://issues.apache.org/jira/browse/AMBARI-19813
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-158442.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19829) Several HDFS/YARN widgets on Heatmaps show N/A

[Qin Liu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Qin Liu updated AMBARI-19829:
-
Status: Patch Available  (was: Open)

> Several HDFS/YARN widgets on Heatmaps show N/A
> --
>
> Key: AMBARI-19829
> URL: https://issues.apache.org/jira/browse/AMBARI-19829
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-19829.patch
>
>
> The following HDFS/YARN widgets on Heatmaps show N/A:
> 1. HDFS - HDFS Bytes Written, HDFS Bytes Read, DataNode Process Disk I/O 
> Utilization, and DataNode Process Network I/O Utilization
> 2. YARN - Container Failures
> The issue was introduced by AMBARI-15835 "Rate metrics requesting widgets do 
> not show up on Ambari" which introduced rate metrics and applied rate metrics 
> to several HBASE/HDFS/YARN widgets on Summary pages  as well as Heatmap 
> pages. Rate metrics work fine on Summary pages but they don't work on Heatmap 
> pages because current Heatmap design can only show point-in-time metrics and 
> rate metrics need a time range.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19829) Several HDFS/YARN widgets on Heatmaps show N/A

[Qin Liu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Qin Liu updated AMBARI-19829:
-
Attachment: AMBARI-19829.patch

> Several HDFS/YARN widgets on Heatmaps show N/A
> --
>
> Key: AMBARI-19829
> URL: https://issues.apache.org/jira/browse/AMBARI-19829
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-19829.patch
>
>
> The following HDFS/YARN widgets on Heatmaps show N/A:
> 1. HDFS - HDFS Bytes Written, HDFS Bytes Read, DataNode Process Disk I/O 
> Utilization, and DataNode Process Network I/O Utilization
> 2. YARN - Container Failures
> The issue was introduced by AMBARI-15835 "Rate metrics requesting widgets do 
> not show up on Ambari" which introduced rate metrics and applied rate metrics 
> to several HBASE/HDFS/YARN widgets on Summary pages  as well as Heatmap 
> pages. Rate metrics work fine on Summary pages but they don't work on Heatmap 
> pages because current Heatmap design can only show point-in-time metrics and 
> rate metrics need a time range.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19806) After setting up hadoop credential, cannot start Hive Metastore

[Nahappan Somasundaram (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849097#comment-15849097
 ] 

Nahappan Somasundaram commented on AMBARI-19806:


Committed to branch-2.5 and trunk.

> After setting up hadoop credential, cannot start Hive Metastore
> ---
>
> Key: AMBARI-19806
> URL: https://issues.apache.org/jira/browse/AMBARI-19806
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: rb56142.patch
>
>
> In HIVE, after javax.jdo.option.ConnectionPassword property and value is 
> moved  into a JCEKS file using hadoop credential store, hive-site.xml looks 
> like this:
> {quote} 
> hadoop.security.credential.provider.path
> jceks://file/usr/lib/hive/conf/hive.jceks
>   {quote}
> instead of:
> {quote} 
> javax.jdo.option.ConnectionPassword
> MyHiveConnectionPassword
>   {quote}
> However, after the above change, HIVE fails to start. This is an Ambari 
> deployed cluster.
> {quote}Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
>  line 259, in 
> HiveMetastore().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 287, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
>  line 59, in start
> self.configure(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
>  line 73, in configure
> hive(name = 'metastore')
>   File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
> line 89, in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
>  line 326, in hive
> create_schema_cmd = format("export HIVE_CONF_DIR={hive_server_conf_dir} ; 
> "
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 95, in format
> return ConfigurationFormatter().format(format_string, args, **result)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 62, in format
> result_unprotected = self.vformat(format_string, args, all_params)
>   File "/usr/lib64/python2.6/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
>   File "/usr/lib64/python2.6/string.py", line 575, in _vformat
> obj = self.convert_field(obj, conversion)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 70, in convert_field_unprotected
> return self._convert_field(value, conversion, False)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 85, in _convert_field
> return utils.PASSWORDS_HIDE_STRING if is_protected else 
> self._convert_field(value, 'e', is_protected)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
>  line 81, in _convert_field
> return quote_bash_args(unicode(value))
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
>  line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in 
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 
> 'javax.jdo.option.ConnectionPassword' was not found in configurations 
> dictionary!{quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19829) Several HDFS/YARN widgets on Heatmaps show N/A

[Qin Liu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Qin Liu updated AMBARI-19829:
-
Attachment: (was: AMBARI-19829.patch)

> Several HDFS/YARN widgets on Heatmaps show N/A
> --
>
> Key: AMBARI-19829
> URL: https://issues.apache.org/jira/browse/AMBARI-19829
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
>
> The following HDFS/YARN widgets on Heatmaps show N/A:
> 1. HDFS - HDFS Bytes Written, HDFS Bytes Read, DataNode Process Disk I/O 
> Utilization, and DataNode Process Network I/O Utilization
> 2. YARN - Container Failures
> The issue was introduced by AMBARI-15835 "Rate metrics requesting widgets do 
> not show up on Ambari" which introduced rate metrics and applied rate metrics 
> to several HBASE/HDFS/YARN widgets on Summary pages  as well as Heatmap 
> pages. Rate metrics work fine on Summary pages but they don't work on Heatmap 
> pages because current Heatmap design can only show point-in-time metrics and 
> rate metrics need a time range.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19829) Several HDFS/YARN widgets on Heatmaps show N/A

[Qin Liu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Qin Liu updated AMBARI-19829:
-
Status: Open  (was: Patch Available)

> Several HDFS/YARN widgets on Heatmaps show N/A
> --
>
> Key: AMBARI-19829
> URL: https://issues.apache.org/jira/browse/AMBARI-19829
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-19829.patch
>
>
> The following HDFS/YARN widgets on Heatmaps show N/A:
> 1. HDFS - HDFS Bytes Written, HDFS Bytes Read, DataNode Process Disk I/O 
> Utilization, and DataNode Process Network I/O Utilization
> 2. YARN - Container Failures
> The issue was introduced by AMBARI-15835 "Rate metrics requesting widgets do 
> not show up on Ambari" which introduced rate metrics and applied rate metrics 
> to several HBASE/HDFS/YARN widgets on Summary pages  as well as Heatmap 
> pages. Rate metrics work fine on Summary pages but they don't work on Heatmap 
> pages because current Heatmap design can only show point-in-time metrics and 
> rate metrics need a time range.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19829) Several HDFS/YARN widgets on Heatmaps show N/A

[Qin Liu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Qin Liu updated AMBARI-19829:
-
Description: 
The following HDFS/YARN widgets on Heatmaps show N/A:
1. HDFS - HDFS Bytes Written, HDFS Bytes Read, DataNode Process Disk I/O 
Utilization, and DataNode Process Network I/O Utilization
2. YARN - Container Failures

The issue was introduced by AMBARI-15835 "Rate metrics requesting widgets do 
not show up on Ambari" which introduced rate metrics and applied rate metrics 
to several HBASE/HDFS/YARN widgets on Summary pages  as well as Heatmap pages. 
Rate metrics work fine on Summary pages but they don't work on Heatmap pages 
because current Heatmap design can only show point-in-time metrics and rate 
metrics need a time range.

  was:
The following HDFS/YARN widgets on Heatmaps show N/A:
1. HDFS - HDFS Bytes Written, HDFS Bytes Read, DataNode Process Disk I/O 
Utilization, and DataNode Process Network I/O Utilization
2. YANR - Container Failures

The issue was introduced by AMBARI-15835 "Rate metrics requesting widgets do 
not show up on Ambari" which introduced rate metrics and applied rate metrics 
to several HBASE/HDFS/YARN widgets on Summary pages  as well as Heatmap pages. 
Rate metrics work fine on Summary pages but they don't work on Heatmap pages 
because current Heatmap design can only show point-in-time metrics and rate 
metrics need a time range.


> Several HDFS/YARN widgets on Heatmaps show N/A
> --
>
> Key: AMBARI-19829
> URL: https://issues.apache.org/jira/browse/AMBARI-19829
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-19829.patch
>
>
> The following HDFS/YARN widgets on Heatmaps show N/A:
> 1. HDFS - HDFS Bytes Written, HDFS Bytes Read, DataNode Process Disk I/O 
> Utilization, and DataNode Process Network I/O Utilization
> 2. YARN - Container Failures
> The issue was introduced by AMBARI-15835 "Rate metrics requesting widgets do 
> not show up on Ambari" which introduced rate metrics and applied rate metrics 
> to several HBASE/HDFS/YARN widgets on Summary pages  as well as Heatmap 
> pages. Rate metrics work fine on Summary pages but they don't work on Heatmap 
> pages because current Heatmap design can only show point-in-time metrics and 
> rate metrics need a time range.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19814) 'num_llap_nodes' should show up as non-editable property when non-ambari managed queue is selected

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849091#comment-15849091
 ] 

Hadoop QA commented on AMBARI-19814:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12850476/AMBARI-19814.backend.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/10367//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/10367//console

This message is automatically generated.

> 'num_llap_nodes' should show up as non-editable property when non-ambari 
> managed queue is selected
> --
>
> Key: AMBARI-19814
> URL: https://issues.apache.org/jira/browse/AMBARI-19814
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
>  Labels: llap
> Fix For: 2.5.0
>
> Attachments: AMBARI-19814.backend.patch, AMBARI-19814.patch
>
>
> - 'num_llap_nodes' as of now is shown as a slider and comes only when we have 
> selected 'llap' named queue and is a child of root level. It is shown because 
> 'num_llap_nodes' visible attribute is set as True by SA.
> - For any other queue, 'num_llap_nodes' is set as visible=false by SA call 
> and is not shown on UI.
> *Expected:*
> A way to show 'num_llap_nodes' node on UI for user, irrespective of the queue 
> selected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19829) Several HDFS/YARN widgets on Heatmaps show N/A

[Qin Liu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Qin Liu updated AMBARI-19829:
-
Attachment: AMBARI-19829.patch

> Several HDFS/YARN widgets on Heatmaps show N/A
> --
>
> Key: AMBARI-19829
> URL: https://issues.apache.org/jira/browse/AMBARI-19829
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-19829.patch
>
>
> The following HDFS/YARN widgets on Heatmaps show N/A:
> 1. HDFS - HDFS Bytes Written, HDFS Bytes Read, DataNode Process Disk I/O 
> Utilization, and DataNode Process Network I/O Utilization
> 2. YANR - Container Failures
> The issue was introduced by AMBARI-15835 "Rate metrics requesting widgets do 
> not show up on Ambari" which introduced rate metrics and applied rate metrics 
> to several HBASE/HDFS/YARN widgets on Summary pages  as well as Heatmap 
> pages. Rate metrics work fine on Summary pages but they don't work on Heatmap 
> pages because current Heatmap design can only show point-in-time metrics and 
> rate metrics need a time range.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19829) Several HDFS/YARN widgets on Heatmaps show N/A

[Qin Liu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Qin Liu updated AMBARI-19829:
-
Status: Patch Available  (was: Open)

> Several HDFS/YARN widgets on Heatmaps show N/A
> --
>
> Key: AMBARI-19829
> URL: https://issues.apache.org/jira/browse/AMBARI-19829
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-19829.patch
>
>
> The following HDFS/YARN widgets on Heatmaps show N/A:
> 1. HDFS - HDFS Bytes Written, HDFS Bytes Read, DataNode Process Disk I/O 
> Utilization, and DataNode Process Network I/O Utilization
> 2. YANR - Container Failures
> The issue was introduced by AMBARI-15835 "Rate metrics requesting widgets do 
> not show up on Ambari" which introduced rate metrics and applied rate metrics 
> to several HBASE/HDFS/YARN widgets on Summary pages  as well as Heatmap 
> pages. Rate metrics work fine on Summary pages but they don't work on Heatmap 
> pages because current Heatmap design can only show point-in-time metrics and 
> rate metrics need a time range.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19789) Hive LLAP and Hive2 log4j changes should be removed from upgrade packs hdp 2.3 and hdp 2.4

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849083#comment-15849083
 ] 

Hudson commented on AMBARI-19789:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #871 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/871/])
AMBARI-19789. Hive LLAP and Hive2 log4j changes should be removed from 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=695d3a5b76994b2088bdb2adb8f337cb75b6cb54])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.4.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.4.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.6.xml


> Hive LLAP and Hive2 log4j changes should be removed from upgrade packs hdp 
> 2.3 and hdp 2.4
> --
>
> Key: AMBARI-19789
> URL: https://issues.apache.org/jira/browse/AMBARI-19789
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19829) Several HDFS/YARN widgets on Heatmaps show N/A

[Qin Liu (JIRA)]

Qin Liu created AMBARI-19829:


 Summary: Several HDFS/YARN widgets on Heatmaps show N/A
 Key: AMBARI-19829
 URL: https://issues.apache.org/jira/browse/AMBARI-19829
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.2.2
Reporter: Qin Liu
Assignee: Qin Liu
 Fix For: trunk


The following HDFS/YARN widgets on Heatmaps show N/A:
1. HDFS - HDFS Bytes Written, HDFS Bytes Read, DataNode Process Disk I/O 
Utilization, and DataNode Process Network I/O Utilization
2. YANR - Container Failures

The issue was introduced by AMBARI-15835 "Rate metrics requesting widgets do 
not show up on Ambari" which introduced rate metrics and applied rate metrics 
to several HBASE/HDFS/YARN widgets on Summary pages  as well as Heatmap pages. 
Rate metrics work fine on Summary pages but they don't work on Heatmap pages 
because current Heatmap design can only show point-in-time metrics and rate 
metrics need a time range.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19805) Add outputFormat attribute to all PXF Hive-related profiles

[Lav Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849076#comment-15849076
 ] 

Lav Jain commented on AMBARI-19805:
---

+1 for the patch

> Add outputFormat attribute to all PXF Hive-related profiles
> ---
>
> Key: AMBARI-19805
> URL: https://issues.apache.org/jira/browse/AMBARI-19805
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19805.patch
>
>
> There was new attribute outputFormat introduced in 
> https://issues.apache.org/jira/browse/HAWQ-1228, which needs to be reflected 
> in PXF as a common service.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19789) Hive LLAP and Hive2 log4j changes should be removed from upgrade packs hdp 2.3 and hdp 2.4

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849070#comment-15849070
 ] 

Hudson commented on AMBARI-19789:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6620 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6620/])
AMBARI-19789. Hive LLAP and Hive2 log4j changes should be removed from 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f36af3da4598db52b2e67fd22c85b5d5a436c00c])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.4.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.4.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml


> Hive LLAP and Hive2 log4j changes should be removed from upgrade packs hdp 
> 2.3 and hdp 2.4
> --
>
> Key: AMBARI-19789
> URL: https://issues.apache.org/jira/browse/AMBARI-19789
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (AMBARI-19816) Agent heartbeat lost due to dead service check process

[Doroszlai, Attila (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Doroszlai, Attila reopened AMBARI-19816:


> Agent heartbeat lost due to dead service check process
> --
>
> Key: AMBARI-19816
> URL: https://issues.apache.org/jira/browse/AMBARI-19816
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19816.2.patch, AMBARI-19816.patch
>
>
> Ambari Agent heartbeat loop can get stuck in getting service status via the 
> {{subprocess}} module. This can happen if the invoked process dies.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19816) Agent heartbeat lost due to dead service check process

[Doroszlai, Attila (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Doroszlai, Attila updated AMBARI-19816:
---
Status: Patch Available  (was: Reopened)

> Agent heartbeat lost due to dead service check process
> --
>
> Key: AMBARI-19816
> URL: https://issues.apache.org/jira/browse/AMBARI-19816
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19816.2.patch, AMBARI-19816.patch
>
>
> Ambari Agent heartbeat loop can get stuck in getting service status via the 
> {{subprocess}} module. This can happen if the invoked process dies.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19816) Agent heartbeat lost due to dead service check process

[Doroszlai, Attila (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Doroszlai, Attila updated AMBARI-19816:
---
Attachment: AMBARI-19816.2.patch

Addendum: covers {{Hardware.osdisks}}, which I missed in the previous patch.

{noformat}
Total run:1182
Total errors:0
Total failures:0
OK
...
Ran 455 tests in 14.433s

OK
{noformat}

> Agent heartbeat lost due to dead service check process
> --
>
> Key: AMBARI-19816
> URL: https://issues.apache.org/jira/browse/AMBARI-19816
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19816.2.patch, AMBARI-19816.patch
>
>
> Ambari Agent heartbeat loop can get stuck in getting service status via the 
> {{subprocess}} module. This can happen if the invoked process dies.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19828) UI changes to resolve discrepancies between what the stack vs Ambari reports as "live" for NodeManagers

[Vivek Ratnavel Subramanian (JIRA)]

Vivek Ratnavel Subramanian created AMBARI-19828:
---

 Summary: UI changes to resolve discrepancies between what the 
stack vs Ambari reports as "live" for NodeManagers
 Key: AMBARI-19828
 URL: https://issues.apache.org/jira/browse/AMBARI-19828
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Vivek Ratnavel Subramanian
Assignee: Vivek Ratnavel Subramanian
 Fix For: 2.5.0


Looks like the changes in https://issues.apache.org/jira/browse/AMBARI-9418 was 
meant to be applied to YARN summary / NodeManagers as well, but that is not 
happening.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19826) Side Nav: menu should be collapsed(expanded) on clicking

[Xi Wang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xi Wang updated AMBARI-19826:
-
Attachment: AMBARI-19826.patch

> Side Nav: menu should be collapsed(expanded) on clicking
> 
>
> Key: AMBARI-19826
> URL: https://issues.apache.org/jira/browse/AMBARI-19826
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-19826.patch, AMBARI-19826.patch
>
>
> Expected: On the Side Navigation, each menu item has a sub-menu should be 
> collapsed/expanded on clicking.
> Current: will be collapsed on clicking the chevron icon.
> (Menus with sub-menu: Services/Admin/Ambari)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19826) Side Nav: menu should be collapsed(expanded) on clicking

[Xi Wang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xi Wang updated AMBARI-19826:
-
Attachment: (was: AMBARI-19826.patch)

> Side Nav: menu should be collapsed(expanded) on clicking
> 
>
> Key: AMBARI-19826
> URL: https://issues.apache.org/jira/browse/AMBARI-19826
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-19826.patch
>
>
> Expected: On the Side Navigation, each menu item has a sub-menu should be 
> collapsed/expanded on clicking.
> Current: will be collapsed on clicking the chevron icon.
> (Menus with sub-menu: Services/Admin/Ambari)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19826) Side Nav: menu should be collapsed(expanded) on clicking

[Xi Wang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xi Wang updated AMBARI-19826:
-
Attachment: AMBARI-19826.patch

> Side Nav: menu should be collapsed(expanded) on clicking
> 
>
> Key: AMBARI-19826
> URL: https://issues.apache.org/jira/browse/AMBARI-19826
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-19826.patch
>
>
> Expected: On the Side Navigation, each menu item has a sub-menu should be 
> collapsed/expanded on clicking.
> Current: will be collapsed on clicking the chevron icon.
> (Menus with sub-menu: Services/Admin/Ambari)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19827) HiveServer2 Interactive won't start in clusters with less memory

[Swapan Shridhar (JIRA)]

Swapan Shridhar created AMBARI-19827:


 Summary: HiveServer2 Interactive won't start in clusters with less 
memory
 Key: AMBARI-19827
 URL: https://issues.apache.org/jira/browse/AMBARI-19827
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.5.0
Reporter: Swapan Shridhar
Assignee: Swapan Shridhar
 Fix For: 2.5.0


HS2 Interactive in a 3 node local cluster with 3.5G memory in each node. The 
task fails due to this exception:

{code:java}
WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns does 
not exist
WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT 
type value
Failed: null
java.lang.IllegalArgumentException
at 
java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1307)
at 
java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1230)
at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151)
at 
org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:197)
at 
org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:112)
INFO cli.LlapServiceDriver: LLAP service driver finished
{code}




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-19826) Side Nav: menu should be collapsed(expanded) on clicking

[Xi Wang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-19826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xi Wang updated AMBARI-19826:
-
Attachment: AMBARI-19826.patch

> Side Nav: menu should be collapsed(expanded) on clicking
> 
>
> Key: AMBARI-19826
> URL: https://issues.apache.org/jira/browse/AMBARI-19826
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-19826.patch
>
>
> Expected: On the Side Navigation, each menu item has a sub-menu should be 
> collapsed/expanded on clicking.
> Current: will be collapsed on clicking the chevron icon.
> (Menus with sub-menu: Services/Admin/Ambari)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19826) Side Nav: menu should be collapsed(expanded) on clicking

[Xi Wang (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848980#comment-15848980
 ] 

Xi Wang commented on AMBARI-19826:
--

20325 passing (27s)
  153 pending

> Side Nav: menu should be collapsed(expanded) on clicking
> 
>
> Key: AMBARI-19826
> URL: https://issues.apache.org/jira/browse/AMBARI-19826
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
>
> Expected: On the Side Navigation, each menu item has a sub-menu should be 
> collapsed/expanded on clicking.
> Current: will be collapsed on clicking the chevron icon.
> (Menus with sub-menu: Services/Admin/Ambari)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-19826) Side Nav: menu should be collapsed(expanded) on clicking

[Xi Wang (JIRA)]

Xi Wang created AMBARI-19826:


 Summary: Side Nav: menu should be collapsed(expanded) on clicking
 Key: AMBARI-19826
 URL: https://issues.apache.org/jira/browse/AMBARI-19826
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 3.0.0
Reporter: Xi Wang
Assignee: Xi Wang
 Fix For: 3.0.0


Expected: On the Side Navigation, each menu item has a sub-menu should be 
collapsed/expanded on clicking.
Current: will be collapsed on clicking the chevron icon.

(Menus with sub-menu: Services/Admin/Ambari)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19814) 'num_llap_nodes' should show up as non-editable property when non-ambari managed queue is selected

[Sumit Mohanty (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848952#comment-15848952
 ] 

Sumit Mohanty commented on AMBARI-19814:


LGTM, +1

> 'num_llap_nodes' should show up as non-editable property when non-ambari 
> managed queue is selected
> --
>
> Key: AMBARI-19814
> URL: https://issues.apache.org/jira/browse/AMBARI-19814
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
>  Labels: llap
> Fix For: 2.5.0
>
> Attachments: AMBARI-19814.backend.patch, AMBARI-19814.patch
>
>
> - 'num_llap_nodes' as of now is shown as a slider and comes only when we have 
> selected 'llap' named queue and is a child of root level. It is shown because 
> 'num_llap_nodes' visible attribute is set as True by SA.
> - For any other queue, 'num_llap_nodes' is set as visible=false by SA call 
> and is not shown on UI.
> *Expected:*
> A way to show 'num_llap_nodes' node on UI for user, irrespective of the queue 
> selected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (AMBARI-19814) 'num_llap_nodes' should show up as non-editable property when non-ambari managed queue is selected

[Swapan Shridhar (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848892#comment-15848892
 ] 

Swapan Shridhar edited comment on AMBARI-19814 at 2/1/17 8:24 PM:
--

Attached is the [^AMBARI-19814.backend.patch] for review, which needs to be 
checkedin as corresponding UI patch is already in -> [^AMBARI-19814.patch]

Review required [~jaimin]  | [~sumitmohanty]


was (Author: swapanshridhar):
Attached is the [^AMBARI-19814.backend.patch] for review, which needs to be 
there as part of patch checkin [^AMBARI-19814.patch]

Review required [~jaimin]  | [~sumitmohanty]

> 'num_llap_nodes' should show up as non-editable property when non-ambari 
> managed queue is selected
> --
>
> Key: AMBARI-19814
> URL: https://issues.apache.org/jira/browse/AMBARI-19814
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
>  Labels: llap
> Fix For: 2.5.0
>
> Attachments: AMBARI-19814.backend.patch, AMBARI-19814.patch
>
>
> - 'num_llap_nodes' as of now is shown as a slider and comes only when we have 
> selected 'llap' named queue and is a child of root level. It is shown because 
> 'num_llap_nodes' visible attribute is set as True by SA.
> - For any other queue, 'num_llap_nodes' is set as visible=false by SA call 
> and is not shown on UI.
> *Expected:*
> A way to show 'num_llap_nodes' node on UI for user, irrespective of the queue 
> selected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)