|
|
|
|
|
|
by ryanbrush
4474 days ago
|
|
|
I believe the ability to configure this behavior is being tracked at the link below. It seems like it's a switch between consistency and availability. By default Kafka prefers availability, and the possible inconsistency results in data loss (because Kafka just discards some inconsistent data it can't resolve). But the JIRA linked below should make that behavior optional, so if a majority of machines fail the cluster will become unavailable rather than inconsistent. https://issues.apache.org/jira/browse/KAFKA-1028 |
|
|