Details
-
Enhancement
-
Resolution: Done
-
Major
-
fuse-7.8-patch-1
-
False
-
False
-
%
-
+
-
+
-
Automated
-
Undefined
-
https://github.com/jboss-fuse/fuse-console-openshift/pull/17, https://github.com/hawtio/hawtio-operator/pull/54, https://github.com/hawtio/hawtio-online/commit/5f145c8e34377b2e34e868d5d5a3378e3d12fb05, https://github.com/hawtio/hawtio-online/pull/86, https://github.com/jboss-fuse/fuse-console-operator-prod-operator-metadata/pull/20
Description
I am using 7.8.1 Fuse Console on OCP 4.X, the console only seems to display for containers with a smaller number of routes. anything above about 30 routes times out/fails to load. We has some pods that have 80/90 routes which don't load with the current setup.
The logs as below:
2021/06/23 20:41:31 [error] 25#0: *630 too big subrequest response while sending to client, client: 172.30.34.1, server: localhost, request: "POST /management/namespaces/esb-tsc/pods/https:sb-camel-app-12-8sk5q:8778/jolokia/?maxDepth=7&maxCollectionSize=5000&ignoreErrors=true&canonicalNaming=false HTTP/1.1", subrequest: "/proxy/https:172.30.11.84:8778/jolokia/", upstream: "https://172.30.11.84:8778/jolokia/", host: "fuse-console-test", referrer: "https://fuse-console-test/integration/?con=sb-camel-app-12-8sk5q"
We have to change the setting /opt/app-root/etc/nginx.d/nginx-gateway.conf on our largest pod
subrequest_output_buffer_size 60m;
and build our own image.
Pls provide an easy way to modify these properties.
# Performance tuning
subrequest_output_buffer_size 10m;
client_body_buffer_size 256k;
proxy_buffers 16 128k;
Attachments
Issue Links
- relates to
-
-
- Done
-
