[jira] [Reopened] (KAFKA-5416) TransactionCoordinator doesn't complete transition to CompleteCommit

[ https://issues.apache.org/jira/browse/KAFKA-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reopened KAFKA-5416: - Assignee: Guozhang Wang This is not a dup of KAFKA-5415. Instead the cause for KAFKA-5415 explai

[jira] [Updated] (KAFKA-5416) TransactionCoordinator doesn't complete transition to CompleteCommit

[ 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 doesn't complete transition to CompleteCommit > ---

[jira] [Assigned] (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 reassigned KAFKA-5415: --- Assignee: Apurva Mehta (was: Guozhang Wang) > TransactionCoordinator gets stuck in PrepareCo

[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=16045051#comment-16045051 ] Apurva Mehta commented on KAFKA-5415: - [~guozhang]'s explanation above actually applie

[jira] [Updated] (KAFKA-5415) TransactionCoordinator doesn't complete transition to 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 doesn't complete transition to PrepareCommit state (was: Transactio

Re: [Vote] KIP-150 - Kafka-Streams Cogroup

+1 -Jay On Thu, Jun 8, 2017 at 11:16 AM, Guozhang Wang wrote: > I think we can continue on this voting thread. > > Currently we have one binding vote and 2 non-binging votes. I would like to > call out for other people especially committers to also take a look at this > proposal and vote. > > >

[jira] [Updated] (KAFKA-5422) Multiple produce request failures causes invalid state transition in TransactionManager

[ https://issues.apache.org/jira/browse/KAFKA-5422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5422: Fix Version/s: 0.11.0.0 > Multiple produce request failures causes invalid state transition in > Tr

Re: [ANNOUNCE] New committer: Damian Guy

Congrats Damian! Eno > On 9 Jun 2017, at 22:04, Ismael Juma wrote: > > Congratulations Damian! :) > > Ismael > > On Fri, Jun 9, 2017 at 9:34 PM, Guozhang Wang wrote: > >> Hello all, >> >> >> The PMC of Apache Kafka is pleased to announce that we have invited Damian >> Guy as a committer t

[GitHub] kafka pull request #3285: KAFKA-5422: Handle multiple transitions to ABORTAB...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/3285 KAFKA-5422: Handle multiple transitions to ABORTABLE_ERROR correctly You can merge this pull request into a Git repository by running: $ git pull https://github.com/apurvam/kafka KAFKA-5422-a

[jira] [Commented] (KAFKA-5422) Multiple produce request failures causes invalid state transition in TransactionManager

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

[jira] [Updated] (KAFKA-5422) Multiple produce request failures causes invalid state transition in TransactionManager

[ https://issues.apache.org/jira/browse/KAFKA-5422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5422: Status: Patch Available (was: Open) > Multiple produce request failures causes invalid state transi

Re: Changing JIRA notifications to remove Single Email Address (dev@kafka.apache.org)

+1 Thanks, Bill On Fri, Jun 9, 2017 at 4:56 PM, Gwen Shapira wrote: > +1, thank you > > On Fri, Jun 9, 2017 at 1:37 PM Jeff Widman wrote: > > > +1 > > > > Thanks for driving this > > > > On Jun 9, 2017 1:22 PM, "Guozhang Wang" wrote: > > > > > I have just confirmed with Jun that de cannot cha

Re: [ANNOUNCE] New committer: Damian Guy

Congrats Damian! On 6/9/17 2:25 PM, Eno Thereska wrote: > Congrats Damian! > > Eno >> On 9 Jun 2017, at 22:04, Ismael Juma wrote: >> >> Congratulations Damian! :) >> >> Ismael >> >> On Fri, Jun 9, 2017 at 9:34 PM, Guozhang Wang wrote: >> >>> Hello all, >>> >>> >>> The PMC of Apache Kafka is pl

Re: Changing JIRA notifications to remove Single Email Address (dev@kafka.apache.org)

+1 On 6/9/17 3:01 PM, Bill Bejeck wrote: > +1 > > Thanks, > Bill > > On Fri, Jun 9, 2017 at 4:56 PM, Gwen Shapira wrote: > >> +1, thank you >> >> On Fri, Jun 9, 2017 at 1:37 PM Jeff Widman wrote: >> >>> +1 >>> >>> Thanks for driving this >>> >>> On Jun 9, 2017 1:22 PM, "Guozhang Wang" wrote:

[jira] [Created] (KAFKA-5423) Broker fails with TopicExistException with auto topic creation enabled

Matthias J. Sax created KAFKA-5423: -- Summary: Broker fails with TopicExistException with auto topic creation enabled Key: KAFKA-5423 URL: https://issues.apache.org/jira/browse/KAFKA-5423 Project: Kaf

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

[ https://issues.apache.org/jira/browse/KAFKA-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicholas Ngorok updated KAFKA-5413: --- Attachment: .log 002148775326.index

Re: [ANNOUNCE] New committer: Damian Guy

Congrats Damian! :) On Fri, Jun 9, 2017 at 3:06 PM, Matthias J. Sax wrote: > Congrats Damian! > > On 6/9/17 2:25 PM, Eno Thereska wrote: > > Congrats Damian! > > > > Eno > >> On 9 Jun 2017, at 22:04, Ismael Juma wrote: > >> > >> Congratulations Damian! :) > >> > >> Ismael > >> > >> On Fri, Jun

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

[ https://issues.apache.org/jira/browse/KAFKA-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicholas Ngorok updated KAFKA-5413: --- Attachment: (was: 002148775326.index) > Log cleaner fails due to large offset in s

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

[ https://issues.apache.org/jira/browse/KAFKA-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicholas Ngorok updated KAFKA-5413: --- Attachment: 002147422683.log > Log cleaner fails due to large offset in segment file >

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

[ https://issues.apache.org/jira/browse/KAFKA-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicholas Ngorok updated KAFKA-5413: --- Attachment: (was: 002148098942.log) > Log cleaner fails due to large offset in seg

[jira] [Commented] (KAFKA-5415) TransactionCoordinator doesn't complete transition to PrepareCommit state

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045151#comment-16045151 ] Apurva Mehta commented on KAFKA-5415: - The problem here seem to be this check: https

[jira] [Commented] (KAFKA-5415) TransactionCoordinator doesn't complete transition to PrepareCommit state

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045162#comment-16045162 ] Apurva Mehta commented on KAFKA-5415: - The last successful metadata update was the fol

[jira] [Comment Edited] (KAFKA-5415) TransactionCoordinator doesn't complete transition to PrepareCommit state

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

Re: [ANNOUNCE] New committer: Damian Guy

Well deserved. Congratulations Damian! On Fri, Jun 9, 2017 at 1:34 PM Guozhang Wang wrote: > Hello all, > > > The PMC of Apache Kafka is pleased to announce that we have invited Damian > Guy as a committer to the project. > > Damian has made tremendous contributions to Kafka. He has not only > c

[GitHub] kafka pull request #3286: KAFKA-5415: Remove timestamp check in completeTran...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/3286 KAFKA-5415: Remove timestamp check in completeTransitionTo This assertion is hard to get right because the system time can roll backward on a host due to NTP (as shown in the ticket), and also becau

[jira] [Commented] (KAFKA-5415) TransactionCoordinator doesn't complete transition to PrepareCommit state

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

[GitHub] kafka pull request #3285: KAFKA-5422: Handle multiple transitions to ABORTAB...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3285 --- 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] [Updated] (KAFKA-5422) Multiple produce request failures causes invalid state transition in TransactionManager

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

[jira] [Commented] (KAFKA-5422) Multiple produce request failures causes invalid state transition in TransactionManager

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

[jira] [Updated] (KAFKA-5415) TransactionCoordinator doesn't complete transition to PrepareCommit state

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5415: Status: Patch Available (was: Open) > TransactionCoordinator doesn't complete transition to Prepare

[jira] [Comment Edited] (KAFKA-5415) TransactionCoordinator doesn't complete transition to PrepareCommit state

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044885#comment-16044885 ] Guozhang Wang edited comment on KAFKA-5415 at 6/9/17 10:59 PM: -

[GitHub] kafka pull request #3287: KAFKA-5416: Re-prepare transition to CompleteCommi...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/3287 KAFKA-5416: Re-prepare transition to CompleteCommit/Abort upon retrying append to log In `TransationStateManager`, we reset the pending state if an error occurred while appending to log; this

[jira] [Commented] (KAFKA-5416) TransactionCoordinator doesn't complete transition to CompleteCommit

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

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

See Changes: [jason] KAFKA-5422; Handle multiple transitions to ABORTABLE_ERROR correctly -- [...truncated 911.44 KB...] at org.gradle.internal.dispatch.ProxyDisp

[jira] [Comment Edited] (KAFKA-5415) TransactionCoordinator doesn't complete transition to PrepareCommit state

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044885#comment-16044885 ] Guozhang Wang edited comment on KAFKA-5415 at 6/9/17 11:28 PM: -

Re: [Vote] KIP-150 - Kafka-Streams Cogroup

+1 On Fri, Jun 9, 2017 at 2:24 PM, Jay Kreps wrote: > +1 > > -Jay > > On Thu, Jun 8, 2017 at 11:16 AM, Guozhang Wang wrote: > > > I think we can continue on this voting thread. > > > > Currently we have one binding vote and 2 non-binging votes. I would like > to > > call out for other people es

[jira] [Updated] (KAFKA-5415) TransactionCoordinator doesn't complete transition to PrepareCommit state

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

[GitHub] kafka pull request #3286: KAFKA-5415: Remove timestamp check in completeTran...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3286 --- 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-5415) TransactionCoordinator doesn't complete transition to PrepareCommit state

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

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

See

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

See Changes: [jason] KAFKA-5415; Remove timestamp check in completeTransitionTo -- [...truncated 22.13 MB...] at java.lang.Thread.run(Thread.java:745) Caused by: j

[jira] [Assigned] (KAFKA-4661) Improve test coverage UsePreviousTimeOnInvalidTimestamp

[ https://issues.apache.org/jira/browse/KAFKA-4661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeyhun Karimov reassigned KAFKA-4661: - Assignee: Jeyhun Karimov > Improve test coverage UsePreviousTimeOnInvalidTimestamp >

[jira] [Commented] (KAFKA-4661) Improve test coverage UsePreviousTimeOnInvalidTimestamp

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

[GitHub] kafka pull request #3288: KAFKA-4661: Improve test coverage UsePreviousTimeO...

GitHub user jeyhunkarimov opened a pull request: https://github.com/apache/kafka/pull/3288 KAFKA-4661: Improve test coverage UsePreviousTimeOnInvalidTimestamp You can merge this pull request into a Git repository by running: $ git pull https://github.com/jeyhunkarimov/kafka KA

[jira] [Created] (KAFKA-5424) KafkaConsumer.listTopics() throws Exception when unauthorized topics exist in cluster

Mike Fagan created KAFKA-5424: - Summary: KafkaConsumer.listTopics() throws Exception when unauthorized topics exist in cluster Key: KAFKA-5424 URL: https://issues.apache.org/jira/browse/KAFKA-5424 Project

[jira] [Commented] (KAFKA-2526) Console Producer / Consumer's serde config is not working

[ https://issues.apache.org/jira/browse/KAFKA-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045296#comment-16045296 ] huxihx commented on KAFKA-2526: --- [~guozhang] No, I am thinking [~mgharat] is working on this

[GitHub] kafka-site pull request #60: Update delivery semantics section for KIP-98

Github user ijuma commented on a diff in the pull request: https://github.com/apache/kafka-site/pull/60#discussion_r121246131 --- Diff: 0110/design.html --- @@ -261,15 +262,23 @@ It can read the messages, process the messages, and finally save its position. In this case th

[GitHub] kafka-site pull request #60: Update delivery semantics section for KIP-98

Github user ijuma commented on a diff in the pull request: https://github.com/apache/kafka-site/pull/60#discussion_r121246230 --- Diff: 0110/design.html --- @@ -261,15 +262,23 @@ It can read the messages, process the messages, and finally save its position. In this case th

[jira] [Commented] (KAFKA-5424) KafkaConsumer.listTopics() throws Exception when unauthorized topics exist in cluster

[ https://issues.apache.org/jira/browse/KAFKA-5424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045301#comment-16045301 ] Ismael Juma commented on KAFKA-5424: Thanks for the report. Can you specify the versio

[jira] [Updated] (KAFKA-5416) TransactionCoordinator doesn't complete transition to CompleteCommit

[ https://issues.apache.org/jira/browse/KAFKA-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5416: --- Status: Patch Available (was: Reopened) > TransactionCoordinator doesn't complete transition to Compl

[jira] [Updated] (KAFKA-5417) Clients get inconsistent connection states when SASL/SSL connection is marked CONECTED and DISCONNECTED at the same time

[ https://issues.apache.org/jira/browse/KAFKA-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5417: --- Fix Version/s: 0.11.0.0 > Clients get inconsistent connection states when SASL/SSL connection is marke

Re: [DISCUSS] KIP-113: Support replicas movement between log directories

Just a few comments on this. 1. One of the issues with using RAID 0 is that a single disk failure causes a hard failure of the broker. Hard failure increases the unavailability window for all the partitions on the failed broker, which includes the failure detection time (tied to ZK session timeout

Re: [ANNOUNCE] New committer: Damian Guy

Congrats! ~ Joe Stein On Fri, Jun 9, 2017 at 6:49 PM, Neha Narkhede wrote: > Well deserved. Congratulations Damian! > > On Fri, Jun 9, 2017 at 1:34 PM Guozhang Wang wrote: > > > Hello all, > > > > > > The PMC of Apache Kafka is pleased to announce that we have invited > Damian > > Guy as a co

[jira] [Commented] (KAFKA-5418) ZkUtils.getAllPartitions() may fail if a topic is marked for deletion

[ https://issues.apache.org/jira/browse/KAFKA-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045321#comment-16045321 ] huxihx commented on KAFKA-5418: --- Is it a duplicate of [KAFKA-1019|https://issues.apache.org

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

See

[jira] [Updated] (KAFKA-5286) Producer should await transaction completion in close

[ https://issues.apache.org/jira/browse/KAFKA-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5286: Fix Version/s: (was: 0.11.0.0) 0.11.0.1 > Producer should await transaction c

[jira] [Updated] (KAFKA-5342) Distinguish abortable failures in transactional producer

[ https://issues.apache.org/jira/browse/KAFKA-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5342: Fix Version/s: (was: 0.11.0.0) 0.11.0.1 > Distinguish abortable failures in t

[jira] [Created] (KAFKA-5425) Kafka replication support all log segment files sync with leader

Pengwei created KAFKA-5425: -- Summary: Kafka replication support all log segment files sync with leader Key: KAFKA-5425 URL: https://issues.apache.org/jira/browse/KAFKA-5425 Project: Kafka Issue Typ

[GitHub] kafka-site pull request #60: Update delivery semantics section for KIP-98

Github user hachikuji commented on a diff in the pull request: https://github.com/apache/kafka-site/pull/60#discussion_r121249508 --- Diff: 0110/design.html --- @@ -261,15 +262,23 @@ It can read the messages, process the messages, and finally save its position. In this cas

[GitHub] kafka-site pull request #60: Update delivery semantics section for KIP-98

Github user hachikuji commented on a diff in the pull request: https://github.com/apache/kafka-site/pull/60#discussion_r121249550 --- Diff: 0110/design.html --- @@ -261,15 +262,23 @@ It can read the messages, process the messages, and finally save its position. In this cas

[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: TransactionMarkerChannelManager seems not to retry failed writes.

[ https://issues.apache.org/jira/browse/KAFKA-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5416: Summary: TransactionCoordinator: TransactionMarkerChannelManager seems not to retry failed writes.

[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: Labels: exactly-once (was: ) > TransactionCoordinator seems to not return NOT_COORDINATOR error > -

[jira] [Commented] (KAFKA-5416) TransactionCoordinator: TransactionMarkerChannelManager seems not to retry failed writes.

[ https://issues.apache.org/jira/browse/KAFKA-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044073#comment-16044073 ] Apurva Mehta commented on KAFKA-5416: - Actually, my grep was bad. the 'retrying:' mess

[jira] [Comment Edited] (KAFKA-5416) TransactionCoordinator: TransactionMarkerChannelManager seems not to retry failed writes.

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

[jira] [Commented] (KAFKA-5416) TransactionCoordinator: TransactionMarkerChannelManager seems not to retry failed writes.

[ https://issues.apache.org/jira/browse/KAFKA-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044081#comment-16044081 ] Apurva Mehta commented on KAFKA-5416: - It appears the 'CompleteCommit' was written to

[jira] [Resolved] (KAFKA-5416) TransactionCoordinator: TransactionMarkerChannelManager seems not to retry failed writes.

[ https://issues.apache.org/jira/browse/KAFKA-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta resolved KAFKA-5416. - Resolution: Duplicate After more digging, this appears to be a duplicate of KAFKA-5415, but the ex

[jira] [Updated] (KAFKA-5416) TransactionCoordinator: TransactionMarkerChannelManager seems not to retry failed writes.

[ 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: (was: 0.11.0.0) > TransactionCoordinator: TransactionMarkerChannelManager seems n

[jira] [Commented] (KAFKA-5402) JmxReporter Fetch metrics for kafka.server should not be created when client quotas are not enabled

[ https://issues.apache.org/jira/browse/KAFKA-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044100#comment-16044100 ] Rajini Sivaram commented on KAFKA-5402: --- [~junrao] Yes, agree that these metrics are

[jira] [Assigned] (KAFKA-5402) JmxReporter Fetch metrics for kafka.server should not be created when client quotas are not enabled

[ https://issues.apache.org/jira/browse/KAFKA-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-5402: - Assignee: Rajini Sivaram > JmxReporter Fetch metrics for kafka.server should not be creat

[jira] [Commented] (KAFKA-5246) Remove backdoor that allows any client to produce to internal topics

[ https://issues.apache.org/jira/browse/KAFKA-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044179#comment-16044179 ] Michal Borowiecki commented on KAFKA-5246: -- Would it instead perhaps make sense t

[GitHub] kafka pull request #3279: KAFKA-5412: Using connect-console-sink/source.prop...

GitHub user ppatierno opened a pull request: https://github.com/apache/kafka/pull/3279 KAFKA-5412: Using connect-console-sink/source.properties raises an exception related to "file" property not found You can merge this pull request into a Git repository by running: $ git pul

[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=16044181#comment-16044181 ] ASF GitHub Bot commented on KAFKA-5412: --- GitHub user ppatierno opened a pull request

Re: Re: synchronous request response using kafka

cc-ed users mailing list, as I think it's more appropriate for this thread. Sanjay, if you what you're after is the following pattern: http://www.enterpriseintegrationpatterns.com/patterns/messaging/RequestReplyJmsExample.html then yes, you can do this in kafka. The outline would be similar to

[GitHub] kafka pull request #3280: Avoid calling interceptors.onSendError() with null...

GitHub user tombentley opened a pull request: https://github.com/apache/kafka/pull/3280 Avoid calling interceptors.onSendError() with null TopicPartition Assign non-null tp as soon as possible once we know the partition. This is so that if ensureValidRecordSize() throws, the

[GitHub] kafka pull request #3281: KAFKA-5388 Replace zkClient.subscribe*Changes meth...

GitHub user baluchicken opened a pull request: https://github.com/apache/kafka/pull/3281 KAFKA-5388 Replace zkClient.subscribe*Changes method with an equivalent zkUtils method @ijuma can you please review if you have time:) ? You can merge this pull request into a Git repository by

[jira] [Commented] (KAFKA-5388) Replace zkClient.subscribe*Changes method with an equivalent zkUtils method

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

[jira] [Updated] (KAFKA-5388) Replace zkClient.subscribe*Changes method with an equivalent zkUtils method

[ https://issues.apache.org/jira/browse/KAFKA-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balint Molnar updated KAFKA-5388: - Status: Patch Available (was: In Progress) > Replace zkClient.subscribe*Changes method with an eq

[jira] [Created] (KAFKA-5417) Clients get inconsistent connection states when SASL/SSL connection is marked CONECTED and DISCONNECTED at the same time

dongeforever created KAFKA-5417: --- Summary: Clients get inconsistent connection states when SASL/SSL connection is marked CONECTED and DISCONNECTED at the same time Key: KAFKA-5417 URL: https://issues.apache.org/jira

[GitHub] kafka pull request #3282: [KAFKA-5417] Clients get inconsistent connection s...

GitHub user dongeforever opened a pull request: https://github.com/apache/kafka/pull/3282 [KAFKA-5417] Clients get inconsistent connection states when SASL/SSL… … connection is marked CONECTED and DISCONNECTED at the same time details are in: https://issues.apache.or

[jira] [Commented] (KAFKA-5417) Clients get inconsistent connection states when SASL/SSL connection is marked CONECTED and DISCONNECTED at the same time

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

[jira] [Updated] (KAFKA-5418) ZkUtils.getAllPartitions() may fail if a topic is marked for deletion

[ https://issues.apache.org/jira/browse/KAFKA-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edoardo Comar updated KAFKA-5418: - Description: Running {{ZkUtils.getAllPartitions()}} on a cluster which had a topic stuck in the '

[jira] [Created] (KAFKA-5418) ZkUtils.getAllPartitions() may fail if a topic is marked for deletion

Edoardo Comar created KAFKA-5418: Summary: ZkUtils.getAllPartitions() may fail if a topic is marked for deletion Key: KAFKA-5418 URL: https://issues.apache.org/jira/browse/KAFKA-5418 Project: Kafka

[jira] [Updated] (KAFKA-5418) ZkUtils.getAllPartitions() may fail if a topic is marked for deletion

[ https://issues.apache.org/jira/browse/KAFKA-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edoardo Comar updated KAFKA-5418: - Description: Running {{ZkUtils.getAllPartitions()}} on a cluster which had a topic stuck in the '

[jira] [Commented] (KAFKA-1955) Explore disk-based buffering in new Kafka Producer

[ https://issues.apache.org/jira/browse/KAFKA-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044512#comment-16044512 ] Brandon Bradley commented on KAFKA-1955: [~cmccabe] I was trying to stick to this

Kafka Multiple Node Installation

Hello Guys, I've been working on setting up a multi node Kafka deployment and need help on it. I've been able to set up a 3 node cluster but am running into issues (performance and getting errors too) every few hours. I've attached the steps that I used to set up the cluster. Can someone pl

[jira] [Created] (KAFKA-5419) Console consumer --key-deserializer and --value-deserializer are always overwritten by ByteArrayDeserializer

Paolo Patierno created KAFKA-5419: - Summary: Console consumer --key-deserializer and --value-deserializer are always overwritten by ByteArrayDeserializer Key: KAFKA-5419 URL: https://issues.apache.org/jira/browse/

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

[ https://issues.apache.org/jira/browse/KAFKA-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044555#comment-16044555 ] Federico Giraud commented on KAFKA-5413: More details (I'm investigating the same

[jira] [Commented] (KAFKA-5419) Console consumer --key-deserializer and --value-deserializer are always overwritten by ByteArrayDeserializer

[ https://issues.apache.org/jira/browse/KAFKA-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044557#comment-16044557 ] Michal Borowiecki commented on KAFKA-5419: -- I think it's a duplicate of KAFKA-252

[jira] [Comment Edited] (KAFKA-5419) Console consumer --key-deserializer and --value-deserializer are always overwritten by ByteArrayDeserializer

[ https://issues.apache.org/jira/browse/KAFKA-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044557#comment-16044557 ] Michal Borowiecki edited comment on KAFKA-5419 at 6/9/17 3:41 PM: --

[jira] [Comment Edited] (KAFKA-5419) Console consumer --key-deserializer and --value-deserializer are always overwritten by ByteArrayDeserializer

[ https://issues.apache.org/jira/browse/KAFKA-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044557#comment-16044557 ] Michal Borowiecki edited comment on KAFKA-5419 at 6/9/17 3:42 PM: --

[jira] [Created] (KAFKA-5420) Console producer --key-serializer and --value-serializer are always overwritten by ByteArraySerializer

Paolo Patierno created KAFKA-5420: - Summary: Console producer --key-serializer and --value-serializer are always overwritten by ByteArraySerializer Key: KAFKA-5420 URL: https://issues.apache.org/jira/browse/KAFKA-

[jira] [Updated] (KAFKA-5420) Console producer --key-serializer and --value-serializer are always overwritten by ByteArraySerializer

[ https://issues.apache.org/jira/browse/KAFKA-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paolo Patierno updated KAFKA-5420: -- Description: Hi, the --key-serializer and --value-serializer options passed to the command line

[jira] [Updated] (KAFKA-5419) Console consumer --key-deserializer and --value-deserializer are always overwritten by ByteArrayDeserializer

[ https://issues.apache.org/jira/browse/KAFKA-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paolo Patierno updated KAFKA-5419: -- Description: Hi, the --key-deserializer and --value-deserializer options passed to the command

[jira] [Created] (KAFKA-5421) Getting InvalidRecordException

Rishi Reddy Bokka created KAFKA-5421: Summary: Getting InvalidRecordException Key: KAFKA-5421 URL: https://issues.apache.org/jira/browse/KAFKA-5421 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-5419) Console consumer --key-deserializer and --value-deserializer are always overwritten by ByteArrayDeserializer

[ https://issues.apache.org/jira/browse/KAFKA-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044572#comment-16044572 ] Paolo Patierno commented on KAFKA-5419: --- Yes I think you are right sorry. I'm going

[jira] [Resolved] (KAFKA-5419) Console consumer --key-deserializer and --value-deserializer are always overwritten by ByteArrayDeserializer

[ https://issues.apache.org/jira/browse/KAFKA-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paolo Patierno resolved KAFKA-5419. --- Resolution: Duplicate Duplicate of KAFKA-2526 > Console consumer --key-deserializer and --val

[jira] [Resolved] (KAFKA-5420) Console producer --key-serializer and --value-serializer are always overwritten by ByteArraySerializer

[ https://issues.apache.org/jira/browse/KAFKA-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paolo Patierno resolved KAFKA-5420. --- Resolution: Duplicate Duplicate of KAFKA-2526 > Console producer --key-serializer and --value

[jira] [Updated] (KAFKA-5421) Getting InvalidRecordException

[ https://issues.apache.org/jira/browse/KAFKA-5421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishi Reddy Bokka updated KAFKA-5421: - Affects Version/s: 0.9.0.1 > Getting InvalidRecordException >

[GitHub] kafka pull request #3283: KAFKA-2170: Updated Fixes For Windows Platform

GitHub user nxmbriggs404 opened a pull request: https://github.com/apache/kafka/pull/3283 KAFKA-2170: Updated Fixes For Windows Platform During stress testing of kafka 0.10.2.1 on a Windows platform, our group has encountered some issues that appear to be known to the community but

  1   2   >