[
https://issues.apache.org/jira/browse/SAMZA-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Homan updated SAMZA-87:
-----------------------------
Attachment: SAMZA-87-4.patch
Updated patch.
* Refactors refreshBrokers s.t. when there is an exception while adding one, we
don't try to re-add all of them. Also makes it a bit more efficient and, I
think, easier to understand
* Fixes an issue in GetOffset when the lastcheckpointed value is the same as
the high watermark, ie no more messages have been written to that topic since
checkpointing, and there was no head to pick from.
> 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-3.patch, SAMZA-87-4.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)
