[jira] [Commented] (KAFKA-4273) Streams DSL - Add TTL / retention period support for intermediate topics and state stores

[ https://issues.apache.org/jira/browse/KAFKA-4273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16010005#comment-16010005 ] Guozhang Wang commented on KAFKA-4273: -- [~vinubarro] I'm wondering if your use case c

[jira] [Commented] (KAFKA-5239) Producer buffer pool allocates memory inside a lock.

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

[GitHub] kafka pull request #3053: KAFKA-5239: Producer buffer pool allocates memory ...

GitHub user smccauliff opened a pull request: https://github.com/apache/kafka/pull/3053 KAFKA-5239: Producer buffer pool allocates memory inside a lock Move byte buffer allocation out of lock. Add unit test for restoring count when OOM is thrown from byte buffer allocation. Yo

[jira] [Created] (KAFKA-5239) Producer buffer pool allocates memory inside a lock.

Sean McCauliff created KAFKA-5239: - Summary: Producer buffer pool allocates memory inside a lock. Key: KAFKA-5239 URL: https://issues.apache.org/jira/browse/KAFKA-5239 Project: Kafka Issue Ty

[jira] [Commented] (KAFKA-5200) Deleting topic when one broker is down will prevent topic to be re-creatable

[ https://issues.apache.org/jira/browse/KAFKA-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009914#comment-16009914 ] huxi commented on KAFKA-5200: - [~ecomar] Seems there is no convenient tool to do this. However

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

See

[jira] [Updated] (KAFKA-5230) Recommended values for Connect transformations contain the wrong class name

[ https://issues.apache.org/jira/browse/KAFKA-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5230: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Recommended values for Connect tr

[GitHub] kafka pull request #3044: KAFKA-5230: Fix conversion of Class configs to han...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3044 --- 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-5230) Recommended values for Connect transformations contain the wrong class name

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

[jira] [Created] (KAFKA-5238) BrokerTopicMetrics can be recreated after topic is deleted

Ismael Juma created KAFKA-5238: -- Summary: BrokerTopicMetrics can be recreated after topic is deleted Key: KAFKA-5238 URL: https://issues.apache.org/jira/browse/KAFKA-5238 Project: Kafka Issue Ty

[jira] [Commented] (KAFKA-5237) SimpleConsumerShell logs terminating message to stdout instead of stderr

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

[GitHub] kafka pull request #3052: KAFKA-5237 - change logging of termination message...

GitHub user deinspanjer opened a pull request: https://github.com/apache/kafka/pull/3052 KAFKA-5237 - change logging of termination message to use stderr instead of stdout You can merge this pull request into a Git repository by running: $ git pull https://github.com/deinspan

[jira] [Created] (KAFKA-5237) SimpleConsumerShell logs terminating message to stdout instead of stderr

Daniel Einspanjer created KAFKA-5237: Summary: SimpleConsumerShell logs terminating message to stdout instead of stderr Key: KAFKA-5237 URL: https://issues.apache.org/jira/browse/KAFKA-5237 Projec

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16009863#comment-16009863 ] Ismael Juma commented on KAFKA-5236: Thanks for the report. The root cause is that the

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

Nick Travers created KAFKA-5236: --- Summary: Regression in on-disk log size when using Snappy compression with 0.8.2 log message format Key: KAFKA-5236 URL: https://issues.apache.org/jira/browse/KAFKA-5236

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

See

[jira] [Commented] (KAFKA-5235) GetOffsetShell: retrieve offsets for all given topics and partitions with single request to the broker

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

[GitHub] kafka pull request #3051: KAFKA-5235: GetOffsetShell: new KafkaConsumer API,...

GitHub user tashoyan opened a pull request: https://github.com/apache/kafka/pull/3051 KAFKA-5235: GetOffsetShell: new KafkaConsumer API, support for multiple topics, minimized number of requests to server This PR addresses two improvements: [KAFKA-5235 GetOffsetShell: retri

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

See Changes: [ismael] MINOR: Handle nulls in NonEmptyListValidator -- [...truncated 858.64 KB...] kafka.log.BrokerCompressionTest > testBrokerSideCompression[4] PASSED ka

[GitHub] kafka pull request #3045: MINOR: Handle nulls in NonEmptyListValidator

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3045 --- 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-4850) RocksDb cannot use Bloom Filters

[ https://issues.apache.org/jira/browse/KAFKA-4850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated KAFKA-4850: -- Status: In Progress (was: Patch Available) > RocksDb cannot use Bloom Filters > ---

[jira] [Commented] (KAFKA-5235) GetOffsetShell: retrieve offsets for all given topics and partitions with single request to the broker

[ https://issues.apache.org/jira/browse/KAFKA-5235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009800#comment-16009800 ] Arseniy Tashoyan commented on KAFKA-5235: - How can I assign this issue on myself?

[jira] [Commented] (KAFKA-5235) GetOffsetShell: retrieve offsets for all given topics and partitions with single request to the broker

[ https://issues.apache.org/jira/browse/KAFKA-5235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009792#comment-16009792 ] Arseniy Tashoyan commented on KAFKA-5235: - Both improvements can be done in scope

[jira] [Created] (KAFKA-5235) GetOffsetShell: retrieve offsets for all given topics and partitions with single request to the broker

Arseniy Tashoyan created KAFKA-5235: --- Summary: GetOffsetShell: retrieve offsets for all given topics and partitions with single request to the broker Key: KAFKA-5235 URL: https://issues.apache.org/jira/browse/KA

[jira] [Created] (KAFKA-5234) GetOffsetShell: retrieve offsets for multiple topics with single request

Arseniy Tashoyan created KAFKA-5234: --- Summary: GetOffsetShell: retrieve offsets for multiple topics with single request Key: KAFKA-5234 URL: https://issues.apache.org/jira/browse/KAFKA-5234 Project:

Please subscribe me

Please subscribe me

[jira] [Commented] (KAFKA-5232) Kafka broker fails to start if a topic containing dot in its name is marked for delete but hasn't been deleted during previous uptime

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

[GitHub] kafka pull request #3050: (trunk) KAFKA-5232 Fix Log.parseTopicPartitionName...

GitHub user jaikiran opened a pull request: https://github.com/apache/kafka/pull/3050 (trunk) KAFKA-5232 Fix Log.parseTopicPartitionName to take into account dot character in topic names of deleted topics The commit here contains a fix and a test case for the issue reported in http

[jira] [Commented] (KAFKA-3356) Remove ConsumerOffsetChecker, deprecated in 0.9, in 0.11

[ https://issues.apache.org/jira/browse/KAFKA-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009693#comment-16009693 ] Mickael Maison commented on KAFKA-3356: --- Features of ConsumerOffsetChecker: - For a

[jira] [Assigned] (KAFKA-5232) Kafka broker fails to start if a topic containing dot in its name is marked for delete but hasn't been deleted during previous uptime

[ https://issues.apache.org/jira/browse/KAFKA-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-5232: -- Assignee: jaikiran pai > Kafka broker fails to start if a topic containing dot in its name is m

[jira] [Updated] (KAFKA-5232) Kafka broker fails to start if a topic containing dot in its name is marked for delete but hasn't been deleted during previous uptime

[ https://issues.apache.org/jira/browse/KAFKA-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5232: --- Priority: Critical (was: Major) > Kafka broker fails to start if a topic containing dot in its name i

[jira] [Updated] (KAFKA-5232) Kafka broker fails to start if a topic containing dot in its name is marked for delete but hasn't been deleted during previous uptime

[ https://issues.apache.org/jira/browse/KAFKA-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5232: --- Fix Version/s: 0.11.0.0 > Kafka broker fails to start if a topic containing dot in its name is marked

[jira] [Updated] (KAFKA-5232) Kafka broker fails to start if a topic containing dot in its name is marked for delete but hasn't been deleted during previous uptime

[ https://issues.apache.org/jira/browse/KAFKA-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5232: --- Fix Version/s: 0.10.2.2 > Kafka broker fails to start if a topic containing dot in its name is marked

RE: [DISCUSS] KIP-148: Add a connect timeout for client

Hi Guozhang, Sorry for the delay, thanks for the question. It seems two different parameters to me: connect.timeout.ms: only work for the connecting phrase, after connected phrase this parameter is not used. connections.max.idle.ms: currently not work in the connecting phrase (only select ret

[GitHub] kafka pull request #3049: MINOR: removed code duplicates from several files ...

GitHub user wlsc opened a pull request: https://github.com/apache/kafka/pull/3049 MINOR: removed code duplicates from several files (KafkaStreams) This PR offers following to KafkaStreams project: * removed code duplication from **TopologyBuilder**'s function **makeNodeGroups**

[jira] [Commented] (KAFKA-3480) Autogenerate metrics documentation

[ https://issues.apache.org/jira/browse/KAFKA-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009633#comment-16009633 ] James Cheng commented on KAFKA-3480: I tried rebasing this PR, and it was way too hard

[jira] [Updated] (KAFKA-5191) Autogenerate Consumer Fetcher metrics

[ https://issues.apache.org/jira/browse/KAFKA-5191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Cheng updated KAFKA-5191: --- Attachment: docs_now_include_partition_level_metrics.png The generated docs now include the partition-