[jira] [Comment Edited] (KAFKA-5403) Transactions system test should dedup consumed messages by offset

[ https://issues.apache.org/jira/browse/KAFKA-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129866#comment-16129866 ] Apurva Mehta edited comment on KAFKA-5403 at 8/17/17 4:19 AM: -- I think we

[jira] [Updated] (KAFKA-5543) We don't remove the LastStableOffsetLag metric when a partition is moved away from a broker

[ https://issues.apache.org/jira/browse/KAFKA-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5543: Fix Version/s: (was: 0.11.0.1) 1.0.0 > We don't remove the

[jira] [Updated] (KAFKA-5482) A CONCURRENT_TRANASCTIONS error for the first AddPartitionsToTxn request slows down transactions significantly

[ https://issues.apache.org/jira/browse/KAFKA-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5482: Fix Version/s: (was: 0.11.0.2) 1.0.0 > A CONCURRENT_TRANASCTIONS error for

[jira] [Commented] (KAFKA-5482) A CONCURRENT_TRANASCTIONS error for the first AddPartitionsToTxn request slows down transactions significantly

[ https://issues.apache.org/jira/browse/KAFKA-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129870#comment-16129870 ] Apurva Mehta commented on KAFKA-5482: - The proposed solution is involved and cannot be part of the

[jira] [Updated] (KAFKA-5347) OutOfSequence error should be fatal

[ https://issues.apache.org/jira/browse/KAFKA-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5347: Fix Version/s: (was: 0.11.0.2) 1.0.0 > OutOfSequence error should be fatal >

[jira] [Updated] (KAFKA-5284) Add tools and metrics to diagnose problems with the idempotent producer and transactions

[ https://issues.apache.org/jira/browse/KAFKA-5284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5284: Fix Version/s: (was: 0.11.0.2) 1.0.0 > Add tools and metrics to diagnose

[jira] [Commented] (KAFKA-5403) Transactions system test should dedup consumed messages by offset

[ https://issues.apache.org/jira/browse/KAFKA-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129866#comment-16129866 ] Apurva Mehta commented on KAFKA-5403: - I think we should punt on this. The problems with the patch are

[jira] [Assigned] (KAFKA-5745) Partition.makeLeader() should convert HW to OffsetMetadata before becoming the leader

[ https://issues.apache.org/jira/browse/KAFKA-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-5745: - Assignee: huxihx > Partition.makeLeader() should convert HW to OffsetMetadata before becoming > the

[jira] [Commented] (KAFKA-5745) Partition.makeLeader() should convert HW to OffsetMetadata before becoming the leader

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

[jira] [Commented] (KAFKA-5676) MockStreamsMetrics should be in o.a.k.test

[ https://issues.apache.org/jira/browse/KAFKA-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129758#comment-16129758 ] Chanchal Singh commented on KAFKA-5676: --- testMetrics() in all three classes seems to be depend on a

[jira] [Commented] (KAFKA-5745) Partition.makeLeader() should convert HW to OffsetMetadata before becoming the leader

[ https://issues.apache.org/jira/browse/KAFKA-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129725#comment-16129725 ] Jun Rao commented on KAFKA-5745: The HW in the follower only includes the offset, but not the log segment

[jira] [Created] (KAFKA-5745) Partition.makeLeader() should convert HW to OffsetMetadata before becoming the leader

Jun Rao created KAFKA-5745: -- Summary: Partition.makeLeader() should convert HW to OffsetMetadata before becoming the leader Key: KAFKA-5745 URL: https://issues.apache.org/jira/browse/KAFKA-5745 Project:

[jira] [Commented] (KAFKA-5233) Changes to punctuate semantics (KIP-138)

[ https://issues.apache.org/jira/browse/KAFKA-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129646#comment-16129646 ] Guozhang Wang commented on KAFKA-5233: -- Thanks [~mihbor]! > Changes to punctuate semantics (KIP-138)

[jira] [Commented] (KAFKA-5733) System tests get exception RocksDBException: db has more levels than options.num_levels

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

[jira] [Commented] (KAFKA-5743) All ducktape services should store their files in subdirectories of /mnt

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

[jira] [Updated] (KAFKA-5743) All ducktape services should store their files in subdirectories of /mnt

[ https://issues.apache.org/jira/browse/KAFKA-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-5743: --- Description: Currently, some ducktape services like KafkaService store their files directly

[jira] [Updated] (KAFKA-5743) All ducktape services should store their files in subdirectories of /mnt

[ https://issues.apache.org/jira/browse/KAFKA-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-5743: --- Summary: All ducktape services should store their files in subdirectories of /mnt (was:

[jira] [Commented] (KAFKA-5744) ShellTest: add tests for attempting to run nonexistent program, error return

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

[jira] [Created] (KAFKA-5744) ShellTest: add tests for attempting to run nonexistent program, error return

Colin P. McCabe created KAFKA-5744: -- Summary: ShellTest: add tests for attempting to run nonexistent program, error return Key: KAFKA-5744 URL: https://issues.apache.org/jira/browse/KAFKA-5744

[jira] [Commented] (KAFKA-5076) Remove usage of java.xml.bind.* classes hidden by default in JDK9

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

[jira] [Commented] (KAFKA-5233) Changes to punctuate semantics (KIP-138)

[ https://issues.apache.org/jira/browse/KAFKA-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129556#comment-16129556 ] Michal Borowiecki commented on KAFKA-5233: -- Hi [~guozhang], I had a look at KStreamTestDriver

[jira] [Created] (KAFKA-5743) Ducktape services should store their files in subdirectories of /mnt

Colin P. McCabe created KAFKA-5743: -- Summary: Ducktape services should store their files in subdirectories of /mnt Key: KAFKA-5743 URL: https://issues.apache.org/jira/browse/KAFKA-5743 Project:

[jira] [Commented] (KAFKA-5233) Changes to punctuate semantics (KIP-138)

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

[jira] [Resolved] (KAFKA-5567) With transformations that mutate the topic-partition committing offsets should to refer to the original topic-partition

[ https://issues.apache.org/jira/browse/KAFKA-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5567. -- Resolution: Fixed > With transformations that mutate the topic-partition

[jira] [Commented] (KAFKA-5742) Support passing ZK chroot in system tests

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

[jira] [Assigned] (KAFKA-5742) Support passing ZK chroot in system tests

[ https://issues.apache.org/jira/browse/KAFKA-5742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté reassigned KAFKA-5742: Assignee: Xavier Léauté > Support passing ZK chroot in system tests >

[jira] [Created] (KAFKA-5742) Support passing ZK chroot in system tests

Xavier Léauté created KAFKA-5742: Summary: Support passing ZK chroot in system tests Key: KAFKA-5742 URL: https://issues.apache.org/jira/browse/KAFKA-5742 Project: Kafka Issue Type: Test

[jira] [Commented] (KAFKA-5740) Use separate file for HTTP logs

[ https://issues.apache.org/jira/browse/KAFKA-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129389#comment-16129389 ] CJ Woolard commented on KAFKA-5740: --- For deployments in Mesos, where you typically have a scheduled

[jira] [Updated] (KAFKA-5441) Fix transaction marker grouping by producerId in TC

[ https://issues.apache.org/jira/browse/KAFKA-5441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5441: - Fix Version/s: (was: 0.11.0.1) 0.11.0.2 1.0.0 > Fix

[jira] [Commented] (KAFKA-5441) Fix transaction marker grouping by producerId in TC

[ https://issues.apache.org/jira/browse/KAFKA-5441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129239#comment-16129239 ] Guozhang Wang commented on KAFKA-5441: -- I'll not do it for 0.11.0.1, moving to 0.11.0.1 / 1.0.0 for

[jira] [Commented] (KAFKA-5545) Kafka Stream not able to successfully restart over new broker ip

[ https://issues.apache.org/jira/browse/KAFKA-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129229#comment-16129229 ] Yogesh BG commented on KAFKA-5545: -- thank you > Kafka Stream not able to successfully restart over

[jira] [Updated] (KAFKA-5545) Kafka Stream not able to successfully restart over new broker ip

[ https://issues.apache.org/jira/browse/KAFKA-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5545: - Fix Version/s: 1.0.0 0.11.0.1 > Kafka Stream not able to successfully restart

[jira] [Commented] (KAFKA-5545) Kafka Stream not able to successfully restart over new broker ip

[ https://issues.apache.org/jira/browse/KAFKA-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129204#comment-16129204 ] Guozhang Wang commented on KAFKA-5545: -- [~yogeshbelur] We have KAFKA-5152 which summarizes the root

[jira] [Resolved] (KAFKA-3796) SslTransportLayerTest.testInvalidEndpointIdentification fails on trunk

[ https://issues.apache.org/jira/browse/KAFKA-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3796. -- Resolution: Cannot Reproduce Pl reopen if you think the issue still exists >

[jira] [Updated] (KAFKA-5696) SourceConnector does not commit offset on rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-5696: - Priority: Critical (was: Major) > SourceConnector does not commit offset on rebalance >

[jira] [Updated] (KAFKA-5741) Prioritize threads in Connect distributed worker process

[ https://issues.apache.org/jira/browse/KAFKA-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-5741: - Priority: Critical (was: Blocker) > Prioritize threads in Connect distributed worker process >

[jira] [Updated] (KAFKA-5696) SourceConnector does not commit offset on rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-5696: - Fix Version/s: (was: 0.10.0.2) > SourceConnector does not commit offset on rebalance >

[jira] [Resolved] (KAFKA-4813) 2h6R1

[ https://issues.apache.org/jira/browse/KAFKA-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4813. -- Resolution: Invalid > 2h6R1 > - > > Key: KAFKA-4813 > URL:

[jira] [Resolved] (KAFKA-4803) OT6Y1

[ https://issues.apache.org/jira/browse/KAFKA-4803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4803. -- Resolution: Invalid > OT6Y1 > - > > Key: KAFKA-4803 > URL:

[jira] [Resolved] (KAFKA-4821) 9244L

[ https://issues.apache.org/jira/browse/KAFKA-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4821. -- Resolution: Invalid > 9244L > - > > Key: KAFKA-4821 > URL:

[jira] [Resolved] (KAFKA-4804) TdOZY

[ https://issues.apache.org/jira/browse/KAFKA-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4804. -- Resolution: Invalid > TdOZY > - > > Key: KAFKA-4804 > URL:

[jira] [Resolved] (KAFKA-4847) 1Y30J

[ https://issues.apache.org/jira/browse/KAFKA-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4847. -- Resolution: Invalid > 1Y30J > - > > Key: KAFKA-4847 > URL:

[jira] [Resolved] (KAFKA-4865) 2X8BF

[ https://issues.apache.org/jira/browse/KAFKA-4865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4865. -- Resolution: Invalid > 2X8BF > - > > Key: KAFKA-4865 > URL:

[jira] [Resolved] (KAFKA-4889) 2G8lc

[ https://issues.apache.org/jira/browse/KAFKA-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4889. -- Resolution: Invalid > 2G8lc > - > > Key: KAFKA-4889 > URL:

[jira] [Resolved] (KAFKA-4951) KafkaProducer may send duplicated message sometimes

[ https://issues.apache.org/jira/browse/KAFKA-4951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4951. -- Resolution: Fixed This scenario is handled in the Idempotent producer (KIP-98) released in Kafka

[jira] [Created] (KAFKA-5740) Use separate file for HTTP logs

Randall Hauch created KAFKA-5740: Summary: Use separate file for HTTP logs Key: KAFKA-5740 URL: https://issues.apache.org/jira/browse/KAFKA-5740 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-5723) Refactor BrokerApiVersionsCommand to use the new AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128985#comment-16128985 ] Andrey Dyachkov commented on KAFKA-5723: [~ppatierno] thank you for clarification, as you can see

[jira] [Commented] (KAFKA-5723) Refactor BrokerApiVersionsCommand to use the new AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128973#comment-16128973 ] Paolo Patierno commented on KAFKA-5723: --- [~adyachkov] sure you can. I think that for having more

[jira] [Commented] (KAFKA-4834) Kafka cannot delete topic with ReplicaStateMachine went wrong

[ https://issues.apache.org/jira/browse/KAFKA-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128899#comment-16128899 ] Ismael Juma commented on KAFKA-4834: cc [~junrao] [~onurkaraman] > Kafka cannot delete topic with

[jira] [Updated] (KAFKA-4834) Kafka cannot delete topic with ReplicaStateMachine went wrong

[ https://issues.apache.org/jira/browse/KAFKA-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4834: --- Component/s: controller > Kafka cannot delete topic with ReplicaStateMachine went wrong >

[jira] [Commented] (KAFKA-4834) Kafka cannot delete topic with ReplicaStateMachine went wrong

[ https://issues.apache.org/jira/browse/KAFKA-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128881#comment-16128881 ] Joao Santos commented on KAFKA-4834: We are experiencing exactly the same issue on 0.11.0.0. Here is

[jira] [Commented] (KAFKA-5714) Allow whitespaces in the principal name

[ https://issues.apache.org/jira/browse/KAFKA-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128831#comment-16128831 ] Manikumar commented on KAFKA-5714: -- >>The point is, that I am expecting the same behavior, whether I put

[jira] [Commented] (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:comment-tabpanel=16128797#comment-16128797 ] ASF GitHub Bot commented on KAFKA-5152: --- GitHub user dguy opened a pull request:

[jira] [Commented] (KAFKA-5739) Rewrite KStreamPeekTest at processor level avoiding driver usage

[ https://issues.apache.org/jira/browse/KAFKA-5739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128795#comment-16128795 ] Paolo Patierno commented on KAFKA-5739: --- [~damianguy] what do you think about that ? > Rewrite

[jira] [Created] (KAFKA-5739) Rewrite KStreamPeekTest at processor level avoiding driver usage

Paolo Patierno created KAFKA-5739: - Summary: Rewrite KStreamPeekTest at processor level avoiding driver usage Key: KAFKA-5739 URL: https://issues.apache.org/jira/browse/KAFKA-5739 Project: Kafka

[jira] [Commented] (KAFKA-5054) ChangeLoggingKeyValueByteStore delete and putIfAbsent should be synchronized

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

[jira] [Commented] (KAFKA-5546) Temporary loss of availability data when the leader is disconnected

[ https://issues.apache.org/jira/browse/KAFKA-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128785#comment-16128785 ] Ismael Juma commented on KAFKA-5546: What guarantees are you aiming for? You can tweak timeouts like

[jira] [Resolved] (KAFKA-5611) One or more consumers in a consumer-group stop consuming after rebalancing

[ https://issues.apache.org/jira/browse/KAFKA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5611. Resolution: Fixed I'm going to mark this as closed. If [~pskianis] or someone else can still see

[jira] [Resolved] (KAFKA-3087) Fix documentation for retention.ms property and update documentation for LogConfig.scala class

[ https://issues.apache.org/jira/browse/KAFKA-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3087. -- Resolution: Fixed This doc issue was fixed in newer Kafka versions. > Fix documentation for

[jira] [Commented] (KAFKA-5737) KafkaAdminClient thread should be daemon

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

[jira] [Created] (KAFKA-5738) Add cumulative count attribute for all Kafka rate metrics

Rajini Sivaram created KAFKA-5738: - Summary: Add cumulative count attribute for all Kafka rate metrics Key: KAFKA-5738 URL: https://issues.apache.org/jira/browse/KAFKA-5738 Project: Kafka

[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 ] Damian Guy updated KAFKA-5152: -- Fix Version/s: (was: 0.10.2.2) 1.0.0 > Kafka Streams keeps restoring state after

[jira] [Updated] (KAFKA-4950) ConcurrentModificationException when iterating over Kafka Metrics

[ https://issues.apache.org/jira/browse/KAFKA-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4950: --- Fix Version/s: (was: 0.11.0.1) 0.11.0.2 > ConcurrentModificationException when

[jira] [Updated] (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 ] Ismael Juma updated KAFKA-5327: --- Fix Version/s: (was: 0.11.0.1) 1.0.0 > Console Consumer should only poll for

[jira] [Commented] (KAFKA-5543) We don't remove the LastStableOffsetLag metric when a partition is moved away from a broker

[ https://issues.apache.org/jira/browse/KAFKA-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128622#comment-16128622 ] Ismael Juma commented on KAFKA-5543: [~apurva], will this make it to 0.11.0.1 (happening soon) or

[jira] [Commented] (KAFKA-5503) Idempotent producer ignores shutdown while fetching ProducerId

[ https://issues.apache.org/jira/browse/KAFKA-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128621#comment-16128621 ] Ismael Juma commented on KAFKA-5503: [~evis], do you intend to submit a PR for this soon? Otherwise,

[jira] [Updated] (KAFKA-5482) A CONCURRENT_TRANASCTIONS error for the first AddPartitionsToTxn request slows down transactions significantly

[ https://issues.apache.org/jira/browse/KAFKA-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5482: --- Fix Version/s: (was: 0.11.0.1) 0.11.0.2 > A CONCURRENT_TRANASCTIONS error for

[jira] [Commented] (KAFKA-5441) Fix transaction marker grouping by producerId in TC

[ https://issues.apache.org/jira/browse/KAFKA-5441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128619#comment-16128619 ] Ismael Juma commented on KAFKA-5441: [~guozhang], are you planning to do this for 0.11.0.1 or shall we

[jira] [Updated] (KAFKA-5383) Additional Test Cases for ReplicaManager

[ https://issues.apache.org/jira/browse/KAFKA-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5383: --- Fix Version/s: (was: 0.11.0.1) 1.0.0 > Additional Test Cases for

[jira] [Updated] (KAFKA-5284) Add tools and metrics to diagnose problems with the idempotent producer and transactions

[ https://issues.apache.org/jira/browse/KAFKA-5284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5284: --- Fix Version/s: (was: 0.11.0.1) 0.11.0.2 > Add tools and metrics to diagnose

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

[ https://issues.apache.org/jira/browse/KAFKA-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128617#comment-16128617 ] Ismael Juma commented on KAFKA-5342: [~hachikuji], we are starting to plan 0.11.0.1. Do we expect to

[jira] [Updated] (KAFKA-3955) Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading to failed broker boot

[ https://issues.apache.org/jira/browse/KAFKA-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3955: --- Fix Version/s: (was: 0.11.0.1) 0.11.0.2 > Kafka log recovery doesn't truncate

[jira] [Updated] (KAFKA-5347) OutOfSequence error should be fatal

[ https://issues.apache.org/jira/browse/KAFKA-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5347: --- Fix Version/s: (was: 0.11.0.1) 0.11.0.2 > OutOfSequence error should be fatal

[jira] [Updated] (KAFKA-4972) Kafka 0.10.0 Found a corrupted index file during Kafka broker startup

[ https://issues.apache.org/jira/browse/KAFKA-4972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4972: --- Fix Version/s: (was: 0.11.0.1) 0.11.0.2 > Kafka 0.10.0 Found a corrupted

[jira] [Updated] (KAFKA-1923) Negative offsets in replication-offset-checkpoint file

[ https://issues.apache.org/jira/browse/KAFKA-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1923: --- Fix Version/s: (was: 0.11.0.1) 0.11.0.2 > Negative offsets in

[jira] [Updated] (KAFKA-5026) DebuggingConsumerId and DebuggingMessageFormatter and message format v2

[ https://issues.apache.org/jira/browse/KAFKA-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5026: --- Fix Version/s: (was: 0.11.0.1) 0.11.0.2 > DebuggingConsumerId and

[jira] [Commented] (KAFKA-5403) Transactions system test should dedup consumed messages by offset

[ https://issues.apache.org/jira/browse/KAFKA-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128614#comment-16128614 ] Ismael Juma commented on KAFKA-5403: [~apurva], we are starting to plan 0.11.0.1. Will this be ready

[jira] [Updated] (KAFKA-4686) Null Message payload is shutting down broker

[ https://issues.apache.org/jira/browse/KAFKA-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4686: --- Fix Version/s: (was: 0.11.0.1) 0.11.0.2 > Null Message payload is shutting

[jira] [Updated] (KAFKA-5272) Improve validation for Alter Configs (KIP-133)

[ https://issues.apache.org/jira/browse/KAFKA-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5272: --- Fix Version/s: (was: 0.11.0.1) 0.11.1.0 > Improve validation for Alter Configs

[jira] [Updated] (KAFKA-3689) Exception when attempting to decrease connection count for address with no connections

[ https://issues.apache.org/jira/browse/KAFKA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3689: --- Fix Version/s: (was: 0.11.0.1) 0.11.0.2 > Exception when attempting to

[jira] [Commented] (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:comment-tabpanel=16128595#comment-16128595 ] ASF GitHub Bot commented on KAFKA-5152: --- Github user dguy closed the pull request at:

[jira] [Resolved] (KAFKA-5440) Kafka Streams report state RUNNING even if all threads are dead

[ https://issues.apache.org/jira/browse/KAFKA-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-5440. --- Resolution: Duplicate > Kafka Streams report state RUNNING even if all threads are dead >

[jira] [Assigned] (KAFKA-5735) Client-ids are not handled consistently by clients and broker

[ https://issues.apache.org/jira/browse/KAFKA-5735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-5735: - Assignee: Mickael Maison (was: Rajini Sivaram) > Client-ids are not handled

[jira] [Resolved] (KAFKA-5684) KStreamPrintProcessor as customized KStreamPeekProcessor

[ https://issues.apache.org/jira/browse/KAFKA-5684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paolo Patierno resolved KAFKA-5684. --- Resolution: Feedback Received > KStreamPrintProcessor as customized KStreamPeekProcessor >

[jira] [Commented] (KAFKA-5684) KStreamPrintProcessor as customized KStreamPeekProcessor

[ https://issues.apache.org/jira/browse/KAFKA-5684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128423#comment-16128423 ] Paolo Patierno commented on KAFKA-5684: --- I'm going to close this JIRA (and the related PR). This

[jira] [Commented] (KAFKA-5684) KStreamPrintProcessor as customized KStreamPeekProcessor

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