kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guozhang Wang (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KAFKA-5797) StoreChangelogReader should be resilient to broker-side metadata not available
Date Wed, 30 Aug 2017 15:44:00 GMT

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

Guozhang Wang resolved KAFKA-5797.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.0

Issue resolved by pull request 3748
[https://github.com/apache/kafka/pull/3748]

> StoreChangelogReader should be resilient to broker-side metadata not available
> ------------------------------------------------------------------------------
>
>                 Key: KAFKA-5797
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5797
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>            Reporter: Guozhang Wang
>            Assignee: Guozhang Wang
>             Fix For: 1.0.0
>
>
> In {{StoreChangelogReader#validatePartitionExists}}, if the metadata for the required
partition is not available, or a timeout exception is thrown, today the function would directly
throw the exception all the way up to user's exception handlers.
> Since we have now extracted the restoration out of the consumer callback, a better way
to handle this, is to only validate the partition during restoring, and if it does not exist
we can just proceed and retry in the next loop



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

Mime
View raw message