[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15662738#comment-15662738 ] Ewen Cheslack-Postava commented on KAFKA-3959: -- [~granthenke] [~onurkaraman] [~toddpalino]

[jira] [Created] (KAFKA-4404) Add knowledge of sign to numeric schema types

Andy Bryant created KAFKA-4404: -- Summary: Add knowledge of sign to numeric schema types Key: KAFKA-4404 URL: https://issues.apache.org/jira/browse/KAFKA-4404 Project: Kafka Issue Type:

[jira] [Resolved] (KAFKA-3967) Excessive Network IO between Kafka brokers

[ https://issues.apache.org/jira/browse/KAFKA-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-3967. -- Resolution: Invalid [~Krishna82] Closing this for now since we haven't heard

[jira] [Commented] (KAFKA-4021) system tests need to enable trace level logging for controller and state-change log

[ https://issues.apache.org/jira/browse/KAFKA-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15662381#comment-15662381 ] Ewen Cheslack-Postava commented on KAFKA-4021: -- [~junrao] Is this actually reasonable to do

Re: Upgrading from kafka-0.8.1.1 to kafka-0.9.0.1

The errors you're seeing sound like an issue where you updated the artifact but didn't recompile against the newer Scala version. Did you recompile or just replace the Kafka jar with a newer one? -Ewen On Wed, Nov 9, 2016 at 4:31 PM, Divyajothi Baskaran wrote: > Hi, >

[jira] [Commented] (KAFKA-4402) Kafka Producer's DefaultPartitioner is actually not round robin as said in the code comments "If no partition or key is present choose a partition in a round-robin fash

[ https://issues.apache.org/jira/browse/KAFKA-4402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15662197#comment-15662197 ] Ewen Cheslack-Postava commented on KAFKA-4402: -- [~Jun Yao] Sorry, missed that update with the

[jira] [Commented] (KAFKA-4402) Kafka Producer's DefaultPartitioner is actually not round robin as said in the code comments "If no partition or key is present choose a partition in a round-robin fash

[ https://issues.apache.org/jira/browse/KAFKA-4402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15662198#comment-15662198 ] Ewen Cheslack-Postava commented on KAFKA-4402: -- [~Jun Yao] Sorry, missed that update with the

[jira] [Commented] (KAFKA-4402) Kafka Producer's DefaultPartitioner is actually not round robin as said in the code comments "If no partition or key is present choose a partition in a round-robin fash

[ https://issues.apache.org/jira/browse/KAFKA-4402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15662168#comment-15662168 ] Jun Yao commented on KAFKA-4402: Hi, Ewen, I updated the description, I am looking at the same producer

[jira] [Created] (KAFKA-4403) Update KafkaBasedLog to use new endOffsets consumer API

Ewen Cheslack-Postava created KAFKA-4403: Summary: Update KafkaBasedLog to use new endOffsets consumer API Key: KAFKA-4403 URL: https://issues.apache.org/jira/browse/KAFKA-4403 Project: Kafka

[jira] [Commented] (KAFKA-4402) Kafka Producer's DefaultPartitioner is actually not round robin as said in the code comments "If no partition or key is present choose a partition in a round-robin fash

[ https://issues.apache.org/jira/browse/KAFKA-4402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15662157#comment-15662157 ] ASF GitHub Bot commented on KAFKA-4402: --- GitHub user yaojuncn opened a pull request:

[GitHub] kafka pull request #2128: KAFKA-4402: make the KafkaProducer true round robi...

GitHub user yaojuncn opened a pull request: https://github.com/apache/kafka/pull/2128 KAFKA-4402: make the KafkaProducer true round robin per topic You can merge this pull request into a Git repository by running: $ git pull https://github.com/yaojuncn/kafka

[jira] [Updated] (KAFKA-4402) Kafka Producer's DefaultPartitioner is actually not round robin as said in the code comments "If no partition or key is present choose a partition in a round-robin fashio

[ https://issues.apache.org/jira/browse/KAFKA-4402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Yao updated KAFKA-4402: --- Description: >From this code comments, it is said that Kafka client Producer's >DefaultPartitioner will do

[jira] [Commented] (KAFKA-4402) Kafka Producer's DefaultPartitioner is actually not round robin as said in the code comments "If no partition or key is present choose a partition in a round-robin fash

[ https://issues.apache.org/jira/browse/KAFKA-4402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15662153#comment-15662153 ] Ewen Cheslack-Postava commented on KAFKA-4402: -- [~Jun Yao] Which code are you looking at for

Re: [VOTE] KIP-89: Allow sink connectors to decouple flush and offset commit

+1 (binding) On Nov 9, 2016 2:17 PM, "Shikhar Bhushan" wrote: > Hi, > > I would like to initiate a vote on KIP-89 > > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 89%3A+Allow+sink+connectors+to+decouple+flush+and+offset+commit > > Best, > > Shikhar >

[jira] [Commented] (KAFKA-4401) Change the KafkaServerTestHarness and IntegrationTestHarness from trait to abstract class.

[ https://issues.apache.org/jira/browse/KAFKA-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15662147#comment-15662147 ] Ewen Cheslack-Postava commented on KAFKA-4401: -- [~becket_qin] We've already done much of this

[jira] [Created] (KAFKA-4402) Kafka Producer's DefaultPartitioner is actually not round robin as said in the code comments "If no partition or key is present choose a partition in a round-robin fashio

Jun Yao created KAFKA-4402: -- Summary: Kafka Producer's DefaultPartitioner is actually not round robin as said in the code comments "If no partition or key is present choose a partition in a round-robin fashion" Key: KAFKA-4402

Re?? [DISCUSS] KIP-68 Add a consumed log retention before log retention

Hi Becket, If using the trim.on.offset.commit parameter, it will help to quickly trim the log, but other consumer group's consumer may find the messages are trimmed. We still need to coordinate many consumer groups to trim the log, it seems difficult for the single consumer to do it.

[jira] [Resolved] (KAFKA-4398) offsetsForTimes returns false starting offset when timestamp of messages are not monotonically increasing

[ https://issues.apache.org/jira/browse/KAFKA-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxi resolved KAFKA-4398. - Resolution: Not A Bug > offsetsForTimes returns false starting offset when timestamp of messages are > not