Thinking Chen
@luocooong About the helm... I noticed that the 1.19 image was recently updated on docker hub. I’ve made some adaptations according to his helm and ran it in the test...
We often also encounter this problem when using postgres-operator. Our current solution is to write a watcher service, create a new headless service, then change the host in the pooler...
@dometec Thank you for your advice~ I think this design should make more sense, but it can be confusing for some beginners if some data is lost when using I'm...
@ozangunalp @dometec I still have frequent problems with buffer full in test and production environments. QOS is a producer property, and my usage scenario has always been consumer, so the...
Also, I found out that actually our current implementation of MQTT receives all messages and then filters them. I'm using the filtering feature to only process some of the topics,...
@dometec Here is the filter codes: https://github.com/smallrye/smallrye-reactive-messaging/blob/d94086362eb1ac28d986c13fb1fd404de4a160d9/smallrye-reactive-messaging-mqtt/src/main/java/io/smallrye/reactive/messaging/mqtt/MqttSource.java#L37-L44 https://github.com/smallrye/smallrye-reactive-messaging/blob/d94086362eb1ac28d986c13fb1fd404de4a160d9/smallrye-reactive-messaging-mqtt/src/main/java/io/smallrye/reactive/messaging/mqtt/MqttSource.java#L53-L56 Perhaps my original expression was wrong, I meant that the code within reactive-messaging is based on a regular filter to receive messages.
You need to add a cluster role binding to your redis service account. Like this: ```yaml kind: RoleBinding apiVersion: rbac.authorization.k8s.io/v1 metadata: name: {{ .Release.Name }}-redis-rolebinding namespace: {{ .Release.Namespace }} subjects:...
I also tried to change the pg directory permissions and rename it, and found that the permissions were still changed after restarting pod. Did a script or program force the...
@denisok The reason for killing pod was because I wanted to test if the pmm-server would work after a restart. I have solved this issue so far, the problem occurred...
@denisok The helm chart version is 1.2.1. Here is the pmm-client logs: ``` [36mINFO[0m[2023-04-21T17:37:15.410+08:00] Run setup: true Sidecar mode: true [36mcomponent[0m=entrypoint [36mINFO[0m[2023-04-21T17:37:15.410+08:00] Starting pmm-agent for liveness probe... [36mcomponent[0m=entrypoint [36mINFO[0m[2023-04-21T17:37:15.410+08:00] Starting...