Build failed in Jenkins: kafka_0.9.0_jdk7 #45

See Changes: [cshapi] KAFKA-2892 Consumer Docs Use Wrong Method -- [...truncated 214 lines...] new UpdateMetadataRequest.BrokerEndPoint(brokerEndPoint.id, brokerEndPoint.host, broke

[jira] [Updated] (KAFKA-2892) Consumer Docs Use Wrong Method

[ https://issues.apache.org/jira/browse/KAFKA-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2892: Resolution: Fixed Fix Version/s: 0.9.1.0 Status: Resolved (was: Patch Available)

[GitHub] kafka pull request: KAFKA-2892 Consumer Docs Use Wrong Method

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/592 --- 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-2892) Consumer Docs Use Wrong Method

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

[jira] [Commented] (KAFKA-2843) when consumer got empty messageset, fetchResponse.highWatermark != current_offset?

[ https://issues.apache.org/jira/browse/KAFKA-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028229#comment-15028229 ] netcafe commented on KAFKA-2843: I did, no result. > when consumer got empty messageset,

[GitHub] kafka pull request: KAFKA-2892 Consumer Docs Use Wrong Method

GitHub user eljefe6a opened a pull request: https://github.com/apache/kafka/pull/592 KAFKA-2892 Consumer Docs Use Wrong Method The KafkaConsumer docs use a non-existent method for assigning partitions (consumer.assign). The JavaDocs show as: ``` String topic = "foo"

[jira] [Commented] (KAFKA-2892) Consumer Docs Use Wrong Method

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

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

See Changes: [wangguoz] MINOR: comments on KStream methods, and fix generics [cshapi] MINOR: Improve broker id documentation -- [...truncated 4894 lines...] kafka.log.BrokerCompressionTest > te

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

See Changes: [wangguoz] MINOR: comments on KStream methods, and fix generics [cshapi] MINOR: Improve broker id documentation -- [...truncated 3707 lines...] org.apache.kafka.common.record.Recor

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

See Changes: [wangguoz] KAFKA-2718: Prevent temp directory being reused in parallel test runs [wangguoz] MINOR: change KStream processor names [cshapi] MINOR: Support GitHub OAuth tokens in kafka-merge-pr.py [cshapi] KAFKA-2643: Run

[GitHub] kafka pull request: MINOR: Improve broker id documentation

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/585 --- 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] [Created] (KAFKA-2896) System test for partition re-assignment

Gwen Shapira created KAFKA-2896: --- Summary: System test for partition re-assignment Key: KAFKA-2896 URL: https://issues.apache.org/jira/browse/KAFKA-2896 Project: Kafka Issue Type: Task

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

See Changes: [wangguoz] KAFKA-2718: Prevent temp directory being reused in parallel test runs [wangguoz] MINOR: change KStream processor names [cshapi] MINOR: Support GitHub OAuth tokens in kafka-merge-pr.py [cshapi] KAFKA-2643: Run

[GitHub] kafka pull request: MINOR: comments on KStream methods, and fix ge...

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

Build failed in Jenkins: kafka_0.9.0_jdk7 #44

See Changes: [wangguoz] KAFKA-2718: Prevent temp directory being reused in parallel test runs [junrao] KAFKA-2878; Guard against OutOfMemory in Kafka broker -- [...truncated 1862 lines...] jdk1.7

Re: All brokers are running but some partitions' leader is -1

Great to know that. Thanks Gwen! On Wed, Nov 25, 2015 at 12:03 PM, Gwen Shapira wrote: > 1. Yes, you can do a rolling upgrade of brokers from 0.8.2 to 0.9.0. The > important thing is to upgrade the brokers before you upgrade any of the > clients. > > 2. I'm not aware of issues with 0.9.0 and Spa

[jira] [Created] (KAFKA-2895) Add certificate authority functionality to TestSslUtils

Flavio Junqueira created KAFKA-2895: --- Summary: Add certificate authority functionality to TestSslUtils Key: KAFKA-2895 URL: https://issues.apache.org/jira/browse/KAFKA-2895 Project: Kafka I

[GitHub] kafka pull request: MINOR: comments on KStream methods, and fix ge...

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/591 MINOR: comments on KStream methods, and fix generics @guozhangwang You can merge this pull request into a Git repository by running: $ git pull https://github.com/ymatsuda/kafka comments Alte

[GitHub] kafka pull request: MINOR: initialize Serdes with ProcessorContext

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/589 --- 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-2643) Run mirror maker tests in ducktape with SSL and SASL

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

[jira] [Resolved] (KAFKA-2643) Run mirror maker tests in ducktape with SSL and SASL

[ https://issues.apache.org/jira/browse/KAFKA-2643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-2643. - Resolution: Fixed Issue resolved by pull request 559 [https://github.com/apache/kafka/pull/559] >

[GitHub] kafka pull request: KAFKA-2643: Run mirror maker ducktape tests wi...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/559 --- 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] [Created] (KAFKA-2894) WorkerSinkTask doesn't handle rewinding offsets on rebalance

Ewen Cheslack-Postava created KAFKA-2894: Summary: WorkerSinkTask doesn't handle rewinding offsets on rebalance Key: KAFKA-2894 URL: https://issues.apache.org/jira/browse/KAFKA-2894 Project: K

[GitHub] kafka pull request: MINOR: Support GitHub OAuth tokens in kafka-me...

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

[GitHub] kafka pull request: MINOR: Support GitHub OAuth tokens in kafka-me...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/590 MINOR: Support GitHub OAuth tokens in kafka-merge-pr.py You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka KOAuth Alternati

[GitHub] kafka pull request: MINOR: change KStream processor names

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

[GitHub] kafka pull request: MINOR: initialize Serdes with ProcessorContext

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/589 MINOR: initialize Serdes with ProcessorContext @guozhangwang You can merge this pull request into a Git repository by running: $ git pull https://github.com/ymatsuda/kafka init_serdes_with_pro

[jira] [Commented] (KAFKA-2718) Reuse of temporary directories leading to transient unit test failures

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

[jira] [Resolved] (KAFKA-2718) Reuse of temporary directories leading to transient unit test failures

[ https://issues.apache.org/jira/browse/KAFKA-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-2718. -- Resolution: Fixed Fix Version/s: (was: 0.9.0.0) 0.9.0.1 Issue reso

[GitHub] kafka pull request: KAFKA-2718: Prevent temp directory being reuse...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/583 --- 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] [Comment Edited] (KAFKA-2892) Consumer Docs Use Wrong Method

[ https://issues.apache.org/jira/browse/KAFKA-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027700#comment-15027700 ] Grant Henke edited comment on KAFKA-2892 at 11/25/15 10:17 PM: -

[jira] [Commented] (KAFKA-2892) Consumer Docs Use Wrong Method

[ https://issues.apache.org/jira/browse/KAFKA-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027700#comment-15027700 ] Grant Henke commented on KAFKA-2892: Hi [~eljefe6aa]. We actually changed the docs pat

[jira] [Updated] (KAFKA-2892) Consumer Docs Use Wrong Method

[ https://issues.apache.org/jira/browse/KAFKA-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Anderson updated KAFKA-2892: -- Attachment: docspatch.diff > Consumer Docs Use Wrong Method > -- > >

[jira] [Updated] (KAFKA-2892) Consumer Docs Use Wrong Method

[ https://issues.apache.org/jira/browse/KAFKA-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Anderson updated KAFKA-2892: -- Fix Version/s: 0.9.0.0 Status: Patch Available (was: Open) > Consumer Docs Use Wrong

[GitHub] kafka pull request: Grammar on README.md

GitHub user simplyianm opened a pull request: https://github.com/apache/kafka/pull/588 Grammar on README.md You can merge this pull request into a Git repository by running: $ git pull https://github.com/simplyianm/kafka patch-1 Alternatively you can review and apply these ch

[GitHub] kafka pull request: MINOR: change KStream processor names

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/587 MINOR: change KStream processor names @guozhangwang You can merge this pull request into a Git repository by running: $ git pull https://github.com/ymatsuda/kafka kstream_processor_names Alt

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

See Changes: [wangguoz] HOTFIX: fix StreamTask.close() -- [...truncated 6675 lines...] org.apache.kafka.connect.json.JsonConverterTest > timeToJson PASSED org.apache.kafka.connect.json.JsonConve

Build failed in Jenkins: kafka_0.9.0_jdk7 #43

See Changes: [wangguoz] KAFKA-2799: skip wakeup in the follow-up poll() call. -- [...truncated 214 lines...] new UpdateMetadataRequest.BrokerEndPoint(brokerEndPoint.id, brokerEndPoi

[GitHub] kafka pull request: HOTFIX: fix StreamTask.close()

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

Re: All brokers are running but some partitions' leader is -1

1. Yes, you can do a rolling upgrade of brokers from 0.8.2 to 0.9.0. The important thing is to upgrade the brokers before you upgrade any of the clients. 2. I'm not aware of issues with 0.9.0 and SparkStreaming. However, definitely do your own testing to make sure. On Wed, Nov 25, 2015 at 11:25 A

[jira] [Updated] (KAFKA-2799) WakupException thrown in the followup poll() could lead to data loss

[ https://issues.apache.org/jira/browse/KAFKA-2799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2799: - Fix Version/s: (was: 0.9.0.0) 0.9.0.1 > WakupException thrown in the follow

[jira] [Commented] (KAFKA-2799) WakupException thrown in the followup poll() could lead to data loss

[ https://issues.apache.org/jira/browse/KAFKA-2799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027502#comment-15027502 ] Guozhang Wang commented on KAFKA-2799: -- [~granthenke] Thanks for reporting this. It i

[GitHub] kafka pull request: HOTFIX: fix StreamTask.close()

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/586 HOTFIX: fix StreamTask.close() @guozhangwang You can merge this pull request into a Git repository by running: $ git pull https://github.com/ymatsuda/kafka fix_streamtask_close Alternatively

Release source doesn't contain .gitignore

The recent release source does not contain the repo's .gitignore file. This is definitely not a major issue, but I wanted to bring it up so it could be added in future releases. I downloaded the source from: https://www.apache.org/dyn/closer.cgi?path=/kafka/0.9.0.0/kafka-0.9.0.0-src.tgz Thanks, G

Re: All brokers are running but some partitions' leader is -1

Hi Gwen, Yes, we're going to upgrade the 0.9.0 version. Regarding the upgrade, we definitely don't want to have down time of our cluster. So the upgrade will be machine by machine. Will the release 0.9.0 work with the Aug's version together in the same Kafka cluster? Also we currently run spark str

[jira] [Created] (KAFKA-2893) Add Negative Partition Seek Check

Jesse Anderson created KAFKA-2893: - Summary: Add Negative Partition Seek Check Key: KAFKA-2893 URL: https://issues.apache.org/jira/browse/KAFKA-2893 Project: Kafka Issue Type: Bug C

[jira] [Created] (KAFKA-2892) Consumer Docs Use Wrong Method

Jesse Anderson created KAFKA-2892: - Summary: Consumer Docs Use Wrong Method Key: KAFKA-2892 URL: https://issues.apache.org/jira/browse/KAFKA-2892 Project: Kafka Issue Type: Bug Comp

[jira] [Commented] (KAFKA-2887) TopicMetadataRequest creates topic if it does not exist

[ https://issues.apache.org/jira/browse/KAFKA-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027357#comment-15027357 ] Andrew Winterman commented on KAFKA-2887: - my only complaint with this approach is

[jira] [Commented] (KAFKA-2891) Gaps in messages delivered by new consumer after Kafka restart

[ https://issues.apache.org/jira/browse/KAFKA-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027301#comment-15027301 ] Ben Stopford commented on KAFKA-2891: - So I'm starting to think the problem may be rel

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

See Changes: [junrao] KAFKA-2878; Guard against OutOfMemory in Kafka broker -- [...truncated 1401 lines...] kafka.log.LogTest > testTruncateTo PASSED kafka.log.LogTest > testCleanShutdownFile P

[jira] [Closed] (KAFKA-2800) Update outdated dependencies

[ https://issues.apache.org/jira/browse/KAFKA-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke closed KAFKA-2800. -- > Update outdated dependencies > > > Key: KAFKA-2800 >

Re: kafka 0.8 producer issue

Hi, >From the information that you've provided, I think your callback is the culprit here. It is seen from the stacktrace:- at com.hpe.ssmamp.kafka.KafkaPDFAProducer$1.onCompletion( KafkaPDFAProducer.java:62) Please provide more information like a code snippet etc, so that we can tell more

[jira] [Commented] (KAFKA-2799) WakupException thrown in the followup poll() could lead to data loss

[ https://issues.apache.org/jira/browse/KAFKA-2799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027255#comment-15027255 ] Grant Henke commented on KAFKA-2799: Was this supposed to make it into 0.9.0.0? I don'

RE: kafka 0.8 producer issue

Hi prabhjot I just realized its not producing to kafka that’s why iam getting this null pointer. In my localhost I can see kafka info/debug logs. But in HDP cluster I cannot see any exceptions. How should I configure the logger to show exceptions in kafka log files thanks -Original Messag

[ANNOUNCE] CFP open for ApacheCon North America 2016

Community growth starts by talking with those interested in your project. ApacheCon North America is coming, are you? We are delighted to announce that the Call For Presentations (CFP) is now open for ApacheCon North America. You can submit your proposed sessions at http://events.linuxfoundation.o

[jira] [Commented] (KAFKA-2878) Kafka broker throws OutOfMemory exception with invalid join group request

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

[jira] [Resolved] (KAFKA-2878) Kafka broker throws OutOfMemory exception with invalid join group request

[ https://issues.apache.org/jira/browse/KAFKA-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-2878. Resolution: Fixed Fix Version/s: 0.9.1.0 Issue resolved by pull request 577 [https://github.com/apach

[GitHub] kafka pull request: KAFKA-2878: Guard against OutOfMemory in Kafka...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/577 --- 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] [Comment Edited] (KAFKA-2891) Gaps in messages delivered by new consumer after Kafka restart

[ https://issues.apache.org/jira/browse/KAFKA-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026907#comment-15026907 ] Ben Stopford edited comment on KAFKA-2891 at 11/25/15 4:01 PM: -

kafka 0.8 producer issue

Hi all I am trying to get the producer working. It was working before but now getting the following issue. I have created a new topic as well just in case if it was the issue with topic but still no luck. I have increased the message size in broker as iam trying to send atleast 3mb message here

[jira] [Comment Edited] (KAFKA-2891) Gaps in messages delivered by new consumer after Kafka restart

[ https://issues.apache.org/jira/browse/KAFKA-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026907#comment-15026907 ] Ben Stopford edited comment on KAFKA-2891 at 11/25/15 3:40 PM: -

[jira] [Comment Edited] (KAFKA-2891) Gaps in messages delivered by new consumer after Kafka restart

[ https://issues.apache.org/jira/browse/KAFKA-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026907#comment-15026907 ] Ben Stopford edited comment on KAFKA-2891 at 11/25/15 3:39 PM: -

[jira] [Comment Edited] (KAFKA-2891) Gaps in messages delivered by new consumer after Kafka restart

[ https://issues.apache.org/jira/browse/KAFKA-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026907#comment-15026907 ] Ben Stopford edited comment on KAFKA-2891 at 11/25/15 3:38 PM: -

[jira] [Commented] (KAFKA-2890) Strange behaviour during partitions reassignment.

[ https://issues.apache.org/jira/browse/KAFKA-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026910#comment-15026910 ] Ismael Juma commented on KAFKA-2890: Thanks for the report. Would you be able to list

[jira] [Created] (KAFKA-2891) Gaps in messages delivered by new consumer after Kafka restart

Rajini Sivaram created KAFKA-2891: - Summary: Gaps in messages delivered by new consumer after Kafka restart Key: KAFKA-2891 URL: https://issues.apache.org/jira/browse/KAFKA-2891 Project: Kafka

[jira] [Commented] (KAFKA-2891) Gaps in messages delivered by new consumer after Kafka restart

[ https://issues.apache.org/jira/browse/KAFKA-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026907#comment-15026907 ] Ben Stopford commented on KAFKA-2891: - Yes. I get exactly the same. Worked fine for ab

[GitHub] kafka pull request: MINOR: Improve broker id documentation

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/585 MINOR: Improve broker id documentation You can merge this pull request into a Git repository by running: $ git pull https://github.com/granthenke/kafka brokerid Alternatively you can review

[jira] [Created] (KAFKA-2890) Strange behaviour during partitions reassignment.

Alexander Kukushkin created KAFKA-2890: -- Summary: Strange behaviour during partitions reassignment. Key: KAFKA-2890 URL: https://issues.apache.org/jira/browse/KAFKA-2890 Project: Kafka I

[jira] [Updated] (KAFKA-2771) Add Rolling Upgrade to Secured Cluster to System Tests

[ https://issues.apache.org/jira/browse/KAFKA-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford updated KAFKA-2771: Description: Ensure we can perform a rolling upgrade to enable SSL, SASL_PLAINTEXT & on a running

[jira] [Updated] (KAFKA-2771) Add Rolling Upgrade to Secured Cluster to System Tests

[ https://issues.apache.org/jira/browse/KAFKA-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford updated KAFKA-2771: Summary: Add Rolling Upgrade to Secured Cluster to System Tests (was: Add SSL Rolling Upgrade Test

Re: group protocol/metadata documentation

Thanks, Jason. I see the range and roundrobin assignment strategies documented in the source. I don't see userdata used by either -- is that correct (I may be misreading)? The notes suggest userdata for something more detailed in the future, like rack-aware placements? One other question: in what