[jira] [Commented] (KAFKA-2632) Move fetchable check from fetchedRecords to fetch response handler

[ https://issues.apache.org/jira/browse/KAFKA-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952176#comment-14952176 ] ASF GitHub Bot commented on KAFKA-2632: --- GitHub user guozhangwang opened a pull requ

[GitHub] kafka pull request: KAFKA-2632: move fetchable check ahead in hand...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/295 KAFKA-2632: move fetchable check ahead in handleFetchResponse You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka K2632 Alte

[jira] [Created] (KAFKA-2632) Move fetchable check from fetchedRecords to fetch response handler

Guozhang Wang created KAFKA-2632: Summary: Move fetchable check from fetchedRecords to fetch response handler Key: KAFKA-2632 URL: https://issues.apache.org/jira/browse/KAFKA-2632 Project: Kafka

Build failed in Jenkins: kafka-trunk-jdk8 #15

See Changes: [junrao] MINOR: Use the correct processor id in the processor thread name -- [...truncated 861 lines...] public MockProducer(boolean autoComplete, Serializer keySerializer, Seria

Jenkins build is back to normal : kafka-trunk-jdk7 #672

See

[GitHub] kafka pull request: MINOR: Use the correct processor id in the pro...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/294 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

[jira] [Commented] (KAFKA-2477) Replicas spuriously deleting all segments in partition

[ https://issues.apache.org/jira/browse/KAFKA-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952128#comment-14952128 ] Chinmay Soman commented on KAFKA-2477: -- Btw, this doesn't happen everywhere but is de

[jira] [Comment Edited] (KAFKA-2477) Replicas spuriously deleting all segments in partition

[ https://issues.apache.org/jira/browse/KAFKA-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952127#comment-14952127 ] Chinmay Soman edited comment on KAFKA-2477 at 10/11/15 1:49 AM:

[jira] [Updated] (KAFKA-2477) Replicas spuriously deleting all segments in partition

[ https://issues.apache.org/jira/browse/KAFKA-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Soman updated KAFKA-2477: - Attachment: Screen Shot 2015-10-10 at 6.54.44 PM.png Max lag observed for the different brokers >

[jira] [Commented] (KAFKA-2477) Replicas spuriously deleting all segments in partition

[ https://issues.apache.org/jira/browse/KAFKA-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952120#comment-14952120 ] Ewen Cheslack-Postava commented on KAFKA-2477: -- [~cpsoman] Interesting, the o

[jira] [Commented] (KAFKA-2477) Replicas spuriously deleting all segments in partition

[ https://issues.apache.org/jira/browse/KAFKA-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952113#comment-14952113 ] Chinmay Soman commented on KAFKA-2477: -- We're hitting this issue quite often (every 1

[GitHub] kafka pull request: MINOR: Use the correct processor id in the pro...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/294 MINOR: Use the correct processor id in the processor thread name You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka fix-processor-thread-n

Build failed in Jenkins: kafka-trunk-jdk8 #14

See Changes: [junrao] KAFKA-2614; No more clients can connect after -- [...truncated 3238 lines...] kafka.api.ConsumerTest > testSeek PASSED kafka.log.LogCleanerIntegrationTest > cleanerTest[3]

[jira] [Commented] (KAFKA-2515) handle oversized messages properly in new consumer

[ https://issues.apache.org/jira/browse/KAFKA-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952094#comment-14952094 ] Jun Rao commented on KAFKA-2515: The following is how you can reproduce this. 1. Create

Build failed in Jenkins: kafka-trunk-jdk7 #671

See Changes: [junrao] KAFKA-2614; No more clients can connect after -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-2 (docker Ubuntu ubun

[GitHub] kafka pull request: KAFKA-2614; No more clients can connect after ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/288 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

[jira] [Commented] (KAFKA-2614) No more clients can connect after `TooManyConnectionsException` threshold (max.connections.per.ip) is reached

[ https://issues.apache.org/jira/browse/KAFKA-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952069#comment-14952069 ] ASF GitHub Bot commented on KAFKA-2614: --- Github user asfgit closed the pull request

[jira] [Updated] (KAFKA-2614) No more clients can connect after `TooManyConnectionsException` threshold (max.connections.per.ip) is reached

[ https://issues.apache.org/jira/browse/KAFKA-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2614: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 288 [https:/

Re: Confluent Clarification

Dinesh, As Grant mentioned, Confluent's mailing list is a better place to ask questions about the Confluent Platform. The version of Kafka (and Zookeeper) match the Apache versions -- currently the CP 1.0.1 release packages the Apache Kafka 0.8.2.2 release directly. In the future, there may be ca

[jira] [Created] (KAFKA-2631) Expose data volume via JMX

Eno Thereska created KAFKA-2631: --- Summary: Expose data volume via JMX Key: KAFKA-2631 URL: https://issues.apache.org/jira/browse/KAFKA-2631 Project: Kafka Issue Type: Improvement Comp

Re: [DISCUSS] KIP-37 - Add namespaces in Kafka

Good write-up Ashish. Looking at one of the rejected alternatives got me thinking: "Modify request/ response formats to take namespace specifically. Solves the issue of delimiting string required in proposed approach and the issue with existing regex consumers. This definitely is the cleanest app