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

Support graceful Decommissioning of Broker

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.7
    • Fix Version/s: 0.8.0
    • Component/s: None
    • Labels:
      None

      Description

      There should be a graceful way of decommissioning the broker so that there is absolutely 0 data loss. Decommissioning is not necessarily related to replication (Kafka-50).

      There should be a way to get the broker out of the cluster only from the produce side. Consumers should be able to continue keep pulling data. When the administrator is sure that all data has been consumed by consumers, broker node can be removed permanently.

      Same would be useful for rolling upgrades without any message loss.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              sharadag Sharad Agarwal
            • Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: