Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stolon-proxy can not reconnect etcd #910

Open
taoasan opened this issue Jun 12, 2023 · 0 comments
Open

stolon-proxy can not reconnect etcd #910

taoasan opened this issue Jun 12, 2023 · 0 comments
Labels

Comments

@taoasan
Copy link

taoasan commented Jun 12, 2023

Dear Boss
In a three-node environment,all three stolon-proxy nodes cannot connect to stolon-keeper,and the error message is
not proxy to master address since aren't in the enabled proxies list {"address":"177,0,0,56:5432"}
master address {"address":"177,0,0,56:5432"}
there is continuously printed.

is is possible to design a strategy that reports an error after failing to eonnect etcd a certain number of times, instead of
diaplaying it as an info level log? in this way,the pod will be restarted and the service can continue to be used.
Compared to data consistency, availability may be more importtant. Alternatively, can we cache the write logs of a certain
time period after reporting an error, so that developers can recover them later?

thanks !

k8s+three node+3 keeper +3 proxy + 3 sentinel +etcd as backend

  • Stolon version: 4bb4107523c2db09fa11c1d96ddfe33bacf405c
@taoasan taoasan added the bug label Jun 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant