[
https://issues.apache.org/jira/browse/KAFKA-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13632656#comment-13632656
]
Cosmin Lehene commented on KAFKA-843:
-
[~junrao] Is the last patch ok?
[
https://issues.apache.org/jira/browse/KAFKA-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13632925#comment-13632925
]
Jay Kreps commented on KAFKA-823:
-
Comments:
- I think moving Log.append to return a tuple
[
https://issues.apache.org/jira/browse/KAFKA-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13633003#comment-13633003
]
Jun Rao commented on KAFKA-843:
---
Thanks for the addendum. It looks fine. I found another mino
More notable differences from Kafka as far as log replication protocol
is concerned -
- Raft considers log entries as committed as soon as it is
acknowledged by a majority of the servers in a cluster. Compare this
to Kafka where we have the notion of "in-sync followers" that are
required to ack ev
Scott Clasen created KAFKA-864:
--
Summary: bin/kafka-gen-reassignment.sh
Key: KAFKA-864
URL: https://issues.apache.org/jira/browse/KAFKA-864
Project: Kafka
Issue Type: Improvement
Affects Ver
[
https://issues.apache.org/jira/browse/KAFKA-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-823:
--
Attachment: kafka-823_v4.patch
Thanks for the review. The suggestions make sense. Attach patch v4 that
addresse
On the last point, in general, Kafka logs are identical among replicas. The
only case that they may not be identical is when an unclean leader election
happens, i.e., a leader has to be elected from a replica not in in-sync
replica set). Unclean leader election should be rare since this requires
mu
