Re?? [DISCUSS] KIP-68 Add a consumed log retention before log retention

Hi All, As per our discussion, there are two ways to clean the consumed log: 1) Use an Admin Tool to find the min commit offset for some topics of the specified set of consumer groups, then send the trim API to all the replicas of the brokers, then the brokers will start to trim the log

[GitHub] kafka pull request #2032: KAFKA-3559: Recycle old tasks when possible

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

[jira] [Commented] (KAFKA-3559) Task creation time taking too long in rebalance callback

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

[jira] [Commented] (KAFKA-3559) Task creation time taking too long in rebalance callback

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

[GitHub] kafka pull request #2032: KAFKA-3559: Recycle old tasks when possible

GitHub user enothereska reopened a pull request: https://github.com/apache/kafka/pull/2032 KAFKA-3559: Recycle old tasks when possible You can merge this pull request into a Git repository by running: $ git pull https://github.com/enothereska/kafka

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

See Changes: [wangguoz] KAFKA-3559: Recycle old tasks when possible [wangguoz] KAFKA-4302: Simplify KTableSource [wangguoz] HOTFIX: improve error message on invalid input record timestamp --

[jira] [Commented] (KAFKA-4348) On Mac OS, KafkaConsumer.poll returns 0 when there are still messages on Kafka server

[ https://issues.apache.org/jira/browse/KAFKA-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15620906#comment-15620906 ] huxi commented on KAFKA-4348: - Are there any non-default configs relating to the timeouts on the server side

[GitHub] kafka pull request #2076: HOTFIX: improve error message on invalid input rec...

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

Re: [DISCUSS] KIP-81: Max in-flight fetches

Hi, Mickael, I agree with others that it's better to be able to control the bytes the consumer can read from sockets, instead of limiting the fetch requests. KIP-72 has a proposal to bound the memory size at the socket selector level. Perhaps that can be leveraged in this KIP too.

[GitHub] kafka pull request #2077: MINOR: Fix document header/footer links

GitHub user gwenshap opened a pull request: https://github.com/apache/kafka/pull/2077 MINOR: Fix document header/footer links Based on: https://github.com/apache/kafka-site/pull/27 I recommend also merging into 10.1.0.0 branch to avoid mishaps when re-publishing docs.

Re: [DISCUSS] KIP-72 Allow Sizing Incoming Request Queue in Bytes

Hi, Radai, Sorry for the late response. How should the benchmark results be interpreted? The higher the ops/s, the better? It would also be useful to test this out on LinkedIn's traffic with enough socket connections to see if there is any performance degradation. Also, there is a separate

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

See Changes: [wangguoz] KAFKA-3559: Recycle old tasks when possible [wangguoz] KAFKA-4302: Simplify KTableSource [wangguoz] HOTFIX: improve error message on invalid input record timestamp --

[GitHub] kafka-site pull request #27: fix includes to missing files in 0101 docs and ...

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

Re: [DISCUSS] KIP-72 Allow Sizing Incoming Request Queue in Bytes

Hi Jun, the benchmarks just spawn 16 threads where each thread allocates a chunk of memory from the pool and immediately releases it. 16 was chosen because its typical for LinkedIn setups. the benchmarks never "consume" more than 16 * [single allocation size] and so do not test out-of-memory

[jira] [Commented] (KAFKA-4350) Can't mirror from Kafka 0.9 to Kafka 0.10.1

[ https://issues.apache.org/jira/browse/KAFKA-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15621249#comment-15621249 ] Emanuele Cesena commented on KAFKA-4350: [~hachikuji] Sorry, I'm a bit confused. I need to

[jira] [Commented] (KAFKA-4350) Can't mirror from Kafka 0.9 to Kafka 0.10.1

[ https://issues.apache.org/jira/browse/KAFKA-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15621305#comment-15621305 ] Jiangjie Qin commented on KAFKA-4350: - [~ecesena] In Kafka the wire protocol compatibility is taken

Re: [VOTE] KIP-85: Dynamic JAAS configuration for Kafka clients

Rajini, Thanks for the KIP. +1 Jun On Wed, Oct 26, 2016 at 8:26 AM, Rajini Sivaram < rajinisiva...@googlemail.com> wrote: > I would like to initiate the voting process for KIP-85: Dynamic JAAS > configuration for Kafka Clients: > >

[GitHub] kafka pull request #2032: KAFKA-3559: Recycle old tasks when possible

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

[jira] [Commented] (KAFKA-3559) Task creation time taking too long in rebalance callback

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

[jira] [Resolved] (KAFKA-3559) Task creation time taking too long in rebalance callback

[ https://issues.apache.org/jira/browse/KAFKA-3559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3559. -- Resolution: Fixed Issue resolved by pull request 2032

[GitHub] kafka pull request #2065: KAFKA-4302: Simplify KTableSource

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

[jira] [Commented] (KAFKA-4302) Simplify KTableSource

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

[jira] [Updated] (KAFKA-4302) Simplify KTableSource

[ https://issues.apache.org/jira/browse/KAFKA-4302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4302: - Resolution: Fixed Fix Version/s: 0.10.2.0 Status: Resolved (was: Patch