No, sorry, it didn't take 90 seconds to connect to ZK (at least I hope not). I
had my consumer open for 90 secs in this case before shutting it down and
disposing of it—hence any races caused by fast startup/shutdown should not have
been relevant.
I build from source off of the 0.8 branch, so i
Hi al,
I'm working on a DC-DC setup with two Kafka 0.8Beta1 setups and want to mirror
the messages between two DC's (DC A and DC B) using MirrorMaker.
The idea should not be very difficult though I encounter some, for me,
unexplainable results and inconsistencies in the available documentation (
I am trying to write a junit test for working with an embedded Kafka 0.8
server where I send and receive messages just to verify my embedded server,
producer and consumer wrappers work. Order of operation in the junit looks
something like:
-Start zk. [own thread] (wait for init)
-Start Kafka [own
What's the revision of the 0.8 branch that you used? If that's older than
the beta1 release, I recommend that you upgrade.
Thanks,
Jun
On Tue, Jul 30, 2013 at 3:09 AM, Hargett, Phil <
phil.harg...@mirror-image.com> wrote:
> No, sorry, it didn't take 90 seconds to connect to ZK (at least I hope
Could you run kafka-list-topics to see whether the leader of those
partitions are distributed on both brokers?
Thanks,
Jun
On Mon, Jul 29, 2013 at 10:48 PM, Hanish Bansal <
hanish.bansal.agar...@gmail.com> wrote:
> Yes, Kafka data shows up in the log dir in kafka-2. We are having 2
> partition
Oh, we're building from source multiple times per week, either until 0.8 comes
out of beta or we ourselves slide towards production. :)
Depending on where the builds were done (Dev vs official), we have commits
76d3905 or b1891e7. Both are more recent than beta 1, I believe.
:)
On Jul 30, 201
Our mirror maker wiki is not up to date with 0.8. In 0.8, the producer only
needs meta.broker.list.
Thanks,
Jun
On Tue, Jul 30, 2013 at 5:23 AM, Roel van der Made wrote:
> Hi al,
>
> I'm working on a DC-DC setup with two Kafka 0.8Beta1 setups and want to
> mirror the messages between two DC'
Nope, that's on a pretty standard GNU/Linux Debian system (jessie/sid) running
a 3.9.8-1 kernel. But you were onto something. Removing the trailing slash is
my log.dir config value made it work.
I'm not sure why this would have an impact since the log directories seem to be
correctly parsed as
Hmmm...is there a reason that stopConnections in ConsumerFetcherManager does
not grab a lock before shutting down the leaderFinderThread?
I don't see what prevents startConnections/stopConnections from causing a race
in certain conditions and if called on separate threads.
Given there are no lo
One thing is that you need to make sure the consumer starts consuming from
the beginning of the topic, otherwise by default, it will start from the
latest message in the topic, from the time it starts up. Since the
consumer and producer are asynchronous, it's hard to assert that the
consumer is co
Hi,
I am running kafka-0.7 but when running producer got error
java.lang.NoSuchMethodError: com.yammer.metrics.core.TimerContext.stop()J.
So I want to downgrade it to metrics 2.2.0 jar, So I replaced 3.x jars with
2.2.0 jars then I am unable to build the jar file getting below errors
/kafka-0.
This is because we populate the key in
ReplicaManager.highWatermarkCheckpoints using the "dirs" config, but look
up the key using log.dir.getParent. So, if you have a trailing slash in the
config, they won't match. This seems a bug that we should fix. Could you
file a jira?
Thanks,
Jun
On Tue,
Hmm, that's a good theory. My understanding is that you have one thread
that first shuts down the consumer connector and then creates new streams
on the same connector. Is that right? If so, I don't think the race
condition can happen. When we shutdown the consumer connector, it waits
until the lea
Hmm, are you sure this is Kafka 0.7? Kafka 0.7 doesn't use yammer metrics
core. Only 0.8 does.
Thanks,
Jun
On Tue, Jul 30, 2013 at 2:20 PM, Nandigam, Sujitha
wrote:
> Hi,
>
> I am running kafka-0.7 but when running producer got error
> java.lang.NoSuchMethodError: com.yammer.metrics.core.Timer
14 matches
Mail list logo
