Build failed in Jenkins: kafka-0.11.0-jdk7 #125

See Changes: [wangguoz] KAFKA-5362: Add EOS system tests for Streams API -- [...truncated 2.37 MB...] org.apache.kafka.streams.integration.QueryableStateIntegrationTest >

Jenkins build is back to normal : kafka-trunk-jdk8 #1680

See

[jira] [Updated] (KAFKA-2378) Add Connect embedded API

[ https://issues.apache.org/jira/browse/KAFKA-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2378: Summary: Add Connect embedded API (was: Add Copycat embedded API) > Add Connect embedded API >

[jira] [Resolved] (KAFKA-5382) Log recovery can fail if topic names contain one of the index suffixes

[ https://issues.apache.org/jira/browse/KAFKA-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5382. Resolution: Fixed Fix Version/s: (was: 0.10.2.2) 0.11.0.0. Mar

[GitHub] kafka pull request #3275: HOTFIX: use atomic boolean for inject errors in st...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/3275 HOTFIX: use atomic boolean for inject errors in streams eos integration test Originally we assume the task will be created exactly three times (twice upon starting up, once for each thread, and

[jira] [Created] (KAFKA-5413) Log cleaner fails due to large offset in segment file

Nicholas Ngorok created KAFKA-5413: -- Summary: Log cleaner fails due to large offset in segment file Key: KAFKA-5413 URL: https://issues.apache.org/jira/browse/KAFKA-5413 Project: Kafka Issue

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

See Changes: [cshapi] KAFKA-5411: AdminClient javadoc and documentation improvements [wangguoz] MINOR: disable flaky Streams EOS integration tests -- [...truncated 956.76

Re: Pull-Requests not worked on

I always thought that we had to repush a commit or close/open the PR in order to retrigger the build. This is the first time I've heard that you can do that. Does "retest this please" cause the tests to be re-run, simply because it's a comment on a PR? Or is it some magic with how we set things

[GitHub] kafka pull request #3276: KAFKA-5361: Add more integration tests for Streams...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/3276 KAFKA-5361: Add more integration tests for Streams EOS - multi-subtopology tests - fencing test You can merge this pull request into a Git repository by running: $ git pull https://github.c

Re: Pull-Requests not worked on

Hi all, A few clarifications: 1. Anyone can see the console output for a failed job, a login is not required for that. 2. One of the reasons why some PRs remain open even if they should be closed is that we have no way to close PRs ourselves without referencing them in a commit or asking Apache

[jira] [Commented] (KAFKA-5361) Add EOS integration tests for Streams API

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

[jira] [Created] (KAFKA-5414) Console consumer offset commit regression

Jason Gustafson created KAFKA-5414: -- Summary: Console consumer offset commit regression Key: KAFKA-5414 URL: https://issues.apache.org/jira/browse/KAFKA-5414 Project: Kafka Issue Type: Bug

Jenkins build is back to normal : kafka-0.11.0-jdk7 #126

See

[GitHub] kafka pull request #3277: KAFKA-5414: Revert "KAFKA-5327: ConsoleConsumer sh...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3277 KAFKA-5414: Revert "KAFKA-5327: ConsoleConsumer should manually commi… …t offsets for records that are returned in receive()" This reverts commit d7d1196a0b542adb46d22eeb5b6d12af950b64

[jira] [Commented] (KAFKA-5414) Console consumer offset commit regression

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

[GitHub] kafka pull request #3278: WIP: MINOR: Add logging and a small bug fix for th...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/3278 WIP: MINOR: Add logging and a small bug fix for the transaction coordinator You can merge this pull request into a Git repository by running: $ git pull https://github.com/apurvam/kafka MINOR

[jira] [Created] (KAFKA-5415) TransactionCoordinator

Apurva Mehta created KAFKA-5415: --- Summary: TransactionCoordinator Key: KAFKA-5415 URL: https://issues.apache.org/jira/browse/KAFKA-5415 Project: Kafka Issue Type: Bug Reporter: Apu

[jira] [Updated] (KAFKA-5415) TransactionCoordinator get stuck in PrepareCommits state.

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5415: Summary: TransactionCoordinator get stuck in PrepareCommits state. (was: TransactionCoordinator )

[jira] [Updated] (KAFKA-5415) TransactionCoordinator gets stuck in PrepareCommits state.

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5415: Summary: TransactionCoordinator gets stuck in PrepareCommits state. (was: TransactionCoordinator ge

[jira] [Updated] (KAFKA-5415) TransactionCoordinator gets stuck in PrepareCommits state.

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5415: Attachment: 6.tgz > TransactionCoordinator gets stuck in PrepareCommits state. > ---

[jira] [Updated] (KAFKA-5415) TransactionCoordinator gets stuck in PrepareCommits state.

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5415: Labels: exactly-once (was: ) > TransactionCoordinator gets stuck in PrepareCommits state. > ---

[jira] [Commented] (KAFKA-5415) TransactionCoordinator gets stuck in PrepareCommits state.

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043731#comment-16043731 ] Apurva Mehta commented on KAFKA-5415: - Logs from one such incident: https://issues.ap

[jira] [Commented] (KAFKA-5415) TransactionCoordinator gets stuck in PrepareCommits state.

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043741#comment-16043741 ] Apurva Mehta commented on KAFKA-5415: - Incriminating evidence from the logs. 1. Tail

[jira] [Comment Edited] (KAFKA-5415) TransactionCoordinator gets stuck in PrepareCommits state.

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043741#comment-16043741 ] Apurva Mehta edited comment on KAFKA-5415 at 6/9/17 12:51 AM: --

[jira] [Comment Edited] (KAFKA-5415) TransactionCoordinator gets stuck in PrepareCommits state.

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043741#comment-16043741 ] Apurva Mehta edited comment on KAFKA-5415 at 6/9/17 12:50 AM: --

[jira] [Updated] (KAFKA-5415) TransactionCoordinator gets stuck in PrepareCommit state

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5415: Summary: TransactionCoordinator gets stuck in PrepareCommit state (was: TransactionCoordinator gets

[jira] [Assigned] (KAFKA-5242) add max_number _of_retries to exponential backoff strategy

[ https://issues.apache.org/jira/browse/KAFKA-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-5242: -- Assignee: Matthias J. Sax > add max_number _of_retries to exponential backoff strategy

[jira] [Updated] (KAFKA-5242) add max_number _of_retries to exponential backoff strategy

[ https://issues.apache.org/jira/browse/KAFKA-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5242: --- Fix Version/s: 0.11.0.1 0.10.2.2 > add max_number _of_retries to exponentia

[jira] [Comment Edited] (KAFKA-5415) TransactionCoordinator gets stuck in PrepareCommit state

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043741#comment-16043741 ] Apurva Mehta edited comment on KAFKA-5415 at 6/9/17 12:59 AM: --

[jira] [Commented] (KAFKA-5242) add max_number _of_retries to exponential backoff strategy

[ https://issues.apache.org/jira/browse/KAFKA-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043753#comment-16043753 ] Matthias J. Sax commented on KAFKA-5242: While trying to add a new integration tes

[jira] [Commented] (KAFKA-5415) TransactionCoordinator gets stuck in PrepareCommit state

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043758#comment-16043758 ] Apurva Mehta commented on KAFKA-5415: - The interesting thing is that it reproduces con

[jira] [Updated] (KAFKA-5152) Kafka Streams keeps restoring state after shutdown is initiated during startup

[ https://issues.apache.org/jira/browse/KAFKA-5152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5152: --- Fix Version/s: 0.11.0.1 0.10.2.2 > Kafka Streams keeps restoring state afte

[jira] [Assigned] (KAFKA-5152) Kafka Streams keeps restoring state after shutdown is initiated during startup

[ https://issues.apache.org/jira/browse/KAFKA-5152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-5152: -- Assignee: Matthias J. Sax > Kafka Streams keeps restoring state after shutdown is initi

[jira] [Resolved] (KAFKA-5414) Console consumer offset commit regression

[ https://issues.apache.org/jira/browse/KAFKA-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5414. Resolution: Fixed Issue resolved by pull request 3277 [https://github.com/apache/kafka/pull/

[GitHub] kafka pull request #3277: KAFKA-5414: Revert "KAFKA-5327: ConsoleConsumer sh...

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

[jira] [Commented] (KAFKA-5414) Console consumer offset commit regression

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

[jira] [Reopened] (KAFKA-5327) Console Consumer should only poll for up to max messages

[ https://issues.apache.org/jira/browse/KAFKA-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reopened KAFKA-5327: I have reverted this change in KAFKA-5414 since it breaks existing usage. It seems like a simpl

[jira] [Commented] (KAFKA-3450) Producer blocks on send to topic that doesn't exist if auto create is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043829#comment-16043829 ] Soumya Bhaumik commented on KAFKA-3450: --- Just checking to see if there is any update

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

See

[GitHub] kafka pull request #862: KAFKA-3199: LoginManager should allow using an exis...

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

[jira] [Commented] (KAFKA-3199) LoginManager should allow using an existing Subject

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

[jira] [Commented] (KAFKA-5412) Using connect-console-sink/source.properties raises an exception related to "file" property not found

[ https://issues.apache.org/jira/browse/KAFKA-5412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043984#comment-16043984 ] Randall Hauch commented on KAFKA-5412: -- [~ppatierno], thanks! Go ahead and submit a p

[jira] [Commented] (KAFKA-5412) Using connect-console-sink/source.properties raises an exception related to "file" property not found

[ https://issues.apache.org/jira/browse/KAFKA-5412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043986#comment-16043986 ] Randall Hauch commented on KAFKA-5412: -- Please fix both the FileStreamSink and FileSt

[jira] [Commented] (KAFKA-5412) Using connect-console-sink/source.properties raises an exception related to "file" property not found

[ https://issues.apache.org/jira/browse/KAFKA-5412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043988#comment-16043988 ] Paolo Patierno commented on KAFKA-5412: --- Thanks [~rhauch] ! I'll do the PR ... Btw I

[jira] [Commented] (KAFKA-3925) Default log.dir=/tmp/kafka-logs is unsafe

[ https://issues.apache.org/jira/browse/KAFKA-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044002#comment-16044002 ] Paolo Patierno commented on KAFKA-3925: --- In my opinion, putting the log in /tmp is g

[jira] [Created] (KAFKA-5416) TransactionCoordinator seems to not return NOT_COORDINATOR error

Apurva Mehta created KAFKA-5416: --- Summary: TransactionCoordinator seems to not return NOT_COORDINATOR error Key: KAFKA-5416 URL: https://issues.apache.org/jira/browse/KAFKA-5416 Project: Kafka

[jira] [Updated] (KAFKA-5416) TransactionCoordinator seems to not return NOT_COORDINATOR error

[ https://issues.apache.org/jira/browse/KAFKA-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5416: Description: In regard to this system test: http://confluent-kafka-branch-builder-system-test-resul

[jira] [Commented] (KAFKA-5416) TransactionCoordinator seems to not return NOT_COORDINATOR error

[ https://issues.apache.org/jira/browse/KAFKA-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044045#comment-16044045 ] Apurva Mehta commented on KAFKA-5416: - cc [~guozhang] [~damianguy] A second pair of

[jira] [Updated] (KAFKA-5416) TransactionCoordinator seems to not return NOT_COORDINATOR error

[ https://issues.apache.org/jira/browse/KAFKA-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5416: Description: In regard to this system test: http://confluent-kafka-branch-builder-system-test-resul

[jira] [Updated] (KAFKA-5416) TransactionCoordinator seems to not return NOT_COORDINATOR error

[ https://issues.apache.org/jira/browse/KAFKA-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5416: Description: In regard to this system test: http://confluent-kafka-branch-builder-system-test-resul

[jira] [Updated] (KAFKA-5416) TransactionCoordinator seems to not return NOT_COORDINATOR error

[ https://issues.apache.org/jira/browse/KAFKA-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5416: Fix Version/s: 0.11.0.0 > TransactionCoordinator seems to not return NOT_COORDINATOR error > ---

[jira] [Updated] (KAFKA-5416) TransactionCoordinator seems to not return NOT_COORDINATOR error

[ https://issues.apache.org/jira/browse/KAFKA-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5416: Priority: Blocker (was: Major) > TransactionCoordinator seems to not return NOT_COORDINATOR error >

<    1   2