---
title: "Discussion on \"Our service discovery caught its own failure and switched itself off\" | Hashnode"
description: "Discussion on \"Our service discovery caught its own failure and switched itself off\". A three-replica cluster kept disagreeing with itself. The cause was in our own code: the peer-discovery routine had a catch block that disabled discovery when multicast failed, and on managed Kubernetes multicast always fails. Here's why we deleted gossip entirely and elected a leader with a blob lease instead, and why the membership you can open in Storage Explorer beats the membership you have to infer."
url: "https://hashnode.com/posts/our-service-discovery-caught-its-own-failure-and-switched-itself-off/6a45baf76d520931001a1747"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Our service discovery caught its own failure and switched itself off](https://authagonal.hashnode.dev/our-service-discovery-caught-its-own-failure-and-switched-itself-off?utm_source=hashnode&utm_medium=feed)

A three-replica cluster kept disagreeing with itself. The cause was in our own code: the peer-discovery routine had a catch block that disabled discovery when multicast failed, and on managed Kubernetes multicast always fails. Here's why we deleted gossip entirely and elected a leader with a blob lease instead, and why the membership you can open in Storage Explorer beats the membership you have to infer.

Jul 2 · 5 min read · authagonal.hashnode.dev  
Read the article

-   [#authentication](https://hashnode.com/tag/authentication)
-   [#distributed-systems](https://hashnode.com/tag/distributed-systems)
-   [#clustering](https://hashnode.com/tag/clustering)
-   [#azure](https://hashnode.com/tag/azure)
-   [#k8s](https://hashnode.com/tag/k8s)

## Written by

[Sam Critchley](https://hashnode.com/@authagonal)

@authagonal

  
[View profile](https://hashnode.com/@authagonal)

The auth platform you migrate to.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
