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

See Changes: [me] KAFKA-4008: Module "tools" should not be dependent on "core" -- [...truncated 7543 lines...] org.apache.kafka.clients.consumer.internals.ConsumerNetworkClientTest > wakeup

[jira] [Commented] (KAFKA-4008) Module "tools" should not be dependent on "core"

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

[jira] [Resolved] (KAFKA-4008) Module "tools" should not be dependent on "core"

[ https://issues.apache.org/jira/browse/KAFKA-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-4008. -- Resolution: Fixed Fix Version/s: 0.10.1.0 Issue resolved by pull request

[GitHub] kafka pull request #1685: KAFKA-4008: Module "tools" should not be dependent...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1685 --- 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

[jira] [Commented] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15402962#comment-15402962 ] Kane Kim commented on KAFKA-3042: - We've found it's also being triggered by packet loss from broker to ZK

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15402900#comment-15402900 ] Joshua Dickerson commented on KAFKA-2729: - This has bit us twice in our live environment. 0.9.0.1

[jira] [Created] (KAFKA-4011) allow sizing RequestQueue in bytes

radai rosenblatt created KAFKA-4011: --- Summary: allow sizing RequestQueue in bytes Key: KAFKA-4011 URL: https://issues.apache.org/jira/browse/KAFKA-4011 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-4010) ConfigDef.toRst() should create sections for each group

Shikhar Bhushan created KAFKA-4010: -- Summary: ConfigDef.toRst() should create sections for each group Key: KAFKA-4010 URL: https://issues.apache.org/jira/browse/KAFKA-4010 Project: Kafka

[jira] [Commented] (KAFKA-4009) Data corruption or EIO leads to data loss

[ https://issues.apache.org/jira/browse/KAFKA-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15402818#comment-15402818 ] Aishwarya Ganesan commented on KAFKA-4009: -- Yes, I used ack=all in the producer. N1 did detect

[jira] [Commented] (KAFKA-4009) Data corruption or EIO leads to data loss

[ https://issues.apache.org/jira/browse/KAFKA-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15402740#comment-15402740 ] Jun Rao commented on KAFKA-4009: [~aganesan], thanks for reporting this. In your test, did the producer

[jira] [Created] (KAFKA-4009) Data corruption or EIO leads to data loss

Aishwarya Ganesan created KAFKA-4009: Summary: Data corruption or EIO leads to data loss Key: KAFKA-4009 URL: https://issues.apache.org/jira/browse/KAFKA-4009 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-1211) Hold the produce request with ack > 1 in purgatory until replicas' HW has larger than the produce offset

[ https://issues.apache.org/jira/browse/KAFKA-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15402622#comment-15402622 ] Jun Rao commented on KAFKA-1211: The following is a draft proposal. [~fpj], does that look reasonable to

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

See Changes: [cshapi] MINOR: lower logging severity for offset reset -- [...truncated 5624 lines...] kafka.common.TopicTest > testTopicHasCollision STARTED kafka.common.TopicTest >

[jira] [Updated] (KAFKA-3847) Connect tasks should not share a producer

[ https://issues.apache.org/jira/browse/KAFKA-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3847: - Assignee: Liquan Pei (was: Ewen Cheslack-Postava) > Connect tasks should not

[jira] [Work started] (KAFKA-4000) Consumer per-topic metrics do not aggregate partitions from the same topic

[ https://issues.apache.org/jira/browse/KAFKA-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4000 started by Vahid Hashemian. -- > Consumer per-topic metrics do not aggregate partitions from the same topic

[GitHub] kafka pull request #1691: MINOR: lower logging severity for offset reset

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1691 --- 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

[jira] [Commented] (KAFKA-2063) Bound fetch response size

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15402263#comment-15402263 ] Jun Rao commented on KAFKA-2063: [~nepal], thanks for the proposal. For a), which server side setting are

[GitHub] kafka pull request #1692: MINOR: Fixed documentation for KStream left join K...

GitHub user jpzk opened a pull request: https://github.com/apache/kafka/pull/1692 MINOR: Fixed documentation for KStream left join KStream-KTable We are not joining in a window here. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] kafka pull request #1691: MINOR: lower logging severity for offset reset

GitHub user cotedm opened a pull request: https://github.com/apache/kafka/pull/1691 MINOR: lower logging severity for offset reset When resetting the first dirty offset to the log start offset, we currently log an ERROR which makes users think the log cleaner has a problem and

Re: [kafka-clients] [VOTE] 0.10.0.1 RC0

Thanks Ismael. On Sat, Jul 30, 2016 at 7:43 PM Ismael Juma wrote: > Hi Dana, > > Thanks for testing releases so promptly. Very much appreciated! > > It's funny, Ewen had suggested something similar with regards to the > release notes a couple of days ago. We now have a Python

Request: Please add me to contributor list.

Hello, I am interested in contributing to Kafka project. Can I please be added to the contributor list so that I can assign newbie tickets to myself and start working on them. Thank you Chetan Singh

Build failed in Jenkins: kafka-0.10.0-jdk7 #174

See -- [...truncated 6390 lines...] org.apache.kafka.connect.storage.KafkaOffsetBackingStoreTest > testGetSet PASSED org.apache.kafka.connect.storage.KafkaOffsetBackingStoreTest > testGetSetNull

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

See -- [...truncated 11729 lines...] org.apache.kafka.streams.state.internals.CompositeReadOnlyKeyValueStoreTest > shouldThrowInvalidStoreExceptionIfNoStoresExistOnRange PASSED

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

See -- [...truncated 6769 lines...] kafka.message.ByteBufferMessageSetTest > testValidBytesWithCompression STARTED kafka.message.ByteBufferMessageSetTest > testValidBytesWithCompression PASSED

JDK configuration for Kafka jobs in Jenkins

Hi all, Just a quick update with regards to the JDK configuration for Kafka Jobs in Jenkins. The Infra team has made some changes on how the JDK is installed in Jenkins slaves and how it should be configured in Jenkins jobs. See the following for details: