Hey Tommy,
Yeah. That totally makes sense. Thanks for explaining it. :)
Thanks!
Navina
On Fri, Sep 16, 2016 at 12:12 PM, Tommy Becker wrote:
> Hey Navina,
>
> This was consistently reproducible both locally and in our integration
> test environment. We have auto.create.topics.enable on our bro
Hey Navina,
This was consistently reproducible both locally and in our integration test
environment. We have auto.create.topics.enable on our brokers (or more
accurately, we do not have it disabled; it's the default). I did not mean to
imply there is a problem with the logic of the change in S
Hi Tommy,
Yi and I discussed about it and initially, we thought it could have
something to do with the topic auto-creation setting on your Kafka server.
Is it enabled or disabled in your case?
I kind of suspect that the request timeout is insufficient. However, we do
have retries on Samza to fetc
Thanks for the response, and done.
https://issues.apache.org/jira/browse/SAMZA-1018
On 09/14/2016 01:14 PM, Yi Pan wrote:
Hi, Tommy,
Could you open a JIRA for this one? Also, could you include the Kafka
broker version in this test?
Thanks!
-Yi
On Wed, Sep 14, 2016 at 6:06 AM, Tommy Becker
Hi, Tommy,
Could you open a JIRA for this one? Also, could you include the Kafka
broker version in this test?
Thanks!
-Yi
On Wed, Sep 14, 2016 at 6:06 AM, Tommy Becker wrote:
> We are testing an upgrade to 0.10.1 from 0.9.1 and noticed a regression.
> When starting a stream job that consumes
