[
https://issues.apache.org/jira/browse/KAFKA-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081989#comment-15081989
]
xingang edited comment on KAFKA-3062 at 1/4/16 11:45 PM:
---------------------------------------------------------
"Likely version based" means:
1) it's Ok for such None-Latency sensitive consumers to fetch data slower than
from the leaders. or even less of them
2) the consistency of replicas could be version-based synced, thus, the
consumers can get the "None-dup, None-loss" eventually, No requirement to be
consistent for a real-time
It will be so GOOD in this way, No more extra storage required but get
History/Realtime consuming separated
was (Author: itismewxg):
"Likely version based" means:
1) it's Ok for such None-Latency consumers to fetch data slower than from the
leaders. or even less of them
2) the consistency of replicas could be version-based synced, thus, the
consumers can get the "None-dup, None-loss" eventually, No requirement to be
consistent for a real-time
It will be so GOOD in this way, No more extra storage required but get
History/Realtime consuming separated
> Read from kafka replication to get data likely Version based
> ------------------------------------------------------------
>
> Key: KAFKA-3062
> URL: https://issues.apache.org/jira/browse/KAFKA-3062
> Project: Kafka
> Issue Type: Improvement
> Reporter: xingang
>
> Since Kafka require all the reading happens in the leader for the consistency.
> If there could be possible for the reading can happens in replication, thus,
> for data have a number of consumers, for the consumers Not latency-sensitive
> But Data-Loss sensitive can fetch its data from replication, in this case, it
> will pollute the Pagecache for other consumers which are latency-sensitive
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
