[jira] [Updated] (AMBARI-15492) Status commands fail randomly
[
https://issues.apache.org/jira/browse/AMBARI-15492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myroslav Papirkovskyy updated AMBARI-15492:
---
Attachment: AMBARI-15492.patch
> Status commands fail randomly
> -
>
> Key: AMBARI-15492
> URL: https://issues.apache.org/jira/browse/AMBARI-15492
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15492.patch
>
>
> We experience random failures of status commands sometimes.
> As we treat any status command failure as "stopped"("installed") result, this
> causes component (or even service if component is master) to appear as
> stopped until next status command fixes status (1 minute interval).
> This tends to be completely random and appear once in 6-8 hours on average.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15492) Status commands fail randomly
[
https://issues.apache.org/jira/browse/AMBARI-15492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myroslav Papirkovskyy updated AMBARI-15492:
---
Status: Open (was: Patch Available)
> Status commands fail randomly
> -
>
> Key: AMBARI-15492
> URL: https://issues.apache.org/jira/browse/AMBARI-15492
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15492.patch
>
>
> We experience random failures of status commands sometimes.
> As we treat any status command failure as "stopped"("installed") result, this
> causes component (or even service if component is master) to appear as
> stopped until next status command fixes status (1 minute interval).
> This tends to be completely random and appear once in 6-8 hours on average.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15492) Status commands fail randomly
[
https://issues.apache.org/jira/browse/AMBARI-15492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myroslav Papirkovskyy updated AMBARI-15492:
---
Attachment: (was: AMBARI-15492.patch)
> Status commands fail randomly
> -
>
> Key: AMBARI-15492
> URL: https://issues.apache.org/jira/browse/AMBARI-15492
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15492.patch
>
>
> We experience random failures of status commands sometimes.
> As we treat any status command failure as "stopped"("installed") result, this
> causes component (or even service if component is master) to appear as
> stopped until next status command fixes status (1 minute interval).
> This tends to be completely random and appear once in 6-8 hours on average.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15492) Status commands fail randomly
[
https://issues.apache.org/jira/browse/AMBARI-15492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myroslav Papirkovskyy updated AMBARI-15492:
---
Status: Patch Available (was: Open)
> Status commands fail randomly
> -
>
> Key: AMBARI-15492
> URL: https://issues.apache.org/jira/browse/AMBARI-15492
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15492.patch
>
>
> We experience random failures of status commands sometimes.
> As we treat any status command failure as "stopped"("installed") result, this
> causes component (or even service if component is master) to appear as
> stopped until next status command fixes status (1 minute interval).
> This tends to be completely random and appear once in 6-8 hours on average.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15492) Status commands fail randomly
[
https://issues.apache.org/jira/browse/AMBARI-15492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15204547#comment-15204547
]
Myroslav Papirkovskyy commented on AMBARI-15492:
Environment class was working incorrectly in case of concurrent usage.
We had other threads using it in same time with status commands (some alerts
for example).
Previously this class used stack-like storage which didn't expect change of
context (thread).
Fix is to use of thread local storage inside this class to avoid such issues.
Also patch adds logging of failures to make possible issues easier to detect in
future.
> Status commands fail randomly
> -
>
> Key: AMBARI-15492
> URL: https://issues.apache.org/jira/browse/AMBARI-15492
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15492.patch
>
>
> We experience random failures of status commands sometimes.
> As we treat any status command failure as "stopped"("installed") result, this
> causes component (or even service if component is master) to appear as
> stopped until next status command fixes status (1 minute interval).
> This tends to be completely random and appear once in 6-8 hours on average.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15492) Status commands fail randomly
[
https://issues.apache.org/jira/browse/AMBARI-15492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myroslav Papirkovskyy updated AMBARI-15492:
---
Status: Patch Available (was: Open)
> Status commands fail randomly
> -
>
> Key: AMBARI-15492
> URL: https://issues.apache.org/jira/browse/AMBARI-15492
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15492.patch
>
>
> We experience random failures of status commands sometimes.
> As we treat any status command failure as "stopped"("installed") result, this
> causes component (or even service if component is master) to appear as
> stopped until next status command fixes status (1 minute interval).
> This tends to be completely random and appear once in 6-8 hours on average.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15492) Status commands fail randomly
[
https://issues.apache.org/jira/browse/AMBARI-15492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myroslav Papirkovskyy updated AMBARI-15492:
---
Attachment: AMBARI-15492.patch
> Status commands fail randomly
> -
>
> Key: AMBARI-15492
> URL: https://issues.apache.org/jira/browse/AMBARI-15492
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15492.patch
>
>
> We experience random failures of status commands sometimes.
> As we treat any status command failure as "stopped"("installed") result, this
> causes component (or even service if component is master) to appear as
> stopped until next status command fixes status (1 minute interval).
> This tends to be completely random and appear once in 6-8 hours on average.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15492) Status commands fail randomly
[
https://issues.apache.org/jira/browse/AMBARI-15492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myroslav Papirkovskyy updated AMBARI-15492:
---
Summary: Status commands fail randomly (was: Services appear as stopped
for 1 minute randomly)
> Status commands fail randomly
> -
>
> Key: AMBARI-15492
> URL: https://issues.apache.org/jira/browse/AMBARI-15492
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.2.2
>
>
> We experience random failures of status commands sometimes.
> As we treat any status command failure as "stopped"("installed") result, this
> causes component (or even service if component is master) to appear as
> stopped until next status command fixes status (1 minute interval).
> This tends to be completely random and appear once in 6-8 hours on average.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-15492) Services appear as stopped for 1 minute randomly
Myroslav Papirkovskyy created AMBARI-15492:
--
Summary: Services appear as stopped for 1 minute randomly
Key: AMBARI-15492
URL: https://issues.apache.org/jira/browse/AMBARI-15492
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.2.2
Reporter: Myroslav Papirkovskyy
Assignee: Myroslav Papirkovskyy
Priority: Critical
Fix For: 2.2.2
We experience random failures of status commands sometimes.
As we treat any status command failure as "stopped"("installed") result, this
causes component (or even service if component is master) to appear as stopped
until next status command fixes status (1 minute interval).
This tends to be completely random and appear once in 6-8 hours on average.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-15400) Loading monitoring page is stuck after cluster deploy (java.lang.StackOverflowError)
Myroslav Papirkovskyy created AMBARI-15400:
--
Summary: Loading monitoring page is stuck after cluster deploy
(java.lang.StackOverflowError)
Key: AMBARI-15400
URL: https://issues.apache.org/jira/browse/AMBARI-15400
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.2.2
Reporter: Myroslav Papirkovskyy
Assignee: Myroslav Papirkovskyy
Priority: Blocker
Fix For: 2.2.2
Sometimes UI loading stuck because backend response with HTTP code 500.
StackOverflowError is present is server logs:
{code:title=ambari-server.log}
13 Mar 2016 04:47:18,462 WARN [qtp-ambari-client-22] ServletHandler:563 -
/api/v1/stacks/HDP/versions/2.4/services/HDFS
java.lang.StackOverflowError
at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
at com.rits.cloning.Cloner.cloneObject(Cloner.java:453)
at com.rits.cloning.Cloner.cloneInternal(Cloner.java:431)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15371) Increase the default http header size of the Ambari server to 64k
[ https://issues.apache.org/jira/browse/AMBARI-15371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyy updated AMBARI-15371: --- Resolution: Fixed Status: Resolved (was: Patch Available) Unit test failure is not related. Pushed to trunk and branch-2.2 > Increase the default http header size of the Ambari server to 64k > - > > Key: AMBARI-15371 > URL: https://issues.apache.org/jira/browse/AMBARI-15371 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Myroslav Papirkovskyy >Assignee: Myroslav Papirkovskyy >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15371.patch, AMBARI-15371_branch-2.2.patch > > > Increase the default http header size to 64k for Ambari server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15375) NPE while gathering JMX ports from configs
[
https://issues.apache.org/jira/browse/AMBARI-15375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myroslav Papirkovskyy updated AMBARI-15375:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to trunk and branch-2.2
> NPE while gathering JMX ports from configs
> --
>
> Key: AMBARI-15375
> URL: https://issues.apache.org/jira/browse/AMBARI-15375
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15375.patch, AMBARI-15375_branch-2.2.patch
>
>
> Sometimes getting JMX ports from configs throws NPE exception.
> {noformat}
> org.apache.ambari.server.controller.spi.SystemException: Caught exception
> getting JMX metrics : null
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider.rethrowSystemException(ThreadPoolEnabledPropertyProvider.java:245)
> at
> org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider.populateResources(ThreadPoolEnabledPropertyProvider.java:155)
> at
> org.apache.ambari.server.controller.internal.StackDefinedPropertyProvider.populateResources(StackDefinedPropertyProvider.java:200)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.populateResources(ClusterControllerImpl.java:146)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:406)
> at
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:216)
> at
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:68)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:106)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:75)
> at
> org.apache.ambari.server.api.services.HostComponentService.getHostComponent(HostComponentService.java:89)
> at sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> 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
>
[jira] [Created] (AMBARI-15375) NPE while gathering JMX ports from configs
Myroslav Papirkovskyy created AMBARI-15375:
--
Summary: NPE while gathering JMX ports from configs
Key: AMBARI-15375
URL: https://issues.apache.org/jira/browse/AMBARI-15375
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.2.2
Reporter: Myroslav Papirkovskyy
Assignee: Myroslav Papirkovskyy
Priority: Critical
Fix For: 2.2.2
Sometimes getting JMX ports from configs throws NPE exception.
{noformat}
org.apache.ambari.server.controller.spi.SystemException: Caught exception
getting JMX metrics : null
at
org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider.rethrowSystemException(ThreadPoolEnabledPropertyProvider.java:245)
at
org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider.populateResources(ThreadPoolEnabledPropertyProvider.java:155)
at
org.apache.ambari.server.controller.internal.StackDefinedPropertyProvider.populateResources(StackDefinedPropertyProvider.java:200)
at
org.apache.ambari.server.controller.internal.ClusterControllerImpl.populateResources(ClusterControllerImpl.java:146)
at
org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:406)
at
org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:216)
at
org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:68)
at
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:106)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:75)
at
org.apache.ambari.server.api.services.HostComponentService.getHostComponent(HostComponentService.java:89)
at sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
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
[jira] [Updated] (AMBARI-15371) Increase the default http header size of the Ambari server to 64k
[ https://issues.apache.org/jira/browse/AMBARI-15371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyy updated AMBARI-15371: --- Status: Open (was: Patch Available) > Increase the default http header size of the Ambari server to 64k > - > > Key: AMBARI-15371 > URL: https://issues.apache.org/jira/browse/AMBARI-15371 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Myroslav Papirkovskyy >Assignee: Myroslav Papirkovskyy >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15371.patch, AMBARI-15371_branch-2.2.patch > > > Increase the default http header size to 64k for Ambari server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15371) Increase the default http header size of the Ambari server to 64k
[ https://issues.apache.org/jira/browse/AMBARI-15371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyy updated AMBARI-15371: --- Status: Patch Available (was: Open) > Increase the default http header size of the Ambari server to 64k > - > > Key: AMBARI-15371 > URL: https://issues.apache.org/jira/browse/AMBARI-15371 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Myroslav Papirkovskyy >Assignee: Myroslav Papirkovskyy >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15371.patch, AMBARI-15371_branch-2.2.patch > > > Increase the default http header size to 64k for Ambari server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15371) Increase the default http header size of the Ambari server to 64k
[ https://issues.apache.org/jira/browse/AMBARI-15371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189451#comment-15189451 ] Myroslav Papirkovskyy commented on AMBARI-15371: Should be covered in integration tests. Unit tests not required. > Increase the default http header size of the Ambari server to 64k > - > > Key: AMBARI-15371 > URL: https://issues.apache.org/jira/browse/AMBARI-15371 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Myroslav Papirkovskyy >Assignee: Myroslav Papirkovskyy >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15371.patch, AMBARI-15371_branch-2.2.patch > > > Increase the default http header size to 64k for Ambari server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15371) Increase the default http header size of the Ambari server to 64k
[ https://issues.apache.org/jira/browse/AMBARI-15371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyy updated AMBARI-15371: --- Attachment: AMBARI-15371.patch AMBARI-15371_branch-2.2.patch > Increase the default http header size of the Ambari server to 64k > - > > Key: AMBARI-15371 > URL: https://issues.apache.org/jira/browse/AMBARI-15371 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Myroslav Papirkovskyy >Assignee: Myroslav Papirkovskyy >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15371.patch, AMBARI-15371_branch-2.2.patch > > > Increase the default http header size to 64k for Ambari server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
