Hi Philip.
Noted and really appreciate for your inputs. There is no problem to
patch the code.
I just didn't want to be coupled with forked version of the storm-kafka
spout. Since my patch will not be in the main branch of the code.
Thanks
Oleg.
On Tue, Nov 19, 2013 at 9:44 PM, Philip O'Toole
The Storm mailing list is probably a better place for this thread. If I
understand the issue, it is not a ZK issue, nor a Kafka config issue. We run
multiple topos draining the same topics all the time.
In any event, you just need to patch the Kafka Spout code to catch this
exception, and ask
Hi Philip.
It looks like this is our case:
https://github.com/nathanmarz/storm-contrib/pull/15
It is interesting that the issue is still open ( after more then 1 year) so
I am curious how people able to work on production without ability to
deploy another topology.
Can community please share i
Don't get scared, this if perfectly normal and easily fixed. :-) The second
topology attempted to fetch messages from an offset in Kafka that does not
exists. This could happen due to Kafka retention policies (messages
deleted) or a bug in your code. Your code needs to catch this exception,
and the
>
> Thanks gurus. :)
>
> Chris
>
> - Original Message -
> From: "Christopher Alexander"
> To: users@kafka.apache.org
> Sent: Thursday, March 14, 2013 11:22:27 AM
> Subject: Re: kafka.common.OffsetOutOfRangeException
>
> OK, I re-reviewed the Kafka design doc
ild a trouble-shooting
solution set for an eventual production release.
Thanks gurus. :)
Chris
- Original Message -
From: "Christopher Alexander"
To: users@kafka.apache.org
Sent: Thursday, March 14, 2013 11:22:27 AM
Subject: Re: kafka.common.OffsetOutOfRangeException
OK, I
ffect another app that
is also using ZK.
2. In Kafka by wiping the mytopic-0 file?
Thanks,
Chris
- Original Message -
From: "Christopher Alexander"
To: users@kafka.apache.org
Sent: Thursday, March 14, 2013 11:02:57 AM
Subject: Re: kafka.common.OffsetOutOfRangeException
Thanks Jun
es
> > vi filename
>
> This reveals binary data. No offset visible.
>
> Are these the locations for finding the current/recent offsets? Thanks.
>
>
> ----- Original Message -
> From: "Philip O'Toole"
> To: users@kafka.apache.org
> Sent: Wednesday, Ma
e
>
> This reveals binary data. No offset visible.
>
> Are these the locations for finding the current/recent offsets? Thanks.
>
>
> - Original Message -
> From: "Philip O'Toole"
> To: users@kafka.apache.org
> Sent: Wednesday, March 13, 2013 5:04:01
isible.
>
> Are these the locations for finding the current/recent offsets? Thanks.
>
>
> - Original Message -
> From: "Philip O'Toole"
> To: users@kafka.apache.org
> Sent: Wednesday, March 13, 2013 5:04:01 PM
> Subject: Re: kafka.common.OffsetOutOfRangeExc
ocations for finding the current/recent offsets? Thanks.
- Original Message -
From: "Philip O'Toole"
To: users@kafka.apache.org
Sent: Wednesday, March 13, 2013 5:04:01 PM
Subject: Re: kafka.common.OffsetOutOfRangeException
Is offset 562949953452239, partition 0, actually av
Is offset 562949953452239, partition 0, actually available on the
Kafka broker? Have you checked?
Philip
On Wed, Mar 13, 2013 at 1:53 PM, Christopher Alexander
wrote:
> Hello All,
>
> I am using Node-Kafka to connect to Kafka 0.7.2. Things were working fine but
> we are experiencing repeated ex
12 matches
Mail list logo
