Re: Review Request 30063: Patch for KAFKA-1840

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/30063/ --- (Updated Feb. 1, 2015, 8:17 a.m.) Review request for kafka. Bugs: KAFKA-1840

[jira] [Commented] (KAFKA-1840) Add a simple message handler in Mirror Maker

[ https://issues.apache.org/jira/browse/KAFKA-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14300109#comment-14300109 ] Jiangjie Qin commented on KAFKA-1840: - Updated reviewboard https://reviews.apache.org/

[jira] [Updated] (KAFKA-1840) Add a simple message handler in Mirror Maker

[ https://issues.apache.org/jira/browse/KAFKA-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-1840: Attachment: KAFKA-1840_2015-02-01_00:16:53.patch > Add a simple message handler in Mirror Maker > --

Re: Cannot stop Kafka server if zookeeper is shutdown first

Hi Gwen, Yes, the KafkaZkClient is a wrapper around ZkClient and not a complete replacement. As for contributing to Zookeeper, yes that indeed in on my mind, but I haven't yet had a chance to really look deeper into Zookeeper or get in touch with their dev team to try and explain this potent

Re: [VOTE] 0.8.2.0 Candidate 3

You may already know this but the producer doesn't require a complete list of brokers in its config, it just requires the connection info for one active broker which it uses to discover the rest of the brokers. We allow you to specify multiple urls here for failover in cases where you aren't using

Re: [VOTE] 0.8.2.0 Candidate 3

Jun: You raise a very good question: let me explain why we use Broker.getConnectionString(), so may be we'll get a supported way to answer our need. We use Broker.getConnectionString() because we deploy "Kafka services" in Amazon EC2 with the following architecture: * Three VMs dedicated to Zooke

Re: [VOTE] 0.8.2.0 Candidate 3

Hello, I ran my own tests made with kafka_2.10-0.8.1.1.tgz binaries with our application: 1st test: == replace all kafka .jar files in our application on consumming side (without recompiling anything) => tests passed, OK 2nd test: === replace all kafka .jar files in our applicati

Re: Review Request 30403: Patch for KAFKA-1906

Yep I totally get that. But...you already have to modify the configs anyway. The primary goals of default values are basically two-fold 1) Get started quickly 2) Provide reasonable values for stuff people don't really know about. I guess I would just rather see people take the time (30s to 1min m

[jira] [Commented] (KAFKA-1910) Refactor KafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14300251#comment-14300251 ] Jay Kreps commented on KAFKA-1910: -- I guess the real question is how to slice it up. Big

[jira] [Created] (KAFKA-1912) Create a simple request re-routing facility

Jay Kreps created KAFKA-1912: Summary: Create a simple request re-routing facility Key: KAFKA-1912 URL: https://issues.apache.org/jira/browse/KAFKA-1912 Project: Kafka Issue Type: Improvement

Re: Review Request 30403: Patch for KAFKA-1906

Yeah I second Jaikiran's take: I think we should stick to something that works "out of the box" without editing config. I think the experience here is important, and adding one manual configuration step quickly cascades into a bunch of these steps (since it is always easier to make something manual

Re: [VOTE] 0.8.2.0 Candidate 3

In Netflix, we have been using route53 DNS name as bootstrap servers in AWS env. Basically, when a kafka broker start, we add it to route53 DNS name for the cluster. this is like the VIP that Jay suggested. But we are also moving toward to use Eureka service registry for bootstrapping. We are worr

Re: Review Request 30482: Add the coordinator to server

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/30482/#review70533 --- core/src/main/scala/kafka/coordinator/ConsumerCoordinator.scala

Re: [VOTE] 0.8.2.0 Candidate 3

+1 (binding). Verified quickstart and unit tests ran ok. On Sun, Feb 1, 2015 at 9:11 AM, Steven Wu wrote: > In Netflix, we have been using route53 DNS name as bootstrap servers in AWS > env. Basically, when a kafka broker start, we add it to route53 DNS name > for the cluster. this is like the V