[jira] [Work started] (KAFKA-4408) KTable doesn't work with ProcessorTopologyTestDriver in Kafka 0.10.1.0

[ https://issues.apache.org/jira/browse/KAFKA-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4408 started by Hamidreza Afzali. --- > KTable doesn't work with ProcessorTopologyTestDriver in Kafka 0.10.1.0 >

[jira] [Assigned] (KAFKA-4408) KTable doesn't work with ProcessorTopologyTestDriver in Kafka 0.10.1.0

[ https://issues.apache.org/jira/browse/KAFKA-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hamidreza Afzali reassigned KAFKA-4408: --- Assignee: Hamidreza Afzali > KTable doesn't work with ProcessorTopologyTestDriver in

[jira] [Commented] (KAFKA-4408) KTable doesn't work with ProcessorTopologyTestDriver in Kafka 0.10.1.0

[ https://issues.apache.org/jira/browse/KAFKA-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15896843#comment-15896843 ] Hamidreza Afzali commented on KAFKA-4408: - This should resolve the issue:

[jira] [Updated] (KAFKA-4845) KafkaConsumer.seekToEnd cannot take effect when integrating with spark streaming

[ https://issues.apache.org/jira/browse/KAFKA-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan updated KAFKA-4845: --- Status: Open (was: Patch Available) > KafkaConsumer.seekToEnd cannot take effect when integrating with spark >

[jira] [Updated] (KAFKA-4845) KafkaConsumer.seekToEnd cannot take effect when integrating with spark streaming

[ https://issues.apache.org/jira/browse/KAFKA-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan updated KAFKA-4845: --- Status: Patch Available (was: Open) > KafkaConsumer.seekToEnd cannot take effect when integrating with spark >

[jira] [Commented] (KAFKA-4844) kafka is holding open file descriptors

[ https://issues.apache.org/jira/browse/KAFKA-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15896815#comment-15896815 ] huxi commented on KAFKA-4844: - What is your OS version? Seems it's a known behavior before NFS 4. > kafka is

[jira] [Created] (KAFKA-4845) KafkaConsumer.seekToEnd cannot take effect when integrating with spark streaming

Dan created KAFKA-4845: -- Summary: KafkaConsumer.seekToEnd cannot take effect when integrating with spark streaming Key: KAFKA-4845 URL: https://issues.apache.org/jira/browse/KAFKA-4845 Project: Kafka

[jira] [Resolved] (KAFKA-4828) ProcessorTopologyTestDriver does not work when using .through()

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

[jira] [Commented] (KAFKA-4828) ProcessorTopologyTestDriver does not work when using .through()

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

[GitHub] kafka pull request #2629: KAFKA-4828: ProcessorTopologyTestDriver does not w...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2629 --- 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-112: Handle disk failure for JBOD

Hey Jun, I am happy to work for a few days if that is what it takes to discuss KIP-113. But if it takes 2+ weeks to discuss KIP-113, I wondering if we can vote for KIP-112 first. We aim to start JBOD test in a test cluster by end of Q1 and there is only three weeks from that. If we can miss the

[jira] [Commented] (KAFKA-4834) Kafka cannot delete topic with ReplicaStateMachine went wrong

[ https://issues.apache.org/jira/browse/KAFKA-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15896740#comment-15896740 ] Dan commented on KAFKA-4834: By invoking AdminUtils.deleteTopic(zkUtils, topic). It seemed something wrong

[jira] [Closed] (KAFKA-4076) Kafka broker shuts down due to irrecoverable IO error

[ https://issues.apache.org/jira/browse/KAFKA-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anyun closed KAFKA-4076. - > Kafka broker shuts down due to irrecoverable IO error > - > >

[jira] [Commented] (KAFKA-4076) Kafka broker shuts down due to irrecoverable IO error

[ https://issues.apache.org/jira/browse/KAFKA-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15896739#comment-15896739 ] Anyun commented on KAFKA-4076: --- Thanks,I changed dir of kafka-logs and error No longer appear any more >

[GitHub] kafka pull request #2640: 0.10.2

Github user sjmittal closed the pull request at: https://github.com/apache/kafka/pull/2640 --- 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-4657) Improve test coverage of CompositeReadOnlyWindowStore

[ https://issues.apache.org/jira/browse/KAFKA-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15896706#comment-15896706 ] Guozhang Wang commented on KAFKA-4657: -- [~damianguy] Could you update the description? > Improve

[jira] [Created] (KAFKA-4844) kafka is holding open file descriptors

chao created KAFKA-4844: --- Summary: kafka is holding open file descriptors Key: KAFKA-4844 URL: https://issues.apache.org/jira/browse/KAFKA-4844 Project: Kafka Issue Type: Bug Affects Versions:

[jira] [Updated] (KAFKA-4842) Streams integration tests occasionally fail with connection error

[ https://issues.apache.org/jira/browse/KAFKA-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4842: --- Component/s: streams > Streams integration tests occasionally fail with connection error >

Re: [VOTE] KIP-123: Allow per stream/table timestamp extractor

Guozhang, about renaming the config parameters. I like this idea, but want to point out, that this change should be done in a backward compatible way. Thus, we need to keep (and only deprecate) the current parameter names. I am not sure about (2)? What do you worry about? Using a "stateful

[jira] [Commented] (KAFKA-4657) Improve test coverage of CompositeReadOnlyWindowStore

[ https://issues.apache.org/jira/browse/KAFKA-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15896576#comment-15896576 ] Andrey Dyachkov commented on KAFKA-4657: I would like to grab, but it is not clear what should be

[jira] [Commented] (KAFKA-3491) Issue with consumer close() in finally block with 'enable.auto.commit=true'

[ https://issues.apache.org/jira/browse/KAFKA-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15896561#comment-15896561 ] Gwen Shapira commented on KAFKA-3491: - Very late to the party, but it looks like the issue is still

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

See Changes: [cshapi] KAFKA-4276: Add REST configuration in connector properties [cshapi] KAFKA-4567 - Connect Producer and Consumer ignore ssl parameters… --

[jira] [Updated] (KAFKA-4825) Likely Data Loss in ReassignPartitionsTest System Test

[ https://issues.apache.org/jira/browse/KAFKA-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4825: --- Labels: reliability (was: ) > Likely Data Loss in ReassignPartitionsTest System Test >

Add to contributor list

Hi, Please add me to contributor list. JIRA user name - geeky.rajaguru Thanks. Regards, Raja Guru T

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

See Changes: [wangguoz] KAFKA-4826: Fix some findbugs warnings in Kafka Streams -- [...truncated 157.03 KB...] kafka.security.auth.SimpleAclAuthorizerTest >

[jira] [Commented] (KAFKA-4567) Connect Producer and Consumer ignore ssl parameters configured for worker

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

[jira] [Resolved] (KAFKA-4567) Connect Producer and Consumer ignore ssl parameters configured for worker

[ https://issues.apache.org/jira/browse/KAFKA-4567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-4567. - Resolution: Fixed Fix Version/s: 0.11.0.0 Issue resolved by pull request 2511

[GitHub] kafka pull request #2511: KAFKA-4567 - Connect Producer and Consumer ignore ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2511 --- 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] [Resolved] (KAFKA-4792) Kafka Connect: Add ByteArray Converter

[ https://issues.apache.org/jira/browse/KAFKA-4792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-4792. - Resolution: Duplicate > Kafka Connect: Add ByteArray Converter >

[jira] [Updated] (KAFKA-4280) Add REST resource for showing available connector plugin configs

[ https://issues.apache.org/jira/browse/KAFKA-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-4280: Labels: newbie (was: ) > Add REST resource for showing available connector plugin configs >

[jira] [Commented] (KAFKA-4276) REST configuration not visible in connector properties config files

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

[jira] [Updated] (KAFKA-4276) REST configuration not visible in connector properties config files

[ https://issues.apache.org/jira/browse/KAFKA-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-4276: Resolution: Fixed Fix Version/s: 0.11.0.0 Status: Resolved (was: Patch Available)

[GitHub] kafka pull request #2505: KAFKA-4276: Add REST configuration in connector pr...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2505 --- 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-4115) Grow default heap settings for distributed Connect from 256M to 1G

[ https://issues.apache.org/jira/browse/KAFKA-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-4115: Labels: newbie (was: ) > Grow default heap settings for distributed Connect from 256M to 1G >

[jira] [Updated] (KAFKA-3832) Kafka Connect's JSON Converter never outputs a null value

[ https://issues.apache.org/jira/browse/KAFKA-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3832: Labels: newbie (was: ) > Kafka Connect's JSON Converter never outputs a null value >

[jira] [Commented] (KAFKA-4826) Fix some findbugs warnings in Kafka Streams

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

[jira] [Resolved] (KAFKA-4826) Fix some findbugs warnings in Kafka Streams

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

[GitHub] kafka pull request #2623: KAFKA-4826. Fix some findbugs warnings in Kafka St...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2623 --- 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-4843) Stream round-robin scheduler is inneficient

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

[GitHub] kafka pull request #2643: KAFKA-4843: More efficient round-robin scheduler

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/2643 KAFKA-4843: More efficient round-robin scheduler - Improves streams efficiency by more than 200K requests/second (small 100 byte requests) - Gets streams efficiency very close to pure

[jira] [Work started] (KAFKA-4843) Stream round-robin scheduler is inneficient

[ https://issues.apache.org/jira/browse/KAFKA-4843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4843 started by Eno Thereska. --- > Stream round-robin scheduler is inneficient >

[jira] [Created] (KAFKA-4843) Stream round-robin scheduler is inneficient

Eno Thereska created KAFKA-4843: --- Summary: Stream round-robin scheduler is inneficient Key: KAFKA-4843 URL: https://issues.apache.org/jira/browse/KAFKA-4843 Project: Kafka Issue Type:

[GitHub] kafka pull request #2642: Fix retryWithBackoff and onPartitionsRevoked issue...

GitHub user sjmittal opened a pull request: https://github.com/apache/kafka/pull/2642 Fix retryWithBackoff and onPartitionsRevoked issues. Fixes related to handling of MAX_POLL_INTERVAL_MS_CONFIG during deadlock and CommitFailedException on partition revoked. You can merge this

[jira] [Created] (KAFKA-4842) Streams integration tests occasionally fail with connection error

Eno Thereska created KAFKA-4842: --- Summary: Streams integration tests occasionally fail with connection error Key: KAFKA-4842 URL: https://issues.apache.org/jira/browse/KAFKA-4842 Project: Kafka

[jira] [Updated] (KAFKA-4841) NetworkClient should only consider a connection to be fail after attempt to connect

[ https://issues.apache.org/jira/browse/KAFKA-4841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-4841: Description: KAFKA-4820 allows new request to be enqueued to unsent by user thread while some other thread

[jira] [Updated] (KAFKA-4841) NetworkClient should only consider a connection to be fail after attempt to connect

[ https://issues.apache.org/jira/browse/KAFKA-4841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-4841: Description: KAFKA-4820 allows new request to be enqueued to unsent by user thread while some other thread

[jira] [Updated] (KAFKA-4841) NetworkClient should only consider a connection to be fail after attempt to connect

[ https://issues.apache.org/jira/browse/KAFKA-4841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-4841: Summary: NetworkClient should only consider a connection to be fail after attempt to connect (was:

[jira] [Created] (KAFKA-4841) NetworkClient should only consider a connection to be fail after attempt to connct

Dong Lin created KAFKA-4841: --- Summary: NetworkClient should only consider a connection to be fail after attempt to connct Key: KAFKA-4841 URL: https://issues.apache.org/jira/browse/KAFKA-4841 Project:

[GitHub] kafka pull request #2641: KAFKA-4586 followup; Fix testMaxPollIntervalMsDela...

GitHub user lindong28 opened a pull request: https://github.com/apache/kafka/pull/2641 KAFKA-4586 followup; Fix testMaxPollIntervalMsDelayInRevocation test failure You can merge this pull request into a Git repository by running: $ git pull https://github.com/lindong28/kafka

[jira] [Commented] (KAFKA-4586) Add purgeDataBefore() API in AdminClient

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

[GitHub] kafka pull request #2640: 0.10.2

GitHub user sjmittal opened a pull request: https://github.com/apache/kafka/pull/2640 0.10.2 Fixes related to handling of MAX_POLL_INTERVAL_MS_CONFIG deadlock and CommitFailedException You can merge this pull request into a Git repository by running: $ git pull