...

JIRA: 

Subsequent KIPs: 

KIP-589 Add API to update Replica state in Controller

KIP-590: Redirect Zookeeper Mutation Protocols to The Controller

Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

...

This KIP expresses a vision of how we would like to evolve Kafka in the future.  We will create follow-on KIPs to hash out the concrete details of each change.

These KIPs will include:

• A KIP to implement Raft replication in Kafka.  This will specify the new replication protocol and the details of each new RPC.
• A KIP for allowing kafka-configs.sh to change topic configurations without using ZooKeeper.  It can already change broker configurations without Zookeeper, but it needs to be able to change all configurations without ZooKeeper.
• A KIP for adding APIs to replace direct ZK access by the brokers.
• A KIP describing the controller changes.  This will also specify how metadata is stored, and so on.

...

• KIP-455: Create an Administrative API for Replica Reassignment
• KIP-497: Add inter-broker API to alter ISR
• KIP-543: Expand ConfigCommand's non-ZK functionality
• KIP-555: Deprecate Direct Zookeeper access in Kafka Administrative Tools
• KIP-589 Add API to update Replica state in Controller
• KIP-590: Redirect Zookeeper Mutation Protocols to The Controller
• KIP-595: A Raft Protocol for the Metadata Quorum
• KIP-631: The Quorum-based Kafka Controller

References

The Raft consensus algorithm

...