typesense-kubernetes icon indicating copy to clipboard operation
typesense-kubernetes copied to clipboard

Make cluster auto-recover

Open Hades32 opened this issue 2 years ago • 2 comments

With these changes (and the update to v0.25) this setup should finally reliably work.

  • The reset-peers flag is needed to recover from pod IP changes
  • read/write-lag flags are made explicit as, depending on cluster topology, folks will want different values here
  • a readiness probe fixes consumers hitting dead nodes and causing even more issues
  • the publishNotReadyAddresses setting ensures that pod IPs are still available for clustering

Hades32 avatar Sep 21 '23 06:09 Hades32

Thanks, I also had to set

          args:
            - --peering-address
            - $(POD_IP)
          env:
            - name: POD_IP
              valueFrom:
                fieldRef:
                  fieldPath: status.podIP

wille avatar Nov 01 '23 12:11 wille

Also update the readme if approved, the config works for me on Google Cloud.

IT-Guy007 avatar Feb 23 '24 06:02 IT-Guy007