Re: [VOTE] 0.8.2.0 Candidate 1

It works ok in gradle but fails if your using maven. taking a look at the patch you uploaded now. /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop

Re: [VOTE] 0.8.2.0 Candidate 1

There seems to be an issue with the pom file for kafka_2.11-0.8.2 jar. It references scala-library 2.11, which doesn't exist in maven central (2.11.1, etc do exist). This seems to be an issue in the 0.8.2 beta as well. I tried to reference kafka_2.11-0.8.2 beta in a project and the build failed bec

Re: [VOTE] 0.8.2.0 Candidate 1

Perhaps you can see if you can reproduce this issue and then file a jira. Thanks, Jun On Fri, Jan 16, 2015 at 4:39 PM, svante karlsson wrote: > Hmm, produce "msg/sec in rate" seems to be per broker and "produce msg/per > sec" should also be per broker and thus be related. The problem is that f

Re: [VOTE] 0.8.2.0 Candidate 1

Hmm, produce "msg/sec in rate" seems to be per broker and "produce msg/per sec" should also be per broker and thus be related. The problem is that for a time period the graphs indicated that 1) messages where only produced to one broker 2) messages where produces to two brokers. when I restarted b

Re: [VOTE] 0.8.2.0 Candidate 1

I did some quick tests and the mbean values look reasonable. On the producer side, produce msg/sec is actually for all brokers. Thanks, Jun On Fri, Jan 16, 2015 at 12:09 PM, svante karlsson wrote: > Disregard the previous message, it was send accidently.. > > Jun, > > I don't know if it was an

Re: [VOTE] 0.8.2.0 Candidate 1

Apache mailing list doesn't allow attachments. Could you file a jira and attach the graph and the description there? Thanks, Jun On Fri, Jan 16, 2015 at 12:09 PM, svante karlsson wrote: > Disregard the previous message, it was send accidently.. > > Jun, > > I don't know if it was an issue with

Re: [VOTE] 0.8.2.0 Candidate 1

Disregard the previous message, it was send accidently.. Jun, I don't know if it was an issue with graphite or the mbean and have not seen it since - and we have tried of several cases of failover. That said, I have the feeling that it was a kafka issue and I'm a bit suspicious about the new mbe

Re: [VOTE] 0.8.2.0 Candidate 1

Jun, I don't know if it was an issue with graphite or the mbean but I have not seen it since - and we have tried of several cases of failover and this problem has only been seen once. That said, I have the feeling that it was a kafka issue and I'm a bit suspicious about the new mbeans. I attach

Re: [VOTE] 0.8.2.0 Candidate 1

Svante, I tested this out locally and the mbeans for those metrics do show up on startup. Can you reproduce the issue reliably? Also, is what you saw an issue with the mbean itself or graphite? Thanks, Jun On Fri, Jan 16, 2015 at 4:38 AM, svante karlsson wrote: > I upgrade two small test clus

Re: [VOTE] 0.8.2.0 Candidate 1

I upgrade two small test cluster and I had two small issues but I'm, not clear yet as to if those were an issue due to us using ansible to configure and deploy the cluster. The first issue could be us doing something bad when distributing the update (I updated, not reinstalled) but it should be ea

Re: [VOTE] 0.8.2.0 Candidate 1

Would make sense to enable it after we have authorization feature and admins can control who can delete what. On Thu, Jan 15, 2015 at 6:32 PM, Jun Rao wrote: > Yes, I agree it's probably better not to enable "delete.topic.enable" by > default. > > Thanks, > > Jun > > On Thu, Jan 15, 2015 at 6:29

Re: [VOTE] 0.8.2.0 Candidate 1

Yes, I agree it's probably better not to enable "delete.topic.enable" by default. Thanks, Jun On Thu, Jan 15, 2015 at 6:29 PM, Joe Stein wrote: > I think that is a change of behavior that organizations may get burned on. > Right now there is no delete data feature. If an operations teams upgra

Re: [VOTE] 0.8.2.0 Candidate 1

I think that is a change of behavior that organizations may get burned on. Right now there is no delete data feature. If an operations teams upgrades to 0.8.2 and someone decides to delete a topic then there will be data loss. The organization may not have wanted that to happen. I would argue to no

Re: [VOTE] 0.8.2.0 Candidate 1

Also can we remove "delete.topic.enable" config property and enable topic deletion by default? On Jan 15, 2015 10:07 PM, "Jun Rao" wrote: > Thanks for reporting this. I will remove that option in RC2. > > Jun > > On Thu, Jan 15, 2015 at 5:21 AM, Jaikiran Pai > wrote: > > > I just downloaded the

Re: [VOTE] 0.8.2.0 Candidate 1

Thanks for reporting this. I will remove that option in RC2. Jun On Thu, Jan 15, 2015 at 5:21 AM, Jaikiran Pai wrote: > I just downloaded the Kafka binary and am trying this on my 32 bit JVM > (Java 7)? Trying to start Zookeeper or Kafka server keeps failing with > "Unrecognized VM option 'UseC

Re: [VOTE] 0.8.2.0 Candidate 1

Yeah, good call on removing it. -Jay On Thu, Jan 15, 2015 at 6:39 AM, scott@heroku wrote: > That opt has been the default for a long while now iirc, maybe it can be > removed? > > Sent from my iPhone > > > On Jan 15, 2015, at 5:21 AM, Jaikiran Pai > wrote: > > > > I just downloaded the Kafka b

Re: [VOTE] 0.8.2.0 Candidate 1

That opt has been the default for a long while now iirc, maybe it can be removed? Sent from my iPhone > On Jan 15, 2015, at 5:21 AM, Jaikiran Pai wrote: > > I just downloaded the Kafka binary and am trying this on my 32 bit JVM (Java > 7)? Trying to start Zookeeper or Kafka server keeps faili

Re: [VOTE] 0.8.2.0 Candidate 1

I just downloaded the Kafka binary and am trying this on my 32 bit JVM (Java 7)? Trying to start Zookeeper or Kafka server keeps failing with "Unrecognized VM option 'UseCompressedOops'": ./zookeeper-server-start.sh ../config/zookeeper.properties Unrecognized VM option 'UseCompressedOops' Error

Re: [VOTE] 0.8.2.0 Candidate 1

+ users mailing list. It would be great if people can test this out and report any blocker issues. Thanks, Jun On Tue, Jan 13, 2015 at 7:16 PM, Jun Rao wrote: > This is the first candidate for release of Apache Kafka 0.8.2.0. There > has been some changes since the 0.8.2 beta release, especial