[jira] [Commented] (KAFKA-5148) Add configurable compression block size to the broker

[ https://issues.apache.org/jira/browse/KAFKA-5148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035423#comment-16035423 ] Ismael Juma commented on KAFKA-5148: The Snappy block size for producer and broker wil

[jira] [Commented] (KAFKA-3704) Improve mechanism for compression stream block size selection in KafkaProducer

[ https://issues.apache.org/jira/browse/KAFKA-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035424#comment-16035424 ] Ismael Juma commented on KAFKA-3704: The Snappy block size for producer and broker wil

[jira] [Commented] (KAFKA-5368) Kafka Streams skipped-records-rate sensor produces nonzero values when the timestamps are valid

[ https://issues.apache.org/jira/browse/KAFKA-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035429#comment-16035429 ] Guozhang Wang commented on KAFKA-5368: -- Sounds good to me. Maybe we can add one in St

[jira] [Updated] (KAFKA-5236) Regression in on-disk log size when using Snappy compression with 0.8.2 log message format

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

[jira] [Created] (KAFKA-5370) Replace uses of old consumer with the new consumer

Vahid Hashemian created KAFKA-5370: -- Summary: Replace uses of old consumer with the new consumer Key: KAFKA-5370 URL: https://issues.apache.org/jira/browse/KAFKA-5370 Project: Kafka Issue T

[jira] [Updated] (KAFKA-5322) Resolve AddPartitions response error code inconsistency

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

[GitHub] kafka pull request #3204: KAFKA-5322: Add an `OPERATION_NOT_ATTEMPTED` error...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3204 --- 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-5322) Resolve AddPartitions response error code inconsistency

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

[jira] [Commented] (KAFKA-5070) org.apache.kafka.streams.errors.LockException: task [0_18] Failed to lock the state directory: /opt/rocksdb/pulse10/0_18

[ https://issues.apache.org/jira/browse/KAFKA-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035452#comment-16035452 ] Kevin Chen commented on KAFKA-5070: --- we saw the similar exceptions in our stream applica

[jira] [Comment Edited] (KAFKA-5070) org.apache.kafka.streams.errors.LockException: task [0_18] Failed to lock the state directory: /opt/rocksdb/pulse10/0_18

[ https://issues.apache.org/jira/browse/KAFKA-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035452#comment-16035452 ] Kevin Chen edited comment on KAFKA-5070 at 6/2/17 9:28 PM: --- we s

[jira] [Commented] (KAFKA-4595) Controller send thread can't stop when broker change listener event trigger for dead brokers

[ https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035465#comment-16035465 ] Onur Karaman commented on KAFKA-4595: - [~ijuma] Yeah I think KAFKA-5028 solved this is

[jira] [Commented] (KAFKA-5070) org.apache.kafka.streams.errors.LockException: task [0_18] Failed to lock the state directory: /opt/rocksdb/pulse10/0_18

[ https://issues.apache.org/jira/browse/KAFKA-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035471#comment-16035471 ] Matthias J. Sax commented on KAFKA-5070: [~kchen] At a regular rebalance, this exc

[jira] [Updated] (KAFKA-4595) Controller send thread can't stop when broker change listener event trigger for dead brokers

[ https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4595: --- Fix Version/s: (was: 0.11.0.1) 0.11.0.0 > Controller send thread can't stop whe

[jira] [Resolved] (KAFKA-4595) Controller send thread can't stop when broker change listener event trigger for dead brokers

[ https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4595. Resolution: Fixed Assignee: Onur Karaman > Controller send thread can't stop when broker chang

[jira] [Created] (KAFKA-5371) SyncProducerTest.testReachableServer has become flaky

Apurva Mehta created KAFKA-5371: --- Summary: SyncProducerTest.testReachableServer has become flaky Key: KAFKA-5371 URL: https://issues.apache.org/jira/browse/KAFKA-5371 Project: Kafka Issue Type:

[jira] [Assigned] (KAFKA-5371) SyncProducerTest.testReachableServer has become flaky

[ https://issues.apache.org/jira/browse/KAFKA-5371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reassigned KAFKA-5371: --- Assignee: Apurva Mehta > SyncProducerTest.testReachableServer has become flaky >

[jira] [Updated] (KAFKA-5371) SyncProducerTest.testReachableServer has become flaky

[ https://issues.apache.org/jira/browse/KAFKA-5371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5371: Description: This test has started failing recently on jenkins with the following {noformat} org.s

[GitHub] kafka pull request #3214: MINOR: syntax brush for java / bash / json / text

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/3214 MINOR: syntax brush for java / bash / json / text You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka KMinor-doc-java-brush

[jira] [Commented] (KAFKA-5070) org.apache.kafka.streams.errors.LockException: task [0_18] Failed to lock the state directory: /opt/rocksdb/pulse10/0_18

[ https://issues.apache.org/jira/browse/KAFKA-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035488#comment-16035488 ] Kevin Chen commented on KAFKA-5070: --- thanks for the quick reply I do not have the rocks

[jira] [Commented] (KAFKA-5070) org.apache.kafka.streams.errors.LockException: task [0_18] Failed to lock the state directory: /opt/rocksdb/pulse10/0_18

[ https://issues.apache.org/jira/browse/KAFKA-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035501#comment-16035501 ] Kevin Chen commented on KAFKA-5070: --- A little background about our topology: the source

[jira] [Commented] (KAFKA-5070) org.apache.kafka.streams.errors.LockException: task [0_18] Failed to lock the state directory: /opt/rocksdb/pulse10/0_18

[ https://issues.apache.org/jira/browse/KAFKA-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035508#comment-16035508 ] Matthias J. Sax commented on KAFKA-5070: If you hit this on a fresh restart, I gue

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

See Changes: [wangguoz] KAFKA-5368: Fix skipped record metrics to use rate of sum instead of [wangguoz] KAFKA-3982: Fix processing order of some of the consumer properties [ismael] KAFKA-5236; Increase the block

[GitHub] kafka pull request #3215: Adding deprecated KTable methods to docs from KIP-...

GitHub user bbejeck opened a pull request: https://github.com/apache/kafka/pull/3215 Adding deprecated KTable methods to docs from KIP-114 You can merge this pull request into a Git repository by running: $ git pull https://github.com/bbejeck/kafka kip114-doc Alternatively yo

[GitHub] kafka pull request #3216: HOTFIX: Reinstate the placeholder for logPrefix in...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/3216 HOTFIX: Reinstate the placeholder for logPrefix in TransactionManager You can merge this pull request into a Git repository by running: $ git pull https://github.com/apurvam/kafka HOTFIX-logg

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

See Changes: [wangguoz] KAFKA-3982: Fix processing order of some of the consumer properties [ismael] KAFKA-5236; Increase the block/buffer size when compressing with Snappy -

[GitHub] kafka pull request #3216: HOTFIX: Reinstate the placeholder for logPrefix in...

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

[GitHub] kafka pull request #3217: KAFKA-5366: Add concurrent reads to transactions s...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/3217 KAFKA-5366: Add concurrent reads to transactions system test This currently fails in multiple ways. One of which is most likely KAFKA-5355, where the concurrent consumer reads duplicates. D

[jira] [Commented] (KAFKA-5366) Add cases for concurrent transactional reads and writes in system tests

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

[jira] [Created] (KAFKA-5372) Unexpected state transition Dead to PendingShutdown

Jason Gustafson created KAFKA-5372: -- Summary: Unexpected state transition Dead to PendingShutdown Key: KAFKA-5372 URL: https://issues.apache.org/jira/browse/KAFKA-5372 Project: Kafka Issue T

[jira] [Updated] (KAFKA-5366) Add cases for concurrent transactional reads and writes in system tests

[ https://issues.apache.org/jira/browse/KAFKA-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5366: Status: Patch Available (was: Open) > Add cases for concurrent transactional reads and writes in sy

[jira] [Updated] (KAFKA-5366) Add cases for concurrent transactional reads and writes in system tests

[ https://issues.apache.org/jira/browse/KAFKA-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5366: Fix Version/s: (was: 0.11.1.0) 0.11.0.1 > Add cases for concurrent transactio

Re: Reg: [VOTE] KIP 157 - Add consumer config options to streams reset tool

Thanks. +1 On Thu, Jun 1, 2017 at 9:40 PM, Matthias J. Sax wrote: > +1 > > Thanks for updating the KIP! > > -Matthias > > On 6/1/17 6:18 PM, Bill Bejeck wrote: > > +1 > > > > Thanks, > > Bill > > > > On Thu, Jun 1, 2017 at 7:45 PM, Guozhang Wang > wrote: > > > >> +1 again. Thanks. > >> > >> On

[jira] [Commented] (KAFKA-5070) org.apache.kafka.streams.errors.LockException: task [0_18] Failed to lock the state directory: /opt/rocksdb/pulse10/0_18

[ https://issues.apache.org/jira/browse/KAFKA-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035590#comment-16035590 ] Kevin Chen commented on KAFKA-5070: --- Hi, Matthias: my state store was not corrupted. I

[jira] [Comment Edited] (KAFKA-5070) org.apache.kafka.streams.errors.LockException: task [0_18] Failed to lock the state directory: /opt/rocksdb/pulse10/0_18

[ https://issues.apache.org/jira/browse/KAFKA-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035590#comment-16035590 ] Kevin Chen edited comment on KAFKA-5070 at 6/2/17 11:03 PM: Hi

[jira] [Created] (KAFKA-5373) ConsoleConsumer prints out object addresses rather than what is expected

Colin P. McCabe created KAFKA-5373: -- Summary: ConsoleConsumer prints out object addresses rather than what is expected Key: KAFKA-5373 URL: https://issues.apache.org/jira/browse/KAFKA-5373 Project: K

[jira] [Created] (KAFKA-5374) AdminClient gets "server returned information about unknown correlation ID" when communicating with older brokers

Colin P. McCabe created KAFKA-5374: -- Summary: AdminClient gets "server returned information about unknown correlation ID" when communicating with older brokers Key: KAFKA-5374 URL: https://issues.apache.org/jira/

[GitHub] kafka pull request #3218: KAFKA-5373 : Revert breaking change to console con...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/3218 KAFKA-5373 : Revert breaking change to console consumer This patch b63e41ea78a58bdea78be33f90bfcb61ce5988d3 since it broke the console consumer -- the consumer prints the addresses of the messages

[jira] [Commented] (KAFKA-5373) ConsoleConsumer prints out object addresses rather than what is expected

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

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

See

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

See

[GitHub] kafka pull request #3219: KAFKA-5374. AdminClient gets "server returned info...

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/3219 KAFKA-5374. AdminClient gets "server returned information about unkno… …wn correlation ID" when communicating with older brokers You can merge this pull request into a Git repository by running:

[jira] [Commented] (KAFKA-5374) AdminClient gets "server returned information about unknown correlation ID" when communicating with older brokers

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

[jira] [Commented] (KAFKA-5374) AdminClient gets "server returned information about unknown correlation ID" when communicating with older brokers

[ https://issues.apache.org/jira/browse/KAFKA-5374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035664#comment-16035664 ] Colin P. McCabe commented on KAFKA-5374: This was introduced by KAFKA-5291. The i

[jira] [Resolved] (KAFKA-5024) Old clients don't support message format V2

[ https://issues.apache.org/jira/browse/KAFKA-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5024. Resolution: Won't Fix I added a note on the KIP. Closing this. > Old clients don't support

[jira] [Commented] (KAFKA-4325) Improve processing of late records for window operations

[ https://issues.apache.org/jira/browse/KAFKA-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035688#comment-16035688 ] Jeyhun Karimov commented on KAFKA-4325: --- [~mjsax], would this jira requre KIP? > I

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

See Changes: [jason] KAFKA-5322; Add `OPERATION_NOT_ATTEMPTED` error code to resolve [jason] HOTFIX: Reinstate the placeholder for logPrefix in TransactionManager -- [...

[GitHub] kafka pull request #3218: KAFKA-5373 : Revert breaking change to console con...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3218 --- 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] [Resolved] (KAFKA-5373) ConsoleConsumer prints out object addresses rather than what is expected

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

[jira] [Commented] (KAFKA-5373) ConsoleConsumer prints out object addresses rather than what is expected

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

[jira] [Commented] (KAFKA-5272) Improve validation for Describe/Alter Configs (KIP-133)

[ https://issues.apache.org/jira/browse/KAFKA-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035728#comment-16035728 ] Ismael Juma commented on KAFKA-5272: I will merge AlterConfigPolicy soon. The rest of

[GitHub] kafka pull request #3180: MINOR: reuse decompression buffers in log cleaner

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3180 --- 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-5150) LZ4 decompression is 4-5x slower than Snappy on small batches / messages

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

[GitHub] kafka pull request #3220: KAFKA-5374: Set allow auto topic creation to false...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3220 KAFKA-5374: Set allow auto topic creation to false when requesting node information only It avoids the need to handle protocol downgrades and it's safe (i.e. it will never cause the auto creation

[jira] [Commented] (KAFKA-5374) AdminClient gets "server returned information about unknown correlation ID" when communicating with older brokers

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

[GitHub] kafka pull request #3210: KAFKA-5272: Policy for Alter Configs (KIP-133)

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3210 --- 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-5272) Improve validation for Describe/Alter Configs (KIP-133)

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

[GitHub] kafka pull request #3221: KAFKA-5355: DelayedFetch should propagate isolatio...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3221 KAFKA-5355: DelayedFetch should propagate isolation level to log read You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-53

[jira] [Commented] (KAFKA-5355) Broker returns messages beyond "latest stable offset" to transactional consumer in read_committed mode

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

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

See

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

See Changes: [ismael] MINOR: Reuse decompression buffers in log cleaner [ismael] KAFKA-5272; Policy for Alter Configs (KIP-133) -- [...truncated 2.02 MB...] org.apache.ka

[GitHub] kafka pull request #3222: MINOR: Code Cleanup

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/3222 MINOR: Code Cleanup Clean up includes - Removing some seemingly unnecessary `@SuppressWarnings` annotations - Resolving some Java warnings - Closing unclosed Closable objects -

[GitHub] kafka pull request #3221: KAFKA-5355: DelayedFetch should propagate isolatio...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3221 --- 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-5355) Broker returns messages beyond "latest stable offset" to transactional consumer in read_committed mode

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

[GitHub] kafka pull request #3220: KAFKA-5374: Set allow auto topic creation to false...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3220 --- 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-5374) AdminClient gets "server returned information about unknown correlation ID" when communicating with older brokers

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

[GitHub] kafka pull request #3212: KAFKA-5019: Upgrades notes for idempotent/transact...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3212 --- 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-5019) Exactly-once upgrade notes

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

[jira] [Commented] (KAFKA-5019) Exactly-once upgrade notes

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

[jira] [Resolved] (KAFKA-5374) AdminClient gets "server returned information about unknown correlation ID" when communicating with older brokers

[ https://issues.apache.org/jira/browse/KAFKA-5374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5374. Resolution: Fixed > AdminClient gets "server returned information about unknown correlation ID" > w

[jira] [Commented] (KAFKA-5355) Broker returns messages beyond "latest stable offset" to transactional consumer in read_committed mode

[ https://issues.apache.org/jira/browse/KAFKA-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035841#comment-16035841 ] Ismael Juma commented on KAFKA-5355: We merged [~hachikuji]'s commit that should fix t

[jira] [Assigned] (KAFKA-4291) TopicCommand --describe shows topics marked for deletion as under-replicated and unavailable (KIP-137)

[ https://issues.apache.org/jira/browse/KAFKA-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-4291: -- Assignee: Mickael Maison (was: Ismael Juma) > TopicCommand --describe shows topics marked for

[jira] [Commented] (KAFKA-5296) Unable to write to some partitions of newly created topic in 10.2

[ https://issues.apache.org/jira/browse/KAFKA-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035862#comment-16035862 ] huxihx commented on KAFKA-5296: --- [~asaikia] Do you mean directories for some partitions coul

[jira] [Commented] (KAFKA-5287) Messages getting repeated in kafka

[ https://issues.apache.org/jira/browse/KAFKA-5287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035864#comment-16035864 ] huxihx commented on KAFKA-5287: --- Do you ensure you check status for the same group? > Mess

[jira] [Commented] (KAFKA-5262) Can't find some consumer group information

[ https://issues.apache.org/jira/browse/KAFKA-5262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035865#comment-16035865 ] huxihx commented on KAFKA-5262: --- Does your client code commit offsets? Besides, a complete o

[jira] [Commented] (KAFKA-5098) KafkaProducer.send() blocks and generates TimeoutException if topic name has illegal char

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

[GitHub] kafka pull request #3223: KAFKA-5098: KafkaProducer.send() should validate t...

GitHub user huxihx opened a pull request: https://github.com/apache/kafka/pull/3223 KAFKA-5098: KafkaProducer.send() should validate topic name before sending KafkaProducer.send() should check topic name before sending the record. You can merge this pull request into a Git repositor

[jira] [Assigned] (KAFKA-5098) KafkaProducer.send() blocks and generates TimeoutException if topic name has illegal char

[ https://issues.apache.org/jira/browse/KAFKA-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-5098: - Assignee: huxihx > KafkaProducer.send() blocks and generates TimeoutException if topic name has > illega

<    1   2