[
https://issues.apache.org/jira/browse/SAMZA-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13828293#comment-13828293
]
Chris Riccomini commented on SAMZA-87:
--------------------------------------
Talked with [~jkreps]. It sounds like you get:
NotLeaderForPartitionCode in cases where the topic/partition exists, but the
broker is not a leader for it.
UnknownTopicOrPartitionCode in cases where the topic doesn't exist.
So it sounds like we need to handle these guys, and either abdicate, or retry.
> BrokerProxy doesn't properly handle offset out of range exceptions
> ------------------------------------------------------------------
>
> Key: SAMZA-87
> URL: https://issues.apache.org/jira/browse/SAMZA-87
> Project: Samza
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Jakob Homan
> Assignee: Jakob Homan
> Priority: Critical
> Fix For: 0.7.0
>
> Attachments: SAMZA-87-2.patch, SAMZA-87.patch
>
>
> Currently BrokerProxy will throw an exception for offset out of range from
> Kafka but does not get a new offset, instead going into an infinite loop of
> sadness.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
