RE: A kafka web monitor

for a kafka web console I've been using this one and it worked well for mejust make sure to install the right version of Play framework (in ReadMe.md) https://github.com/claudemamo/kafka-web-console > Date: Fri, 27 Mar 2015 15:28:09 -0400 > Subject: Re: A kafka web monitor > From: yuheng.du.h..

Re: A kafka web monitor

Hi Wan, I tried to install this DCMonitor, but when I try to clone the project, but it gives me "Permission denied, the remote end hung up unexpectedly". Can you provide any suggestions to this issue? Thanks. best, Yuheng On Mon, Mar 23, 2015 at 8:54 AM, Wan Wei wrote: > We have make a simple

Re: 2 kafka cluster sharing same ZK Ensemble.

Well, I'm using 1 ZK cluster with 3 Kafka clusters. Chroot works perfectly. On Fri, Mar 27, 2015 at 10:20 PM Rendy Bambang Junior < rendy.b.jun...@gmail.com> wrote: > Based on documentation, as long as you define different folder zookeeper > chroot at broker configuration, it should be OK. Cmiiw.

Re: 2 kafka cluster sharing same ZK Ensemble.

Based on documentation, as long as you define different folder zookeeper chroot at broker configuration, it should be OK. Cmiiw. Disclaimer: myself never tried this scheme. Rendy On Mar 28, 2015 2:14 AM, "Shrikant Patel" wrote: > Can 2 separate kafka cluster share same ZK Ensemble?? > If yes, h

2 kafka cluster sharing same ZK Ensemble.

Can 2 separate kafka cluster share same ZK Ensemble?? If yes, how does ZK deal with that 2 clusters having brokers with same id. Thanks, Shri This message and its contents (to include attachments) are the property of National Health Systems, Inc. and may contain

Re: Kafka 8.2.1 Offset fetch Request

In your case you are trying to issue an offsetRequest and not a fetchOffsetRequest. I know this is little confusing. Let me point you to a scala patch which has a client for doing fetch offset and commit offset. I am going to rewrite that in java. Here is the Kafka ticket : https://issues.apache

Re: Kafka 8.2.1 Offset fetch Request

Other thing is if you are using SimpleConsumer, it is up to your app to do the offsetManagement. The ZK based offsets or Kafka based offsets will work if you are using the HighLevel Consumer. Thanks, Mayuresh On Fri, Mar 27, 2015 at 9:17 AM, Mayuresh Gharat wrote: > Hi Madhukar, > > I am going

Re: Kafka 8.2.1 Offset fetch Request

Hi Madhukar, I am going through your code now. Let me see what I can find. Where were you storing your offsets before? Was it always Zookeeper or was it Kafka? If it was Zookeeper, the correct way to migrate from zookeeper to kafka based offsets is this : 1) Config Change : - offsets.storag

Re: Kafka Sync Producer threads(ack=0) are blocked

Hi ankit, I think you could find out the stacktrace of the lock "*0x000602358ee8" *that blocks the producer. Thanks, Manu On Fri, Mar 27, 2015 at 3:11 PM ankit tyagi wrote: > any insight would be useful. > > On Tue, Mar 24, 2015 at 11:06 AM, ankit tyagi > wrote: > >> Hi All, >> >> Currentl

Re: Dropping support for Scala 2.9.x

+1. But can we also look at this from the deployment base point view and find out how many production deployments are still using 2.9? If there is not any, dropping it is really an easy decision. Thanks Sent from my iPhone > On Mar 27, 2015, at 8:21 AM, Ismael Juma wrote: > > Hi all, > > The K

Re: Dropping support for Scala 2.9.x

+1 I was on a project that ended up not using kafka - and this was one reason: there are many other third party libraries that do not even have 2.9 versions so the interdependencies did not work. 2015-03-27 7:34 GMT-07:00 Stevo Slavić : > +1 for dropping 2.9.x support > > Kind regards, > Stevo S

Re: Dropping support for Scala 2.9.x

+1 for dropping 2.9.x support Kind regards, Stevo Slavic. On Fri, Mar 27, 2015 at 3:20 PM, Ismael Juma wrote: > Hi all, > > The Kafka build currently includes support for Scala 2.9, which means that > it cannot take advantage of features introduced in Scala 2.10 or depend on > libraries that re

Dropping support for Scala 2.9.x

Hi all, The Kafka build currently includes support for Scala 2.9, which means that it cannot take advantage of features introduced in Scala 2.10 or depend on libraries that require it. This restricts the solutions available while trying to solve existing issues. I was browsing JIRA looking for ar

Re: New Java Producer Client handling unreachable Kafka

Hi Samuel, you can use *metadata.fetch.timeout.ms *property to reduce the blocking time while cluster is unreachable. The default value of this property is 1min. *waitOnMetadata*() is blocking call which blocks current thread waiting for the metadata fetch to

Re: Kafka Sync Producer threads(ack=0) are blocked

any insight would be useful. On Tue, Mar 24, 2015 at 11:06 AM, ankit tyagi wrote: > Hi All, > > Currently we are using kafka_2.8.0-0.8.0-beta1 in our production system. I > am using sync producer with ack=0 to send the events to broker. > > but I am seeing most of my producer threads are block