Thanks for drafting this. Made some minor edits and added some comments.
Thanks,
Jun
On Thu, Nov 29, 2012 at 3:17 PM, Jay Kreps jay.kr...@gmail.com wrote:
I started trying to document the 0.8 protocol from the code and write a
guide to client implementation. This is meant to be a more
That sounds goods to me.
Thanks,
Jun
On Mon, Dec 10, 2012 at 3:05 PM, Jay Kreps jay.kr...@gmail.com wrote:
https://issues.apache.org/jira/browse/KAFKA-667
Goal would just be forward compatibility with a more sane naming scheme...
-Jay
Hi,
I can't seem to commit to Kafka svn since this morning. The commit is on a
fresh checkout. Do you know what the issue is?
jrao-mn:0.8_top_temp jrao$ svn commit --username junrao -m trivial fix to
increase offset commit interval to reduce ZK load
Sending
the tires before we cut over?
-Jay
On Wed, Dec 12, 2012 at 6:34 PM, Gavin McDonald ga...@16degrees.com.auwrote:
Issue is you are migrating to git.
** **
https://issues.apache.org/jira/browse/INFRA-5111
** **
** **
** **
*From:* Jun Rao [mailto:jun...@gmail.com]
*Sent
- origin/trunk
origin/consumer_redesign
origin/legacy_client_libraries
origin/trunk
On Thu, Dec 13, 2012 at 9:49 AM, Jun Rao jun...@gmail.com wrote:
https://git-wip-us.apache.org/repos/asf/kafka.git seems to be pointing
to
trunk. Do you know where is the 0.8 branch?
Thanks
Basically, we spread partitions among multiple brokers. If a message is
sent without a key, the producer picks a random partition to balance the
load. If a message has a key, the default partitioner hashes the key to one
of the partitions deterministically. Then, the load may not always be
All apis for 0.8 are documented in
https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol
However, there is no need for a producer to call the metadata api directly.
Our producer client does this for you automatically.
For your first question, if a new broker is added,
Posted a couple of comments on the wiki.
Thanks,
Jun
On Wed, Jan 16, 2013 at 8:18 PM, Jay Kreps jay.kr...@gmail.com wrote:
I added a first pass at a proposal for moving topic configuration into
zookeeper so that you would specify the config when you created the topic
and config could be
Using separate ZK paths for replicas assignment and configs seems better
since it allows each of them to be updated independently. Yes, we should
make a path of values stored in ZK for future extension. Could you file a
jira?
Thanks,
Jun
On Wed, Jan 16, 2013 at 7:47 PM, Jay Kreps
We also did some perf test on 0.8 using the following command. All configs
on the broker are the defaults.
bin/kafka-run-class.sh kafka.perf.ProducerPerformance --broker-list
localhost:9092 --initial-message-id 0 --messages 200 --topics topic_001
--request-num-acks -1 --batch-size 100
The change looks good. Would you mind attaching a patch to the jira? This
will indicate that you are ok with donating the code to Apache.
Thanks,
Jun
On Wed, Jan 30, 2013 at 1:21 PM, fsaintjacques g...@git.apache.org wrote:
GitHub user fsaintjacques opened a pull request:
Netz,
Thanks a lot. I just updated the site with those changes.
Jun
On Thu, Feb 7, 2013 at 10:17 PM, Nelz nelz9...@gmail.com wrote:
Hello,
I was recently doing some reading of your materials, and I found a
couple of typo's. In the spirit of Open Source, I thought I'd just jot
a quick note
David,
The benefit of the strategy used in Solr is that it simplifies client
routing. The downside is potential additional RPC overhead and a bit more
logic in the server. Technically, you can achieve what Solr does in the
client layer too. You can run a proxy that runs the java version of Kafka
If there is enough interest, we could do a 0.7.3 release.
However, there weren't that many fixes after 0.7.2 and 0.8 will probably be
out in Mar. I am wondering if it's worth doing another 0.7 release.
Thanks,
Jun
On Thu, Feb 14, 2013 at 11:31 AM, David Arthur mum...@gmail.com wrote:
I think
it see
suller adoption having the best posible .7.x in place give folks confidence
in the overall Kafka project.
Joe
On Fri, Feb 15, 2013 at 10:14 PM, Jun Rao jun...@gmail.com wrote:
If there is enough interest, we could do a 0.7.3 release.
However, there weren't that many fixes after
Did you upgrade your console consumer?
Thanks,
Jun
On Wed, Feb 27, 2013 at 3:40 AM, ben fleis b...@monkey.org wrote:
Sorry, I should have clarified something -- using the normal
ConsoleConsumer does *not* produce this error. So something in my
formatter, or in the logic of a custom
Jonathan,
My understanding is that channel is a local concept in Flume. So, are you
using a single local Kafka broker to build channel? Will it make more sense
to build a Kafka sink in Fume?
Thanks,
Jun
On Fri, Mar 1, 2013 at 10:56 PM, Jonathan Creasy j...@box.com wrote:
I started hacking on
Matan,
Thanks for picking this up. Yes, this is likely a post 0.8 item and should
go into trunk. Could you file a jira and post your initial design there for
discussion?
Jun
On Sat, Mar 2, 2013 at 12:53 PM, matan ma...@cloudaloe.org wrote:
Hi,
I am designing a patch on top the 0.8 code
Thanks, Daniel. It works now.
Jun
On Wed, Mar 6, 2013 at 10:02 AM, Daniel Shahaf d...@daniel.shahaf.namewrote:
Should work now
Jun Rao wrote on Wed, Mar 06, 2013 at 09:34:34 -0800:
Hi,
It seems that git push or pull hang on Apache Kafka git repo this
morning.
Could you help
All committers have to file the following agreement:
http://www.apache.org/licenses/icla.txt
Contributor submits patches to a jira. The patches will be reviewed and if
accepted, they will be checked in by a committer. If a contributor makes
significant contribution, he/she will be nominated as a
Probably we should add this as a subtask for the 0.8 beta release?
Thanks,
Jun
On Mon, Apr 1, 2013 at 8:46 AM, Neha Narkhede neha.narkh...@gmail.comwrote:
Cosmin,
The release-zip target worked for a short while but has been broken
for a long time now. Its purpose was to create a deployable
David,
The release related blockers are listed in
https://issues.apache.org/jira/browse/KAFKA-833. Do you think you can help
out on https://issues.apache.org/jira/browse/KAFKA-843?
Thanks,
Jun
On Thu, Apr 4, 2013 at 6:29 AM, David Arthur mum...@gmail.com wrote:
What issues are blocking the
Hi,
We started the work on deleting topics in 0.8 (kafka-330). We realized that
it touches quite a few critical components such as controller, replica
manager, and log, and it will take some time to stabilize this. In order
not to delay the 0.8 release too much, I propose that we push this
David,
We'd be open to a new build tool if SBT is deemed too hard to use. We can
revisit this post 0.8. Do you want to open a jira to track this?
Thanks,
Jun
On Fri, Apr 5, 2013 at 12:55 PM, David Arthur mum...@gmail.com wrote:
After getting frustrated with SBT, and being unable to figure
that differs,
instead of ~1500 lines). See my recent patches in KAFKA-717.
On 4/7/13 10:17 PM, Jun Rao jun...@gmail.com wrote:
Scott,
Yes, we are still using scala 2.8.0 at LinkedIn. We do plan to upgrade to
a
later version of scala at some point. However, this may take some time
since we
That should be fine. Thanks for doing this.
Jun
On Wed, Apr 10, 2013 at 1:36 PM, Anja Skrba an...@webhostinggeeks.comwrote:
Dear Sir,
I am writing to inquire regarding your web page about Kafka where I have
found a lot of useful information. My name is Anja and I'm currently
studying at
Thanks for the link. This paper provides an alternative, but similar
implementation to that in Zookeeper. The key difference seems to be that
the former supports membership reconfiguration.
Kafka replication is simpler because it separates the leader election part
from log replication. Such
Cosmin,
At this moment, 0.8 is only open for blockers. Everything else should go to
trunk. We plan to merge changes from 0.8 to trunk as we stabilize 0.8.
Thanks,
Jun
On Mon, Apr 15, 2013 at 7:31 AM, Cosmin Lehene cleh...@adobe.com wrote:
Hi,
The documentation on the website mentions
, where
we allow the logs to divert and don't reconcile perfectly.
Thanks,
Neha
On Sun, Apr 14, 2013 at 9:42 PM, Jun Rao jun...@gmail.com wrote:
Thanks for the link. This paper provides an alternative, but similar
implementation to that in Zookeeper. The key difference seems
In 0.7, we create a new socket after reconnect.interval messages. Messages
sent through different sockets may not arrive at the broker in order. The
reason to have reconnect.interval is for the producer to get a chance to
see the new broker added to a load balancer (if one uses a VIP to send
) I apologize, please let me know
the right way to contribute.
Cheers,
Andrea
On 04/24/2013 04:56 PM, Jun Rao wrote:
We have moved to git. Updated the wiki.
Thanks,
Jun
On Wed, Apr 24, 2013 at 6:41 AM, Andrea Gazzarini
andrea.gazzar...@gmail.com wrote:
Hi, looking at these pages
We are investigating a metadata related issue when there are a large number
of clients (1000+). This issue, if not resolved, may cause the whole
cluster to be unavailable. We are testing a fix. Once the issue is
resolved, we can start the release process.
Thanks,
Jun
Dave,
Currently, the broker expects each producer request to specify the exact
partition id (-1 is on longer valid). The mapping from a message to a
partition is done at the producer client. The producer can choose a random
partition (from the existing list of partitions) or deterministically
It will only send those brokers on which those topics are assigned.
Thanks,
Jun
On Wed, Jun 12, 2013 at 2:24 PM, Dave Peterson dspeter...@tagged.comwrote:
Suppose I send a metadata request for a single topic or some small
subset of the entire set of available topics. Will the response
+1. Verified unit tests and quick start.
Thanks,
Jun
On Thu, Jun 13, 2013 at 2:41 PM, Joe Stein crypt...@gmail.com wrote:
Hello, this is the first candidate release for Kafka 0.8.0 Beta 1
This release fixes the following issues
Hi, Everyone,
We will be having our user group meeting next Thursday evening at LinkedIn
in Mountain View. The following is the venue and the tentative agenda.
http://www.meetup.com/http-kafka-apache-org/events/125887332/
Hope to see many of you there!
Jun
Yes, I think that would be better.
Thanks,
Jun
On Mon, Jun 24, 2013 at 10:30 AM, Jay Kreps jay.kr...@gmail.com wrote:
I have noticed we don't do a good job of updating the FAQs. Would we
do better if I migrated it to the wiki so it was easier to edit?
-Jay
As for offset management, we have a summer intern starting this week and
our plan is to have the intern work on this.
Thanks,
Jun
On Tue, Jun 25, 2013 at 7:53 AM, Sam Meder sam.me...@jivesoftware.comwrote:
On Jun 24, 2013, at 9:41 AM, Jay Kreps jay.kr...@gmail.com wrote:
Hey Sam,
Sam,
Also, just want to say thank you for fixing kafka-938. That's an awesome
fix!
Jun
On Sun, Jun 23, 2013 at 11:01 PM, Sam Meder sam.me...@jivesoftware.comwrote:
Hey,
I now have roughly a day a week I can dedicate to working on Kafka, so I
am looking for issues in the 0.8.1 batch that
!
On Thu, Jun 20, 2013 at 8:25 AM, Jun Rao jun...@gmail.com wrote:
+1. Verified both unit tests and quick start.
Thanks,
Jun
On Wed, Jun 19, 2013 at 9:28 PM, Joe Stein crypt...@gmail.com
wrote:
This is the second release candidate vote for the Apache Kafka
0.8.0-beta1
My vote is that a patch can go into 0.8 if (1) it fixes a critical issue or
(2) the change is trivial and it makes the 0.8 experience better (e.g.,
improving log4j readability). kafka-946 may fall into (2).
Thanks,
Jun
On Tue, Jul 2, 2013 at 7:34 PM, Joe Stein crypt...@gmail.com wrote:
How
Sam,
Interested in taking a look at
KAFKA-959https://issues.apache.org/jira/browse/KAFKA-959
?
Thanks,
Jun
On Sun, Jun 23, 2013 at 11:01 PM, Sam Meder sam.me...@jivesoftware.comwrote:
Hey,
I now have roughly a day a week I can dedicate to working on Kafka, so I
am looking for issues in
/DefaultEventHandler.scala#L152
On Wed, Jul 3, 2013 at 2:18 PM, S Ahmed sahmed1...@gmail.com wrote:
Jun,
Looks like the update would happen around here?
On Wed, Jul 3, 2013 at 12:53 PM, Jun Rao jun...@gmail.com wrote:
Sam,
Interested in taking a look at
KAFKA-959https://issues.apache.org
Cosmin,
That's a good idea. In the past, for major new features, we tend to create
a wiki page to outline the design. The wiki pages can be organized better.
Is this what you are looking for?
Thanks,
Jun
On Wed, Jul 10, 2013 at 1:17 AM, Cosmin Lehene cleh...@adobe.com wrote:
I'm not sure if
No. If you point an 0.8 broker to a ZK with 0.7 layout, it will still hit
some weird exception, maybe not exactly the same as specified in the jira.
Thanks,
Jun
On Thu, Jul 11, 2013 at 3:15 PM, Jay Kreps jay.kr...@gmail.com wrote:
This JIRA has a patch but I thought we already did something
to get the recording there, nm.
-Jay
On Tue, Jul 2, 2013 at 12:47 PM, Jay Kreps jay.kr...@gmail.com wrote:
The recording for the user group talks is available here:
http://www.ustream.tv/linkedin-events
-Jay
On Wed, Jun 26, 2013 at 8:22 AM, Jun Rao jun...@gmail.com wrote:
Hi
David,
Thanks for sharing this.
Jun
On Thu, Jul 18, 2013 at 9:19 PM, David Arthur mum...@gmail.com wrote:
There is a Hadoop meetup happening in Durham next week. I'm presenting an
intro to Kafka.
I don't suspect there are any Kafka users in the area who are not already
members of TriHUG,
For 1, you can write a tool that uses our getOffsetBefore api and
SimpleConsumer. The offset returned is at the log segment boundary. So it's
not going to match the specified time precisely.
For 2, you can configure a topic to be rolled by timestamp
(log.roll.hours and topic.log.roll.hours). Then
+1 for 296
Thanks,
Jun
On Wed, Jul 31, 2013 at 1:34 PM, Jay Kreps jay.kr...@gmail.com wrote:
Okay folks we did a survey on the JIRA (KAFKA-982) and it was more or less
a tie between two logos:
https://issues.apache.org/jira/secure/attachment/12593545/296.png
)
Not sure is message.max.bytes only counts payload or whole message + any
headers, so it may be that it should be a bit larger even.
/Sam
On Aug 1, 2013, at 7:04 AM, Jun Rao jun...@gmail.com wrote:
server: replica.fetch.max.bytes should be = message.max.bytes.
Otherwise,
the follower will get
Sorry for the delay. Reviewed both.
Jun
On Sat, Aug 3, 2013 at 10:52 AM, Jay Kreps jay.kr...@gmail.com wrote:
This is a set of good housekeeping things for 0.8 open source release:
https://issues.apache.org/jira/browse/KAFKA-718
This is just a small set of trivial cleanups that are very
I think Joel answered a similar question in the user mailing list.
You can run the preferred replica leader election tool after the
restarts (
https://cwiki.apache.org/confluence/display/KAFKA/Replication+tools)
Thanks,
Jun
On Wed, Aug 14, 2013 at 6:22 AM, Kumar, Vaibhav
Could you create a jira in Kafka and attach a patch there? This is to make
sure that you grant permission to Apache.
Thanks,
Jun
On Tue, Aug 27, 2013 at 9:04 AM, vpernin g...@git.apache.org wrote:
GitHub user vpernin opened a pull request:
https://github.com/apache/kafka/pull/8
?
core/src/main/scala/kafka/utils/Annotations_2.9+.scala
https://reviews.apache.org/r/14013/#comment50707
How does this affect IDEs like Intellij? Are you able to build the project
in IDE with both version of threadsafe annotation?
- Jun Rao
On Sept. 8, 2013, 9:47 p.m., Christopher Freeman
This means the broker somehow closed the socket connection. Anything in the
broker log around the same time?
Thanks,
Jun
On Wed, Sep 11, 2013 at 6:07 PM, prashant amar amasin...@gmail.com wrote:
Also noticed another issue
Specified below is the current configuration
Topic1 - n Partitions
Hi, Everyone,
We have been stabilizing the 0.8 branch since the beta1 release. I think we
are getting close to an 0.8 final release. I made an initial list of the
remaining jiras that should be fixed in 0.8.
Joe,
Thanks for bringing this up. I want to clarify this a bit.
1. Currently, the producer side logic is that if the partitioning key is
not provided (i.e., it is null), the partitioner won't be called. We did
that because we want to select a random and available partition to send
messages so
wanted on this extra item (including the discussion) to 0.8.1 or greater?
I am always of the mind of reduce complexity unless that complexity is in
fact better than not having it.
On Sun, Sep 22, 2013 at 8:56 PM, Jun Rao jun...@gmail.com wrote:
It's reasonable to make the behavior of random
}
}
/***
Joe Stein
Founder, Principal Consultant
Big Data Open Source Security LLC
http://www.stealth.ly
Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop
/
On Fri, Sep 27, 2013 at 12:46 PM, Jun Rao jun...@gmail.com wrote:
Joe
,
right?
private class RandomMetaRefreshPartitioner[T](props: VerifiableProperties =
null) extends Partitioner[T] {
def partition(key: T, numPartitions: Int): Int = {
Utils.abs(key.hashCode) % numPartitions
}
}
On Fri, Sep 27, 2013 at 1:10 PM, Jun Rao jun...@gmail.com wrote
in DefaultEventHandler, and do that in partitioner.
One thing about this idea is any customized partitioner also has to
consider key == null case then.
Guozhang
On Fri, Sep 27, 2013 at 9:12 PM, Jun Rao jun...@gmail.com wrote:
We have the following code in DefaultEventHandler:
val partition
/browse/KAFKA-1068
Repository: kafka
Description
---
kafka-1068
Diffs
-
core/src/main/scala/kafka/controller/KafkaController.scala
aef41ad5f087817862dcbd9dfbb4674e49e21f91
Diff: https://reviews.apache.org/r/14399/diff/
Testing
---
Thanks,
Jun Rao
, 2013 at 12:14 PM, Jun Rao jun...@gmail.com wrote:
The main issue is that if we do that, when key is null, we can only
select
a random partition, but not a random and available partition, without
changing the partitioner api. Being able to do the latter is important in
my opinion
://www.stealth.ly
Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop
/
On Tue, Oct 1, 2013 at 11:26 AM, Jun Rao jun...@gmail.com wrote:
This proposal still doesn't address the following fundamental issue: The
random partitioner cannot
I will follow up on this.
Thanks,
Jun
On Wed, Oct 2, 2013 at 5:56 AM, David Arthur mum...@gmail.com wrote:
This morning I noticed that the topic in the #kafka IRC channel was
thanks., so I changed it to something more appropriate. This led me to
discover that #kafka has no OPs and is not
f333d29bf36bb7fdc66b3bf9af16e7ee19ad7e48
Diff: https://reviews.apache.org/r/14496/diff/
Testing
---
Thanks,
Jun Rao
/diff/
Testing
---
Thanks,
Jun Rao
%20Available%22)
Do people agree with this list?
Joe,
I don't have good understanding of KAFKA-1018. Do you think this needs to
be fixed in 0.8 final?
Thanks,
Jun
On Fri, Sep 13, 2013 at 9:18 AM, Jun Rao jun...@gmail.com wrote:
Hi, Everyone,
We have been stabilizing the 0.8 branch since
/browse/KAFKA-1069
Repository: kafka
Description
---
kafka-1069
Diffs
-
core/src/main/scala/kafka/cluster/Partition.scala
a9bb3c8c450f99d8e110ae6709c5fe1fe09a8f77
Diff: https://reviews.apache.org/r/14534/diff/
Testing
---
Thanks,
Jun Rao
/browse/KAFKA-954
Repository: kafka
Description
---
kafka-954
Diffs
-
README.md 9879427d4103354c7c3872c0b6caf454c1204a76
Diff: https://reviews.apache.org/r/14538/diff/
Testing
---
Thanks,
Jun Rao
KAFKA-1008 has been checked into the 0.8 branch and needs to be manually
double-committed to trunk. To avoid merging problems, I suggest that for
all future changes in the 0.8 branch, we double commit them to trunk. Any
objections?
Thanks,
Jun
On Mon, Oct 7, 2013 at 5:33 PM, Jun Rao jun
://reviews.apache.org/r/14554/#comment52173
Ditto for the comment above.
- Jun Rao
On Oct. 9, 2013, 6:48 a.m., Sriram Subramanian wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14554
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14571/#review26865
---
Ship it!
Do we want to address issue #2 in the patch too?
- Jun
logic in zkclient.
Assuming there is already a unit test in zkclient itself, is there any value in
including this unit test in Kafka?
- Jun Rao
On Oct. 10, 2013, 10:14 p.m., Anatoly Fayngelerin wrote:
---
This is an automatically
/tools/GetOffsetShell.scala
https://reviews.apache.org/r/14638/#comment52623
Should we name this option partitions?
- Jun Rao
On Oct. 14, 2013, 10:50 p.m., Neha Narkhede wrote:
---
This is an automatically generated e-mail
The value of the state path for a partition in ZK can be updated by both
the controller (for choosing the new leader and potentially shrinking Isr)
and the leader replica (for expanding/shrinking Isr). After the controller
modified the state path, we don't want the old leader to modify Isr
/browse/KAFKA-1090
Repository: kafka
Description
---
kafka-1090
Diffs
-
core/src/test/scala/unit/kafka/network/SocketServerTest.scala
94b5a2a36b2b82377576c2479a91e6799ae2e326
Diff: https://reviews.apache.org/r/14675/diff/
Testing
---
Thanks,
Jun Rao
/browse/KAFKA-1091
Repository: kafka
Description
---
kafka-1091
Diffs
-
core/src/main/scala/kafka/server/KafkaApis.scala
338d1cc6533fd219941f2afb9bc0ea122b368bbe
Diff: https://reviews.apache.org/r/14676/diff/
Testing
---
Thanks,
Jun Rao
94b5a2a36b2b82377576c2479a91e6799ae2e326
Diff: https://reviews.apache.org/r/14675/diff/
Testing
---
Thanks,
Jun Rao
the importance of the ordering of the steps, i.e.,
removing fetchers, truncate log(and checkpoint flushing offset) and adding
fetchers?
- Jun Rao
On Oct. 18, 2013, 2:15 a.m., Guozhang Wang wrote:
---
This is an automatically generated
one.
https://issues.apache.org/jira/browse/KAFKA-1008
-Jay
On Wed, Oct 9, 2013 at 8:56 AM, Jun Rao jun...@gmail.com wrote:
KAFKA-1008 has been checked into the 0.8 branch and needs to be
manually
double-committed to trunk. To avoid merging problems, I suggest that
for
all
with a filter (actually a relatively large number of
topics, some of which are newly created over time). I'm still not
sure
whether the new version is solving this issue (since it was a rare
transient thing anyway).
Thanks,
Jason
On Sat, Oct 19, 2013 at 2:03 AM, Jun Rao jun
is no longer accurate
after a broker restart.
Also, this patch should probably be done in trunk, instead of 0.8 since it
doesn't seem to be a blocker.
- Jun Rao
On Oct. 19, 2013, 10:34 p.m., Swapnil Ghike wrote:
---
This is an automatically
Hi, Everyone,
At this moment, we have only one remaining jira (KAFKA-1097) that we plan
to fix in 0.8. After that, we can cut the final 0.8 release.
Thanks,
Jun
On Mon, Oct 7, 2013 at 5:33 PM, Jun Rao jun...@gmail.com wrote:
Hi, Everyone,
I made another pass of the remaining jiras that we
expecting any exceptions here? If so, what about the error code in
the response?
- Jun Rao
On Oct. 21, 2013, 8:35 p.m., Guozhang Wang wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14730
() and makeFollower(). In the former, we force all replicas to
be created. In the latter, we just need to make sure the local replica is
created. In Partition.updateLeaderHWAndMaybeExpandIsr(), we can then use
getReplica(), instead of getOrCreateReplica().
- Jun Rao
On Oct. 23, 2013, 4:34 a.m., Neha
At this moment, we have resolved all jiras that we intend to fix in 0.8.0
final.
Joe,
Would you like to drive the 0.8.0 final release again?
Thanks,
Jun
On Mon, Oct 21, 2013 at 8:53 PM, Jun Rao jun...@gmail.com wrote:
Hi, Everyone,
At this moment, we have only one remaining jira (KAFKA
/RequestChannel.scala
https://reviews.apache.org/r/14898/#comment53644
We probably should rename this to RequestQueueTimeMs.
- Jun Rao
On Oct. 27, 2013, 1:45 a.m., Guozhang Wang wrote:
---
This is an automatically generated e-mail
/server/ReplicaManager.scala
https://reviews.apache.org/r/14730/#comment53744
catched == caught
core/src/main/scala/kafka/server/ReplicaManager.scala
https://reviews.apache.org/r/14730/#comment53748
Ditto as above.
- Jun Rao
On Oct. 28, 2013, 10:13 p.m., Guozhang Wang wrote
/controller/KafkaController.scala
https://reviews.apache.org/r/14865/#comment54014
Should we throw an exception here?
- Jun Rao
On Oct. 29, 2013, 5:49 p.m., Neha Narkhede wrote:
---
This is an automatically generated e-mail. To reply
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14865/#review28020
---
Ship it!
- Jun Rao
On Nov. 1, 2013, 4:55 p.m., Neha Narkhede
Thanks for preparing the release. Is the binary release compiled with java
7? Got the following error using a java 6 runtime.
bin/kafka-console-consumer.sh --zookeeper localhost:2181 --topic test
--from-beginning
Exception in thread main java.lang.UnsupportedClassVersionError:
/browse/KAFKA-1117
Repository: kafka
Description
---
kafka-1117
Diffs
-
core/src/main/scala/kafka/tools/ReplicaVerificationTool.scala PRE-CREATION
Diff: https://reviews.apache.org/r/15201/diff/
Testing
---
Thanks,
Jun Rao
+1
Thanks,
Jun
On Fri, Nov 8, 2013 at 12:56 PM, Joe Stein joe.st...@stealth.ly wrote:
This is the third candidate for release of Apache Kafka 0.8.0. This
release candidate artifacts changed in regards to
https://issues.apache.org/jira/browse/KAFKA-1126 along with updating the
release
/ReplicaVerificationTool.scala PRE-CREATION
Diff: https://reviews.apache.org/r/15201/diff/
Testing
---
Thanks,
Jun Rao
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15201/#review28186
---
On Nov. 11, 2013, 4:44 p.m., Jun Rao wrote
-log4j.properties 79240490149835656e2a013a9702c5aa41c104f1
core/src/main/scala/kafka/api/OffsetResponse.scala
08dc3cd3d166efba6b2b43f6e148f636b175affe
core/src/main/scala/kafka/tools/ReplicaVerificationTool.scala PRE-CREATION
Diff: https://reviews.apache.org/r/15201/diff/
Testing
---
Thanks,
Jun
wrote:
core/src/main/scala/kafka/tools/ReplicaVerificationTool.scala, line 385
https://reviews.apache.org/r/15201/diff/3/?file=382691#file382691line385
typo
changed.
On Nov. 13, 2013, 7:43 a.m., Jun Rao wrote:
Another caveat seems to be that the tool cannot handle changes in 1
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15201/#review28744
---
On Nov. 12, 2013, 4:34 p.m., Jun Rao wrote
/src/main/scala/kafka/api/OffsetResponse.scala
08dc3cd3d166efba6b2b43f6e148f636b175affe
core/src/main/scala/kafka/tools/ReplicaVerificationTool.scala PRE-CREATION
Diff: https://reviews.apache.org/r/15201/diff/
Testing
---
Thanks,
Jun Rao
1 - 100 of 5140 matches
Mail list logo
