Thanks for the note, Owen ! Filed a ticket for Kafka's website -
https://issues.apache.org/jira/browse/INFRA-5577
-Neha
On Wed, Nov 28, 2012 at 4:43 PM, Owen O'Malley omal...@apache.org wrote:
You need to file an INFRA jira. For the list of infra tickets that we used
in Giraph, look at:
[
https://issues.apache.org/jira/browse/KAFKA-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13506119#comment-13506119
]
Neha Narkhede commented on KAFKA-622:
-
9. Sounds good.
14. That's a good suggestion but
[
https://issues.apache.org/jira/browse/KAFKA-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13506190#comment-13506190
]
David Arthur edited comment on KAFKA-637 at 11/29/12 3:48 AM:
--
I see someone filed a jira, we'll answer there
Neha Narkhede wrote on Wed, Nov 28, 2012 at 16:43:08 -0800:
Gavin,
Thanks for moving the repository. Any idea what needs to be done to
get the website moved ?
-Neha
On Wed, Nov 28, 2012 at 4:08 PM, Gavin McDonald ga...@16degrees.com.au
John Fung created KAFKA-640:
---
Summary: System Test Failures :
kafka.common.InvalidClientIdException in broker log4j messages
Key: KAFKA-640
URL: https://issues.apache.org/jira/browse/KAFKA-640
Project:
Yes, we are working on it. We will notify everyone once the git repo is ready.
Thanks,
Neha
On Thu, Nov 29, 2012 at 7:25 AM, David Arthur mum...@gmail.com wrote:
Has there ever been discussion of moving to Git?
-David
[
https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13506824#comment-13506824
]
Otis Gospodnetic commented on KAFKA-133:
There you have it:
zkclient 0.2:
[
https://issues.apache.org/jira/browse/KAFKA-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13506858#comment-13506858
]
Neha Narkhede commented on KAFKA-633:
-
That happens due to the test failure. If the
[
https://issues.apache.org/jira/browse/KAFKA-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-640:
Attachment: kafka-640.patch
This happened because ClientId.validate(clientId) in SimpleConsumer did
[
https://issues.apache.org/jira/browse/KAFKA-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy reassigned KAFKA-633:
Assignee: Joel Koshy
AdminTest.testShutdownBroker fails
--
[
https://issues.apache.org/jira/browse/KAFKA-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13506917#comment-13506917
]
Jay Kreps commented on KAFKA-633:
-
But that's a problem, no? Those test harnesses are
Okay here is a proposal to address the issues I raised.
1, 2. Correlation id. This is not strictly speaking needed, but it is maybe
useful for debugging to be able to trace a particular request from client
to server. So we will extend this across all the requests.
3. For metadata response I will
Is the 0.8 protocol pretty much frozen at this point? If so, I'd like to start
updating my python client.
Also, I'm guessing 0.8 will be backwards compatible with 0.7 (due to the API
versioning)
-David
On Nov 29, 2012, at 7:47 PM, Jay Kreps wrote:
Okay here is a proposal to address the
Not quite. I noticed a few bugs that I pointed out in the previous email. I
would like to correct these today before we officially freeze it. So maybe
give me through Monday? At that point it would be absolutely fantastic to
have someone try to work off the document rather than off our code, and
[
https://issues.apache.org/jira/browse/KAFKA-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede closed KAFKA-640.
---
System Test Failures : kafka.common.InvalidClientIdException in broker log4j
messages
Looks like the previous one got closed due to a Apache process issue.
Filed another one identical to Giraph's -
https://issues.apache.org/jira/browse/INFRA-5583
Thanks,
Neha
On Wed, Nov 28, 2012 at 5:19 PM, Neha Narkhede neha.narkh...@gmail.com wrote:
Thanks for the note, Owen ! Filed a ticket
[
https://issues.apache.org/jira/browse/KAFKA-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-598:
-
Attachment: KAFKA-598-v1.patch
I spent the better part of a day rebasing - serves me right for letting
Issue Subscription
Filter: outstanding kafka patches (55 issues)
The list of outstanding kafka patches
Subscriber: kafka-mailing-list
Key Summary
KAFKA-642 Protocol tweaks for 0.8
https://issues.apache.org/jira/browse/KAFKA-642
KAFKA-637 Separate log4j environment
[
https://issues.apache.org/jira/browse/KAFKA-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede closed KAFKA-608.
---
getTopicMetadata does not respect producer config settings
I've tried sending an email to:
kafka-dev-unsubscr...@incubator.apache.org
kafka-dev-unsubscr...@kafka.apache.org
No luck.
any ideas?
thanks,
/m
[
https://issues.apache.org/jira/browse/KAFKA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-597:
Attachment: KAFKA-597-v1.patch
This patch refactors the scheduler as described above except that I didn't
I signed up on some. cool.
We should maybe match these to JIRA components?
On Mon, Dec 3, 2012 at 2:42 PM, Jonathan Creasy jcre...@box.com wrote:
I signed up under command line tools since no one had. I'll work on getting
up to speed there.
Looking forward to working with you all!
On Dec
Yeah that is a good idea.
-Jay
On Tue, Dec 4, 2012 at 5:32 AM, Joe Stein crypt...@gmail.com wrote:
I signed up on some. cool.
We should maybe match these to JIRA components?
On Mon, Dec 3, 2012 at 2:42 PM, Jonathan Creasy jcre...@box.com wrote:
I signed up under command line tools
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
[
https://issues.apache.org/jira/browse/KAFKA-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13509943#comment-13509943
]
John Fung commented on KAFKA-645:
-
Attached kafka-645-v1.patch which is a simple patch to
[
https://issues.apache.org/jira/browse/KAFKA-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike reassigned KAFKA-646:
---
Assignee: Swapnil Ghike
Provide aggregate stats at the high level Producer and
[
https://issues.apache.org/jira/browse/KAFKA-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-532.
-
Multiple controllers can co-exist during soft failures
--
[
https://issues.apache.org/jira/browse/KAFKA-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-514.
-
Replication with Leader Failure Test: Log segment files checksum mismatch
[
https://issues.apache.org/jira/browse/KAFKA-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-496:
--
Fix Version/s: (was: 0.8)
0.8.1
Moving this to 0.8.1.
high level
[
https://issues.apache.org/jira/browse/KAFKA-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung closed KAFKA-444.
---
Simple message replication test with multiple partitions and log segments
[
https://issues.apache.org/jira/browse/KAFKA-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung closed KAFKA-446.
---
Message replication with failures and varied producer acks
[
https://issues.apache.org/jira/browse/KAFKA-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung resolved KAFKA-450.
-
Resolution: Fixed
testcase_0301 ~ testcase_0308 cover the test requirements of this JIRA. So mark
this
[
https://issues.apache.org/jira/browse/KAFKA-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13510663#comment-13510663
]
Jun Rao commented on KAFKA-608:
---
I guess that you are talking about ClientUtils. Currently,
Jae,
We modified the zkclient read API to expose the zookeeper Stat object.
This is because we need to do conditional writes in some places in
Kafka. Exposing the Stat object allows us to read the previous version
of the zookeeper value, and we can use that to write the new value if
the expected
[
https://issues.apache.org/jira/browse/KAFKA-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-595:
Labels: feature (was: feature features)
Description:
In 0.7 Kafka always appended messages to the
[
https://issues.apache.org/jira/browse/KAFKA-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13511489#comment-13511489
]
Jay Kreps commented on KAFKA-642:
-
60. This isn't an implict conversion. In java the method
[
https://issues.apache.org/jira/browse/KAFKA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-252:
Priority: Major (was: Critical)
Description:
The relevant discussion is here -
Jay Kreps created KAFKA-659:
---
Summary: Support request pipelining in the network server
Key: KAFKA-659
URL: https://issues.apache.org/jira/browse/KAFKA-659
Project: Kafka
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/KAFKA-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-560:
Labels: project (was: )
Garbage Collect obsolete topics
---
[
https://issues.apache.org/jira/browse/KAFKA-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-554:
Labels: project (was: )
Move all per-topic configuration into ZK and add to the CreateTopicCommand
[
https://issues.apache.org/jira/browse/KAFKA-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13511571#comment-13511571
]
Jay Kreps commented on KAFKA-642:
-
Ack, you're right.
Protocol tweaks for
[
https://issues.apache.org/jira/browse/KAFKA-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-330:
Labels: features project (was: features)
Add delete topic support
-
Good point - fixed.
On Wed, Dec 5, 2012 at 9:22 PM, Jay Kreps jay.kr...@gmail.com wrote:
Hey your wiki on mirror maker is very good. It doesn't actually say how to
run it, though, does it?
-Jay
[
https://issues.apache.org/jira/browse/KAFKA-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13512081#comment-13512081
]
Neha Narkhede commented on KAFKA-654:
-
The bug is inside
[
https://issues.apache.org/jira/browse/KAFKA-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-660:
Affects Version/s: (was: 0.8)
0.8.1
Change (topic, partition)
[
https://issues.apache.org/jira/browse/KAFKA-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-633:
-
Attachment: KAFKA-633-v1.patch
This is a timing issue that affects low-volume topics (and in this case an
[
https://issues.apache.org/jira/browse/KAFKA-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13526028#comment-13526028
]
Jun Rao commented on KAFKA-633:
---
Thanks for the patch. +1.
[
https://issues.apache.org/jira/browse/KAFKA-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy closed KAFKA-633.
Checked into 0.8. Will file separate jira to protect the ISR from re-expansion.
[
https://issues.apache.org/jira/browse/KAFKA-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy resolved KAFKA-633.
--
Resolution: Fixed
AdminTest.testShutdownBroker fails
--
[
https://issues.apache.org/jira/browse/KAFKA-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-642:
Attachment: KAFKA-642-remove-response-versions.patch
This patch removes the response version. There was a
[
https://issues.apache.org/jira/browse/KAFKA-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13526125#comment-13526125
]
Jay Kreps commented on KAFKA-642:
-
It also baselines all versions, including the message
[
https://issues.apache.org/jira/browse/KAFKA-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
antoine vianey updated KAFKA-581:
-
Attachment: zookeeper-server-stop.bat
kafka-server-stop.bat
Can you add this
[
https://issues.apache.org/jira/browse/KAFKA-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13526440#comment-13526440
]
antoine vianey edited comment on KAFKA-581 at 12/7/12 3:11 PM:
So I was testing my own code, and using the console consumer against my
seemingly-working-producer code. Since the last update, the console
consumer crashes. I am going to try to track it down in the debugger and
will come back with a patch if found.
John Fung created KAFKA-663:
---
Summary: Add deploy feature to System Test
Key: KAFKA-663
URL: https://issues.apache.org/jira/browse/KAFKA-663
Project: Kafka
Issue Type: Task
Reporter:
Neha Narkhede created KAFKA-664:
---
Summary: Kafka server threads die due to OOME during long running
test
Key: KAFKA-664
URL: https://issues.apache.org/jira/browse/KAFKA-664
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13526590#comment-13526590
]
Neha Narkhede commented on KAFKA-664:
-
Another observation - The server is probably
[
https://issues.apache.org/jira/browse/KAFKA-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung updated KAFKA-651:
Status: Patch Available (was: Open)
Create testcases on auto create topics
[
https://issues.apache.org/jira/browse/KAFKA-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung updated KAFKA-651:
Attachment: kafka-651-v1.patch
Uploaded kafka-651-v1.patch with 1 testcase to cover each functional group:
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13526719#comment-13526719
]
Neha Narkhede commented on KAFKA-664:
-
Heap dump is here -
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13526720#comment-13526720
]
Neha Narkhede commented on KAFKA-664:
-
I'm re-running the tests with that option now
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13526808#comment-13526808
]
Neha Narkhede commented on KAFKA-664:
-
The root cause seems to be that watchersForKey
[
https://issues.apache.org/jira/browse/KAFKA-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13526851#comment-13526851
]
Neha Narkhede commented on KAFKA-644:
-
+1. Thanks for the patch !
[
https://issues.apache.org/jira/browse/KAFKA-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede closed KAFKA-644.
---
System Test should run properly with mixed File System Pathname
[
https://issues.apache.org/jira/browse/KAFKA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-597:
Attachment: KAFKA-597-v4.patch
Patch v4.
- Rebased
- Makes use of thread factory
- Fixed broken scaladoc
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13526876#comment-13526876
]
Joel Koshy commented on KAFKA-664:
--
To clarify, the map itself shouldn't grow indefinitely
[
https://issues.apache.org/jira/browse/KAFKA-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-636:
Attachment: KAFKA-636-v1.patch
This patch implements asynchronous delete in the log.
To do this Log.scala
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13526883#comment-13526883
]
Joel Koshy commented on KAFKA-664:
--
Okay I'm slightly confused. Even on expiration the
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13526887#comment-13526887
]
Jay Kreps commented on KAFKA-664:
-
Another issue is that we are saving the full producer
[
https://issues.apache.org/jira/browse/KAFKA-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung updated KAFKA-644:
Attachment: kafka-644-v2.patch
Uploaded kafka-644-v2.patch which supports the property auto_create_topic
[
https://issues.apache.org/jira/browse/KAFKA-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-646:
Attachment: kafka-646-patch-num1-v1.patch
This patch has a bunch of refactoring changes and a
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-664:
Attachment: watchersForKey.png
kafka-664-draft.patch
The problem was ever
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13526973#comment-13526973
]
Neha Narkhede edited comment on KAFKA-664 at 12/8/12 1:56 AM:
--
[
https://issues.apache.org/jira/browse/KAFKA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-597:
Attachment: KAFKA-597-v5.patch
Thanks, new patch v5 addresses your comments:
- Improved javadoc
- This is
[
https://issues.apache.org/jira/browse/KAFKA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527168#comment-13527168
]
Jay Kreps commented on KAFKA-597:
-
Nice catch on the brace, will fix before check in.
With
You need to tell us HOW to create it,
either as a CMS site or using svnpubsub!
From: Jay Kreps jay.kr...@gmail.com
To: infrastruct...@apache.org infrastruct...@apache.org
Cc: dev@kafka.apache.org
Sent: Monday, December 10, 2012 12:30 PM
Subject: Re: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13528116#comment-13528116
]
Yang Ye commented on KAFKA-604:
---
Sure, I'll do that soon
Best,
---
[
https://issues.apache.org/jira/browse/KAFKA-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede resolved KAFKA-654.
-
Resolution: Fixed
Assignee: Neha Narkhede
Thanks for the review, committed patch v1 to 0.8
Cool, makes sense. Let's go with SVN and svnpubsub then. The site
subdirectory that we would published is
https://svn.apache.org/repos/asf/kafka/site
In the future if we switch to git we will just leave the site in svn and
continue to use that for site updates.
-Jay
On Mon, Dec 10, 2012 at
Hello fellow log maintainers, I have a patch and would love your feedback:
https://issues.apache.org/jira/browse/KAFKA-636
There will be a few more in this series as I finish off the log compaction
work. This patch is against trunk, though we may end up needing to backport
it if we hit
Our experience with CMS has been good, btw. Consider as an option. You
get a very simple mark-down based web site with browser editing if you like
it. Works very well.
On Mon, Dec 10, 2012 at 10:26 AM, Jay Kreps jay.kr...@gmail.com wrote:
Cool, makes sense. Let's go with SVN and svnpubsub
Issue Subscription
Filter: outstanding kafka patches (57 issues)
The list of outstanding kafka patches
Subscriber: kafka-mailing-list
Key Summary
KAFKA-664 Kafka server threads die due to OOME during long running test
https://issues.apache.org/jira/browse/KAFKA-664
[
https://issues.apache.org/jira/browse/KAFKA-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13528183#comment-13528183
]
Neha Narkhede commented on KAFKA-646:
-
Patch v2 looks good to me. Few minor questions -
[
https://issues.apache.org/jira/browse/KAFKA-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-646:
Attachment: kafka-646-patch-num1-v3.patch
Thanks for reviewing.
Patch v3:
1. Oh, that's because
[
https://issues.apache.org/jira/browse/KAFKA-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung updated KAFKA-647:
Attachment: kafka-647-v1.patch
Uploaded kafka-647-v1.patch for the following changes:
1. To let System
[
https://issues.apache.org/jira/browse/KAFKA-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung updated KAFKA-647:
Status: Patch Available (was: Open)
Provide a property in System Test for no. of topics and topics
[
https://issues.apache.org/jira/browse/KAFKA-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-646:
Attachment: kafka-646-patch-num1-v4.patch
Fixed a typo in FetchRequestAndResponseStats mbean
Jay Kreps created KAFKA-667:
---
Summary: Rename .highwatermark file
Key: KAFKA-667
URL: https://issues.apache.org/jira/browse/KAFKA-667
Project: Kafka
Issue Type: Improvement
Affects Versions:
https://issues.apache.org/jira/browse/KAFKA-667
Goal would just be forward compatibility with a more sane naming scheme...
-Jay
Prefer doing this now than later.
Thanks,
Neha
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
[
https://issues.apache.org/jira/browse/KAFKA-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13528432#comment-13528432
]
Jay Kreps commented on KAFKA-513:
-
It would be nice if we updated our log4j.properties as
[
https://issues.apache.org/jira/browse/KAFKA-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13528559#comment-13528559
]
Jun Rao commented on KAFKA-646:
---
Thanks for patch v4. Looks good overall. A few minor
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
[
https://issues.apache.org/jira/browse/KAFKA-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13528688#comment-13528688
]
Jun Rao commented on KAFKA-581:
---
Thanks for the patch. Committed the stop scripts to 0.8.
[
https://issues.apache.org/jira/browse/KAFKA-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13528690#comment-13528690
]
Jun Rao commented on KAFKA-374:
---
Should this be a post 0.8 item?
Move to
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13528707#comment-13528707
]
Jun Rao commented on KAFKA-664:
---
If the problem is due to an expired request not being
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13528723#comment-13528723
]
Jun Rao commented on KAFKA-664:
---
Got it. So the issue is that for low volume topics, the
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13528733#comment-13528733
]
Neha Narkhede edited comment on KAFKA-664 at 12/11/12 6:45 AM:
[
https://issues.apache.org/jira/browse/KAFKA-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13528932#comment-13528932
]
Jay Kreps commented on KAFKA-374:
-
Yes, this should go on trunk.
Move to
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13528948#comment-13528948
]
Jay Kreps commented on KAFKA-664:
-
This seems to iterate the whole list for every
1 - 100 of 133238 matches
Mail list logo
