[
https://issues.apache.org/jira/browse/KAFKA-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13552781#comment-13552781
]
Maxime Brugidou commented on KAFKA-693:
---
I looked up the code in details and I am
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
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 ja...@twitter.com wrote:
I tried to grep
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
[
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 =
[
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
[
https://issues.apache.org/jira/browse/KAFKA-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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-tabpanelfocusedCommentId=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 id
[
https://issues.apache.org/jira/browse/KAFKA-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13553392#comment-13553392
]
Neha Narkhede commented on KAFKA-698:
-
+1 on the patch
broker may
[
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
[
https://issues.apache.org/jira/browse/KAFKA-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13553499#comment-13553499
]
Jun Rao commented on KAFKA-702:
---
I am wondering if the following approach will break the
[
https://issues.apache.org/jira/browse/KAFKA-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13553509#comment-13553509
]
Neha Narkhede commented on KAFKA-702:
-
I like this idea better than having separate
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
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
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
18 matches
Mail list logo