-
Whether the redis client will block the nginx event loop in implementation, or the read timeout is caused by lua's own coroutine scheduling, because I found that the redis server responds quickly, and…
-
### Gloo Edge Version
1.10.x
### Kubernetes Version
1.23.x
### Describe the bug
Having VirtualService point to upstream with empty `static.hosts` configuration causes the gloo pod to panic on ups…
-
# Problem
The service `nginx` expects 8 instances of `html5-frontend` for load-balancing in `/etc/nginx/conf.d/default.conf`:
```
upstream poolhtml5servers {
zone poolhtml5servers 32k;
le…
maxee updated
3 years ago
-
## Synopsis
`go-mysql-server` v0.16.0+ fails to build in a [Bazel](https://bazel.build/) build environment due to an issue with the dolthub flatbuffers fork. An updated flatbuffers release should f…
-
### Gloo Edge Version
1.11.x (latest stable)
### Kubernetes Version
_No response_
### Describe the bug
With `settings.consulDiscovery.useTlsTagging: true`, the generated upstream does not contain…
-
### Your question
mosn是不是upstream的数据buffer好了后才发送给downstream?或者说server sent event、渐进式jpeg这类的数据,我想客户端是实时展示网络数据,mosn代理之后客户端还能实时接受数据吗?
### Environment
- MOSN Version
### Logs
- Paste the logs…
-
Further errors with web servers, this is occurring frequently during normal operation.
```
2023/06/02 21:39:00 [error] 61225#61225: *40743 upstream timed out (110: Unknown error) while reading respons…
-
ngx_http_dyups_module 通过RESTAPI 可以修改upstream 中的server list
但是修改实际是重置整个upstream 中内容,若upstream 中有其他比如session sticky的参数,在修改后参数被丢失。请问是否提供接口只修改server list 中member,而不修改upstream 中其他设定参数
-
`
upstream server1 {
server 192.168.56.1:8080;
server 192.168.56.2:8080;
}
upstream server2 {
server 192.168.56.2:8080;
server 192.168.56.3:8080;
}
`
没太看懂代码,请问192.168.56.2:8080这个ip端口会…
solio updated
8 years ago
-
I'm not sure if this is an upstream issue or not (or my issue for that matter), but the server runs as v2024.02.3.0 no matter what. Poking around, I noticed this is being set in the Dockerfile, and ev…