Test failures are stable with the latest trunk, I am building Mac OSX with
Java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
The followings are log snippet from gradle build:
kafka.server.LogOffsetTest > t
Yes, our use is not an atomic commit coordinated between kafka and Hadoop, but
best effort. We err on the side of no duplicates and minimal loss, but the
loss is understood and acceptable, so far. How could that aggregate commit be
made atomic - XA? I wish there was a good high-available, p2p
Is this error stable? could you check out a clean trunk and retry unit
tests?
Guozhang
2014-02-14 22:56 GMT-08:00 Bae, Jae Hyeon :
>- LogOffsetTest .
>
>
> testEmptyLogsGetOffsets
>- LogOffsetTest .
>
>
> testGetOffsetsBeforeEarliestTime
>- LogOffsetTest .
>
>
> testGetOffsets
Hello David,
Did you create my-topic before creating the producer? I am not very
familiar with the kafka python producer client, but from the trace it seems
the producing is trying to first load the topic metadata from Kafka server
but cannot since the topic may not exist.
Guozhang
On Sat, Feb
+1 I think those are good. It is a little weird that changing the fetch
point is not batched but changing the commit point is, but I suppose there
is no helping that.
-Jay
On Sat, Feb 15, 2014 at 7:52 AM, Neha Narkhede wrote:
> Jay,
>
> That makes sense. position/seek deal with changing the con
Hi
I am getting the following errors
state-change.log:[2014-02-16 10:23:20,708] ERROR Controller 0 epoch 2
encountered error while changing partition [request_trace,18]'s state from
New to Online since LeaderAndIsr path already exists with value
{"leader":0,"leader_epoch":0,"isr":[0,1]} and contr
