[jira] [Commented] (AMBARI-18779) Fix the backend for HAWQ View BETA
[
https://issues.apache.org/jira/browse/AMBARI-18779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631741#comment-15631741
]
Hadoop QA commented on AMBARI-18779:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836703/AMBARI-18779-trunk-orig.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 12 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
contrib/views/hawq
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9114//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9114//console
This message is automatically generated.
> Fix the backend for HAWQ View BETA
> --
>
> Key: AMBARI-18779
> URL: https://issues.apache.org/jira/browse/AMBARI-18779
> Project: Ambari
> Issue Type: Bug
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18779-trunk-orig.patch
>
>
> Fix the backend for HAWQ View so that the backend is able to query from
> pg_stat_activity table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18074) umask value should less than 18 when check hosts in the step 3 of install ambari
[
https://issues.apache.org/jira/browse/AMBARI-18074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631675#comment-15631675
]
Hadoop QA commented on AMBARI-18074:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836706/AMBARI-18074.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-web
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9113//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9113//console
This message is automatically generated.
> umask value should less than 18 when check hosts in the step 3 of install
> ambari
>
>
> Key: AMBARI-18074
> URL: https://issues.apache.org/jira/browse/AMBARI-18074
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: trunk
>Reporter: wuhui
> Fix For: trunk
>
> Attachments: AMBARI-18074.patch
>
>
> if umask value big than 18 ,some hdfs user may not have the privilege to
> operate the hdfs system.
> so i suggest to notice people to revise the umask value when the umask value
> it not narmal in the step 3 of host check.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18778) Ambari-server: Blueprint enhancements to support enabling or disabling credential store
[
https://issues.apache.org/jira/browse/AMBARI-18778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631614#comment-15631614
]
Hadoop QA commented on AMBARI-18778:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836707/rb53412.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9112//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9112//console
This message is automatically generated.
> Ambari-server: Blueprint enhancements to support enabling or disabling
> credential store
>
>
> Key: AMBARI-18778
> URL: https://issues.apache.org/jira/browse/AMBARI-18778
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53412.patch
>
>
> When deploying a cluster using a blueprint, users must be able to specify
> whether they want to enable the use of hadoop credential store for a service
> if it supports it.
> { "settings" :
> {
> "service_settings" : [
> { "name" : "RANGER",
> "recovery_enabled" : "true",
> "credential_store_enabled" : "true"
> },
> { "name" : "HIVE",
> "recovery_enabled" : "true",
> "credential_store_enabled" : "false"
> }
> ]
> }
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18766) Add Service failed when none of the host components report version
[
https://issues.apache.org/jira/browse/AMBARI-18766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631508#comment-15631508
]
Hudson commented on AMBARI-18766:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5921 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5921/])
AMBARI-18766. Add Service failed when none of the host components report
(jaimin:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=94573ad709ffe62a3df2a2198edc2984eedd8442])
* (edit) ambari-web/app/controllers/wizard/step8_controller.js
* (edit) ambari-web/test/controllers/wizard/step8_test.js
> Add Service failed when none of the host components report version
> --
>
> Key: AMBARI-18766
> URL: https://issues.apache.org/jira/browse/AMBARI-18766
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Jaimin Jetly
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18766.2.patch, AMBARI-18766.patch
>
>
> When the underlying packages do not support versioned layout or do not report
> version (basically distro-select is not supported) then the stack version
> associated with the cluster is not changed to CURRENT from INIT.
> This blocks the UI from discovering the stack version associated with the
> cluster. UI instead should simply rely on the stack version that is specified
> in the cluster resource.
> *Cluster resource* ("version": "ODPi-1.0")
> {code}
> {
> "href": "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1";,
> "Clusters": {
> "cluster_id": 2,
> "cluster_name": "c1",
> "health_report": {
> "Host/stale_config": 1,
> "Host/maintenance_state": 0,
> "Host/host_status/ALERT": 0
> },
> "provisioning_state": "INSTALLED",
> "security_type": "NONE",
> "total_hosts": 1,
> "version": "ODPi-1.0",
> {code}
> *stack_version resource* ("state": "INIT")
> {code}
> {
> "href":
> "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1/stack_versions/1";,
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 1,
> "repository_version": 1,
> "stack": "ODPi",
> "state": "INIT",
> "version": "1.0",
> "host_states": {
> "CURRENT": [],
> "INIT": [],
> "INSTALLED": [],
> "INSTALLING": [],
> "INSTALL_FAILED": [],
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18766) Add Service failed when none of the host components report version
[
https://issues.apache.org/jira/browse/AMBARI-18766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631489#comment-15631489
]
Hudson commented on AMBARI-18766:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #251 (See
[https://builds.apache.org/job/Ambari-branch-2.5/251/])
AMBARI-18766. Add Service failed when none of the host components report
(jaimin:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8f47dcd88c2f8c5be7757209fe0aa9b26b245707])
* (edit) ambari-web/app/controllers/wizard/step8_controller.js
* (edit) ambari-web/test/controllers/wizard/step8_test.js
> Add Service failed when none of the host components report version
> --
>
> Key: AMBARI-18766
> URL: https://issues.apache.org/jira/browse/AMBARI-18766
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Jaimin Jetly
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18766.2.patch, AMBARI-18766.patch
>
>
> When the underlying packages do not support versioned layout or do not report
> version (basically distro-select is not supported) then the stack version
> associated with the cluster is not changed to CURRENT from INIT.
> This blocks the UI from discovering the stack version associated with the
> cluster. UI instead should simply rely on the stack version that is specified
> in the cluster resource.
> *Cluster resource* ("version": "ODPi-1.0")
> {code}
> {
> "href": "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1";,
> "Clusters": {
> "cluster_id": 2,
> "cluster_name": "c1",
> "health_report": {
> "Host/stale_config": 1,
> "Host/maintenance_state": 0,
> "Host/host_status/ALERT": 0
> },
> "provisioning_state": "INSTALLED",
> "security_type": "NONE",
> "total_hosts": 1,
> "version": "ODPi-1.0",
> {code}
> *stack_version resource* ("state": "INIT")
> {code}
> {
> "href":
> "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1/stack_versions/1";,
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 1,
> "repository_version": 1,
> "stack": "ODPi",
> "state": "INIT",
> "version": "1.0",
> "host_states": {
> "CURRENT": [],
> "INIT": [],
> "INSTALLED": [],
> "INSTALLING": [],
> "INSTALL_FAILED": [],
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18766) Add Service failed when none of the host components report version
[
https://issues.apache.org/jira/browse/AMBARI-18766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin Jetly updated AMBARI-18766:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Patch committed to trunk, branch-2.5 and branch-2.4
> Add Service failed when none of the host components report version
> --
>
> Key: AMBARI-18766
> URL: https://issues.apache.org/jira/browse/AMBARI-18766
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Jaimin Jetly
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18766.2.patch, AMBARI-18766.patch
>
>
> When the underlying packages do not support versioned layout or do not report
> version (basically distro-select is not supported) then the stack version
> associated with the cluster is not changed to CURRENT from INIT.
> This blocks the UI from discovering the stack version associated with the
> cluster. UI instead should simply rely on the stack version that is specified
> in the cluster resource.
> *Cluster resource* ("version": "ODPi-1.0")
> {code}
> {
> "href": "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1";,
> "Clusters": {
> "cluster_id": 2,
> "cluster_name": "c1",
> "health_report": {
> "Host/stale_config": 1,
> "Host/maintenance_state": 0,
> "Host/host_status/ALERT": 0
> },
> "provisioning_state": "INSTALLED",
> "security_type": "NONE",
> "total_hosts": 1,
> "version": "ODPi-1.0",
> {code}
> *stack_version resource* ("state": "INIT")
> {code}
> {
> "href":
> "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1/stack_versions/1";,
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 1,
> "repository_version": 1,
> "stack": "ODPi",
> "state": "INIT",
> "version": "1.0",
> "host_states": {
> "CURRENT": [],
> "INIT": [],
> "INSTALLED": [],
> "INSTALLING": [],
> "INSTALL_FAILED": [],
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18778) Ambari-server: Blueprint enhancements to support enabling or disabling credential store
[
https://issues.apache.org/jira/browse/AMBARI-18778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-18778:
---
Status: Patch Available (was: Open)
> Ambari-server: Blueprint enhancements to support enabling or disabling
> credential store
>
>
> Key: AMBARI-18778
> URL: https://issues.apache.org/jira/browse/AMBARI-18778
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53412.patch
>
>
> When deploying a cluster using a blueprint, users must be able to specify
> whether they want to enable the use of hadoop credential store for a service
> if it supports it.
> { "settings" :
> {
> "service_settings" : [
> { "name" : "RANGER",
> "recovery_enabled" : "true",
> "credential_store_enabled" : "true"
> },
> { "name" : "HIVE",
> "recovery_enabled" : "true",
> "credential_store_enabled" : "false"
> }
> ]
> }
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18778) Ambari-server: Blueprint enhancements to support enabling or disabling credential store
[
https://issues.apache.org/jira/browse/AMBARI-18778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-18778:
---
Attachment: rb53412.patch
> Ambari-server: Blueprint enhancements to support enabling or disabling
> credential store
>
>
> Key: AMBARI-18778
> URL: https://issues.apache.org/jira/browse/AMBARI-18778
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53412.patch
>
>
> When deploying a cluster using a blueprint, users must be able to specify
> whether they want to enable the use of hadoop credential store for a service
> if it supports it.
> { "settings" :
> {
> "service_settings" : [
> { "name" : "RANGER",
> "recovery_enabled" : "true",
> "credential_store_enabled" : "true"
> },
> { "name" : "HIVE",
> "recovery_enabled" : "true",
> "credential_store_enabled" : "false"
> }
> ]
> }
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-18074) umask value should less than 18 when check hosts in the step 3 of install ambari
[ https://issues.apache.org/jira/browse/AMBARI-18074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631244#comment-15631244 ] wuhui edited comment on AMBARI-18074 at 11/3/16 2:18 AM: - Hello,I have uploaded a new patch according to the trunk.Please review and commit the patch for me.thanks you. was (Author: wuhui): Hello,I have upload a new patch according to the trunk.Please review and commit the patch for me!thanks you. > umask value should less than 18 when check hosts in the step 3 of install > ambari > > > Key: AMBARI-18074 > URL: https://issues.apache.org/jira/browse/AMBARI-18074 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: wuhui > Fix For: trunk > > Attachments: AMBARI-18074.patch > > > if umask value big than 18 ,some hdfs user may not have the privilege to > operate the hdfs system. > so i suggest to notice people to revise the umask value when the umask value > it not narmal in the step 3 of host check. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18074) umask value should less than 18 when check hosts in the step 3 of install ambari
[ https://issues.apache.org/jira/browse/AMBARI-18074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631244#comment-15631244 ] wuhui commented on AMBARI-18074: Hello,I have upload a new patch according to the trunk.Please review and commit the patch for me!thanks you. > umask value should less than 18 when check hosts in the step 3 of install > ambari > > > Key: AMBARI-18074 > URL: https://issues.apache.org/jira/browse/AMBARI-18074 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: wuhui > Fix For: trunk > > Attachments: AMBARI-18074.patch > > > if umask value big than 18 ,some hdfs user may not have the privilege to > operate the hdfs system. > so i suggest to notice people to revise the umask value when the umask value > it not narmal in the step 3 of host check. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18074) umask value should less than 18 when check hosts in the step 3 of install ambari
[ https://issues.apache.org/jira/browse/AMBARI-18074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wuhui updated AMBARI-18074: --- Attachment: AMBARI-18074.patch > umask value should less than 18 when check hosts in the step 3 of install > ambari > > > Key: AMBARI-18074 > URL: https://issues.apache.org/jira/browse/AMBARI-18074 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: wuhui > Fix For: trunk > > Attachments: AMBARI-18074.patch > > > if umask value big than 18 ,some hdfs user may not have the privilege to > operate the hdfs system. > so i suggest to notice people to revise the umask value when the umask value > it not narmal in the step 3 of host check. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18074) umask value should less than 18 when check hosts in the step 3 of install ambari
[ https://issues.apache.org/jira/browse/AMBARI-18074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wuhui updated AMBARI-18074: --- Attachment: (was: AMBARI-18074.patch) > umask value should less than 18 when check hosts in the step 3 of install > ambari > > > Key: AMBARI-18074 > URL: https://issues.apache.org/jira/browse/AMBARI-18074 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: wuhui > Fix For: trunk > > Attachments: AMBARI-18074.patch > > > if umask value big than 18 ,some hdfs user may not have the privilege to > operate the hdfs system. > so i suggest to notice people to revise the umask value when the umask value > it not narmal in the step 3 of host check. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-18781) ambari server StackOverflowError in IBM PPC64
[ https://issues.apache.org/jira/browse/AMBARI-18781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wuhui resolved AMBARI-18781. Resolution: Fixed > ambari server StackOverflowError in IBM PPC64 > - > > Key: AMBARI-18781 > URL: https://issues.apache.org/jira/browse/AMBARI-18781 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: wuhui > Fix For: trunk > > Attachments: AMBARI-18781.patch > > > 02 Nov 2016 09:27:22,301 INFO [qtp-client-85] PersistKeyValueService:82 - > Looking for keyName CLUSTER_CURRENT_STATUS > 02 Nov 2016 09:27:25,360 INFO [qtp-client-125] PersistKeyValueService:82 - > Looking for keyName CLUSTER_CURRENT_STATUS > 02 Nov 2016 09:28:32,681 WARN [qtp-client-85] ServletHandler:538 - > javax.servlet.ServletException: java.lang.StackOverflowError > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:420) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) > at > org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) > at > org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:182) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18781) ambari server StackOverflowError in IBM PPC64
[ https://issues.apache.org/jira/browse/AMBARI-18781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wuhui updated AMBARI-18781: --- Attachment: AMBARI-18781.patch > ambari server StackOverflowError in IBM PPC64 > - > > Key: AMBARI-18781 > URL: https://issues.apache.org/jira/browse/AMBARI-18781 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: wuhui > Fix For: trunk > > Attachments: AMBARI-18781.patch > > > 02 Nov 2016 09:27:22,301 INFO [qtp-client-85] PersistKeyValueService:82 - > Looking for keyName CLUSTER_CURRENT_STATUS > 02 Nov 2016 09:27:25,360 INFO [qtp-client-125] PersistKeyValueService:82 - > Looking for keyName CLUSTER_CURRENT_STATUS > 02 Nov 2016 09:28:32,681 WARN [qtp-client-85] ServletHandler:538 - > javax.servlet.ServletException: java.lang.StackOverflowError > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:420) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) > at > org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) > at > org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:182) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18781) ambari server StackOverflowError in IBM PPC64
[ https://issues.apache.org/jira/browse/AMBARI-18781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631217#comment-15631217 ] wuhui commented on AMBARI-18781: I think we should set Xss for ambari-server thread to make sure the java process run heathy in IBM PPC enviroment.so I upload the patch to fix the issue! please commit for me! thank you. > ambari server StackOverflowError in IBM PPC64 > - > > Key: AMBARI-18781 > URL: https://issues.apache.org/jira/browse/AMBARI-18781 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: wuhui > Fix For: trunk > > > 02 Nov 2016 09:27:22,301 INFO [qtp-client-85] PersistKeyValueService:82 - > Looking for keyName CLUSTER_CURRENT_STATUS > 02 Nov 2016 09:27:25,360 INFO [qtp-client-125] PersistKeyValueService:82 - > Looking for keyName CLUSTER_CURRENT_STATUS > 02 Nov 2016 09:28:32,681 WARN [qtp-client-85] ServletHandler:538 - > javax.servlet.ServletException: java.lang.StackOverflowError > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:420) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) > at > org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) > at > org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:182) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18779) Fix the backend for HAWQ View BETA
[ https://issues.apache.org/jira/browse/AMBARI-18779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt updated AMBARI-18779: -- Attachment: AMBARI-18779-trunk-orig.patch > Fix the backend for HAWQ View BETA > -- > > Key: AMBARI-18779 > URL: https://issues.apache.org/jira/browse/AMBARI-18779 > Project: Ambari > Issue Type: Bug >Reporter: Matt >Assignee: Matt >Priority: Minor > Fix For: trunk, 2.5.0, 2.4.2 > > Attachments: AMBARI-18779-trunk-orig.patch > > > Fix the backend for HAWQ View so that the backend is able to query from > pg_stat_activity table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18779) Fix the backend for HAWQ View BETA
[ https://issues.apache.org/jira/browse/AMBARI-18779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt updated AMBARI-18779: -- Status: Patch Available (was: Open) > Fix the backend for HAWQ View BETA > -- > > Key: AMBARI-18779 > URL: https://issues.apache.org/jira/browse/AMBARI-18779 > Project: Ambari > Issue Type: Bug >Reporter: Matt >Assignee: Matt >Priority: Minor > Fix For: trunk, 2.5.0, 2.4.2 > > Attachments: AMBARI-18779-trunk-orig.patch > > > Fix the backend for HAWQ View so that the backend is able to query from > pg_stat_activity table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18781) ambari server StackOverflowError in IBM PPC64
wuhui created AMBARI-18781: -- Summary: ambari server StackOverflowError in IBM PPC64 Key: AMBARI-18781 URL: https://issues.apache.org/jira/browse/AMBARI-18781 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: wuhui Fix For: trunk 02 Nov 2016 09:27:22,301 INFO [qtp-client-85] PersistKeyValueService:82 - Looking for keyName CLUSTER_CURRENT_STATUS 02 Nov 2016 09:27:25,360 INFO [qtp-client-125] PersistKeyValueService:82 - Looking for keyName CLUSTER_CURRENT_STATUS 02 Nov 2016 09:28:32,681 WARN [qtp-client-85] ServletHandler:538 - javax.servlet.ServletException: java.lang.StackOverflowError at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:420) at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540) at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:182) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) at org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13109) Verify that max logs parameter wouldn't cause premature region flush
[ https://issues.apache.org/jira/browse/AMBARI-13109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-13109: Description: For hbase, the following relationship should be maintained: dfs.blocksize * 0.95 * hbase.regionserver.maxlogs (default 32) > hbase.regionserver.global.memstore.upperLimit * HBASE_HEAPSIZE The rationale is to avoid premature region flush due to log roll which is triggered by insufficiently high max logs. When user changes the values for max logs, memstore upper limit or max heap size, we should verify that the above relationship is satisfied. was: For hbase, the following relationship should be maintained: dfs.blocksize * 0.95 * hbase.regionserver.maxlogs (default 32) > hbase.regionserver.global.memstore.upperLimit * HBASE_HEAPSIZE The rationale is to avoid premature region flush due to log roll which is triggered by insufficiently high max logs. When user changes the values for max logs, memstore upper limit or max heap size, we should verify that the above relationship is satisfied. > Verify that max logs parameter wouldn't cause premature region flush > > > Key: AMBARI-13109 > URL: https://issues.apache.org/jira/browse/AMBARI-13109 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu > > For hbase, the following relationship should be maintained: > dfs.blocksize * 0.95 * hbase.regionserver.maxlogs (default 32) > > hbase.regionserver.global.memstore.upperLimit * HBASE_HEAPSIZE > The rationale is to avoid premature region flush due to log roll which is > triggered by insufficiently high max logs. > When user changes the values for max logs, memstore upper limit or max heap > size, we should verify that the above relationship is satisfied. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13135) Provide recommendation w.r.t. CMSInitiatingOccupancy for HBase
[
https://issues.apache.org/jira/browse/AMBARI-13135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated AMBARI-13135:
Description:
The following options are recommended for HBase when ConcMarkSweepGC is used:
{code}
-XX:CMSInitiatingOccupancyFraction=50
-XX:+UseCMSInitiatingOccupancyOnly
{code}
The band for CMSInitiatingOccupancyFraction is [40, 60], depending on workload.
This should be reflected in stack_advisor.py
was:
The following options are recommended for HBase when ConcMarkSweepGC is used:
{code}
-XX:CMSInitiatingOccupancyFraction=50
-XX:+UseCMSInitiatingOccupancyOnly
{code}
The band for CMSInitiatingOccupancyFraction is [40, 60], depending on workload.
This should be reflected in stack_advisor.py
> Provide recommendation w.r.t. CMSInitiatingOccupancy for HBase
> --
>
> Key: AMBARI-13135
> URL: https://issues.apache.org/jira/browse/AMBARI-13135
> Project: Ambari
> Issue Type: Improvement
>Reporter: Ted Yu
>
> The following options are recommended for HBase when ConcMarkSweepGC is used:
> {code}
> -XX:CMSInitiatingOccupancyFraction=50
> -XX:+UseCMSInitiatingOccupancyOnly
> {code}
> The band for CMSInitiatingOccupancyFraction is [40, 60], depending on
> workload.
> This should be reflected in stack_advisor.py
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-13671) Ambari should check for duplicate config values
[ https://issues.apache.org/jira/browse/AMBARI-13671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-13671: Description: Using /#/main/services/HBASE/configs, I was able to save duplicate values for hbase.coprocessor.region.classes : org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint,org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint Ambari should check for duplicate config values. was: Using /#/main/services/HBASE/configs, I was able to save duplicate values for hbase.coprocessor.region.classes : org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint,org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint Ambari should check for duplicate config values. > Ambari should check for duplicate config values > --- > > Key: AMBARI-13671 > URL: https://issues.apache.org/jira/browse/AMBARI-13671 > Project: Ambari > Issue Type: Bug >Reporter: Ted Yu > > Using /#/main/services/HBASE/configs, I was able to save duplicate values for > hbase.coprocessor.region.classes : > org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint,org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint > Ambari should check for duplicate config values. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18780) Fix livy configuration upgrade from HDP 2.5 to HDP 2.6
[ https://issues.apache.org/jira/browse/AMBARI-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated AMBARI-18780: Fix Version/s: 2.5.0 > Fix livy configuration upgrade from HDP 2.5 to HDP 2.6 > -- > > Key: AMBARI-18780 > URL: https://issues.apache.org/jira/browse/AMBARI-18780 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang > Fix For: 2.5.0 > > > Follow up work for upgrade fix of AMBARI-18758 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18758) Livy configuration change for upgrade
[ https://issues.apache.org/jira/browse/AMBARI-18758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated AMBARI-18758: Description: 2 configuration key are changed. livy.server.kerberos.keytab --> livy.server.launch.kerberos.keytab livy.server.kerberos.principal --> livy.server.launch.kerberos.principal > Livy configuration change for upgrade > - > > Key: AMBARI-18758 > URL: https://issues.apache.org/jira/browse/AMBARI-18758 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang > Fix For: 2.5.0 > > > 2 configuration key are changed. > livy.server.kerberos.keytab --> livy.server.launch.kerberos.keytab > livy.server.kerberos.principal --> livy.server.launch.kerberos.principal -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18780) Fix livy configuration upgrade from HDP 2.5 to HDP 2.6
[ https://issues.apache.org/jira/browse/AMBARI-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated AMBARI-18780: Description: Follow up work for upgrade fix of AMBARI-18758 > Fix livy configuration upgrade from HDP 2.5 to HDP 2.6 > -- > > Key: AMBARI-18780 > URL: https://issues.apache.org/jira/browse/AMBARI-18780 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang > > Follow up work for upgrade fix of AMBARI-18758 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18780) Fix livy configuration upgrade from HDP 2.5 to HDP 2.6
Jeff Zhang created AMBARI-18780: --- Summary: Fix livy configuration upgrade from HDP 2.5 to HDP 2.6 Key: AMBARI-18780 URL: https://issues.apache.org/jira/browse/AMBARI-18780 Project: Ambari Issue Type: Bug Affects Versions: 2.4.0 Reporter: Jeff Zhang Assignee: Jeff Zhang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18769) Proxy user fixes for Hive view 2.0
[ https://issues.apache.org/jira/browse/AMBARI-18769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18769: --- Fix Version/s: (was: 2.4.1) 2.4.2 > Proxy user fixes for Hive view 2.0 > -- > > Key: AMBARI-18769 > URL: https://issues.apache.org/jira/browse/AMBARI-18769 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.2 > > Attachments: AMBARI-18769.2.trunk.patch, AMBARI-18769.4.trunk.patch, > AMBARI-18769.trunk.patch > > > Hive view must allow user proxying -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18766) Add Service failed when none of the host components report version
[
https://issues.apache.org/jira/browse/AMBARI-18766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631143#comment-15631143
]
Sumit Mohanty commented on AMBARI-18766:
LGTM, +1
> Add Service failed when none of the host components report version
> --
>
> Key: AMBARI-18766
> URL: https://issues.apache.org/jira/browse/AMBARI-18766
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Jaimin Jetly
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18766.2.patch, AMBARI-18766.patch
>
>
> When the underlying packages do not support versioned layout or do not report
> version (basically distro-select is not supported) then the stack version
> associated with the cluster is not changed to CURRENT from INIT.
> This blocks the UI from discovering the stack version associated with the
> cluster. UI instead should simply rely on the stack version that is specified
> in the cluster resource.
> *Cluster resource* ("version": "ODPi-1.0")
> {code}
> {
> "href": "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1";,
> "Clusters": {
> "cluster_id": 2,
> "cluster_name": "c1",
> "health_report": {
> "Host/stale_config": 1,
> "Host/maintenance_state": 0,
> "Host/host_status/ALERT": 0
> },
> "provisioning_state": "INSTALLED",
> "security_type": "NONE",
> "total_hosts": 1,
> "version": "ODPi-1.0",
> {code}
> *stack_version resource* ("state": "INIT")
> {code}
> {
> "href":
> "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1/stack_versions/1";,
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 1,
> "repository_version": 1,
> "stack": "ODPi",
> "state": "INIT",
> "version": "1.0",
> "host_states": {
> "CURRENT": [],
> "INIT": [],
> "INSTALLED": [],
> "INSTALLING": [],
> "INSTALL_FAILED": [],
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18779) Fix the backend for HAWQ View BETA
Matt created AMBARI-18779: - Summary: Fix the backend for HAWQ View BETA Key: AMBARI-18779 URL: https://issues.apache.org/jira/browse/AMBARI-18779 Project: Ambari Issue Type: Bug Reporter: Matt Assignee: Matt Priority: Minor Fix For: trunk, 2.5.0, 2.4.2 Fix the backend for HAWQ View so that the backend is able to query from pg_stat_activity table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18766) Add Service failed when none of the host components report version
[
https://issues.apache.org/jira/browse/AMBARI-18766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631112#comment-15631112
]
Hadoop QA commented on AMBARI-18766:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836681/AMBARI-18766.2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9111//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9111//console
This message is automatically generated.
> Add Service failed when none of the host components report version
> --
>
> Key: AMBARI-18766
> URL: https://issues.apache.org/jira/browse/AMBARI-18766
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Jaimin Jetly
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18766.2.patch, AMBARI-18766.patch
>
>
> When the underlying packages do not support versioned layout or do not report
> version (basically distro-select is not supported) then the stack version
> associated with the cluster is not changed to CURRENT from INIT.
> This blocks the UI from discovering the stack version associated with the
> cluster. UI instead should simply rely on the stack version that is specified
> in the cluster resource.
> *Cluster resource* ("version": "ODPi-1.0")
> {code}
> {
> "href": "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1";,
> "Clusters": {
> "cluster_id": 2,
> "cluster_name": "c1",
> "health_report": {
> "Host/stale_config": 1,
> "Host/maintenance_state": 0,
> "Host/host_status/ALERT": 0
> },
> "provisioning_state": "INSTALLED",
> "security_type": "NONE",
> "total_hosts": 1,
> "version": "ODPi-1.0",
> {code}
> *stack_version resource* ("state": "INIT")
> {code}
> {
> "href":
> "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1/stack_versions/1";,
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 1,
> "repository_version": 1,
> "stack": "ODPi",
> "state": "INIT",
> "version": "1.0",
> "host_states": {
> "CURRENT": [],
> "INIT": [],
> "INSTALLED": [],
> "INSTALLING": [],
> "INSTALL_FAILED": [],
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18476) Ambari UI changes to support PAM authentication
[
https://issues.apache.org/jira/browse/AMBARI-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631062#comment-15631062
]
Hadoop QA commented on AMBARI-18476:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836688/AMBARI-18476.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/9110//console
This message is automatically generated.
> Ambari UI changes to support PAM authentication
> ---
>
> Key: AMBARI-18476
> URL: https://issues.apache.org/jira/browse/AMBARI-18476
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: trunk
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Attachments: AMBARI-18476.patch
>
>
> AMBARI-12263 adds support for PAM as authentication mechanism for accessing
> Ambari UI/REST.
> Since a new column group_type has been added for groups, the UI will display
> labels for group type and enable/disable group delete/add member
> functionality based on the group_type instead of the ldap_group flag.
> The user_type will be used to determine if the user can be deleted or if the
> user's password can be changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18769) Proxy user fixes for Hive view 2.0
[
https://issues.apache.org/jira/browse/AMBARI-18769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631058#comment-15631058
]
Hadoop QA commented on AMBARI-18769:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836694/AMBARI-18769.4.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:red}-1 core tests{color}. The test build failed in
contrib/views/hive-next
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9109//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9109//console
This message is automatically generated.
> Proxy user fixes for Hive view 2.0
> --
>
> Key: AMBARI-18769
> URL: https://issues.apache.org/jira/browse/AMBARI-18769
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Ashwin Rajeev
>Assignee: Ashwin Rajeev
> Fix For: 2.4.1
>
> Attachments: AMBARI-18769.2.trunk.patch, AMBARI-18769.4.trunk.patch,
> AMBARI-18769.trunk.patch
>
>
> Hive view must allow user proxying
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-18775) Host Page filter not working properly
[ https://issues.apache.org/jira/browse/AMBARI-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang resolved AMBARI-18775. - Resolution: Not A Bug > Host Page filter not working properly > - > > Key: AMBARI-18775 > URL: https://issues.apache.org/jira/browse/AMBARI-18775 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Vivek Rathod >Assignee: Zhe (Joe) Wang > Fix For: 2.4.2 > > > STR: > Go to hosts page and filter by Resourcemanager. The hosts filtered does not > contain resourcemanager. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-18775) Host Page filter not working properly
[ https://issues.apache.org/jira/browse/AMBARI-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang reassigned AMBARI-18775: --- Assignee: Zhe (Joe) Wang > Host Page filter not working properly > - > > Key: AMBARI-18775 > URL: https://issues.apache.org/jira/browse/AMBARI-18775 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Vivek Rathod >Assignee: Zhe (Joe) Wang > Fix For: 2.4.2 > > > STR: > Go to hosts page and filter by Resourcemanager. The hosts filtered does not > contain resourcemanager. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18769) Proxy user fixes for Hive view 2.0
[ https://issues.apache.org/jira/browse/AMBARI-18769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-18769: --- Attachment: (was: AMBARI-18769.3.trunk.patch) > Proxy user fixes for Hive view 2.0 > -- > > Key: AMBARI-18769 > URL: https://issues.apache.org/jira/browse/AMBARI-18769 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.1 > > Attachments: AMBARI-18769.2.trunk.patch, AMBARI-18769.4.trunk.patch, > AMBARI-18769.trunk.patch > > > Hive view must allow user proxying -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18769) Proxy user fixes for Hive view 2.0
[ https://issues.apache.org/jira/browse/AMBARI-18769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-18769: --- Attachment: AMBARI-18769.4.trunk.patch > Proxy user fixes for Hive view 2.0 > -- > > Key: AMBARI-18769 > URL: https://issues.apache.org/jira/browse/AMBARI-18769 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.1 > > Attachments: AMBARI-18769.2.trunk.patch, AMBARI-18769.4.trunk.patch, > AMBARI-18769.trunk.patch > > > Hive view must allow user proxying -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18769) Proxy user fixes for Hive view 2.0
[ https://issues.apache.org/jira/browse/AMBARI-18769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-18769: --- Attachment: AMBARI-18769.3.trunk.patch > Proxy user fixes for Hive view 2.0 > -- > > Key: AMBARI-18769 > URL: https://issues.apache.org/jira/browse/AMBARI-18769 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.1 > > Attachments: AMBARI-18769.2.trunk.patch, AMBARI-18769.3.trunk.patch, > AMBARI-18769.trunk.patch > > > Hive view must allow user proxying -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17703) Hosts page: after component filter hosts have wrong list of components
[ https://issues.apache.org/jira/browse/AMBARI-17703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630933#comment-15630933 ] Hudson commented on AMBARI-17703: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5920 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5920/]) Revert "AMBARI-17703 - Hosts page: after component filter hosts have (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=47b926fae8206a76725304c5e4d19201869fdf9a]) * (edit) ambari-web/app/controllers/main/host.js * (edit) ambari-web/app/controllers/global/update_controller.js > Hosts page: after component filter hosts have wrong list of components > -- > > Key: AMBARI-17703 > URL: https://issues.apache.org/jira/browse/AMBARI-17703 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.4.0 > > Attachments: AMBARI-17703.patch > > > Go to Hosts page, filter by component. > Result: each host has only filtered component. > Filtering by stack version produce the same behavior too. > Filtering by sub-resource should be carry out in two calls, as it was before > new filter were introduced. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18476) Ambari UI changes to support PAM authentication
[ https://issues.apache.org/jira/browse/AMBARI-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630905#comment-15630905 ] Sangeeta Ravindran commented on AMBARI-18476: - Hi Henning, I had missed updating the patch in the jira when I updated the review request. The final patch was attached in the review. This has all the necessary changes. > Ambari UI changes to support PAM authentication > --- > > Key: AMBARI-18476 > URL: https://issues.apache.org/jira/browse/AMBARI-18476 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Attachments: AMBARI-18476.patch > > > AMBARI-12263 adds support for PAM as authentication mechanism for accessing > Ambari UI/REST. > Since a new column group_type has been added for groups, the UI will display > labels for group type and enable/disable group delete/add member > functionality based on the group_type instead of the ldap_group flag. > The user_type will be used to determine if the user can be deleted or if the > user's password can be changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18778) Ambari-server: Blueprint enhancements to support enabling or disabling credential store
[
https://issues.apache.org/jira/browse/AMBARI-18778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-18778:
---
Description:
When deploying a cluster using a blueprint, users must be able to specify
whether they want to enable the use of hadoop credential store for a service if
it supports it.
{ "settings" :
{
"service_settings" : [
{ "name" : "RANGER",
"recovery_enabled" : "true",
"credential_store_enabled" : "true"
},
{ "name" : "HIVE",
"recovery_enabled" : "true",
"credential_store_enabled" : "false"
}
]
}
}
was:
When deploying a cluster using a blueprint, users must be able to specify
whether they want to enable the use of hadoop credential store for a service if
it supports it.
{quote}
{ "settings" :
{
"service_settings" : [
{ "name" : "RANGER",
"recovery_enabled" : "true",
"credential_store_enabled" : "true"
},
{ "name" : "HIVE",
"recovery_enabled" : "true",
"credential_store_enabled" : "false"
}
]
}
}
{quote}
> Ambari-server: Blueprint enhancements to support enabling or disabling
> credential store
>
>
> Key: AMBARI-18778
> URL: https://issues.apache.org/jira/browse/AMBARI-18778
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
>
> When deploying a cluster using a blueprint, users must be able to specify
> whether they want to enable the use of hadoop credential store for a service
> if it supports it.
> { "settings" :
> {
> "service_settings" : [
> { "name" : "RANGER",
> "recovery_enabled" : "true",
> "credential_store_enabled" : "true"
> },
> { "name" : "HIVE",
> "recovery_enabled" : "true",
> "credential_store_enabled" : "false"
> }
> ]
> }
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18476) Ambari UI changes to support PAM authentication
[ https://issues.apache.org/jira/browse/AMBARI-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18476: Attachment: AMBARI-18476.patch Final patch that was updated in the review request > Ambari UI changes to support PAM authentication > --- > > Key: AMBARI-18476 > URL: https://issues.apache.org/jira/browse/AMBARI-18476 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Attachments: AMBARI-18476.patch > > > AMBARI-12263 adds support for PAM as authentication mechanism for accessing > Ambari UI/REST. > Since a new column group_type has been added for groups, the UI will display > labels for group type and enable/disable group delete/add member > functionality based on the group_type instead of the ldap_group flag. > The user_type will be used to determine if the user can be deleted or if the > user's password can be changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18778) Ambari-server: Blueprint enhancements to support enabling or disabling credential store
Nahappan Somasundaram created AMBARI-18778:
--
Summary: Ambari-server: Blueprint enhancements to support enabling
or disabling credential store
Key: AMBARI-18778
URL: https://issues.apache.org/jira/browse/AMBARI-18778
Project: Ambari
Issue Type: Task
Components: ambari-server
Affects Versions: 2.4.2
Reporter: Nahappan Somasundaram
Assignee: Nahappan Somasundaram
Fix For: 2.5.0
When deploying a cluster using a blueprint, users must be able to specify
whether they want to enable the use of hadoop credential store for a service if
it supports it.
{quote}
{ "settings" :
{
"service_settings" : [
{ "name" : "RANGER",
"recovery_enabled" : "true",
"credential_store_enabled" : "true"
},
{ "name" : "HIVE",
"recovery_enabled" : "true",
"credential_store_enabled" : "false"
}
]
}
}
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18476) Ambari UI changes to support PAM authentication
[ https://issues.apache.org/jira/browse/AMBARI-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18476: Attachment: (was: AMBARI-18476.patch) > Ambari UI changes to support PAM authentication > --- > > Key: AMBARI-18476 > URL: https://issues.apache.org/jira/browse/AMBARI-18476 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > > AMBARI-12263 adds support for PAM as authentication mechanism for accessing > Ambari UI/REST. > Since a new column group_type has been added for groups, the UI will display > labels for group type and enable/disable group delete/add member > functionality based on the group_type instead of the ldap_group flag. > The user_type will be used to determine if the user can be deleted or if the > user's password can be changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17703) Hosts page: after component filter hosts have wrong list of components
[ https://issues.apache.org/jira/browse/AMBARI-17703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630880#comment-15630880 ] Hudson commented on AMBARI-17703: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #250 (See [https://builds.apache.org/job/Ambari-branch-2.5/250/]) Revert "AMBARI-17703 - Hosts page: after component filter hosts have (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9d0bf6d64cf54e27a1cda39f49a4a63811620cb2]) * (edit) ambari-web/app/controllers/global/update_controller.js * (edit) ambari-web/app/controllers/main/host.js > Hosts page: after component filter hosts have wrong list of components > -- > > Key: AMBARI-17703 > URL: https://issues.apache.org/jira/browse/AMBARI-17703 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.4.0 > > Attachments: AMBARI-17703.patch > > > Go to Hosts page, filter by component. > Result: each host has only filtered component. > Filtering by stack version produce the same behavior too. > Filtering by sub-resource should be carry out in two calls, as it was before > new filter were introduced. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18766) Add Service failed when none of the host components report version
[
https://issues.apache.org/jira/browse/AMBARI-18766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin Jetly updated AMBARI-18766:
--
Attachment: AMBARI-18766.2.patch
> Add Service failed when none of the host components report version
> --
>
> Key: AMBARI-18766
> URL: https://issues.apache.org/jira/browse/AMBARI-18766
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Jaimin Jetly
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18766.2.patch, AMBARI-18766.patch
>
>
> When the underlying packages do not support versioned layout or do not report
> version (basically distro-select is not supported) then the stack version
> associated with the cluster is not changed to CURRENT from INIT.
> This blocks the UI from discovering the stack version associated with the
> cluster. UI instead should simply rely on the stack version that is specified
> in the cluster resource.
> *Cluster resource* ("version": "ODPi-1.0")
> {code}
> {
> "href": "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1";,
> "Clusters": {
> "cluster_id": 2,
> "cluster_name": "c1",
> "health_report": {
> "Host/stale_config": 1,
> "Host/maintenance_state": 0,
> "Host/host_status/ALERT": 0
> },
> "provisioning_state": "INSTALLED",
> "security_type": "NONE",
> "total_hosts": 1,
> "version": "ODPi-1.0",
> {code}
> *stack_version resource* ("state": "INIT")
> {code}
> {
> "href":
> "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1/stack_versions/1";,
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 1,
> "repository_version": 1,
> "stack": "ODPi",
> "state": "INIT",
> "version": "1.0",
> "host_states": {
> "CURRENT": [],
> "INIT": [],
> "INSTALLED": [],
> "INSTALLING": [],
> "INSTALL_FAILED": [],
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18346) SmartSense Mandatory Install
[ https://issues.apache.org/jira/browse/AMBARI-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630844#comment-15630844 ] Hudson commented on AMBARI-18346: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5919 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5919/]) AMBARI-18346 SmartSense Mandatory Install (Vivek Ratnavel Subramanian (zhewang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=950d1db879b203a9d8090f414cc75fb54a5deb55]) * (edit) ambari-web/app/mappers/stack_service_mapper.js * (edit) ambari-web/app/models/stack_service.js * (edit) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/metainfo.xml * (edit) ambari-web/app/controllers/wizard/step4_controller.js * (edit) ambari-web/app/templates/wizard/step4.hbs > SmartSense Mandatory Install > > > Key: AMBARI-18346 > URL: https://issues.apache.org/jira/browse/AMBARI-18346 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18346.v0.patch, AMBARI-18346.v1.patch, > AMBARI-18346.v1Trunk.patch > > > Perform a UI hack to force selection of SmartSense for HDP stacks (the user > cannot deselect). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18595) Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11
[ https://issues.apache.org/jira/browse/AMBARI-18595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630845#comment-15630845 ] Hudson commented on AMBARI-18595: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5919 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5919/]) Revert "AMBARI-18595 Icons don't display in Windows 10 Microsoft Edge or (zhewang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=780bf944aa02ef2c075ddcd3215ff9fb81ee025d]) * (edit) ambari-web/pom.xml > Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11 > > > Key: AMBARI-18595 > URL: https://issues.apache.org/jira/browse/AMBARI-18595 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 > Environment: Microsoft Windows 10 > - Microsoft Edge > - Microsoft Internet Explorer 11 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18595.v0.patch, Capture.PNG > > > Icons do not display in any page as shown in the screen-shot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18346) SmartSense Mandatory Install
[ https://issues.apache.org/jira/browse/AMBARI-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630815#comment-15630815 ] Hudson commented on AMBARI-18346: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #249 (See [https://builds.apache.org/job/Ambari-branch-2.5/249/]) AMBARI-18346 SmartSense Mandatory Install (Vivek Ratnavel Subramanian (zhewang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6ed95d5d6981b3c6b28f7260887742b4eda8d525]) * (edit) ambari-web/app/templates/wizard/step4.hbs * (edit) ambari-web/app/mappers/stack_service_mapper.js * (edit) ambari-web/app/models/stack_service.js * (edit) ambari-web/app/controllers/wizard/step4_controller.js > SmartSense Mandatory Install > > > Key: AMBARI-18346 > URL: https://issues.apache.org/jira/browse/AMBARI-18346 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18346.v0.patch, AMBARI-18346.v1.patch, > AMBARI-18346.v1Trunk.patch > > > Perform a UI hack to force selection of SmartSense for HDP stacks (the user > cannot deselect). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18595) Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11
[ https://issues.apache.org/jira/browse/AMBARI-18595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630816#comment-15630816 ] Hudson commented on AMBARI-18595: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #249 (See [https://builds.apache.org/job/Ambari-branch-2.5/249/]) Revert "AMBARI-18595 Icons don't display in Windows 10 Microsoft Edge or (zhewang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e5f0dfc8d73c35fe08a3a66d479aabda48f8ec5e]) * (edit) ambari-web/pom.xml > Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11 > > > Key: AMBARI-18595 > URL: https://issues.apache.org/jira/browse/AMBARI-18595 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 > Environment: Microsoft Windows 10 > - Microsoft Edge > - Microsoft Internet Explorer 11 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18595.v0.patch, Capture.PNG > > > Icons do not display in any page as shown in the screen-shot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18743) Improve wizard styles and apply on Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630776#comment-15630776 ] Hudson commented on AMBARI-18743: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5918 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5918/]) AMBARI-18743. Improve wizard styles and apply on Ambari - update (xiwang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7f931ba896d7a1cfdc8c6d3e58b5e7db3241028e]) * (edit) ambari-web/app/styles/theme/bootstrap-ambari.css > Improve wizard styles and apply on Ambari > - > > Key: AMBARI-18743 > URL: https://issues.apache.org/jira/browse/AMBARI-18743 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-18743.patch > > > Wizard improvements on Ambari UI: > The footer of the wizard (back & next button area) should be separated, not > with the content panel > The content panel should be on a white canvas, separated from step > title/description. > Changes from the style guides: > 1. Narrow down wizard nav items. > 2. In wizard header and footer, should reduce the padding > 3. In wizard content, there should be no border for content panel, also > should reduce step title margin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18777) Component actions confirmation window (from host details page) don't have the details about action to be confirmed
[
https://issues.apache.org/jira/browse/AMBARI-18777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630764#comment-15630764
]
Hadoop QA commented on AMBARI-18777:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836658/AMBARI-18777.v0.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9108//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9108//console
This message is automatically generated.
> Component actions confirmation window (from host details page) don't have the
> details about action to be confirmed
> ---
>
> Key: AMBARI-18777
> URL: https://issues.apache.org/jira/browse/AMBARI-18777
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 3.0.0
>
> Attachments: AMBARI-18777.v0.patch
>
>
> Component actions confirmation modal window (from host details page) don't
> have the details about action to be confirmed.
> The window asks the user "Are you sure" only for any action selected except
> delete e.g Stop, Start, Turn On Maintenance Mode, Restart.
> Steps to reproduce the issue:
> 1. Login to Ambari
> 2. Navigate to Hosts Tab
> 3. Click on Service action drop down of any service available
> 4. Click on any component action e.g Restart/Stop/Start
> 5. The confirmation window should have the action to be performed E.g In Case
> of Restart, "You are about to Restart Service NodeManager, Confirm?".
> But it just have text "Are you sure" for any action selected except delete
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18346) SmartSense Mandatory Install
[ https://issues.apache.org/jira/browse/AMBARI-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18346: Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to trunk 950d1db879b203a9d8090f414cc75fb54a5deb55 and branch-2.5 6ed95d5d6981b3c6b28f7260887742b4eda8d525 > SmartSense Mandatory Install > > > Key: AMBARI-18346 > URL: https://issues.apache.org/jira/browse/AMBARI-18346 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18346.v0.patch, AMBARI-18346.v1.patch, > AMBARI-18346.v1Trunk.patch > > > Perform a UI hack to force selection of SmartSense for HDP stacks (the user > cannot deselect). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-18595) Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11
[ https://issues.apache.org/jira/browse/AMBARI-18595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang reopened AMBARI-18595: - Reverted on trunk 780bf944aa02ef2c075ddcd3215ff9fb81ee025d and branch-2.5 e5f0dfc8d73c35fe08a3a66d479aabda48f8ec5e > Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11 > > > Key: AMBARI-18595 > URL: https://issues.apache.org/jira/browse/AMBARI-18595 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 > Environment: Microsoft Windows 10 > - Microsoft Edge > - Microsoft Internet Explorer 11 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18595.v0.patch, Capture.PNG > > > Icons do not display in any page as shown in the screen-shot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-17703) Hosts page: after component filter hosts have wrong list of components
[ https://issues.apache.org/jira/browse/AMBARI-17703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang reopened AMBARI-17703: --- Fix for this issue cause caused inconsistencies in Host model. Need to find another way to fix it. > Hosts page: after component filter hosts have wrong list of components > -- > > Key: AMBARI-17703 > URL: https://issues.apache.org/jira/browse/AMBARI-17703 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.4.0 > > Attachments: AMBARI-17703.patch > > > Go to Hosts page, filter by component. > Result: each host has only filtered component. > Filtering by stack version produce the same behavior too. > Filtering by sub-resource should be carry out in two calls, as it was before > new filter were introduced. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18746) Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
[
https://issues.apache.org/jira/browse/AMBARI-18746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630706#comment-15630706
]
Hadoop QA commented on AMBARI-18746:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836662/AMBARI-18746-rebased.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/9107//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9107//console
This message is automatically generated.
> Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
> ---
>
> Key: AMBARI-18746
> URL: https://issues.apache.org/jira/browse/AMBARI-18746
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.4.0, 2.5.0
> Environment: Redhat 6.6, Sqoop 1.4.6+Hadoop 2.7.2
>Reporter: Ying Cao
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18746-rebased.patch, AMBARI-18746.1.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> The parameter hadoop_home is pointed to hbase-client in params_linux.py, and
> need to be updated.
> ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py
> # For stack versions supporting rolling upgrade
> if stack_version_formatted and
>
> hadoop_home = format("{stack_root}/current/hbase-client")
> ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18733) Perf: Allow running multiple Ambari Agents on the same host
[ https://issues.apache.org/jira/browse/AMBARI-18733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630666#comment-15630666 ] Hudson commented on AMBARI-18733: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #248 (See [https://builds.apache.org/job/Ambari-branch-2.5/248/]) AMBARI-18733. Perf: Allow running multiple Ambari Agents on the same (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b144a1f2da4cb428e1c8d6e675b0fb89b49a2d4a]) * (edit) ambari-agent/src/test/python/ambari_agent/TestMain.py * (edit) ambari-agent/conf/windows/service_wrapper.py * (edit) ambari-agent/src/main/python/ambari_agent/AmbariConfig.py * (edit) ambari-agent/src/main/python/ambari_agent/Facter.py * (edit) ambari-agent/src/main/python/ambari_agent/Hardware.py * (edit) ambari-agent/src/test/python/ambari_agent/TestHardware.py * (edit) ambari-agent/src/test/python/ambari_agent/TestCheckWebUI.py * (edit) ambari-agent/src/main/python/ambari_agent/Register.py * (edit) ambari-agent/conf/unix/ambari-agent * (edit) ambari-agent/src/main/python/ambari_agent/main.py * (edit) ambari-agent/src/main/python/ambari_agent/Heartbeat.py > Perf: Allow running multiple Ambari Agents on the same host > --- > > Key: AMBARI-18733 > URL: https://issues.apache.org/jira/browse/AMBARI-18733 > Project: Ambari > Issue Type: Story > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-18733.patch > > > Currently there are limitations to running multiple Ambari Agents on the same > host because it uses a single path for > /etc/ambari-agent/conf/ambari-agent.ini > /var/run/ambari-agent/ambari-agent.pid > /var/lib/ambari-agent/data > /var/log/ambari-agent/ > Ambari Agent already has a way to change the port, log dir, and pid dir > through its config file, so we also need it to support its own unique home > directory with its own unique config file. > Furthermore, the agent will have to override its hostname. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18346) SmartSense Mandatory Install
[
https://issues.apache.org/jira/browse/AMBARI-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630644#comment-15630644
]
Hadoop QA commented on AMBARI-18346:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836665/AMBARI-18346.v1Trunk.patch
against trunk revision .
{color:red}-1 patch{color}. Trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9106//console
This message is automatically generated.
> SmartSense Mandatory Install
>
>
> Key: AMBARI-18346
> URL: https://issues.apache.org/jira/browse/AMBARI-18346
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-18346.v0.patch, AMBARI-18346.v1.patch,
> AMBARI-18346.v1Trunk.patch
>
>
> Perform a UI hack to force selection of SmartSense for HDP stacks (the user
> cannot deselect).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18774) Install Package for non-HDP stack fails with non-VDF repo version
[
https://issues.apache.org/jira/browse/AMBARI-18774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630629#comment-15630629
]
Hadoop QA commented on AMBARI-18774:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836610/AMBARI-18774.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.controller.metrics.JMXPropertyProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9105//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9105//console
This message is automatically generated.
> Install Package for non-HDP stack fails with non-VDF repo version
> -
>
> Key: AMBARI-18774
> URL: https://issues.apache.org/jira/browse/AMBARI-18774
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18774.patch
>
>
> Install Package fails when registering a new non-HDP version without using a
> VDF. This is because the repo version is saved as display name (i.e.
> "HDF-2.1.0.0-30" instead of "2.1.0.0-30"). If a new version is registered
> using VDF, we dont run into this issue as the version is set correctly.
> {code}
> Ambari cannot install version HDF-2.1.0.0. Version 2.0.1.0-12 is already
> installed.
> {code}
> Fix:
> Remove HDP specific hardcodings from RepositoryVersionEntity.java
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18732) Perf: Create PERF stack with mix of HDP core services and dummy services
[ https://issues.apache.org/jira/browse/AMBARI-18732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630602#comment-15630602 ] Hudson commented on AMBARI-18732: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5917 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5917/]) AMBARI-18732. Perf: Create PERF stack with mix of HDP core services and (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fca6f1c3a56aa13c7fda385cba5fdae59dc990ed]) * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/package/scripts/service_check.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/hooks/before-START/scripts/hook.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/repos/repoinfo.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/metainfo.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/properties/stack_tools.json * (add) ambari-server/src/main/resources/stacks/PERF/1.0/hooks/before-ANY/scripts/hook.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/metainfo.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/hooks/after-INSTALL/scripts/hook.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/package/scripts/snow_white.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/configuration/cluster-env.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/themes/theme.json * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/configuration/happy-site.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/properties/stack_features.json * (add) ambari-server/src/main/resources/stacks/PERF/1.0/metainfo.xml * (add) ambari-common/src/main/python/resource_management/libraries/script/dummy.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/package/scripts/service_check.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/hooks/before-RESTART/scripts/hook.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/configuration/snow-site.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/themes/theme.json * (add) ambari-server/src/main/resources/stacks/PERF/1.0/hooks/before-INSTALL/scripts/hook.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/role_command_order.json * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/package/scripts/dwarf.py > Perf: Create PERF stack with mix of HDP core services and dummy services > > > Key: AMBARI-18732 > URL: https://issues.apache.org/jira/browse/AMBARI-18732 > Project: Ambari > Issue Type: Story > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-18732.patch > > > We need a fake stack that will make it easier to perform lifecycle commands > such as Start, Stop, Restart, Status, Service Checks etc. > This stack will eventually support UI themes, Kerberos, Alerts, etc. > For now, the PERF stack should have 8+ services (HDFS, YARN, MR, ZK, plus > dummy ones like Happy, Sleepy, Grumpy, etc). > We do want some of the complexity of the Hadoop core services and their > configs, and we also want really simple services (like the dwarfs) that can > be deployed on their own. > This stack should serve as a sample for how to implement a new stack, and > also abstract some of the complexity of the HDP stack in order to run > performance tests that stress the server by overloading it with heartbeats, > alerts, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18733) Perf: Allow running multiple Ambari Agents on the same host
[ https://issues.apache.org/jira/browse/AMBARI-18733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630603#comment-15630603 ] Hudson commented on AMBARI-18733: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5917 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5917/]) AMBARI-18733. Perf: Allow running multiple Ambari Agents on the same (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4e96cf51c5a796c7efc8415c7106ca5d071678a2]) * (edit) ambari-agent/src/main/python/ambari_agent/Hardware.py * (edit) ambari-agent/src/main/python/ambari_agent/main.py * (edit) ambari-agent/src/test/python/ambari_agent/TestCheckWebUI.py * (edit) ambari-agent/src/main/python/ambari_agent/Register.py * (edit) ambari-agent/conf/windows/service_wrapper.py * (edit) ambari-agent/src/main/python/ambari_agent/AmbariConfig.py * (edit) ambari-agent/src/main/python/ambari_agent/Heartbeat.py * (edit) ambari-agent/src/test/python/ambari_agent/TestHardware.py * (edit) ambari-agent/src/test/python/ambari_agent/TestMain.py * (edit) ambari-agent/src/main/python/ambari_agent/Facter.py * (edit) ambari-agent/conf/unix/ambari-agent > Perf: Allow running multiple Ambari Agents on the same host > --- > > Key: AMBARI-18733 > URL: https://issues.apache.org/jira/browse/AMBARI-18733 > Project: Ambari > Issue Type: Story > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-18733.patch > > > Currently there are limitations to running multiple Ambari Agents on the same > host because it uses a single path for > /etc/ambari-agent/conf/ambari-agent.ini > /var/run/ambari-agent/ambari-agent.pid > /var/lib/ambari-agent/data > /var/log/ambari-agent/ > Ambari Agent already has a way to change the port, log dir, and pid dir > through its config file, so we also need it to support its own unique home > directory with its own unique config file. > Furthermore, the agent will have to override its hostname. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18732) Perf: Create PERF stack with mix of HDP core services and dummy services
[ https://issues.apache.org/jira/browse/AMBARI-18732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630591#comment-15630591 ] Hudson commented on AMBARI-18732: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #247 (See [https://builds.apache.org/job/Ambari-branch-2.5/247/]) AMBARI-18732. Perf: Create PERF stack with mix of HDP core services and (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e38da0dab6c31c3f56f22e690c22105498b76684]) * (add) ambari-server/src/main/resources/stacks/PERF/1.0/hooks/before-ANY/scripts/hook.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/configuration/snow-site.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/metainfo.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/package/scripts/snow_white.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/repos/repoinfo.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/role_command_order.json * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/package/scripts/service_check.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/themes/theme.json * (add) ambari-server/src/main/resources/stacks/PERF/1.0/configuration/cluster-env.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/properties/stack_tools.json * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/themes/theme.json * (add) ambari-server/src/main/resources/stacks/PERF/1.0/hooks/before-INSTALL/scripts/hook.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/hooks/before-START/scripts/hook.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/hooks/after-INSTALL/scripts/hook.py * (add) ambari-common/src/main/python/resource_management/libraries/script/dummy.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/configuration/happy-site.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/package/scripts/dwarf.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/package/scripts/service_check.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/metainfo.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/hooks/before-RESTART/scripts/hook.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/metainfo.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/properties/stack_features.json > Perf: Create PERF stack with mix of HDP core services and dummy services > > > Key: AMBARI-18732 > URL: https://issues.apache.org/jira/browse/AMBARI-18732 > Project: Ambari > Issue Type: Story > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-18732.patch > > > We need a fake stack that will make it easier to perform lifecycle commands > such as Start, Stop, Restart, Status, Service Checks etc. > This stack will eventually support UI themes, Kerberos, Alerts, etc. > For now, the PERF stack should have 8+ services (HDFS, YARN, MR, ZK, plus > dummy ones like Happy, Sleepy, Grumpy, etc). > We do want some of the complexity of the Hadoop core services and their > configs, and we also want really simple services (like the dwarfs) that can > be deployed on their own. > This stack should serve as a sample for how to implement a new stack, and > also abstract some of the complexity of the HDP stack in order to run > performance tests that stress the server by overloading it with heartbeats, > alerts, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18346) SmartSense Mandatory Install
[ https://issues.apache.org/jira/browse/AMBARI-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18346: Status: Open (was: Patch Available) > SmartSense Mandatory Install > > > Key: AMBARI-18346 > URL: https://issues.apache.org/jira/browse/AMBARI-18346 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18346.v0.patch, AMBARI-18346.v1.patch, > AMBARI-18346.v1Trunk.patch > > > Perform a UI hack to force selection of SmartSense for HDP stacks (the user > cannot deselect). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18346) SmartSense Mandatory Install
[ https://issues.apache.org/jira/browse/AMBARI-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18346: Status: Patch Available (was: Open) > SmartSense Mandatory Install > > > Key: AMBARI-18346 > URL: https://issues.apache.org/jira/browse/AMBARI-18346 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18346.v0.patch, AMBARI-18346.v1.patch, > AMBARI-18346.v1Trunk.patch > > > Perform a UI hack to force selection of SmartSense for HDP stacks (the user > cannot deselect). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18346) SmartSense Mandatory Install
[ https://issues.apache.org/jira/browse/AMBARI-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18346: Attachment: AMBARI-18346.v1Trunk.patch > SmartSense Mandatory Install > > > Key: AMBARI-18346 > URL: https://issues.apache.org/jira/browse/AMBARI-18346 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18346.v0.patch, AMBARI-18346.v1.patch, > AMBARI-18346.v1Trunk.patch > > > Perform a UI hack to force selection of SmartSense for HDP stacks (the user > cannot deselect). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18587) Post user creation hook
[
https://issues.apache.org/jira/browse/AMBARI-18587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630529#comment-15630529
]
Hadoop QA commented on AMBARI-18587:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836616/AMBARI-18587-trunk.v10.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 12 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.TestHeartbeatHandler
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9104//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9104//console
This message is automatically generated.
> Post user creation hook
> ---
>
> Key: AMBARI-18587
> URL: https://issues.apache.org/jira/browse/AMBARI-18587
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
>Reporter: Laszlo Puskas
>Assignee: Laszlo Puskas
> Fix For: 2.5.0
>
> Attachments: AMBARI-18587-trunk.v10.patch
>
> Original Estimate: 336h
> Time Spent: 240h
> Remaining Estimate: 48h
>
> Ability to execute post user creation script
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18733) Perf: Allow running multiple Ambari Agents on the same host
[ https://issues.apache.org/jira/browse/AMBARI-18733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18733: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk, commit 4e96cf51c5a796c7efc8415c7106ca5d071678a2 branch-2.5: commit b144a1f2da4cb428e1c8d6e675b0fb89b49a2d4a > Perf: Allow running multiple Ambari Agents on the same host > --- > > Key: AMBARI-18733 > URL: https://issues.apache.org/jira/browse/AMBARI-18733 > Project: Ambari > Issue Type: Story > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-18733.patch > > > Currently there are limitations to running multiple Ambari Agents on the same > host because it uses a single path for > /etc/ambari-agent/conf/ambari-agent.ini > /var/run/ambari-agent/ambari-agent.pid > /var/lib/ambari-agent/data > /var/log/ambari-agent/ > Ambari Agent already has a way to change the port, log dir, and pid dir > through its config file, so we also need it to support its own unique home > directory with its own unique config file. > Furthermore, the agent will have to override its hostname. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18746) Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
[
https://issues.apache.org/jira/browse/AMBARI-18746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Di Li updated AMBARI-18746:
---
Attachment: AMBARI-18746-rebased.patch
> Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
> ---
>
> Key: AMBARI-18746
> URL: https://issues.apache.org/jira/browse/AMBARI-18746
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.4.0, 2.5.0
> Environment: Redhat 6.6, Sqoop 1.4.6+Hadoop 2.7.2
>Reporter: Ying Cao
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18746-rebased.patch, AMBARI-18746.1.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> The parameter hadoop_home is pointed to hbase-client in params_linux.py, and
> need to be updated.
> ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py
> # For stack versions supporting rolling upgrade
> if stack_version_formatted and
>
> hadoop_home = format("{stack_root}/current/hbase-client")
> ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18732) Perf: Create PERF stack with mix of HDP core services and dummy services
[ https://issues.apache.org/jira/browse/AMBARI-18732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18732: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk, commit fca6f1c3a56aa13c7fda385cba5fdae59dc990ed branch-2.5, commit e38da0dab6c31c3f56f22e690c22105498b76684 > Perf: Create PERF stack with mix of HDP core services and dummy services > > > Key: AMBARI-18732 > URL: https://issues.apache.org/jira/browse/AMBARI-18732 > Project: Ambari > Issue Type: Story > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-18732.patch > > > We need a fake stack that will make it easier to perform lifecycle commands > such as Start, Stop, Restart, Status, Service Checks etc. > This stack will eventually support UI themes, Kerberos, Alerts, etc. > For now, the PERF stack should have 8+ services (HDFS, YARN, MR, ZK, plus > dummy ones like Happy, Sleepy, Grumpy, etc). > We do want some of the complexity of the Hadoop core services and their > configs, and we also want really simple services (like the dwarfs) that can > be deployed on their own. > This stack should serve as a sample for how to implement a new stack, and > also abstract some of the complexity of the HDP stack in order to run > performance tests that stress the server by overloading it with heartbeats, > alerts, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18746) Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
[
https://issues.apache.org/jira/browse/AMBARI-18746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Di Li updated AMBARI-18746:
---
Status: Patch Available (was: Open)
> Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
> ---
>
> Key: AMBARI-18746
> URL: https://issues.apache.org/jira/browse/AMBARI-18746
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
> Environment: Redhat 6.6, Sqoop 1.4.6+Hadoop 2.7.2
>Reporter: Ying Cao
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18746-rebased.patch, AMBARI-18746.1.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> The parameter hadoop_home is pointed to hbase-client in params_linux.py, and
> need to be updated.
> ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py
> # For stack versions supporting rolling upgrade
> if stack_version_formatted and
>
> hadoop_home = format("{stack_root}/current/hbase-client")
> ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18746) Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
[
https://issues.apache.org/jira/browse/AMBARI-18746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Di Li updated AMBARI-18746:
---
Affects Version/s: 2.5.0
trunk
> Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
> ---
>
> Key: AMBARI-18746
> URL: https://issues.apache.org/jira/browse/AMBARI-18746
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.4.0, 2.5.0
> Environment: Redhat 6.6, Sqoop 1.4.6+Hadoop 2.7.2
>Reporter: Ying Cao
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18746-rebased.patch, AMBARI-18746.1.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> The parameter hadoop_home is pointed to hbase-client in params_linux.py, and
> need to be updated.
> ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py
> # For stack versions supporting rolling upgrade
> if stack_version_formatted and
>
> hadoop_home = format("{stack_root}/current/hbase-client")
> ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18746) Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
[
https://issues.apache.org/jira/browse/AMBARI-18746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Di Li updated AMBARI-18746:
---
Status: Open (was: Patch Available)
> Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
> ---
>
> Key: AMBARI-18746
> URL: https://issues.apache.org/jira/browse/AMBARI-18746
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
> Environment: Redhat 6.6, Sqoop 1.4.6+Hadoop 2.7.2
>Reporter: Ying Cao
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18746.1.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> The parameter hadoop_home is pointed to hbase-client in params_linux.py, and
> need to be updated.
> ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py
> # For stack versions supporting rolling upgrade
> if stack_version_formatted and
>
> hadoop_home = format("{stack_root}/current/hbase-client")
> ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18746) Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
[
https://issues.apache.org/jira/browse/AMBARI-18746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Di Li updated AMBARI-18746:
---
Fix Version/s: (was: 2.4.1)
2.5.0
trunk
> Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
> ---
>
> Key: AMBARI-18746
> URL: https://issues.apache.org/jira/browse/AMBARI-18746
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
> Environment: Redhat 6.6, Sqoop 1.4.6+Hadoop 2.7.2
>Reporter: Ying Cao
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18746.1.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> The parameter hadoop_home is pointed to hbase-client in params_linux.py, and
> need to be updated.
> ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py
> # For stack versions supporting rolling upgrade
> if stack_version_formatted and
>
> hadoop_home = format("{stack_root}/current/hbase-client")
> ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18767) E2E Integration for Manage JournalNode Wizard
[ https://issues.apache.org/jira/browse/AMBARI-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630407#comment-15630407 ] Hudson commented on AMBARI-18767: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5916 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5916/]) AMBARI-18767 - E2E Integration for Manage JournalNode Wizard (rzang) (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c9362c897e87c79aaba9f171717fe6a2dd63f4cc]) * (edit) ambari-web/app/controllers/main/admin/highAvailability/journalNode/step2_controller.js * (add) ambari-web/app/controllers/main/admin/highAvailability/journalNode/step8_controller.js * (edit) ambari-web/app/controllers.js * (edit) ambari-web/app/controllers/main/admin/highAvailability/journalNode/step1_controller.js * (edit) ambari-web/app/templates/main/admin/highAvailability/journalNode/wizard.hbs * (add) ambari-web/app/controllers/main/admin/highAvailability/journalNode/step7_controller.js * (add) ambari-web/app/templates/main/admin/highAvailability/journalNode/step7.hbs * (add) ambari-web/app/templates/main/admin/highAvailability/journalNode/step8.hbs * (edit) ambari-web/app/views/main/admin/highAvailability/journalNode/step2_view.js * (edit) ambari-web/app/views/main/admin/highAvailability/journalNode/step5_view.js * (edit) ambari-web/app/templates/main/admin/highAvailability/journalNode/step2.hbs * (edit) ambari-web/app/styles/application.less * (edit) ambari-web/app/views/main/admin/highAvailability/journalNode/step3_view.js * (edit) ambari-web/app/controllers/main/admin/highAvailability/journalNode/wizard_controller.js * (edit) ambari-web/app/routes/manage_journalnode_routes.js * (add) ambari-web/app/views/main/admin/highAvailability/journalNode/step8_view.js * (edit) ambari-web/app/views.js * (add) ambari-web/app/views/main/admin/highAvailability/journalNode/step7_view.js * (edit) ambari-web/app/controllers/main/admin/highAvailability/journalNode/step6_controller.js * (edit) ambari-web/app/controllers/main/admin/highAvailability/journalNode/step4_controller.js * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/views/main/admin/highAvailability/journalNode/wizard_view.js > E2E Integration for Manage JournalNode Wizard > - > > Key: AMBARI-18767 > URL: https://issues.apache.org/jira/browse/AMBARI-18767 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-18767.patch, AMBARI-18767_branch-2.5.patch > > > E2E Integration for Manage JournalNode Wizard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18767) E2E Integration for Manage JournalNode Wizard
[ https://issues.apache.org/jira/browse/AMBARI-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630400#comment-15630400 ] Hudson commented on AMBARI-18767: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #246 (See [https://builds.apache.org/job/Ambari-branch-2.5/246/]) AMBARI-18767 - E2E Integration for Manage JournalNode Wizard (rzang) (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e1d4a44b02425073cfc653402c8c2b3457a3e4d9]) * (add) ambari-web/app/templates/main/admin/highAvailability/journalNode/step7.hbs * (add) ambari-web/app/views/main/admin/highAvailability/journalNode/step7_view.js * (edit) ambari-web/app/views/main/admin/highAvailability/journalNode/step5_view.js * (edit) ambari-web/app/views/main/admin/highAvailability/journalNode/wizard_view.js * (edit) ambari-web/app/views.js * (edit) ambari-web/app/controllers/main/admin/highAvailability/journalNode/step1_controller.js * (add) ambari-web/app/controllers/main/admin/highAvailability/journalNode/step8_controller.js * (edit) ambari-web/app/controllers/main/admin/highAvailability/journalNode/step2_controller.js * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/controllers/main/admin/highAvailability/journalNode/step4_controller.js * (edit) ambari-web/app/controllers/main/admin/highAvailability/journalNode/step6_controller.js * (edit) ambari-web/app/routes/manage_journalnode_routes.js * (edit) ambari-web/app/views/main/admin/highAvailability/journalNode/step3_view.js * (add) ambari-web/app/views/main/admin/highAvailability/journalNode/step8_view.js * (add) ambari-web/app/templates/main/admin/highAvailability/journalNode/step8.hbs * (edit) ambari-web/app/views/main/admin/highAvailability/journalNode/step2_view.js * (edit) ambari-web/app/templates/main/admin/highAvailability/journalNode/step2.hbs * (add) ambari-web/app/controllers/main/admin/highAvailability/journalNode/step7_controller.js * (edit) ambari-web/app/controllers/main/admin/highAvailability/journalNode/wizard_controller.js * (edit) ambari-web/app/styles/application.less * (edit) ambari-web/app/controllers.js * (edit) ambari-web/app/templates/main/admin/highAvailability/journalNode/wizard.hbs > E2E Integration for Manage JournalNode Wizard > - > > Key: AMBARI-18767 > URL: https://issues.apache.org/jira/browse/AMBARI-18767 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-18767.patch, AMBARI-18767_branch-2.5.patch > > > E2E Integration for Manage JournalNode Wizard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18777) Component actions confirmation window (from host details page) don't have the details about action to be confirmed
[ https://issues.apache.org/jira/browse/AMBARI-18777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18777: Attachment: AMBARI-18777.v0.patch > Component actions confirmation window (from host details page) don't have the > details about action to be confirmed > --- > > Key: AMBARI-18777 > URL: https://issues.apache.org/jira/browse/AMBARI-18777 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 3.0.0 > > Attachments: AMBARI-18777.v0.patch > > > Component actions confirmation modal window (from host details page) don't > have the details about action to be confirmed. > The window asks the user "Are you sure" only for any action selected except > delete e.g Stop, Start, Turn On Maintenance Mode, Restart. > Steps to reproduce the issue: > 1. Login to Ambari > 2. Navigate to Hosts Tab > 3. Click on Service action drop down of any service available > 4. Click on any component action e.g Restart/Stop/Start > 5. The confirmation window should have the action to be performed E.g In Case > of Restart, "You are about to Restart Service NodeManager, Confirm?". > But it just have text "Are you sure" for any action selected except delete -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18696) Add Hive&Tez View Links to Hive Summary Page
[ https://issues.apache.org/jira/browse/AMBARI-18696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630399#comment-15630399 ] Hudson commented on AMBARI-18696: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #246 (See [https://builds.apache.org/job/Ambari-branch-2.5/246/]) AMBARI-18696 - Add Hive&Tez View Links to Hive Summary Page (rzang) (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=052de09b9a1fbef002b2d7f8417fcbf577d96fe3]) * (edit) ambari-web/app/templates/main/dashboard/widgets/hbase_links.hbs * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/templates/main/dashboard/widgets/hdfs_links.hbs * (edit) ambari-web/app/controllers/main/service/info/summary.js * (edit) ambari-web/app/views/main/service/services/hive.js * (edit) ambari-web/app/views/common/quick_view_link_view.js * (edit) ambari-web/app/views/common/log_search_ui_link_view.js * (edit) ambari-web/app/templates/main/service/item.hbs * (edit) ambari-web/app/templates/main/dashboard/widgets/yarn_links.hbs * (edit) ambari-web/app/templates/main/service/services/hive.hbs > Add Hive&Tez View Links to Hive Summary Page > > > Key: AMBARI-18696 > URL: https://issues.apache.org/jira/browse/AMBARI-18696 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-18696.patch > > > Add Hive&Tez View Links to Hive Summary Page -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18777) Component actions confirmation window (from host details page) don't have the details about action to be confirmed
[ https://issues.apache.org/jira/browse/AMBARI-18777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18777: Status: Patch Available (was: In Progress) > Component actions confirmation window (from host details page) don't have the > details about action to be confirmed > --- > > Key: AMBARI-18777 > URL: https://issues.apache.org/jira/browse/AMBARI-18777 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 3.0.0 > > Attachments: AMBARI-18777.v0.patch > > > Component actions confirmation modal window (from host details page) don't > have the details about action to be confirmed. > The window asks the user "Are you sure" only for any action selected except > delete e.g Stop, Start, Turn On Maintenance Mode, Restart. > Steps to reproduce the issue: > 1. Login to Ambari > 2. Navigate to Hosts Tab > 3. Click on Service action drop down of any service available > 4. Click on any component action e.g Restart/Stop/Start > 5. The confirmation window should have the action to be performed E.g In Case > of Restart, "You are about to Restart Service NodeManager, Confirm?". > But it just have text "Are you sure" for any action selected except delete -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18744) Ambari-server: REST API changes to GET and PUT credential store information
[
https://issues.apache.org/jira/browse/AMBARI-18744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630378#comment-15630378
]
Hadoop QA commented on AMBARI-18744:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836617/rb53283.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/9103//console
This message is automatically generated.
> Ambari-server: REST API changes to GET and PUT credential store information
> ---
>
> Key: AMBARI-18744
> URL: https://issues.apache.org/jira/browse/AMBARI-18744
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53283.patch
>
>
> *Support stack definition for credential store information*
> To support backward compatibility, services must be tagged to indicate
> whether they support credential store backed passwords. This requires changes
> in the stack definition object model.
> {code}
>
> SERVICE_NAME
> :
>
> true
> false
>
> :
> :
>
> {code}
> *REST API support is required to GET _credential_store_supported_ and
> _credential_store_enabled_ values for a service:*
> {quote}api/v1/clusters//services?fields=ServiceInfo/service_name,ServiceInfo/credential_store_supported,ServiceInfo/credential_store_enabled{quote}
> *REST API support is required to PUT _credential_store_enabled_ value for a
> service:*
> {quote}curl -u admin:admin -H "X-Requested-By: ambari"
> http://localhost:8080/api/v1/clusters/cl1/services -X PUT -d
> '{"ServceInfo":{"credential_store_enabled":"true"},
> "RequestInfo":{"query":"ServiceInfo/service_name.in(HIVE,YARN)"}}'{quote}
> {quote}api/v1/clusters/testcluster/services/RANGER -X PUT -d '{"ServiceInfo"
> : {"credential_store_enabled":"true"}}'
> {quote}
> {quote}api/v1/clusters/testcluster/services?ServiceInfo/service_name=ZOOKEEPER
> -X PUT -d '{"ServiceInfo" : {"credential_store_enabled":"false"}}'{quote}
> *REST API to get Stack definition*
> {quote}
> curl -u admin:admin -H "X-Requested-By: ambari" -X GET
> http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services
> {quote}
> {quote}
> {
> "href" : "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/";,
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/YARN";,
> "StackServices" : {
> "service_name" : "YARN",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> },
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/ZOOKEEPER";,
> "StackServices" : {
> "service_name" : "ZOOKEEPER",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> }
> ]
> }
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18777) Component actions confirmation window (from host details page) don't have the details about action to be confirmed
Vivek Ratnavel Subramanian created AMBARI-18777: --- Summary: Component actions confirmation window (from host details page) don't have the details about action to be confirmed Key: AMBARI-18777 URL: https://issues.apache.org/jira/browse/AMBARI-18777 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 3.0.0 Component actions confirmation modal window (from host details page) don't have the details about action to be confirmed. The window asks the user "Are you sure" only for any action selected except delete e.g Stop, Start, Turn On Maintenance Mode, Restart. Steps to reproduce the issue: 1. Login to Ambari 2. Navigate to Hosts Tab 3. Click on Service action drop down of any service available 4. Click on any component action e.g Restart/Stop/Start 5. The confirmation window should have the action to be performed E.g In Case of Restart, "You are about to Restart Service NodeManager, Confirm?". But it just have text "Are you sure" for any action selected except delete -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18776) DB consistency check should inform user about warnings but not fail ambari-server start
[
https://issues.apache.org/jira/browse/AMBARI-18776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630376#comment-15630376
]
Hadoop QA commented on AMBARI-18776:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836630/AMBARI-18776_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 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9102//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9102//console
This message is automatically generated.
> DB consistency check should inform user about warnings but not fail
> ambari-server start
> ---
>
> Key: AMBARI-18776
> URL: https://issues.apache.org/jira/browse/AMBARI-18776
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18776_trunk.patch
>
>
> As of now we don't show any info about warnings in db consistency check for
> user. I think we should print some information for user into command line.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18768) Session invalidation for hive view
[ https://issues.apache.org/jira/browse/AMBARI-18768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18768: --- Fix Version/s: (was: 2.4.0) 2.4.2 > Session invalidation for hive view > -- > > Key: AMBARI-18768 > URL: https://issues.apache.org/jira/browse/AMBARI-18768 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.2 > > Attachments: AMBARI-18768.2.trunk.patch, AMBARI-18786.trunk.patch > > > In some cases , HS2 may restart/be restarted when the hive view is in use, > This usually manifests as a session expired/broken pipe exception > Change the error shown to a connection error and indicate that user must > retry the query -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18767) E2E Integration for Manage JournalNode Wizard
[ https://issues.apache.org/jira/browse/AMBARI-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-18767: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and 2.5 e1d4a44b02425073cfc653402c8c2b3457a3e4d9 > E2E Integration for Manage JournalNode Wizard > - > > Key: AMBARI-18767 > URL: https://issues.apache.org/jira/browse/AMBARI-18767 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-18767.patch, AMBARI-18767_branch-2.5.patch > > > E2E Integration for Manage JournalNode Wizard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18768) Session invalidation for hive view
[ https://issues.apache.org/jira/browse/AMBARI-18768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630277#comment-15630277 ] Hudson commented on AMBARI-18768: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5915 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5915/]) AMBARI-18768. Session invalidation for hive view. (Ashwin Rajeev via (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a8727af88fd5f6ba5d889854589093e19efdf27a]) * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/JdbcConnector.java * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/client/AsyncJobRunnerImpl.java > Session invalidation for hive view > -- > > Key: AMBARI-18768 > URL: https://issues.apache.org/jira/browse/AMBARI-18768 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.0 > > Attachments: AMBARI-18768.2.trunk.patch, AMBARI-18786.trunk.patch > > > In some cases , HS2 may restart/be restarted when the hive view is in use, > This usually manifests as a session expired/broken pipe exception > Change the error shown to a connection error and indicate that user must > retry the query -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18744) Ambari-server: REST API changes to GET and PUT credential store information
[
https://issues.apache.org/jira/browse/AMBARI-18744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630278#comment-15630278
]
Hudson commented on AMBARI-18744:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5915 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5915/])
AMBARI-18744: Ambari-server: REST API changes to GET and PUT credential
(nsomasundaram:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=33a4119539107b781270a4347a5364e0f40652d7])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceInfo.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/ServiceResponse.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/ServiceRequest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/StackServiceRequest.java
* (edit) ambari-server/src/main/resources/properties.json
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/StackServiceResponse.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ServiceResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackServiceResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceImpl.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/ServiceInfoTest.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/state/CredentialStoreInfo.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ServiceResourceProviderTest.java
> Ambari-server: REST API changes to GET and PUT credential store information
> ---
>
> Key: AMBARI-18744
> URL: https://issues.apache.org/jira/browse/AMBARI-18744
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53283.patch
>
>
> *Support stack definition for credential store information*
> To support backward compatibility, services must be tagged to indicate
> whether they support credential store backed passwords. This requires changes
> in the stack definition object model.
> {code}
>
> SERVICE_NAME
> :
>
> true
> false
>
> :
> :
>
> {code}
> *REST API support is required to GET _credential_store_supported_ and
> _credential_store_enabled_ values for a service:*
> {quote}api/v1/clusters//services?fields=ServiceInfo/service_name,ServiceInfo/credential_store_supported,ServiceInfo/credential_store_enabled{quote}
> *REST API support is required to PUT _credential_store_enabled_ value for a
> service:*
> {quote}curl -u admin:admin -H "X-Requested-By: ambari"
> http://localhost:8080/api/v1/clusters/cl1/services -X PUT -d
> '{"ServceInfo":{"credential_store_enabled":"true"},
> "RequestInfo":{"query":"ServiceInfo/service_name.in(HIVE,YARN)"}}'{quote}
> {quote}api/v1/clusters/testcluster/services/RANGER -X PUT -d '{"ServiceInfo"
> : {"credential_store_enabled":"true"}}'
> {quote}
> {quote}api/v1/clusters/testcluster/services?ServiceInfo/service_name=ZOOKEEPER
> -X PUT -d '{"ServiceInfo" : {"credential_store_enabled":"false"}}'{quote}
> *REST API to get Stack definition*
> {quote}
> curl -u admin:admin -H "X-Requested-By: ambari" -X GET
> http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services
> {quote}
> {quote}
> {
> "href" : "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/";,
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/YARN";,
> "StackServices" : {
> "service_name" : "YARN",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> },
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/ZOOKEEPER";,
> "StackServices" : {
> "service_name" : "ZOOKEEPER",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> }
> ]
> }
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18741) Not able to change the default port ambari server listens to
[
https://issues.apache.org/jira/browse/AMBARI-18741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630248#comment-15630248
]
Hadoop QA commented on AMBARI-18741:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836631/AMBARI-18741-Nov2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9101//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9101//console
This message is automatically generated.
> Not able to change the default port ambari server listens to
>
>
> Key: AMBARI-18741
> URL: https://issues.apache.org/jira/browse/AMBARI-18741
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
> Fix For: trunk
>
> Attachments: AMBARI-18741-Nov2.patch,
> AMBARI-18741-oct31-updated.patch, AMBARI-18741.patch
>
>
> After including client.api.port in ambari.properties, ambari-server still
> tries to connect to port 8080
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18768) Session invalidation for hive view
[ https://issues.apache.org/jira/browse/AMBARI-18768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630235#comment-15630235 ] Hudson commented on AMBARI-18768: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #245 (See [https://builds.apache.org/job/Ambari-branch-2.5/245/]) AMBARI-18768. Session invalidation for hive view. (Ashwin Rajeev via (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ca185fcd67d3bbaddaddafac9c6337099536090b]) * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/client/AsyncJobRunnerImpl.java * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/JdbcConnector.java > Session invalidation for hive view > -- > > Key: AMBARI-18768 > URL: https://issues.apache.org/jira/browse/AMBARI-18768 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.0 > > Attachments: AMBARI-18768.2.trunk.patch, AMBARI-18786.trunk.patch > > > In some cases , HS2 may restart/be restarted when the hive view is in use, > This usually manifests as a session expired/broken pipe exception > Change the error shown to a connection error and indicate that user must > retry the query -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18670) Hive view 1.5 does not refresh LDAP credentials for user
[ https://issues.apache.org/jira/browse/AMBARI-18670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630207#comment-15630207 ] Hudson commented on AMBARI-18670: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5914 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5914/]) AMBARI-18670. Hive view 1.0/1.5 does not refresh LDAP credentials for (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e9b251210d2e3fb4265413229bc2dcd793f5bc3e]) * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/client/AsyncJobRunnerImpl.java * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/app/services/ldap.js * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/resources/browser/HiveBrowserService.java * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/routes/splash.js * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/utils/constants.js * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/client/ConnectionConfig.java * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/resources/jobs/JobService.java * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/controllers/splash.js * (edit) contrib/views/hive-next/src/main/resources/view.xml * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/JdbcConnector.java * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/client/AsyncJobRunner.java * (add) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/resources/browser/ConnectionService.java * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/initializers/i18n.js * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/ConnectionFactory.java * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/controllers/index/history-query/logs.js * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/ConnectionSystem.java * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/internal/Connectable.java * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/internal/HiveConnectionWrapper.java > Hive view 1.5 does not refresh LDAP credentials for user > > > Key: AMBARI-18670 > URL: https://issues.apache.org/jira/browse/AMBARI-18670 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.5.0 > > Attachments: AMBARI-18670.trunk.2.patch, AMBARI-18670.trunk.patch > > Original Estimate: 120h > Remaining Estimate: 120h > > Hive view 1.5 has not support for LDAP authentication. > * Ask LDAP password during splash screen > * Ask LDAP password if password changed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18746) Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
[
https://issues.apache.org/jira/browse/AMBARI-18746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630172#comment-15630172
]
Hadoop QA commented on AMBARI-18746:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836130/AMBARI-18746.1.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9100//console
This message is automatically generated.
> Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
> ---
>
> Key: AMBARI-18746
> URL: https://issues.apache.org/jira/browse/AMBARI-18746
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
> Environment: Redhat 6.6, Sqoop 1.4.6+Hadoop 2.7.2
>Reporter: Ying Cao
>Assignee: Di Li
>Priority: Minor
> Fix For: 2.4.1
>
> Attachments: AMBARI-18746.1.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> The parameter hadoop_home is pointed to hbase-client in params_linux.py, and
> need to be updated.
> ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py
> # For stack versions supporting rolling upgrade
> if stack_version_formatted and
>
> hadoop_home = format("{stack_root}/current/hbase-client")
> ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18685) Add validations and attributes to support HOST_ORDERED upgrades
[
https://issues.apache.org/jira/browse/AMBARI-18685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-18685:
-
Attachment: AMBARI-18685.patch
> Add validations and attributes to support HOST_ORDERED upgrades
> ---
>
> Key: AMBARI-18685
> URL: https://issues.apache.org/jira/browse/AMBARI-18685
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18685.patch
>
>
> Augment the API of creating an Upgrade with the following:
> {noformat}
> POST api/v1/clusters/c1/upgrades
> {
> "Upgrade": {
> "repository_version": "2.5.0.0-965",
> "upgrade_type": "HOST_ORDERED", <-- new value other than
> ROLLING/NON_ROLLING
> "skip_failures": "false",
> "skip_prerequisite_checks": "false",
> "skip_manual_verification": "false",
> "host_order": [<-- new
>{
> "hosts": [ "c6401.ambari.apache.org, "c6402.ambari.apache.org",
> "c6403.ambari.apache.org" ],
> "service_checks": ["ZOOKEEPER"]
>},
>{
> "hosts": [ "c6404.ambari.apache.org, "c6405.ambari.apache.org"],
> "service_checks": ["ZOOKEEPER", "KAFKA"]
>}
> ]
> }
> }
> {noformat}
> {{skip_failures}} must be {{false}} when the upgrade_type is HOST_ORDERED
> {{skip_manual_verification}} must be omitted or {{false}} when upgrade_type
> is HOST_ORDERED
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18685) Add validations and attributes to support HOST_ORDERED upgrades
[
https://issues.apache.org/jira/browse/AMBARI-18685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-18685:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Add validations and attributes to support HOST_ORDERED upgrades
> ---
>
> Key: AMBARI-18685
> URL: https://issues.apache.org/jira/browse/AMBARI-18685
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18685.patch
>
>
> Augment the API of creating an Upgrade with the following:
> {noformat}
> POST api/v1/clusters/c1/upgrades
> {
> "Upgrade": {
> "repository_version": "2.5.0.0-965",
> "upgrade_type": "HOST_ORDERED", <-- new value other than
> ROLLING/NON_ROLLING
> "skip_failures": "false",
> "skip_prerequisite_checks": "false",
> "skip_manual_verification": "false",
> "host_order": [<-- new
>{
> "hosts": [ "c6401.ambari.apache.org, "c6402.ambari.apache.org",
> "c6403.ambari.apache.org" ],
> "service_checks": ["ZOOKEEPER"]
>},
>{
> "hosts": [ "c6404.ambari.apache.org, "c6405.ambari.apache.org"],
> "service_checks": ["ZOOKEEPER", "KAFKA"]
>}
> ]
> }
> }
> {noformat}
> {{skip_failures}} must be {{false}} when the upgrade_type is HOST_ORDERED
> {{skip_manual_verification}} must be omitted or {{false}} when upgrade_type
> is HOST_ORDERED
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18670) Hive view 1.5 does not refresh LDAP credentials for user
[ https://issues.apache.org/jira/browse/AMBARI-18670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630150#comment-15630150 ] Hudson commented on AMBARI-18670: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #244 (See [https://builds.apache.org/job/Ambari-branch-2.5/244/]) AMBARI-18670. Hive view 1.0/1.5 does not refresh LDAP credentials for (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=62992e5fd3430f1fb7cfcc763f095397205daf60]) * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/initializers/i18n.js * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/client/AsyncJobRunner.java * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/controllers/splash.js * (edit) contrib/views/hive-next/src/main/resources/view.xml * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/resources/jobs/JobService.java * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/controllers/index/history-query/logs.js * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/ConnectionSystem.java * (add) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/resources/browser/ConnectionService.java * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/ConnectionFactory.java * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/client/ConnectionConfig.java * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/utils/constants.js * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/client/AsyncJobRunnerImpl.java * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/app/services/ldap.js * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/JdbcConnector.java * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/internal/HiveConnectionWrapper.java * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/resources/browser/HiveBrowserService.java * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/routes/splash.js * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/internal/Connectable.java > Hive view 1.5 does not refresh LDAP credentials for user > > > Key: AMBARI-18670 > URL: https://issues.apache.org/jira/browse/AMBARI-18670 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.5.0 > > Attachments: AMBARI-18670.trunk.2.patch, AMBARI-18670.trunk.patch > > Original Estimate: 120h > Remaining Estimate: 120h > > Hive view 1.5 has not support for LDAP authentication. > * Ask LDAP password during splash screen > * Ask LDAP password if password changed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18685) Add validations and attributes to support HOST_ORDERED upgrades
[
https://issues.apache.org/jira/browse/AMBARI-18685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-18685:
-
Status: Patch Available (was: Open)
> Add validations and attributes to support HOST_ORDERED upgrades
> ---
>
> Key: AMBARI-18685
> URL: https://issues.apache.org/jira/browse/AMBARI-18685
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
>
> Augment the API of creating an Upgrade with the following:
> {noformat}
> POST api/v1/clusters/c1/upgrades
> {
> "Upgrade": {
> "repository_version": "2.5.0.0-965",
> "upgrade_type": "HOST_ORDERED", <-- new value other than
> ROLLING/NON_ROLLING
> "skip_failures": "false",
> "skip_prerequisite_checks": "false",
> "skip_manual_verification": "false",
> "host_order": [<-- new
>{
> "hosts": [ "c6401.ambari.apache.org, "c6402.ambari.apache.org",
> "c6403.ambari.apache.org" ],
> "service_checks": ["ZOOKEEPER"]
>},
>{
> "hosts": [ "c6404.ambari.apache.org, "c6405.ambari.apache.org"],
> "service_checks": ["ZOOKEEPER", "KAFKA"]
>}
> ]
> }
> }
> {noformat}
> {{skip_failures}} must be {{false}} when the upgrade_type is HOST_ORDERED
> {{skip_manual_verification}} must be omitted or {{false}} when upgrade_type
> is HOST_ORDERED
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18768) Session invalidation for hive view
[ https://issues.apache.org/jira/browse/AMBARI-18768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-18768: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2.5, branch-2.5 > Session invalidation for hive view > -- > > Key: AMBARI-18768 > URL: https://issues.apache.org/jira/browse/AMBARI-18768 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.0 > > Attachments: AMBARI-18768.2.trunk.patch, AMBARI-18786.trunk.patch > > > In some cases , HS2 may restart/be restarted when the hive view is in use, > This usually manifests as a session expired/broken pipe exception > Change the error shown to a connection error and indicate that user must > retry the query -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18670) Hive view 1.5 does not refresh LDAP credentials for user
[ https://issues.apache.org/jira/browse/AMBARI-18670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-18670: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2.5, branch-2.4 > Hive view 1.5 does not refresh LDAP credentials for user > > > Key: AMBARI-18670 > URL: https://issues.apache.org/jira/browse/AMBARI-18670 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.5.0 > > Attachments: AMBARI-18670.trunk.2.patch, AMBARI-18670.trunk.patch > > Original Estimate: 120h > Remaining Estimate: 120h > > Hive view 1.5 has not support for LDAP authentication. > * Ask LDAP password during splash screen > * Ask LDAP password if password changed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18768) Session invalidation for hive view
[ https://issues.apache.org/jira/browse/AMBARI-18768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-18768: --- Attachment: AMBARI-18768.2.trunk.patch > Session invalidation for hive view > -- > > Key: AMBARI-18768 > URL: https://issues.apache.org/jira/browse/AMBARI-18768 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.4.0 > > Attachments: AMBARI-18768.2.trunk.patch, AMBARI-18786.trunk.patch > > > In some cases , HS2 may restart/be restarted when the hive view is in use, > This usually manifests as a session expired/broken pipe exception > Change the error shown to a connection error and indicate that user must > retry the query -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-18746) Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
[
https://issues.apache.org/jira/browse/AMBARI-18746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Di Li reassigned AMBARI-18746:
--
Assignee: Di Li
> Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
> ---
>
> Key: AMBARI-18746
> URL: https://issues.apache.org/jira/browse/AMBARI-18746
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
> Environment: Redhat 6.6, Sqoop 1.4.6+Hadoop 2.7.2
>Reporter: Ying Cao
>Assignee: Di Li
>Priority: Minor
> Fix For: 2.4.1
>
> Attachments: AMBARI-18746.1.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> The parameter hadoop_home is pointed to hbase-client in params_linux.py, and
> need to be updated.
> ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py
> # For stack versions supporting rolling upgrade
> if stack_version_formatted and
>
> hadoop_home = format("{stack_root}/current/hbase-client")
> ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18746) Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
[
https://issues.apache.org/jira/browse/AMBARI-18746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Di Li updated AMBARI-18746:
---
Status: Patch Available (was: Reopened)
> Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
> ---
>
> Key: AMBARI-18746
> URL: https://issues.apache.org/jira/browse/AMBARI-18746
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
> Environment: Redhat 6.6, Sqoop 1.4.6+Hadoop 2.7.2
>Reporter: Ying Cao
>Priority: Minor
> Fix For: 2.4.1
>
> Attachments: AMBARI-18746.1.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> The parameter hadoop_home is pointed to hbase-client in params_linux.py, and
> need to be updated.
> ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py
> # For stack versions supporting rolling upgrade
> if stack_version_formatted and
>
> hadoop_home = format("{stack_root}/current/hbase-client")
> ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18741) Not able to change the default port ambari server listens to
[ https://issues.apache.org/jira/browse/AMBARI-18741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18741: -- Attachment: AMBARI-18741-Nov2.patch > Not able to change the default port ambari server listens to > > > Key: AMBARI-18741 > URL: https://issues.apache.org/jira/browse/AMBARI-18741 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-18741-Nov2.patch, > AMBARI-18741-oct31-updated.patch, AMBARI-18741.patch > > > After including client.api.port in ambari.properties, ambari-server still > tries to connect to port 8080 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18776) DB consistency check should inform user about warnings but not fail ambari-server start
[ https://issues.apache.org/jira/browse/AMBARI-18776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18776: --- Status: Patch Available (was: Open) > DB consistency check should inform user about warnings but not fail > ambari-server start > --- > > Key: AMBARI-18776 > URL: https://issues.apache.org/jira/browse/AMBARI-18776 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18776_trunk.patch > > > As of now we don't show any info about warnings in db consistency check for > user. I think we should print some information for user into command line. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18776) DB consistency check should inform user about warnings but not fail ambari-server start
[ https://issues.apache.org/jira/browse/AMBARI-18776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18776: --- Attachment: AMBARI-18776_trunk.patch > DB consistency check should inform user about warnings but not fail > ambari-server start > --- > > Key: AMBARI-18776 > URL: https://issues.apache.org/jira/browse/AMBARI-18776 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18776_trunk.patch > > > As of now we don't show any info about warnings in db consistency check for > user. I think we should print some information for user into command line. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18776) DB consistency check should inform user about warnings but not fail ambari-server start
Vitaly Brodetskyi created AMBARI-18776: -- Summary: DB consistency check should inform user about warnings but not fail ambari-server start Key: AMBARI-18776 URL: https://issues.apache.org/jira/browse/AMBARI-18776 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Vitaly Brodetskyi Assignee: Vitaly Brodetskyi Priority: Critical Fix For: 2.5.0 As of now we don't show any info about warnings in db consistency check for user. I think we should print some information for user into command line. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
