[jira] [Commented] (KAFKA-6881) Kafka 1.1 Broker version crashes when deleting log

[ https://issues.apache.org/jira/browse/KAFKA-6881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16509191#comment-16509191 ] xiaojing zhou commented on KAFKA-6881: -- I have the same issue, the 

[jira] [Commented] (KAFKA-7043) Connect isolation whitelist does not include new primitive converters (KIP-305)

[ https://issues.apache.org/jira/browse/KAFKA-7043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16509082#comment-16509082 ] ASF GitHub Bot commented on KAFKA-7043: --- rhauch opened a new pull request #5198: KAFKA-7043:

[jira] [Commented] (KAFKA-7045) Consumer may not be able to consume all messages when down-conversion is required

[ https://issues.apache.org/jira/browse/KAFKA-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16509076#comment-16509076 ] Dhruvil Shah commented on KAFKA-7045: - Attached topic data that reproduces case (1) described in the

[jira] [Commented] (KAFKA-6966) Extend `TopologyDescription.Sink` to return `TopicNameExtractor`

[ https://issues.apache.org/jira/browse/KAFKA-6966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16509072#comment-16509072 ] Matthias J. Sax commented on KAFKA-6966: Thanks for your interest in contributing to Kafka! I

[jira] [Updated] (KAFKA-7045) Consumer may not be able to consume all messages when down-conversion is required

[ https://issues.apache.org/jira/browse/KAFKA-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhruvil Shah updated KAFKA-7045: Attachment: log-cleaner-test.zip > Consumer may not be able to consume all messages when

[jira] [Updated] (KAFKA-7045) Consumer may not be able to consume all messages when down-conversion is required

[ https://issues.apache.org/jira/browse/KAFKA-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhruvil Shah updated KAFKA-7045: Description: When down-conversion is required, the consumer might fail consuming messages under

[jira] [Assigned] (KAFKA-6966) Extend `TopologyDescription.Sink` to return `TopicNameExtractor`

[ https://issues.apache.org/jira/browse/KAFKA-6966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-6966: -- Assignee: Nishanth Pradeep > Extend `TopologyDescription.Sink` to return

[jira] [Updated] (KAFKA-7045) Consumer may not be able to consume all messages when down-conversion is required

[ https://issues.apache.org/jira/browse/KAFKA-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhruvil Shah updated KAFKA-7045: Description: When down-conversion is required, the consumer might fail consuming messages under

[jira] [Updated] (KAFKA-7045) Consumer may not be able to consume all messages when down-conversion is required

[ https://issues.apache.org/jira/browse/KAFKA-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhruvil Shah updated KAFKA-7045: Description: When down-conversion is required, the consumer might fail consuming messages under

[jira] [Updated] (KAFKA-7045) Consumer may not be able to consume all messages when down-conversion is required

[ https://issues.apache.org/jira/browse/KAFKA-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhruvil Shah updated KAFKA-7045: Description: When down-conversion is required, the consumer might fail consuming messages under

[jira] [Updated] (KAFKA-7045) Consumer may not be able to consume all messages when down-conversion is required

[ https://issues.apache.org/jira/browse/KAFKA-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhruvil Shah updated KAFKA-7045: Description: When down-conversion is required, the consumer might fail consuming messages under

[jira] [Updated] (KAFKA-7045) Consumer may not be able to consume all messages when down-conversion is required

[ https://issues.apache.org/jira/browse/KAFKA-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhruvil Shah updated KAFKA-7045: Description: When down-conversion is required, the consumer might fail consuming messages under

[jira] [Created] (KAFKA-7045) Consumer may not be able to consume all messages when down-conversion is required

Dhruvil Shah created KAFKA-7045: --- Summary: Consumer may not be able to consume all messages when down-conversion is required Key: KAFKA-7045 URL: https://issues.apache.org/jira/browse/KAFKA-7045

[jira] [Commented] (KAFKA-6966) Extend `TopologyDescription.Sink` to return `TopicNameExtractor`

[ https://issues.apache.org/jira/browse/KAFKA-6966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16509062#comment-16509062 ] Nishanth Pradeep commented on KAFKA-6966: - Hello [~mjsax]. I would like to pick this up ticket as

[jira] [Assigned] (KAFKA-7044) kafka-consumer-groups.sh NullPointerException describing round robin or sticky assignors

[ https://issues.apache.org/jira/browse/KAFKA-7044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-7044: -- Assignee: Vahid Hashemian > kafka-consumer-groups.sh NullPointerException describing

[jira] [Created] (KAFKA-7044) kafka-consumer-groups.sh NullPointerException describing round robin or sticky assignors

Jeff Field created KAFKA-7044: - Summary: kafka-consumer-groups.sh NullPointerException describing round robin or sticky assignors Key: KAFKA-7044 URL: https://issues.apache.org/jira/browse/KAFKA-7044

[jira] [Commented] (KAFKA-7023) Kafka Streams RocksDB bulk loading config may not be honored with customized RocksDBConfigSetter

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

[jira] [Commented] (KAFKA-6906) Kafka Streams does not commit transactions if data is produced via wall-clock punctuation

[ https://issues.apache.org/jira/browse/KAFKA-6906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508991#comment-16508991 ] ASF GitHub Bot commented on KAFKA-6906: --- mjsax opened a new pull request #5196: MINOR: code cleanup

[jira] [Commented] (KAFKA-7021) Source KTable checkpoint is not correct

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

[jira] [Resolved] (KAFKA-6906) Kafka Streams does not commit transactions if data is produced via wall-clock punctuation

[ https://issues.apache.org/jira/browse/KAFKA-6906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6906. Resolution: Fixed Fix Version/s: 1.1.1 2.0.0 > Kafka Streams

[jira] [Commented] (KAFKA-7021) Source KTable checkpoint is not correct

[ https://issues.apache.org/jira/browse/KAFKA-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508927#comment-16508927 ] ASF GitHub Bot commented on KAFKA-7021: --- guozhangwang closed pull request #5163: KAFKA-7021: Reuse

[jira] [Commented] (KAFKA-7040) The replica fetcher thread may truncate accepted messages during multiple fast leadership transitions

[ https://issues.apache.org/jira/browse/KAFKA-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508907#comment-16508907 ] Lucas Wang commented on KAFKA-7040: --- To be more specific, I think the following sequence of events may

[jira] [Commented] (KAFKA-6977) Kafka Streams - java.lang.IllegalStateException: Unexpected error code 2 while fetching data

[ https://issues.apache.org/jira/browse/KAFKA-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508902#comment-16508902 ] Eugen Feller commented on KAFKA-6977: - I think it was 0.11.0.1 consumer as I have used the 

[jira] [Commented] (KAFKA-7040) The replica fetcher thread may truncate accepted messages during multiple fast leadership transitions

[ https://issues.apache.org/jira/browse/KAFKA-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508867#comment-16508867 ] Lucas Wang commented on KAFKA-7040: --- [~lindong] Thanks for pointing out the truncation may happen below

[jira] [Commented] (KAFKA-7003) Add headers with error context in messages written to the Connect DeadLetterQueue topic

[ https://issues.apache.org/jira/browse/KAFKA-7003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508849#comment-16508849 ] ASF GitHub Bot commented on KAFKA-7003: --- ewencp closed pull request #5159: KAFKA-7003: Set error

[jira] [Commented] (KAFKA-7040) The replica fetcher thread may truncate accepted messages during multiple fast leadership transitions

[ https://issues.apache.org/jira/browse/KAFKA-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508847#comment-16508847 ] Dong Lin commented on KAFKA-7040: - [~luwang] Nice catch. It is indeed problematic (with some probability

[jira] [Resolved] (KAFKA-7003) Add headers with error context in messages written to the Connect DeadLetterQueue topic

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

[jira] [Commented] (KAFKA-7042) Fall back to the old behavior when the broker is too old to recognize LIST_OFFSET versions

[ https://issues.apache.org/jira/browse/KAFKA-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508845#comment-16508845 ] Ismael Juma commented on KAFKA-7042: Maybe they should not turn it on for older brokers? > Fall back

[jira] [Commented] (KAFKA-6990) CommitFailedException; this task may be no longer owned by the thread

[ https://issues.apache.org/jira/browse/KAFKA-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508843#comment-16508843 ] Eugen Feller commented on KAFKA-6990: - Thanks a lot. For sake of completeness. Logs sent via Slack.

[jira] [Commented] (KAFKA-5570) Join request's timeout should be slightly higher than the rebalance timeout

[ https://issues.apache.org/jira/browse/KAFKA-5570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508828#comment-16508828 ] ASF GitHub Bot commented on KAFKA-5570: --- ijuma closed pull request #3503: KAFKA-5570: Join

[jira] [Commented] (KAFKA-7042) Fall back to the old behavior when the broker is too old to recognize LIST_OFFSET versions

[ https://issues.apache.org/jira/browse/KAFKA-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508815#comment-16508815 ] Guozhang Wang commented on KAFKA-7042: -- System tests. > Fall back to the old behavior when the

[jira] [Commented] (KAFKA-6906) Kafka Streams does not commit transactions if data is produced via wall-clock punctuation

[ https://issues.apache.org/jira/browse/KAFKA-6906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508805#comment-16508805 ] ASF GitHub Bot commented on KAFKA-6906: --- mjsax closed pull request #5105: KAFKA-6906: Fixed to

[jira] [Created] (KAFKA-7043) Connect isolation whitelist does not include new primitive converters (KIP-305)

Randall Hauch created KAFKA-7043: Summary: Connect isolation whitelist does not include new primitive converters (KIP-305) Key: KAFKA-7043 URL: https://issues.apache.org/jira/browse/KAFKA-7043

[jira] [Commented] (KAFKA-7040) The replica fetcher thread may truncate accepted messages during multiple fast leadership transitions

[ https://issues.apache.org/jira/browse/KAFKA-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508771#comment-16508771 ] Ismael Juma commented on KAFKA-7040: cc [~apovzner] > The replica fetcher thread may truncate

[jira] [Commented] (KAFKA-7042) Fall back to the old behavior when the broker is too old to recognize LIST_OFFSET versions

[ https://issues.apache.org/jira/browse/KAFKA-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508768#comment-16508768 ] Ismael Juma commented on KAFKA-7042: Who is turning on READ_COMMITTED in this case? > Fall back to

[jira] [Comment Edited] (KAFKA-7040) The replica fetcher thread may truncate accepted messages during multiple fast leadership transitions

[ https://issues.apache.org/jira/browse/KAFKA-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508763#comment-16508763 ] Dong Lin edited comment on KAFKA-7040 at 6/11/18 9:15 PM: -- [~luwang] Say message

[jira] [Commented] (KAFKA-7040) The replica fetcher thread may truncate accepted messages during multiple fast leadership transitions

[ https://issues.apache.org/jira/browse/KAFKA-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508763#comment-16508763 ] Dong Lin commented on KAFKA-7040: - [~luwang] Say message m0 is truncated in step 5. Is that message acked

[jira] [Comment Edited] (KAFKA-7040) The replica fetcher thread may truncate accepted messages during multiple fast leadership transitions

[ https://issues.apache.org/jira/browse/KAFKA-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508763#comment-16508763 ] Dong Lin edited comment on KAFKA-7040 at 6/11/18 9:14 PM: -- [~luwang] Say message

[jira] [Comment Edited] (KAFKA-7040) The replica fetcher thread may truncate accepted messages during multiple fast leadership transitions

[ https://issues.apache.org/jira/browse/KAFKA-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508763#comment-16508763 ] Dong Lin edited comment on KAFKA-7040 at 6/11/18 9:14 PM: -- [~luwang] Say message

[jira] [Commented] (KAFKA-7042) Fall back to the old behavior when the broker is too old to recognize LIST_OFFSET versions

[ https://issues.apache.org/jira/browse/KAFKA-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508761#comment-16508761 ] Guozhang Wang commented on KAFKA-7042: -- cc [~hachikuji] > Fall back to the old behavior when the

[jira] [Created] (KAFKA-7042) Fall back to the old behavior when the broker is too old to recognize LIST_OFFSET versions

Guozhang Wang created KAFKA-7042: Summary: Fall back to the old behavior when the broker is too old to recognize LIST_OFFSET versions Key: KAFKA-7042 URL: https://issues.apache.org/jira/browse/KAFKA-7042

[jira] [Updated] (KAFKA-7024) Rocksdb state directory should be created before opening the DB

[ https://issues.apache.org/jira/browse/KAFKA-7024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-7024: - Labels: user-experience (was: ) > Rocksdb state directory should be created before opening the

[jira] [Created] (KAFKA-7041) Using RocksDB bulk loading for StandbyTasks

Matthias J. Sax created KAFKA-7041: -- Summary: Using RocksDB bulk loading for StandbyTasks Key: KAFKA-7041 URL: https://issues.apache.org/jira/browse/KAFKA-7041 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-7037) delete topic command replaces '+' from the topic name which leads incorrect topic deletion

[ https://issues.apache.org/jira/browse/KAFKA-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508735#comment-16508735 ] ASF GitHub Bot commented on KAFKA-7037: --- vahidhashemian opened a new pull request #5193:

[jira] [Commented] (KAFKA-7023) Kafka Streams RocksDB bulk loading config may not be honored with customized RocksDBConfigSetter

[ https://issues.apache.org/jira/browse/KAFKA-7023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508694#comment-16508694 ] ASF GitHub Bot commented on KAFKA-7023: --- guozhangwang closed pull request #5166: KAFKA-7023: Move

[jira] [Commented] (KAFKA-6990) CommitFailedException; this task may be no longer owned by the thread

[ https://issues.apache.org/jira/browse/KAFKA-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508693#comment-16508693 ] Matthias J. Sax commented on KAFKA-6990: There are two thread one for heartbeats and one for

[jira] [Resolved] (KAFKA-7005) Remove duplicate Java Resource class.

[ https://issues.apache.org/jira/browse/KAFKA-7005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-7005. Resolution: Fixed merged the PR to trunk and 2.0 branch. > Remove duplicate Java Resource class. >

[jira] [Commented] (KAFKA-7030) Add configuration to disable message down-conversion

[ https://issues.apache.org/jira/browse/KAFKA-7030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508688#comment-16508688 ] ASF GitHub Bot commented on KAFKA-7030: --- dhruvilshah3 opened a new pull request #5192: KAFKA-7030:

[jira] [Commented] (KAFKA-7005) Remove duplicate Java Resource class.

[ https://issues.apache.org/jira/browse/KAFKA-7005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508684#comment-16508684 ] ASF GitHub Bot commented on KAFKA-7005: --- junrao closed pull request #5184: KAFKA-7005: Remove

[jira] [Commented] (KAFKA-6977) Kafka Streams - java.lang.IllegalStateException: Unexpected error code 2 while fetching data

[ https://issues.apache.org/jira/browse/KAFKA-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508683#comment-16508683 ] Matthias J. Sax commented on KAFKA-6977: Hard to tell where the corruption occurs. I could be on

[jira] [Created] (KAFKA-7040) The replica fetcher thread may truncate accepted messages during multiple fast leadership transitions

Lucas Wang created KAFKA-7040: - Summary: The replica fetcher thread may truncate accepted messages during multiple fast leadership transitions Key: KAFKA-7040 URL: https://issues.apache.org/jira/browse/KAFKA-7040

[jira] [Commented] (KAFKA-6977) Kafka Streams - java.lang.IllegalStateException: Unexpected error code 2 while fetching data

[ https://issues.apache.org/jira/browse/KAFKA-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508661#comment-16508661 ] Eugen Feller commented on KAFKA-6977: - Hi [~mjsax]. Interesting. Thanks a lot. I think the topic

[jira] [Comment Edited] (KAFKA-6977) Kafka Streams - java.lang.IllegalStateException: Unexpected error code 2 while fetching data

[ https://issues.apache.org/jira/browse/KAFKA-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508661#comment-16508661 ] Eugen Feller edited comment on KAFKA-6977 at 6/11/18 8:13 PM: -- Hi [~mjsax].

[jira] [Comment Edited] (KAFKA-6990) CommitFailedException; this task may be no longer owned by the thread

[ https://issues.apache.org/jira/browse/KAFKA-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508566#comment-16508566 ] Eugen Feller edited comment on KAFKA-6990 at 6/11/18 7:11 PM: -- Hi [~mjsax].

[jira] [Comment Edited] (KAFKA-6990) CommitFailedException; this task may be no longer owned by the thread

[ https://issues.apache.org/jira/browse/KAFKA-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508566#comment-16508566 ] Eugen Feller edited comment on KAFKA-6990 at 6/11/18 7:10 PM: -- Hi [~mjsax].

[jira] [Comment Edited] (KAFKA-6990) CommitFailedException; this task may be no longer owned by the thread

[ https://issues.apache.org/jira/browse/KAFKA-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508566#comment-16508566 ] Eugen Feller edited comment on KAFKA-6990 at 6/11/18 7:09 PM: -- Hi [~mjsax].

[jira] [Comment Edited] (KAFKA-6990) CommitFailedException; this task may be no longer owned by the thread

[ https://issues.apache.org/jira/browse/KAFKA-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508566#comment-16508566 ] Eugen Feller edited comment on KAFKA-6990 at 6/11/18 7:08 PM: -- Hi [~mjsax].

[jira] [Comment Edited] (KAFKA-6990) CommitFailedException; this task may be no longer owned by the thread

[ https://issues.apache.org/jira/browse/KAFKA-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508566#comment-16508566 ] Eugen Feller edited comment on KAFKA-6990 at 6/11/18 7:08 PM: -- Hi [~mjsax].

[jira] [Commented] (KAFKA-6990) CommitFailedException; this task may be no longer owned by the thread

[ https://issues.apache.org/jira/browse/KAFKA-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508566#comment-16508566 ] Eugen Feller commented on KAFKA-6990: - Hi [~mjsax]. Thank you very much for your inputs. That makes

[jira] [Commented] (KAFKA-7039) DelegatingClassLoader creates plugin instance even if its not Versioned

[ https://issues.apache.org/jira/browse/KAFKA-7039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508556#comment-16508556 ] ASF GitHub Bot commented on KAFKA-7039: --- mageshn opened a new pull request #5191: KAFKA-7039 :

[jira] [Created] (KAFKA-7039) DelegatingClassLoader creates plugin instance even if its not Versioned

Magesh kumar Nandakumar created KAFKA-7039: -- Summary: DelegatingClassLoader creates plugin instance even if its not Versioned Key: KAFKA-7039 URL: https://issues.apache.org/jira/browse/KAFKA-7039

[jira] [Commented] (KAFKA-6546) Add ENDPOINT_NOT_FOUND_ON_LEADER error code for missing listener

[ https://issues.apache.org/jira/browse/KAFKA-6546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508476#comment-16508476 ] ASF GitHub Bot commented on KAFKA-6546: --- rajinisivaram opened a new pull request #5189: KAFKA-6546:

[jira] [Commented] (KAFKA-7029) ReplicaVerificationTool should not use the deprecated SimpleConsumer

[ https://issues.apache.org/jira/browse/KAFKA-7029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508472#comment-16508472 ] ASF GitHub Bot commented on KAFKA-7029: --- omkreddy opened a new pull request #5188: KAFKA-7029:

[jira] [Updated] (KAFKA-6697) JBOD configured broker should not die if log directory is invalid

[ https://issues.apache.org/jira/browse/KAFKA-6697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-6697: Issue Type: Bug (was: Improvement) > JBOD configured broker should not die if log directory is invalid >

[jira] [Assigned] (KAFKA-7037) delete topic command replaces '+' from the topic name which leads incorrect topic deletion

[ https://issues.apache.org/jira/browse/KAFKA-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-7037: -- Assignee: Vahid Hashemian > delete topic command replaces '+' from the topic name

[jira] [Resolved] (KAFKA-6946) Keep the session id for incremental fetch when fetch responses are throttled

[ https://issues.apache.org/jira/browse/KAFKA-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-6946. - Resolution: Fixed > Keep the session id for incremental fetch when fetch responses are throttled >

[jira] [Commented] (KAFKA-6860) NPE when reinitializeStateStores with eos enabled

[ https://issues.apache.org/jira/browse/KAFKA-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508424#comment-16508424 ] ASF GitHub Bot commented on KAFKA-6860: --- mjsax opened a new pull request #5187: KAFKA-6860: Fix NPE

[jira] [Commented] (KAFKA-7035) Kafka Processor's init() method sometimes is not called

[ https://issues.apache.org/jira/browse/KAFKA-7035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508425#comment-16508425 ] Oleksandr Konopko commented on KAFKA-7035: -- ok, but processor constructor and processor.init()

[jira] [Commented] (KAFKA-6946) Keep the session id for incremental fetch when fetch responses are throttled

[ https://issues.apache.org/jira/browse/KAFKA-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508420#comment-16508420 ] ASF GitHub Bot commented on KAFKA-6946: --- lindong28 closed pull request #5164: KAFKA-6946: Keep the

[jira] [Commented] (KAFKA-7035) Kafka Processor's init() method sometimes is not called

[ https://issues.apache.org/jira/browse/KAFKA-7035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508402#comment-16508402 ] Guozhang Wang commented on KAFKA-7035: -- Hi [~akonopko], processor.init() should always be called

[jira] [Updated] (KAFKA-6860) NPE when reinitializeStateStores with eos enabled

[ https://issues.apache.org/jira/browse/KAFKA-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-6860: --- Fix Version/s: 2.0.0 > NPE when reinitializeStateStores with eos enabled >

[jira] [Assigned] (KAFKA-6860) NPE when reinitializeStateStores with eos enabled

[ https://issues.apache.org/jira/browse/KAFKA-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-6860: -- Assignee: Matthias J. Sax > NPE when reinitializeStateStores with eos enabled >

[jira] [Commented] (KAFKA-6860) NPE when reinitializeStateStores with eos enabled

[ https://issues.apache.org/jira/browse/KAFKA-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508317#comment-16508317 ] Guozhang Wang commented on KAFKA-6860: -- I see. Thanks for the explanation [~mjsax]. And your

[jira] [Updated] (KAFKA-6889) Fix Streams system test to only specify used log files

[ https://issues.apache.org/jira/browse/KAFKA-6889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Kozlovski updated KAFKA-6889: --- Attachment: (was: Screen Shot 2018-06-11 at 7.15.02 PM.png) > Fix Streams system

[jira] [Commented] (KAFKA-6889) Fix Streams system test to only specify used log files

[ https://issues.apache.org/jira/browse/KAFKA-6889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508285#comment-16508285 ] Stanislav Kozlovski commented on KAFKA-6889: What do you mean the Jenkins has read access?

[jira] [Updated] (KAFKA-6889) Fix Streams system test to only specify used log files

[ https://issues.apache.org/jira/browse/KAFKA-6889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Kozlovski updated KAFKA-6889: --- Attachment: Screen Shot 2018-06-11 at 7.15.02 PM.png > Fix Streams system test to

[jira] [Updated] (KAFKA-6889) Fix Streams system test to only specify used log files

[ https://issues.apache.org/jira/browse/KAFKA-6889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Kozlovski updated KAFKA-6889: --- Attachment: Screen Shot 2018-06-11 at 7.15.02 PM.png > Fix Streams system test to

[jira] [Updated] (KAFKA-6889) Fix Streams system test to only specify used log files

[ https://issues.apache.org/jira/browse/KAFKA-6889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Kozlovski updated KAFKA-6889: --- Attachment: (was: Screen Shot 2018-06-11 at 7.15.02 PM.png) > Fix Streams system

[jira] [Created] (KAFKA-7038) Support AdminClient Example

darion yaphet created KAFKA-7038: Summary: Support AdminClient Example Key: KAFKA-7038 URL: https://issues.apache.org/jira/browse/KAFKA-7038 Project: Kafka Issue Type: New Feature

[jira] [Commented] (KAFKA-6889) Fix Streams system test to only specify used log files

[ https://issues.apache.org/jira/browse/KAFKA-6889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508243#comment-16508243 ] Guozhang Wang commented on KAFKA-6889: -- Confluent jenkins has read access but not write access: i.e.

[jira] [Updated] (KAFKA-7037) delete topic command replaces '+' from the topic name which leads incorrect topic deletion

[ https://issues.apache.org/jira/browse/KAFKA-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Nemuri updated KAFKA-7037: -- Description: While executing a delete command kafka cli tool is removing the "+" symbol and

[jira] [Commented] (KAFKA-6788) Grouping consumer requests per consumer coordinator in admin client

[ https://issues.apache.org/jira/browse/KAFKA-6788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508215#comment-16508215 ] ASF GitHub Bot commented on KAFKA-6788: --- cyrusv closed pull request #4878: KAFKA-6788: Combine

[jira] [Commented] (KAFKA-7033) Modify AbstractOptions's timeoutMs as Long type

[ https://issues.apache.org/jira/browse/KAFKA-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508205#comment-16508205 ] ASF GitHub Bot commented on KAFKA-7033: --- darionyaphet opened a new pull request #5186: [KAFKA-7033]

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

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-3042: -- Fix Version/s: (was: 2.0.0) 2.1.0 Moving this out to 2.1.0 since there

[jira] [Updated] (KAFKA-4682) Committed offsets should not be deleted if a consumer is still active (KIP-211)

[ https://issues.apache.org/jira/browse/KAFKA-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4682: -- Fix Version/s: (was: 2.0.0) 2.1.0 Moving this out to 2.1.0. >

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

[ https://issues.apache.org/jira/browse/KAFKA-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-5054: -- Fix Version/s: (was: 2.0.0) 2.1.0 Since there has been no activity on

[jira] [Updated] (KAFKA-3190) KafkaProducer should not invoke callback in send()

[ https://issues.apache.org/jira/browse/KAFKA-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-3190: -- Fix Version/s: (was: 2.0.0) 2.1.0 Since there has been no activity on

[jira] [Updated] (KAFKA-4701) Allow kafka brokers to dynamically reload truststore without restarting.

[ https://issues.apache.org/jira/browse/KAFKA-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4701: -- Fix Version/s: (was: 2.0.0) 2.1.0 We have added dynamic update of

[jira] [Updated] (KAFKA-4808) send of null key to a compacted topic should throw error back to user

[ https://issues.apache.org/jira/browse/KAFKA-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4808: -- Fix Version/s: (was: 2.0.0) 2.1.0 Since there has been no activity on

[jira] [Updated] (KAFKA-4850) RocksDb cannot use Bloom Filters

[ https://issues.apache.org/jira/browse/KAFKA-4850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4850: -- Fix Version/s: (was: 2.0.0) 2.1.0 Since there has been no activity on

[jira] [Updated] (KAFKA-3297) More optimally balanced partition assignment strategy (new consumer)

[ https://issues.apache.org/jira/browse/KAFKA-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-3297: -- Fix Version/s: (was: 2.0.0) 2.1.0 Since there has been no activity on

[jira] [Updated] (KAFKA-5952) Refactor Consumer Fetcher metrics

[ https://issues.apache.org/jira/browse/KAFKA-5952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-5952: -- Fix Version/s: (was: 2.0.0) 2.1.0 Since there has been no activity on

[jira] [Updated] (KAFKA-5951) Autogenerate Producer RecordAccumulator metrics

[ https://issues.apache.org/jira/browse/KAFKA-5951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-5951: -- Fix Version/s: (was: 2.0.0) 2.1.0 Since there has been no activity on

[jira] [Updated] (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:all-tabpanel ] Rajini Sivaram updated KAFKA-5403: -- Fix Version/s: (was: 2.0.0) 2.1.0 Since there has been no activity on

[jira] [Updated] (KAFKA-4862) Kafka client connect to a shutdown node will block for a long time

[ https://issues.apache.org/jira/browse/KAFKA-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4862: -- Fix Version/s: (was: 2.0.0) 2.1.0 The KIP associated with this JIRA has

[jira] [Updated] (KAFKA-4665) Inconsistent handling of non-existing topics in offset fetch handling

[ https://issues.apache.org/jira/browse/KAFKA-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4665: -- Fix Version/s: (was: 2.0.0) 2.1.0 Since there has been no activity on

[jira] [Updated] (KAFKA-4307) Inconsistent parameters between console producer and consumer

[ https://issues.apache.org/jira/browse/KAFKA-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4307: -- Fix Version/s: (was: 2.0.0) 2.1.0 Since there has been no activity on

[jira] [Updated] (KAFKA-4249) Document how to customize GC logging options for broker

[ https://issues.apache.org/jira/browse/KAFKA-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4249: -- Fix Version/s: (was: 2.0.0) 2.1.0 Since there has been no activity on

[jira] [Updated] (KAFKA-3554) Generate actual data with specific compression ratio and add multi-thread support in the ProducerPerformance tool.

[ https://issues.apache.org/jira/browse/KAFKA-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-3554: -- Fix Version/s: (was: 2.0.0) 2.1.0 Since there has been no activity on

[jira] [Updated] (KAFKA-4203) Java producer default max message size does not align with broker default

[ https://issues.apache.org/jira/browse/KAFKA-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4203: -- Fix Version/s: (was: 2.0.0) 2.1.0 Since there has been no activity on

  1   2   >