Description
Bug report
- [X ] I confirm this is a bug with Supabase, not with my own application.
- [ X] I confirm I have searched the Docs, GitHub Discussions, and Discord.
Describe the bug
When I redeploy supavisor on k8, got multiple errors on logs (receive serveral times) :
09:39:11.732 region=local [error] [description: 'Unexpected peer, aborting', expected: :"supavisor@pooler-74f8465477-84db8", got: :"supavisor@pooler-56fc9986b5-n2bth"]
When I first déploy supavisor, all run fine !
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
- Deploy supavisor with kubectl
- All is working fine
- Redeploy supavisor
- See error
2024-08-27T09:39:11.734727477Z 09:39:11.732 region=local [error] GenServer #PID<0.3230.0> terminating
2024-08-27T09:39:11.734753412Z ** (stop) {:unexpected_peer, :"supavisor@pooler-56fc9986b5-n2bth", :"supavisor@pooler-74f8465477-84db8"}
2024-08-27T09:39:11.734770332Z Last message: {:tcp, #Port<0.89>, <<131, 104, 2, 100, 0, 5, 104, 101, 108, 108, 111, 100, 0, 33, 115, 117, 112, 97, 118, 105, 115, 111, 114, 64, 112, 111, 111, 108, 101, 114, 45, 53, 54, 102, 99, 57, 57, 56, 54, 98, 53, 45, 110, 50, 98, 116, 104>>}
2024-08-27T09:39:11.734864293Z 09:39:11.733 region=local [error] GenServer #PID<0.3231.0> terminating
2024-0
Expected behavior
Works as the first deploy
System information
- OS: kubernetes
Keep up the good work, you rulez !