Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-1793

Allow replacing ZooKeeper with a different distributed coordination system

    XMLWordPrintableJSON

Details

    • Wish
    • Status: Resolved
    • Minor
    • Resolution: Won't Do
    • 0.8.1.1
    • None
    • replication
    • None

    Description

      It would simplify our deployment infrastructure if we could reuse our current service discovery and distributed configuration system (Consul) instead of requiring a separate ZK installation.

      I looked through the code and it looks like ZK code (specifically zkClient), is scattered throughout the codebase.

      It would be nice if any distributed coordination code that used ZK was behind a single (or set of) API. It would then hopefully be straightforward to provide a replacement implementation for that API. The implementing class could be specified in the config.

      One potential benefit would be the ability to provide implementations for different versions of ZK.

      Is there any interest in having this feature available?

      Attachments

        Activity

          People

            nehanarkhede Neha Narkhede
            plorenz Paul Lorenz
            Votes:
            43 Vote for this issue
            Watchers:
            16 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: