Hi, Everyone,
We identified a blocker issue related to Yammer jmx reporter (
https://issues.apache.org/jira/browse/KAFKA-1902). We are addressing this
issue right now. Once it's resolved, we will roll out a new RC for voting.
Thanks,
Jun
On Mon, Jan 26, 2015 at 5:14 PM, Otis Gospodnetic
Hi Kafka Team,
I just wanted to bring this to your attention regarding Java New Producer
limitation compare to old producer.
a) Partition Increasing is limited to configured memory allocation.
buffer.memory
batch.size
The maximum partition you could have before impacting (New Java Producers)
+1 (binding) Verified quick start and unit tests.
Thanks,
Jun
On Wed, Jan 21, 2015 at 8:28 AM, Jun Rao j...@confluent.io wrote:
This is the second candidate for release of Apache Kafka 0.8.2.0. There
has been some changes since the 0.8.2 beta release, especially in the new
java producer api
+1 (binding)
artifacts and quick start look good. I ran in some client code, minor edits
from 0-8.2-beta https://github.com/stealthly/scala-kafka/pull/26
On Mon, Jan 26, 2015 at 3:38 AM, Manikumar Reddy ku...@nmsworks.co.in
wrote:
+1 (Non-binding)
Verified source package, unit tests, release
Hi,
Don't use Graphite, so I don't know. Kyle, maybe you can share more info?
What do you mean by reported to Yammer for example? And when you say
Yammer/Graphite, are you trying to say that you are using the Graphite
Reporter? If so, can you try other Yammer Reporters and see if there is a
This is still preliminary, but it looks as if the change to metric names
for per-topic metrics (bytes/messages in/out) is preventing these metrics
from being reported to Yammer/Graphite. If this isn't intentional, it
should probably be addressed before release.
On Wed, Jan 21, 2015 at 9:28 AM,
Hmm, that's not the intention. The per-topic mbeans are definitely
registered by Yammer. So, not sure why it's not reported to Graphite.
Otis, Vladimir,
Do you guys know?
Thanks,
Jun
On Mon, Jan 26, 2015 at 4:08 PM, Kyle Banker kyleban...@gmail.com wrote:
This is still preliminary, but it
Kyle,
Also, which reporter are you using for Graphite?
Thanks,
Jun
On Mon, Jan 26, 2015 at 4:08 PM, Kyle Banker kyleban...@gmail.com wrote:
This is still preliminary, but it looks as if the change to metric names
for per-topic metrics (bytes/messages in/out) is preventing these metrics
+1 (Non-binding)
Verified source package, unit tests, release build, topic deletion,
compaction and random testing
On Mon, Jan 26, 2015 at 6:14 AM, Neha Narkhede n...@confluent.io wrote:
+1 (binding)
Verified keys, quick start, unit tests.
On Sat, Jan 24, 2015 at 4:26 PM, Joe Stein
Maybe. I think the StringSerialzer could look more like a typical type of
message. Instead of encoding being a property it would be more typically
just written in the bytes.
On Sat, Jan 24, 2015 at 12:12 AM, Jay Kreps jay.kr...@gmail.com wrote:
I don't think so--see if you buy my explanation.
But I think the flaw in trying to guess what kind of serializer they will
use is when we get it wrong. Basically let's say we guess String. Say 30%
of the time we will be right and we will save the two configuration lines.
70% of the time we will be wrong and the user gets a super cryptic
That makes sense, thanks!
On Sat, Jan 24, 2015 at 7:00 PM, Jay Kreps jay.kr...@gmail.com wrote:
But I think the flaw in trying to guess what kind of serializer they will
use is when we get it wrong. Basically let's say we guess String. Say 30%
of the time we will be right and we will save the
This is a reminder that the deadline for the vote is this Monday, Jan 26,
7pm PT.
Thanks,
Jun
On Wed, Jan 21, 2015 at 8:28 AM, Jun Rao j...@confluent.io wrote:
This is the second candidate for release of Apache Kafka 0.8.2.0. There
has been some changes since the 0.8.2 beta release,
I don't think so--see if you buy my explanation. We previously defaulted to
the byte array serializer and it was a source of unending frustration and
confusion. Since it wasn't a required config people just went along
plugging in whatever objects they had, and thinking that changing the
parametric
For the maven artifacts listed above, there doesn't seem to be any
distinction between rc1 or rc2, so is it assumed that this is release2
here?:
https://repository.apache.org/content/groups/staging/org/apache/kafka/kafka_2.11/0.8.2.0/
Thanks!
Jason
On Wed, Jan 21, 2015 at 8:28 AM, Jun Rao
That's right. What's in maven staging is always for the latest RC being
voted. The stuff in maven staging will be promoted to maven central once
the vote passes.
Thanks,
Jun
On Wed, Jan 21, 2015 at 10:35 AM, Jason Rosenberg j...@squareup.com wrote:
For the maven artifacts listed above, there
This is the second candidate for release of Apache Kafka 0.8.2.0. There has
been some changes since the 0.8.2 beta release, especially in the new java
producer api and jmx mbean names. It would be great if people can test this
out thoroughly.
Release Notes for the 0.8.2.0 release
17 matches
Mail list logo
