[GitHub] kafka-site issue #29: Update the website repo link in code.html to point to ...

Github user becketqin commented on the issue: https://github.com/apache/kafka-site/pull/29 @ijuma The github site has stated that it is mirrored from the Apache repo. I added the link anyways. --- If your project is set up for it, you can reply to this email and have your reply

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

See

[jira] [Commented] (KAFKA-4381) Add per partition lag metric to KafkaConsumer.

[ https://issues.apache.org/jira/browse/KAFKA-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15638178#comment-15638178 ] Jiangjie Qin commented on KAFKA-4381: - [~hachikuji] [~junrao] [~guozhang] [~ewencp] Do you think we

[GitHub] kafka-site issue #29: Update the website repo link in code.html to point to ...

Github user ijuma commented on the issue: https://github.com/apache/kafka-site/pull/29 Good catch, you probably want to include that link to that Apache Git repo as well. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well.

[GitHub] kafka-site pull request #29: Update the website repo link in code.html to po...

GitHub user becketqin opened a pull request: https://github.com/apache/kafka-site/pull/29 Update the website repo link in code.html to point to github. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka-site

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

here are my proposed changes: https://github.com/radai-rosenblatt/kafka/commit/8d7744ab8a6c660c4749b495b033b948a68efd3c at this point i've run this code on a test cluster under load that OOMs "vanilla" 0.10.1.0 and verified that my code deployed under the same condition remains stable. what

[GitHub] kafka pull request #2099: MINOR: Fix re-raise of python error in system test...

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

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

See Changes: [me] MINOR: missing fullstop in doc for `max.partition.fetch.bytes` -- [...truncated 7217 lines...] kafka.admin.AdminTest > testShutdownBroker STARTED kafka.admin.AdminTest >

[jira] [Created] (KAFKA-4383) Update API design subsection to reflect the current implementation of Producer/Consumer

Konstantine Karantasis created KAFKA-4383: - Summary: Update API design subsection to reflect the current implementation of Producer/Consumer Key: KAFKA-4383 URL:

[jira] [Created] (KAFKA-4382) Fix broken fragments in site docs

Konstantine Karantasis created KAFKA-4382: - Summary: Fix broken fragments in site docs Key: KAFKA-4382 URL: https://issues.apache.org/jira/browse/KAFKA-4382 Project: Kafka Issue

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

See Changes: [me] MINOR: missing fullstop in doc for `max.partition.fetch.bytes` -- [...truncated 3866 lines...] kafka.integration.SaslPlaintextTopicMetadataTest >

[jira] [Work started] (KAFKA-4381) Add per partition lag metric to KafkaConsumer.

[ https://issues.apache.org/jira/browse/KAFKA-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4381 started by Jiangjie Qin. --- > Add per partition lag metric to KafkaConsumer. >

[jira] [Created] (KAFKA-4381) Add per partition lag metric to KafkaConsumer.

Jiangjie Qin created KAFKA-4381: --- Summary: Add per partition lag metric to KafkaConsumer. Key: KAFKA-4381 URL: https://issues.apache.org/jira/browse/KAFKA-4381 Project: Kafka Issue Type: Task

[jira] [Commented] (KAFKA-4161) Decouple flush and offset commits

[ https://issues.apache.org/jira/browse/KAFKA-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15637718#comment-15637718 ] Shikhar Bhushan commented on KAFKA-4161: Created KIP-89 for this

[DISCUSS] KIP-89: Allow sink connectors to decouple flush and offset commit

Hi all, I created KIP-89 for making a Connect API change that allows for sink connectors to decouple flush and offset commits. https://cwiki.apache.org/confluence/display/KAFKA/KIP-89%3A+Allow+sink+connectors+to+decouple+flush+and+offset+commit I'd welcome your input. Best, Shikhar

[jira] [Updated] (KAFKA-4322) StateRestoreCallback begin and end indication

[ https://issues.apache.org/jira/browse/KAFKA-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Shelton updated KAFKA-4322: Flags: Patch > StateRestoreCallback begin and end indication >

[GitHub] kafka pull request #1968: MINOR: missing whitespace in doc for `ssl.cipher.s...

Github user shikhar closed the pull request at: https://github.com/apache/kafka/pull/1968 --- 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-4322) StateRestoreCallback begin and end indication

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

[GitHub] kafka pull request #2105: KAFKA-4322 StateRestoreCallback begin and end indi...

GitHub user markcshelton opened a pull request: https://github.com/apache/kafka/pull/2105 KAFKA-4322 StateRestoreCallback begin and end indication This adds a begin and end callback to StateRestoreCallback. The contribution is my original work and I license the work to

[jira] [Commented] (KAFKA-4380) Remove CleanShutdownFile as 0.8.2 has been released

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

[GitHub] kafka pull request #2104: [KAFKA-4380] Remove cleanshutdownfile

GitHub user holdenk opened a pull request: https://github.com/apache/kafka/pull/2104 [KAFKA-4380] Remove cleanshutdownfile This PR removes the cleanshutdownfile as suggested in the code comments as a TODO. Use of this seems to be well covered by existing tests (some of

[jira] [Commented] (KAFKA-4380) Remove CleanShutdownFile as 0.8.2 has been released

[ https://issues.apache.org/jira/browse/KAFKA-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15637658#comment-15637658 ] holdenk commented on KAFKA-4380: Working on this, but I don't seem to be able to assign it to myself. >

[jira] [Created] (KAFKA-4380) Remove CleanShutdownFile as 0.8.2 has been released

holdenk created KAFKA-4380: -- Summary: Remove CleanShutdownFile as 0.8.2 has been released Key: KAFKA-4380 URL: https://issues.apache.org/jira/browse/KAFKA-4380 Project: Kafka Issue Type:

[GitHub] kafka pull request #1969: MINOR: missing fullstop in doc for `max.partition....

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

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

See Changes: [me] KAFKA-4372: Kafka Connect REST API does not handle DELETE of connector -- [...truncated 7941 lines...] kafka.utils.CommandLineUtilsTest > testParseSingleArg STARTED

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

See

[jira] [Updated] (KAFKA-3994) Deadlock between consumer heartbeat expiration and offset commit.

[ https://issues.apache.org/jira/browse/KAFKA-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3994: --- Fix Version/s: (was: 0.10.2.0) 0.10.1.1 > Deadlock between consumer

Re: 0.10.1.0 - KafkaConsumer.poll() blocks background heartbeat thread causing consumer to be considered dead?

Hey Jaikiran, Thanks for the report. We shouldn't hold the lock in poll() longer than the heartbeat interval, so if you're seeing this, it's probably a bug. Let me see if I can reproduce it. One quick question about the code snippet. What kind of executor are you using? Is the load on the topic

[jira] [Resolved] (KAFKA-4372) Kafka Connect REST API does not handle DELETE of connector with slashes in their names

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

[jira] [Commented] (KAFKA-4372) Kafka Connect REST API does not handle DELETE of connector with slashes in their names

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

[GitHub] kafka pull request #2096: KAFKA-4372: Kafka Connect REST API does not handle...

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

Hi Evan, Thanks for the detailed comments. Sorry for the late reply. As most of the community members are not in favor of of adding Rest proxy to Kafka, we decided to drop the KIP proposal. We will work with Confluent's kafka-rest project community to contribute new features. Also, thanks for

Re: why cant SslTransportLayer be muted before handshake completion?

the root issue is i may not have enough available memory to read from the socket. I'll do the simple thing and just avoid muting handshaking sockets, for now. On Wed, Nov 2, 2016 at 6:59 PM, Harsha Chintalapani wrote: > HI Radai, > One main reason is to keep the

ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted message

Hi all, We recently discovered an issue in Kafka 0.9.0.1 (), where ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted message. As the same logic exists also in Kafka 0.10.0.0 and 0.10.0.1, they may have the similar issue. Here are system logs related to this issue. >

[jira] [Updated] (KAFKA-4366) KafkaStreams.close() blocks indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-4366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4366: -- Status: Patch Available (was: In Progress) > KafkaStreams.close() blocks indefinitely >

[jira] [Updated] (KAFKA-4379) Remove caching of dirty and removed keys from StoreChangeLogger

[ https://issues.apache.org/jira/browse/KAFKA-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4379: -- Status: Patch Available (was: In Progress) > Remove caching of dirty and removed keys from

[jira] [Commented] (KAFKA-3151) kafka-consumer-groups.sh fail with sasl enabled

[ https://issues.apache.org/jira/browse/KAFKA-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15636247#comment-15636247 ] Balint Molnar commented on KAFKA-3151: -- [~linbao111] please create a for example grouprop.properties

[GitHub] kafka pull request #2103: KAFKA-4379: Remove caching of dirty and removed ke...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2103 KAFKA-4379: Remove caching of dirty and removed keys from StoreChangeLogger The `StoreChangeLogger` currently keeps a cache of dirty and removed keys and will batch the changelog records such that we

[jira] [Commented] (KAFKA-4379) Remove caching of dirty and removed keys from StoreChangeLogger

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

[jira] [Work started] (KAFKA-4379) Remove caching of dirty and removed keys from StoreChangeLogger

[ https://issues.apache.org/jira/browse/KAFKA-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4379 started by Damian Guy. - > Remove caching of dirty and removed keys from StoreChangeLogger >

[jira] [Created] (KAFKA-4379) Remove caching of dirty and removed keys from StoreChangeLogger

Damian Guy created KAFKA-4379: - Summary: Remove caching of dirty and removed keys from StoreChangeLogger Key: KAFKA-4379 URL: https://issues.apache.org/jira/browse/KAFKA-4379 Project: Kafka

[jira] [Resolved] (KAFKA-4371) Sporadic ConnectException shuts down the whole connect process

[ https://issues.apache.org/jira/browse/KAFKA-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Rao resolved KAFKA-4371. -- Resolution: Not A Problem > Sporadic ConnectException shuts down the whole connect process >

[jira] [Commented] (KAFKA-4371) Sporadic ConnectException shuts down the whole connect process

[ https://issues.apache.org/jira/browse/KAFKA-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15636091#comment-15636091 ] Sagar Rao commented on KAFKA-4371: -- [~ewencp] By shutting down I meant that the processing of data

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

See Changes: [jason] KAFKA-4024; Override client metadata backoff on topic changes and avoid [jason] MINOR: Add description of how consumer wakeup acts if no threads are -- [...truncated 6618

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

See Changes: [jason] KAFKA-4024; Override client metadata backoff on topic changes and avoid [jason] MINOR: Add description of how consumer wakeup acts if no threads are -- [...truncated 954

[GitHub] kafka pull request #2093: MINOR: Add description of how consumer wakeup acts...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2093 --- 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] [Updated] (KAFKA-4024) First metadata update always take retry.backoff.ms milliseconds to complete

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

[GitHub] kafka pull request #1707: KAFKA-4024: Fix metadata update to not apply backo...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1707 --- 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-4024) First metadata update always take retry.backoff.ms milliseconds to complete

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