[jira] [Created] (KAFKA-4674) Frequent ISR shrinking and expanding and disconnects among brokers

Kaiming Wan created KAFKA-4674: -- Summary: Frequent ISR shrinking and expanding and disconnects among brokers Key: KAFKA-4674 URL: https://issues.apache.org/jira/browse/KAFKA-4674 Project: Kafka

[jira] [Updated] (KAFKA-4674) Frequent ISR shrinking and expanding and disconnects among brokers

[ https://issues.apache.org/jira/browse/KAFKA-4674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kaiming Wan updated KAFKA-4674: --- Description: We use a kafka cluster with 3 brokers in production environment. It works well for

[jira] [Updated] (KAFKA-4674) Frequent ISR shrinking and expanding and disconnects among brokers

[ https://issues.apache.org/jira/browse/KAFKA-4674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kaiming Wan updated KAFKA-4674: --- Description: We use a kafka cluster with 3 brokers in production environment. It works well for

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829392#comment-15829392 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829383#comment-15829383 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[GitHub] kafka pull request #2405: KAFKA-3896: Fix KStreamRepartitionJoinTest [WIP]

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/2405 KAFKA-3896: Fix KStreamRepartitionJoinTest [WIP] You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka

[jira] [Commented] (KAFKA-3896) Unstable test KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations

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

[jira] [Commented] (KAFKA-4631) Refresh consumer metadata more frequently for unknown subscribed topics

[ https://issues.apache.org/jira/browse/KAFKA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829268#comment-15829268 ] Guozhang Wang commented on KAFKA-4631: -- I think we do not need a new config for this, hard-coded

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829178#comment-15829178 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829170#comment-15829170 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

Re: [VOTE] KIP-107 Add purgeDataBefore() API in AdminClient

Thanks to everyone who voted and provided feedback! This KIP is now adopted with 3 binding +1s (Jun, Joel, Becket) and 2 non-binding +1s (Radai, Mayuresh). Thanks, Dong On Wed, Jan 18, 2017 at 6:05 PM, Jun Rao wrote: > Hi, Dong, > > Thanks for the update. +1 > > Jun > > On

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

See Changes: [ismael] KAFKA-4457; Add BrokerApiVersionsCommand [wangguoz] KAFKA-4060; Follow-up: Throw exceptions when internal topics to create -- [...truncated 4150 lines...]

Re: [VOTE] KIP-107 Add purgeDataBefore() API in AdminClient

Hi, Dong, Thanks for the update. +1 Jun On Wed, Jan 18, 2017 at 1:44 PM, Dong Lin wrote: > Hi Jun, > > After some more thinking, I agree with you that it is better to simply > throw OffsetOutOfRangeException and not update low_watermark if > offsetToPurge is larger than

[jira] [Commented] (KAFKA-4222) Transient failure in QueryableStateIntegrationTest.queryOnRebalance

[ https://issues.apache.org/jira/browse/KAFKA-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829117#comment-15829117 ] Guozhang Wang commented on KAFKA-4222: -- [~mjsax] Found this failure again after the previous PR is

[jira] [Work started] (KAFKA-4631) Refresh consumer metadata more frequently for unknown subscribed topics

[ https://issues.apache.org/jira/browse/KAFKA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4631 started by Matthias J. Sax. -- > Refresh consumer metadata more frequently for unknown subscribed topics >

[jira] [Commented] (KAFKA-4631) Refresh consumer metadata more frequently for unknown subscribed topics

[ https://issues.apache.org/jira/browse/KAFKA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829053#comment-15829053 ] Matthias J. Sax commented on KAFKA-4631: I don't think we want to add a new config. I like the

[jira] [Commented] (KAFKA-4060) Remove ZkClient dependency in Kafka Streams

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

[GitHub] kafka pull request #2404: KAFKA-4060 and KAFKA-4476 follow up

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2404 KAFKA-4060 and KAFKA-4476 follow up You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka kafka-4060-zk-test-follow-up Alternatively you

[jira] [Created] (KAFKA-4673) Python VerifiableConsumer service has thread-safety bug for event_handlers

Ewen Cheslack-Postava created KAFKA-4673: Summary: Python VerifiableConsumer service has thread-safety bug for event_handlers Key: KAFKA-4673 URL: https://issues.apache.org/jira/browse/KAFKA-4673

[GitHub] kafka pull request #2389: Kafka 4060 remove zk client dependency in kafka st...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2389 --- 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-4457) Add a command to list the broker version information

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

[GitHub] kafka pull request #2184: KAFKA-4457. Add BrokerVersionCommand

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2184 --- 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-4457) Add a command to list the broker version information

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

[GitHub] kafka pull request #2403: MINOR: add Streams system test for broker backward...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2403 MINOR: add Streams system test for broker backwards compatibility You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka

[jira] [Updated] (KAFKA-4672) KIP-100 api changes break Java 8 lambda expressions in some cases

[ https://issues.apache.org/jira/browse/KAFKA-4672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-4672: - Status: Patch Available (was: In Progress) > KIP-100 api changes break Java 8 lambda expressions

[jira] [Commented] (KAFKA-4672) KIP-100 api changes break Java 8 lambda expressions in some cases

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

[jira] [Work started] (KAFKA-4672) KIP-100 api changes break Java 8 lambda expressions in some cases

[ https://issues.apache.org/jira/browse/KAFKA-4672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4672 started by Xavier Léauté. > KIP-100 api changes break Java 8 lambda expressions in some cases >

[GitHub] kafka pull request #2402: KAFKA-4672 fix source compatibility for lambda exp...

GitHub user xvrl opened a pull request: https://github.com/apache/kafka/pull/2402 KAFKA-4672 fix source compatibility for lambda expressions please cherry-pick into 0.10.2.x You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828859#comment-15828859 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[jira] [Updated] (KAFKA-4672) KIP-100 api changes break Java 8 lambda expressions in some cases

[ https://issues.apache.org/jira/browse/KAFKA-4672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-4672: - Description: Variance changes introduced in KIP-100 cause compilation failures with lambda

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828850#comment-15828850 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

Re: [VOTE] KIP-107 Add purgeDataBefore() API in AdminClient

Hi Jun, After some more thinking, I agree with you that it is better to simply throw OffsetOutOfRangeException and not update low_watermark if offsetToPurge is larger than high_watermark. My use-case of allowing low_watermark > high_watermark in 2(b) is to allow user to purge all the data in the

[jira] [Updated] (KAFKA-4671) Fix Streams window retention policy

[ https://issues.apache.org/jira/browse/KAFKA-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4671: --- Status: Patch Available (was: Open) > Fix Streams window retention policy >

[jira] [Commented] (KAFKA-4671) Fix Streams window retention policy

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

[GitHub] kafka pull request #2401: KAFKA-4671: Fix Streams window retention policy

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2401 KAFKA-4671: Fix Streams window retention policy You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka kafka-4671-window-retention-policy

[jira] [Created] (KAFKA-4672) KIP-100 api changes break Java 8 lambda expressions in some cases

Xavier Léauté created KAFKA-4672: Summary: KIP-100 api changes break Java 8 lambda expressions in some cases Key: KAFKA-4672 URL: https://issues.apache.org/jira/browse/KAFKA-4672 Project: Kafka

[GitHub] kafka pull request #2392: MINOR: refactor streams system test class hierachy

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

[GitHub] kafka pull request #2400: MINOR: Clarify misleading comment in WordCount exa...

GitHub user gwenshap opened a pull request: https://github.com/apache/kafka/pull/2400 MINOR: Clarify misleading comment in WordCount example You can merge this pull request into a Git repository by running: $ git pull https://github.com/gwenshap/kafka wordcount-comment

[GitHub] kafka-site pull request #40: Add Grant to committers page

GitHub user granthenke opened a pull request: https://github.com/apache/kafka-site/pull/40 Add Grant to committers page You can merge this pull request into a Git repository by running: $ git pull https://github.com/granthenke/kafka-site add-grant Alternatively you can

[jira] [Created] (KAFKA-4671) Fix Streams window retention policy

Matthias J. Sax created KAFKA-4671: -- Summary: Fix Streams window retention policy Key: KAFKA-4671 URL: https://issues.apache.org/jira/browse/KAFKA-4671 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-3853) Report offsets for empty groups in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828620#comment-15828620 ] Jeff Widman commented on KAFKA-3853: Thanks again for this! Really looking forward to it. > Report

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

See

Re: [VOTE] KIP-107 Add purgeDataBefore() API in AdminClient

Hi, Dong, For 2(b), it seems a bit weird to allow highWatermark to be smaller than lowWatermark. Also, from the consumer's perspective, messages are available only up to highWatermark. What if we simply throw OffsetOutOfRangeException if offsetToPurge is larger than highWatermark? Thanks, Jun

[jira] [Updated] (KAFKA-4596) KIP-73 rebalance throttling breaks on plans for specific partitions

[ https://issues.apache.org/jira/browse/KAFKA-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford updated KAFKA-4596: Status: Patch Available (was: In Progress) > KIP-73 rebalance throttling breaks on plans for

[jira] [Work started] (KAFKA-4596) KIP-73 rebalance throttling breaks on plans for specific partitions

[ https://issues.apache.org/jira/browse/KAFKA-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4596 started by Ben Stopford. --- > KIP-73 rebalance throttling breaks on plans for specific partitions >

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

I've updated the KIP to mention this. I've currently set the size limit to 1Kb. It's large enough so group/heartbeat messages are smaller than it and also small enough so the consumer memory usage stays under control. If there are no more comments, I'll restart the vote On Wed, Jan 18, 2017 at

[jira] [Created] (KAFKA-4670) Kafka Consumer should validate FetchResponse

Roger Hoover created KAFKA-4670: --- Summary: Kafka Consumer should validate FetchResponse Key: KAFKA-4670 URL: https://issues.apache.org/jira/browse/KAFKA-4670 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828491#comment-15828491 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828467#comment-15828467 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

Re: [VOTE] KIP-107 Add purgeDataBefore() API in AdminClient

I forgot to mention this in response to question 2 c). If logEndOffset < offsetToPurge, leader will set low_watermark to min(leader's logEndOffset, max(low_watermark, offsetToPurge)) = logEndOffset. I made this

[GitHub] kafka pull request #2397: HOTFIX: ChangeLoggingKeyValueStore.name() returns ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2397 --- 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-4041) kafka unable to reconnect to zookeeper behind an ELB

[ https://issues.apache.org/jira/browse/KAFKA-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828420#comment-15828420 ] Ryan P commented on KAFKA-4041: --- This is actually the result of a ZK bug which is being actively worked on

[GitHub] kafka pull request #2399: KAFKA 4596: Throttled Replica Reassignment Error

GitHub user benstopford opened a pull request: https://github.com/apache/kafka/pull/2399 KAFKA 4596: Throttled Replica Reassignment Error Fixes a logic error in the Reassignment process which throws an exception if you don't rebalance all partitions. You can merge this pull

[GitHub] kafka pull request #2398: HOTFIX: KIP-104 for code freeze

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/2398 HOTFIX: KIP-104 for code freeze This is the HOTFIX PR for any issues detected with KIP-104 until code freeze. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-4663) Update documentation for Authorizer

[ https://issues.apache.org/jira/browse/KAFKA-4663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828384#comment-15828384 ] Joseph Aliase commented on KAFKA-4663: -- [~ijuma] Yeah would like submit a PR. Let me know how I can

ApacheCon CFP closing soon (11 February)

Hello, fellow Apache enthusiast. Thanks for your participation, and interest in, the projects of the Apache Software Foundation. I wanted to remind you that the Call For Papers (CFP) for ApacheCon North America, and Apache: Big Data North America, closes in less than a month. If you've been

MirrorMaker across Kafka Clusters with different versions

Can MirrorMaker can work across different major versions of Kafka, specifically from a v10 producer to a v8 consumer? I suspect, given that the client API is not backwards compatible, that the answer unfortunately is no. But it would be useful to get a definitive answer on that, and any

[GitHub] kafka pull request #2396: MINOR: Fix javadoc typos in KStream#process

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

[GitHub] kafka pull request #2397: HOTFIX: ChangeLoggingKeyValueStore.name() returns ...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2397 HOTFIX: ChangeLoggingKeyValueStore.name() returns null This class doesn't need to override this method as it is handled appropriately by the super class You can merge this pull request into a Git

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

See Changes: [ismael] KAFKA-4568; Simplify test code for multiple SASL mechanisms -- [...truncated 32745 lines...] kafka.security.auth.SimpleAclAuthorizerTest > testLoadCache PASSED

[GitHub] kafka pull request #2396: MINOR: Fix javadoc typos in KStream#process

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2396 MINOR: Fix javadoc typos in KStream#process interface for `Processor` in comments incorrectly had `transform` rather than `process`. You can merge this pull request into a Git repository by running:

[jira] [Commented] (KAFKA-3155) Transient Failure in kafka.api.PlaintextProducerSendTest.testFlush

[ https://issues.apache.org/jira/browse/KAFKA-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828134#comment-15828134 ] Ismael Juma commented on KAFKA-3155: I ran it on my laptop 250 times with no failures. Will need to

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828122#comment-15828122 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[jira] [Work started] (KAFKA-4639) Kafka Streams metrics are undocumented

[ https://issues.apache.org/jira/browse/KAFKA-4639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4639 started by Eno Thereska. --- > Kafka Streams metrics are undocumented > --

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828084#comment-15828084 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[jira] [Commented] (KAFKA-4615) AdminClient.send function poll without timeout

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

[jira] [Updated] (KAFKA-4615) AdminClient.send function poll without timeout

[ https://issues.apache.org/jira/browse/KAFKA-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Grossetie updated KAFKA-4615: --- Status: Patch Available (was: Open) > AdminClient.send function poll without timeout

[GitHub] kafka pull request #2395: KAFKA-4615: Use a timeout when polling the request...

GitHub user Mogztter opened a pull request: https://github.com/apache/kafka/pull/2395 KAFKA-4615: Use a timeout when polling the request in AdminClient You can merge this pull request into a Git repository by running: $ git pull https://github.com/Mogztter/kafka patch-1

[jira] [Updated] (KAFKA-4669) KafkaProducer.flush hangs when NetworkClient.handleCompletedReceives throws exception

[ https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4669: --- Priority: Critical (was: Major) > KafkaProducer.flush hangs when

[jira] [Resolved] (KAFKA-4568) Simplify multiple mechanism support in SaslTestHarness

[ https://issues.apache.org/jira/browse/KAFKA-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4568. Resolution: Fixed Fix Version/s: 0.10.2.0 Issue resolved by pull request 2373

[jira] [Commented] (KAFKA-4568) Simplify multiple mechanism support in SaslTestHarness

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

[jira] [Updated] (KAFKA-4669) KafkaProducer.flush hangs when NetworkClient.handleCompletedReceives throws exception

[ https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4669: --- Labels: reliability (was: ) > KafkaProducer.flush hangs when NetworkClient.handleCompletedReceives

[jira] [Updated] (KAFKA-4669) KafkaProducer.flush hangs when NetworkClient.handleCompletedReceives throws exception

[ https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4669: --- Fix Version/s: 0.10.2.0 > KafkaProducer.flush hangs when NetworkClient.handleCompletedReceives throws

[GitHub] kafka pull request #2373: KAFKA-4568: Simplify test code for multiple SASL m...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2373 --- 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-114: KTable materialization and improved semantics

I think changing it to `toKStream` would make it absolutely clear what we are converting it to. I'd say we should probably change the KStreamBuilder methods (but not in this KIP). Thanks Eno > On 17 Jan 2017, at 13:59, Michael Noll wrote: > >> Rename toStream() to

Re: [DISCUSS] KIP-114: KTable materialization and improved semantics

Hi Michael, Answers inline: > On 17 Jan 2017, at 12:09, Michael Noll wrote: > > If a KTable models a changelog, why do we call it a KTable, rather than > (say) KChangelogStream? (Perhaps the use of the word "log" in "changelog" > invokes the concept of a "stream" more

Re: [DISCUSS] KIP-114: KTable materialization and improved semantics

Good point, thanks, will update. Eno > On 17 Jan 2017, at 12:04, Michael Noll wrote: > > I think section "Compatibility, Deprecation, and Migration Plan" needs > updating. It currently reads "No impact on existing users" but the KIP > proposes to remove existing API

[jira] [Commented] (KAFKA-1843) Metadata fetch/refresh in new producer should handle all node connection states gracefully

[ https://issues.apache.org/jira/browse/KAFKA-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827789#comment-15827789 ] Rajeev Jain commented on KAFKA-1843: I am still facing the issue addressed by [~omkreddy] in the

[jira] [Updated] (KAFKA-4669) KafkaProducer.flush hangs when NetworkClient.handleCompletedReceives throws exception

[ https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cheng Ju updated KAFKA-4669: Description: There is no try catch in NetworkClient.handleCompletedReceives. If an exception is thrown

[jira] [Created] (KAFKA-4669) KafkaProducer.flush hangs when NetworkClient.handleCompletedReceives throws exception

Cheng Ju created KAFKA-4669: --- Summary: KafkaProducer.flush hangs when NetworkClient.handleCompletedReceives throws exception Key: KAFKA-4669 URL: https://issues.apache.org/jira/browse/KAFKA-4669 Project:

[jira] [Commented] (KAFKA-4668) Mirrormaker should default to auto.offset.reset=earliest

[ https://issues.apache.org/jira/browse/KAFKA-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827769#comment-15827769 ] Jeff Widman commented on KAFKA-4668: Also KAFKA-3848 > Mirrormaker should default to

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827760#comment-15827760 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[jira] [Commented] (KAFKA-1207) Launch Kafka from within Apache Mesos

[ https://issues.apache.org/jira/browse/KAFKA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827733#comment-15827733 ] postmas...@inn.ru commented on KAFKA-1207: -- Delivery is delayed to these recipients or groups:

[jira] [Updated] (KAFKA-4625) Streams smoke tests fails when there is only 1 broker

[ https://issues.apache.org/jira/browse/KAFKA-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4625: Fix Version/s: 0.10.2.0 > Streams smoke tests fails when there is only 1 broker >

[jira] [Updated] (KAFKA-4625) Streams smoke tests fails when there is only 1 broker

[ https://issues.apache.org/jira/browse/KAFKA-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4625: Assignee: Eno Thereska (was: Ewen Cheslack-Postava) > Streams smoke tests fails when there is only

[jira] [Commented] (KAFKA-4668) Mirrormaker should default to auto.offset.reset=earliest

[ https://issues.apache.org/jira/browse/KAFKA-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827680#comment-15827680 ] James Cheng commented on KAFKA-4668: Somewhat related to KAFKA-3370 > Mirrormaker should default to

Re: Is this a bug or just unintuitive behavior?

There is some discussion going on in https://issues.apache.org/jira/browse/KAFKA-3370 about this, as well. I've added a link to your JIRA about it. -James > On Jan 17, 2017, at 9:35 PM, Jeff Widman wrote: > > Agree on

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

See Changes: [jason] KAFKA-3502; move RocksDB options construction to init() -- [...truncated 19318 lines...] org.apache.kafka.streams.processor.internals.RecordCollectorTest >

[Suggestion] Issues on StreamConfig Builder

Hello. This mail is related to KAFKA-4436[^1], which Matthias left a comment recently. I started to investigate this issue from last weekend, and I thought that it would be much better to take your advice. What I would like to talk about this issue is following two things: 1. This issue is much