[
https://issues.apache.org/jira/browse/KAFKA-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552759#comment-13552759
]
Maxime Brugidou commented on KAFKA-691:
---
So I wait for your feedback first, but I gue
[
https://issues.apache.org/jira/browse/KAFKA-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552781#comment-13552781
]
Maxime Brugidou commented on KAFKA-693:
---
I looked up the code in details and I am stu
[
https://issues.apache.org/jira/browse/KAFKA-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxime Brugidou updated KAFKA-701:
--
Attachment: KAFKA-701.patch
> ConsoleProducer does not exit correctly and fix some config pr
Maxime Brugidou created KAFKA-701:
-
Summary: ConsoleProducer does not exit correctly and fix some
config properties following KAFKA-648
Key: KAFKA-701
URL: https://issues.apache.org/jira/browse/KAFKA-701
[
https://issues.apache.org/jira/browse/KAFKA-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxime Brugidou updated KAFKA-701:
--
Status: Patch Available (was: Open)
> ConsoleProducer does not exit correctly and fix some
[
https://issues.apache.org/jira/browse/KAFKA-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552854#comment-13552854
]
Jun Rao commented on KAFKA-693:
---
That's a good point. I overlooked this. Your understanding i
[
https://issues.apache.org/jira/browse/KAFKA-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552866#comment-13552866
]
John Fung commented on KAFKA-697:
-
Tested kafka-697.patch and it fixes the exception. Ran a
[
https://issues.apache.org/jira/browse/KAFKA-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-701:
--
Resolution: Fixed
Fix Version/s: 0.8
Assignee: Maxime Brugidou
Status: Resolved (was:
[
https://issues.apache.org/jira/browse/KAFKA-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-698:
Attachment: KAFKA-698-v1.patch
Attached is a hacky but small patch that should fix this.
The proper fix is
in kafka 0.8, is it possible for a consumer to send a request to the broker
to
delete some topics? If yes, is it possible to provide some sample code
snippet to do it?
I would highly appreciate it.
Thanks in advance!
[
https://issues.apache.org/jira/browse/KAFKA-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552951#comment-13552951
]
Maxime Brugidou commented on KAFKA-693:
---
Looks good, It should work but I still have
Joel Koshy created KAFKA-702:
Summary: Livelock between request handler/processor threads
Key: KAFKA-702
URL: https://issues.apache.org/jira/browse/KAFKA-702
Project: Kafka
Issue Type: Bug
Af
Issue Subscription
Filter: outstanding kafka patches (58 issues)
The list of outstanding kafka patches
Subscriber: kafka-mailing-list
Key Summary
KAFKA-699 Disallow clients to set replicaId in FetchRequest
https://issues.apache.org/jira/browse/KAFKA-699
KAFKA-698 br
[
https://issues.apache.org/jira/browse/KAFKA-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553023#comment-13553023
]
Jun Rao commented on KAFKA-698:
---
+1 on the patch.
> broker may expose uncomm
[
https://issues.apache.org/jira/browse/KAFKA-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriram Subramanian updated KAFKA-703:
-
Assignee: (was: Joel Koshy)
> A fetch request in Fetch Purgatory can double count
Sriram Subramanian created KAFKA-703:
Summary: A fetch request in Fetch Purgatory can double count the
bytes from the same delayed produce request
Key: KAFKA-703
URL: https://issues.apache.org/jira/browse/KAFK
[
https://issues.apache.org/jira/browse/KAFKA-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-702:
Component/s: network
Labels: bugs (was: )
Description:
We have seen this a couple of t
I need to use some of the newly added functions of kafka 0.8. However, in
our system,
we support scala 2.9.2. I build my code together kafka 0.8 and scala 2.9.2
and I got alot
of runtime issues, one of them is:
Exception in thread "main" java.lang.NoClassDefFoundError:
scala/Tuple2$mcLL$sp
at kafka
Jane,
In 0.8, topics can be deleted only via an admin command. The JIRA for this
feature is still open - https://issues.apache.org/jira/browse/KAFKA-330
Thanks,
Neha
On Mon, Jan 14, 2013 at 10:19 AM, Jane Wang wrote:
> in kafka 0.8, is it possible for a consumer to send a request to the broke
I tried to grep getMetadata from kafka 0.8. However, I failed to find it.
does the api belong to a particular of kafka 0.8?
Does this getMetadata an api belong to consumer?
On Fri, Jan 11, 2013 at 9:04 PM, Jun Rao wrote:
> getMetadata
[
https://issues.apache.org/jira/browse/KAFKA-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553136#comment-13553136
]
Jun Rao commented on KAFKA-693:
---
Another quick thought on this. Instead of using Option for o
There is one on the SyncProducer and another on the SimpleConsumer, both
available through java apis -
send(request: kafka.javaapi.TopicMetadataRequest):
kafka.javaapi.TopicMetadataResponse
Thanks,
Neha
On Mon, Jan 14, 2013 at 1:25 PM, Jane Wang wrote:
> I tried to grep getMetadata from kafka
[
https://issues.apache.org/jira/browse/KAFKA-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps reassigned KAFKA-702:
---
Assignee: Jay Kreps
> Deadlock between request handler/processor threads
> ---
I am still confused:
(1) What I observed is that not only the first msg got wrong partition
number, but also
the second message.
(2) If kafka uses the first msg to get the correct msg. Does it mean that
if we use the
customized partitioner, we cannot get the right partition for this message?
[
https://issues.apache.org/jira/browse/KAFKA-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung updated KAFKA-688:
Attachment: kafka-688-v2.patch
Uploaded kafka-688-v2.patch to revert the change of log.file.size =>
log.seg
[
https://issues.apache.org/jira/browse/KAFKA-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriram Subramanian reassigned KAFKA-696:
Assignee: Sriram Subramanian (was: Neha Narkhede)
> Fix toString() API for all
[
https://issues.apache.org/jira/browse/KAFKA-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriram Subramanian reassigned KAFKA-700:
Assignee: Sriram Subramanian
> log client ip when we log each request on the bro
[
https://issues.apache.org/jira/browse/KAFKA-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-688:
--
Resolution: Fixed
Fix Version/s: 0.8
Status: Resolved (was: Patch Available)
Thanks for patch
[
https://issues.apache.org/jira/browse/KAFKA-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung closed KAFKA-688.
---
> System Test - Update all testcase__properties.json for properties keys
> uniform naming convention
> --
Jane,
I changed the version of scala in project/build.properties to 2.9.2 and did
a ./sbt clean update package. It seems to build and run fine for me.
I would check the classpath to see if there are conflicting versions of
scala.
Thanks,
Neha
On Mon, Jan 14, 2013 at 1:22 PM, Jane Wang wrote:
[
https://issues.apache.org/jira/browse/KAFKA-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553345#comment-13553345
]
Neha Narkhede commented on KAFKA-697:
-
Unfortunately, this rule of not allowing a '.' i
[
https://issues.apache.org/jira/browse/KAFKA-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553345#comment-13553345
]
Neha Narkhede edited comment on KAFKA-697 at 1/15/13 12:41 AM:
--
[
https://issues.apache.org/jira/browse/KAFKA-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553351#comment-13553351
]
Sriram Subramanian commented on KAFKA-697:
--
+1 on Neha's comment. It is simpler to
[
https://issues.apache.org/jira/browse/KAFKA-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike reassigned KAFKA-697:
---
Assignee: Swapnil Ghike
> ConsoleConsumer throws InvalidConfigException for "." in client
[
https://issues.apache.org/jira/browse/KAFKA-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-697:
Attachment: kafka-697-allow-dot.patch
Thanks for your comments. I agree that allowing dot will make
[
https://issues.apache.org/jira/browse/KAFKA-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553392#comment-13553392
]
Neha Narkhede commented on KAFKA-698:
-
+1 on the patch
> broker may ex
[
https://issues.apache.org/jira/browse/KAFKA-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-698:
Assignee: Jay Kreps
> broker may expose uncommitted data to a consumer
> ---
[
https://issues.apache.org/jira/browse/KAFKA-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriram Subramanian updated KAFKA-671:
-
Attachment: outOfMemFix-v1.patch
This is one possible fix. The fix would largely depend on
[
https://issues.apache.org/jira/browse/KAFKA-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553499#comment-13553499
]
Jun Rao commented on KAFKA-702:
---
I am wondering if the following approach will break the dead
[
https://issues.apache.org/jira/browse/KAFKA-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553509#comment-13553509
]
Neha Narkhede commented on KAFKA-702:
-
I like this idea better than having separate res
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
balanced
>
>
> Than how it achieve zookeeper-based load balance on per-request basis?
You are asking two related but different questions. One is how does load
balancing work and the other is how does broker discovery works. Jun
explained how load balancing works and how requests are routed to
partitons. I
In 0.8, we got rid of zookeeper from the producer and replaced it with a
metadata API.
What is the API like? Can we call the API manually?
On startup and whenever a request fails, the producer refreshes its view of the
cluster by sending a metadata request to any of the brokers.
But in my test, i
Thanks for your kindly reply.
From: Jun Rao [mailto:jun...@gmail.com]
Sent: 2013年1月15日 13:53
To: dev@kafka.apache.org; Jun Guo -X (jungu - CIIC at Cisco)
Subject: Re: About kafka 0.8 producer zookeeper-based load balancing on
per-request basis
Basically, we spread partitions among multiple broke
Hi,
We know in Kafka 0.7, we can specify zk.connect. And with zookeeper, the
producer can dynamically detect broker. But in Kafka 0.8, we can't specify
zk.connect for producer. How does the producer in Kafka 0.8 auto detect broker?
I have done two experiments.
In first one, I configure the broke
45 matches
Mail list logo
