[
https://issues.apache.org/jira/browse/KAFKA-5537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070553#comment-16070553
]
Michael Andre Pearce edited comment on KAFKA-5537 at 6/30/17 6:41 PM:
----------------------------------------------------------------------
RE the test, this is just simulating what we are finding in our more formal
tests and application behaviour to try show the issue.
What you suggest is what we were expecting that maybe we just need to increase
delays, but in this case we have set it to wait even longer 60 seconds even
(with as noted just only two consumers), and still nothing returns (e.g. we are
seeing no messages in our real deployed applications, when running on 0.11). To
me this does not seem right.
was (Author: michael.andre.pearce):
RE the test, this is just simulating what we are finding in our more formal
tests and application behaviour to try show the issue.
What you suggest is what we were expecting that maybe we just need to increase
delays, but in this case we have set it to wait even longer 60 seconds even
(with as noted just two consumers), and still nothing returns (e.g. we are
seeing no messages in our real deployed applications, when running on 0.11). To
me this does not seem right.
> Subscribe Earliest is not working as in 0.10.2.1
> ------------------------------------------------
>
> Key: KAFKA-5537
> URL: https://issues.apache.org/jira/browse/KAFKA-5537
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.11.0.0
> Reporter: Michael Andre Pearce
> Priority: Critical
> Attachments: KafkaSub.java, KafkaSubLatest.java
>
>
> We have seen issue with subscription where auto offset when set to earliest
> does not behave the same as in 0.10.2.1 release.
> We have managed to create a repeatable test for this, which passes when
> pointing to 0.10.2.1 broker.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
