You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Matthias J. Sax (JIRA)" <ji...@apache.org> on 2017/11/04 14:53:00 UTC

[jira] [Resolved] (KAFKA-6031) Expose standby replicas endpoints in StreamsMetadata

     [ https://issues.apache.org/jira/browse/KAFKA-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias J. Sax resolved KAFKA-6031.
------------------------------------
    Resolution: Duplicate

Closing this because title of KAFKA-6144 is more descriptive.

> Expose standby replicas endpoints in StreamsMetadata
> ----------------------------------------------------
>
>                 Key: KAFKA-6031
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6031
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Stanislav Chizhov
>            Priority: Major
>              Labels: needs-kip
>
> Currently reads for a key are served by single replica, which has 2 drawbacks:
> - if replica is down there is a down time in serving reads for keys it was responsible for until a standby replica takes over
> - in case of semantic partitioning some replicas might become hot and there is no easy way to scale the read load
> If standby replicas would have endpoints that are exposed in StreamsMetadata it would enable serving reads from several replicas, which would mitigate the above drawbacks. 
> Due to the lag between replicas reading from multiple replicas simultaneously would have weaker (eventual) consistency comparing to reads from single replica. This however should be acceptable tradeoff in many cases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)