[jira] [Updated] (KAFKA-4679) Remove unstable markers from Connect APIs

[ https://issues.apache.org/jira/browse/KAFKA-4679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4679: - Status: Patch Available (was: Open) > Remove unstable markers from Connect APIs >

[jira] [Updated] (KAFKA-4679) Remove unstable markers from Connect APIs

[ https://issues.apache.org/jira/browse/KAFKA-4679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4679: - Priority: Blocker (was: Major) > Remove unstable markers from Connect APIs >

[jira] [Updated] (KAFKA-4450) Add missing 0.10.1.x upgrade tests and ensure ongoing compatibility checks

[ https://issues.apache.org/jira/browse/KAFKA-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4450: - Status: Patch Available (was: Open) > Add missing 0.10.1.x upgrade tests and ensu

[jira] [Updated] (KAFKA-3209) Support single message transforms in Kafka Connect

[ https://issues.apache.org/jira/browse/KAFKA-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3209: - Status: Patch Available (was: Reopened) > Support single message transforms in Ka

[jira] [Commented] (KAFKA-3209) Support single message transforms in Kafka Connect

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

[GitHub] kafka pull request #2458: KAFKA-3209: KIP-66: Flatten and Cast single messag...

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/2458 KAFKA-3209: KIP-66: Flatten and Cast single message transforms You can merge this pull request into a Git repository by running: $ git pull https://github.com/ewencp/kafka kafka-3209-even-more-

[jira] [Created] (KAFKA-4706) Unify StreamsKafkaClient instances

Matthias J. Sax created KAFKA-4706: -- Summary: Unify StreamsKafkaClient instances Key: KAFKA-4706 URL: https://issues.apache.org/jira/browse/KAFKA-4706 Project: Kafka Issue Type: Improvement

[jira] [Updated] (KAFKA-3209) Support single message transforms in Kafka Connect

[ https://issues.apache.org/jira/browse/KAFKA-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3209: - Priority: Blocker (was: Major) > Support single message transforms in Kafka Conne

[jira] [Reopened] (KAFKA-3209) Support single message transforms in Kafka Connect

[ https://issues.apache.org/jira/browse/KAFKA-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reopened KAFKA-3209: -- Assignee: Ewen Cheslack-Postava (was: Shikhar Bhushan) > Support single messa

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

See Changes: [wangguoz] MINOR: Update JavaDoc for DSL PAPI-API [jason] MINOR: Close create topics policy during shutdown and more tests [wangguoz] MINOR: Add Streams system test for broker backwards compatibility [wangguoz] MINOR: S

Re: [DISCUSS]- JIRA ISSUE KAFKA-4566 : Can't Symlink to Kafka bins

Hi Colin, I had picked up this bug from when it was reported specifically for the script 'kafka-console-consumer.sh'. Going through the bug description it seemed the reporter wanted to call the scripts form maybe another location using symlinks. Hence the extra code to replicate the readlink

Re: [DISCUSS] KIP-98: Exactly Once Delivery and Transactional Messaging

Eugen, moving your email to the main thread so that it doesn't get split. The `transaction.app.id` is a prerequisite for using transactional APIs. And only messages wrapped inside transactions will enjoy idempotent guarantees across sessions, and that too only when they employ a consume-process-pr

[GitHub] kafka pull request #2437: MINOR: Streams API JavaDoc improvements

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

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

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

[GitHub] kafka pull request #2443: MINOR: Close create topics policy during shutdown ...

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

[GitHub] kafka pull request #2413: MINOR: update JavaDoc for DSL PAPI-API

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

Guaranteeing cross-session idempotency with KIP-98

KIP-98 says > transaction.app.id: A unique and persistent way to identify a producer. This is used to ensure idempotency and to enable transaction recovery or rollback across producer sessions. This is optional: you will lose cross-session guarantees if this is blank. which might suggest th

[jira] [Commented] (KAFKA-4450) Add missing 0.10.1.x upgrade tests and ensure ongoing compatibility checks

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

[GitHub] kafka pull request #2457: KAFKA-4450: Add upgrade tests for 0.10.1 releases ...

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/2457 KAFKA-4450: Add upgrade tests for 0.10.1 releases and rename TRUNK to CURRENT_BRANCH to reduce confusion. You can merge this pull request into a Git repository by running: $ git pull https://g

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

See

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

See Changes: [jason] MINOR: Change logging level for ignored maybeAddMetric from debug to [ismael] KAFKA-4636; Per listener security settings overrides (KIP-103) -- [...truncated 8307 lines...]

Re: [DISCUSS] KIP-111 : Kafka should preserve the Principal generated by the PrincipalBuilder while processing the request received on socket channel, on the broker.

Hi Dong, Thanks for the review. Please see the replies inline. 1. I am not sure we need to add the method buildPrincipal(Map principalConfigs). It seems that user can simply do principalBuilder.configure(...).buildPrincipal(...) without using that method. -> I am not sure if I understand

[jira] [Commented] (KAFKA-4636) Per listener security setting overrides (KIP-103)

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

[jira] [Updated] (KAFKA-4636) Per listener security setting overrides (KIP-103)

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

[GitHub] kafka pull request #2406: KAFKA-4636; Per listener security settings overrid...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2406 --- 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-4705) ConfigDef should support deprecated keys as synonyms

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

[jira] [Updated] (KAFKA-4705) ConfigDef should support deprecated keys as synonyms

[ https://issues.apache.org/jira/browse/KAFKA-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-4705: --- Status: Patch Available (was: Open) > ConfigDef should support deprecated keys as synonyms >

[jira] [Created] (KAFKA-4705) ConfigDef should support deprecated keys as synonyms

Colin P. McCabe created KAFKA-4705: -- Summary: ConfigDef should support deprecated keys as synonyms Key: KAFKA-4705 URL: https://issues.apache.org/jira/browse/KAFKA-4705 Project: Kafka Issue

[GitHub] kafka pull request #2456: KAFKA-4705: ConfigDef should support deprecated ke...

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/2456 KAFKA-4705: ConfigDef should support deprecated keys as synonyms You can merge this pull request into a Git repository by running: $ git pull https://github.com/cmccabe/kafka KAFKA-4705 Alter

[GitHub] kafka pull request #2454: MINOR: Change loggin for ignored maybeAddMetric fr...

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

Re: Trying to understand design decision about producer ack and min.insync.replicas

I was thinking about the situation where you have less brokers in the ISR list than the number set in min.insync.replicas. My idea was that if I, as an administrator, for a given topic, want to favor durability over availability, then if that topic has less ISR than the value set in min.insync.rep

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

See Changes: [jason] KAFKA-4699; Invoke producer callbacks before completing the future -- [...truncated 19165 lines...] org.apache.kafka.streams.kstream.KStreamBuilderTest > shouldHaveCorrect

[jira] [Commented] (KAFKA-4704) Group coordinator cache loading fails if groupId is used first for consumer groups and then for simple consumer

[ https://issues.apache.org/jira/browse/KAFKA-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840663#comment-15840663 ] Onur Karaman commented on KAFKA-4704: - It might be worth mentioning that I hit a simil

Jenkins build is back to normal : kafka-0.10.2-jdk7 #41

See

[jira] [Commented] (KAFKA-4704) Group coordinator cache loading fails if groupId is used first for consumer groups and then for simple consumer

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

[GitHub] kafka pull request #2455: KAFKA-4704: Coordinator cache loading fails if gro...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/2455 KAFKA-4704: Coordinator cache loading fails if groupId is reused for offset storage after group is removed You can merge this pull request into a Git repository by running: $ git pull https

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

See

[GitHub] kafka pull request #2453: MINOR: Escape '<' and '>' symbols in quickstart st...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2453 --- 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] [Created] (KAFKA-4704) Group coordinator cache loading fails if groupId is used first for consumer groups and then for simple consumer

Jason Gustafson created KAFKA-4704: -- Summary: Group coordinator cache loading fails if groupId is used first for consumer groups and then for simple consumer Key: KAFKA-4704 URL: https://issues.apache.org/jira/br

[jira] [Created] (KAFKA-4703) Test with two SASL_SSL listeners with different JAAS contexts

Ismael Juma created KAFKA-4703: -- Summary: Test with two SASL_SSL listeners with different JAAS contexts Key: KAFKA-4703 URL: https://issues.apache.org/jira/browse/KAFKA-4703 Project: Kafka Issu

[jira] [Commented] (KAFKA-4700) StreamsKafkaClient drops security configs

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

Re: Kafka Multiple Consumer Group for Same Topic

Hi Senthil, You can just try it yourself, using kafka-consumer-perf-test.sh bundled with Apache Kafka. You can start 2 in parallel with different groups and see what happens if you tune some parameters. Joris On Wed, Jan 25, 2017, 08:38 Senthil Kumar wrote: > Thanks Sharninder! > > Adding dev

[GitHub] kafka pull request #2441: KAFKA-4700: Don't drop security configs in `Stream...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2441 --- 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-4700) StreamsKafkaClient drops security configs

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

[GitHub] kafka pull request #2433: Update kafka-run-class.bat

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

[GitHub] kafka pull request #2454: MINOR: Change loggin for ignored maybeAddMetric fr...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/2454 MINOR: Change loggin for ignored maybeAddMetric from debug to trace You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka KMi

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840494#comment-15840494 ] Dave Thomas commented on KAFKA-2729: Same with us, on 0.10.1.1 (following upgrade from

[GitHub] kafka pull request #2436: HOTFIX: Consumer offsets not properly loaded on co...

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

[GitHub] kafka pull request #2453: MINOR: Escape '<' and '>' symbols in quickstart st...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/2453 MINOR: Escape '<' and '>' symbols in quickstart streams code snippet This was missing from [an earlier PR](https://github.com/apache/kafka/pull/2247) that escaped these symbols in another se

[jira] [Commented] (KAFKA-4665) Inconsistent handling of non-existing topics in offset fetch handling

[ https://issues.apache.org/jira/browse/KAFKA-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840346#comment-15840346 ] Vahid Hashemian commented on KAFKA-4665: {quote} Note also that currently the cons

[jira] [Work started] (KAFKA-4665) Inconsistent handling of non-existing topics in offset fetch handling

[ https://issues.apache.org/jira/browse/KAFKA-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4665 started by Vahid Hashemian. -- > Inconsistent handling of non-existing topics in offset fetch handling > ---

Build failed in Jenkins: kafka-0.10.2-jdk7 #40

See Changes: [jason] KAFKA-4699; Invoke producer callbacks before completing the future -- [...truncated 4065 lines...] kafka.integration.SslTopicMetadataTest > testAliveBrokersListWithNoTopics

[jira] [Commented] (KAFKA-4517) Remove kafka-consumer-offset-checker.sh script since already deprecated in Kafka 9

[ https://issues.apache.org/jira/browse/KAFKA-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840259#comment-15840259 ] Ewen Cheslack-Postava commented on KAFKA-4517: -- oh, I missed the PR, but yeah

[jira] [Updated] (KAFKA-4667) Connect should create internal topics

[ https://issues.apache.org/jira/browse/KAFKA-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4667: - Summary: Connect should create internal topics (was: Connect (and Stream?) should

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

See Changes: [jason] KAFKA-4699; Invoke producer callbacks before completing the future -- [...truncated 4064 lines...] kafka.producer.AsyncProducerTest > testInvalidPartition STARTED kafka.pr

Re: Trying to understand design decision about producer ack and min.insync.replicas

The acks setting for the producer doesn't affect the final durability guarantees. These are still enforced by the replication and min ISR settings. Instead, the ack setting just lets the producer control how durable the write is before *that producer* can consider the write "complete", i.e. before

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

Hey Colin, Thanks much for the comment. Please see me comment inline. On Thu, Jan 26, 2017 at 10:15 AM, Colin McCabe wrote: > On Wed, Jan 25, 2017, at 13:50, Dong Lin wrote: > > Hey Colin, > > > > Good point! Yeah we have actually considered and tested this solution, > > which we call one-broke

[jira] [Updated] (KAFKA-3429) Remove Serdes needed for repartitioning in KTable stateful operations

[ https://issues.apache.org/jira/browse/KAFKA-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3429: --- Fix Version/s: (was: 0.10.2.0) > Remove Serdes needed for repartitioning in KTable statefu

[jira] [Updated] (KAFKA-4649) Improve test coverage GlobalStateManagerImpl

[ https://issues.apache.org/jira/browse/KAFKA-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4649: -- Status: Patch Available (was: Open) > Improve test coverage GlobalStateManagerImpl > --

[jira] [Commented] (KAFKA-4649) Improve test coverage GlobalStateManagerImpl

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

[GitHub] kafka pull request #2452: KAFKA-4649: Improve test coverage GlobalStateManag...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2452 KAFKA-4649: Improve test coverage GlobalStateManagerImpl Add coverage for exception paths in `initialize()` You can merge this pull request into a Git repository by running: $ git pull https://git

[jira] [Assigned] (KAFKA-4649) Improve test coverage GlobalStateManagerImpl

[ https://issues.apache.org/jira/browse/KAFKA-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-4649: - Assignee: Damian Guy > Improve test coverage GlobalStateManagerImpl > ---

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

On Wed, Jan 25, 2017, at 13:50, Dong Lin wrote: > Hey Colin, > > Good point! Yeah we have actually considered and tested this solution, > which we call one-broker-per-disk. It would work and should require no > major change in Kafka as compared to this JBOD KIP. So it would be a good > short term

[jira] [Commented] (KAFKA-4640) Improve Streams unit test coverage

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

[jira] [Updated] (KAFKA-4648) Improve test coverage StreamTask

[ https://issues.apache.org/jira/browse/KAFKA-4648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4648: -- Status: Patch Available (was: Open) > Improve test coverage StreamTask > --

[GitHub] kafka pull request #2451: KAFKA-4640: Improve test coverage StreamTask

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2451 KAFKA-4640: Improve test coverage StreamTask Provide test coverage for exception paths in: `schedule()`, `closeTopology()`, and `punctuate()` You can merge this pull request into a Git repository by r

[jira] [Commented] (KAFKA-4699) Transient Failure PlaintextConsumerTest.testInterceptros

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

[GitHub] kafka pull request #2440: KAFKA-4699: Invoke producer callbacks before compl...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2440 --- 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] [Resolved] (KAFKA-4699) Transient Failure PlaintextConsumerTest.testInterceptros

[ https://issues.apache.org/jira/browse/KAFKA-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-4699. Resolution: Fixed Issue resolved by pull request 2440 [https://github.com/apache/kafka/pull/

[jira] [Assigned] (KAFKA-4648) Improve test coverage StreamTask

[ https://issues.apache.org/jira/browse/KAFKA-4648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-4648: - Assignee: Damian Guy > Improve test coverage StreamTask > > >

Re: [VOTE] KIP-115: Enforce offsets.topic.replication.factor

+1 (non-binding) On Wed, Jan 25, 2017, at 16:34, Onur Karaman wrote: > I'd like to start the vote for KIP-115: Enforce > offsets.topic.replication.factor > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-115%3A+Enforce+offsets.topic.replication.factor > > - Onur

Re: [DISCUSS] KIP-115: Enforce offsets.topic.replication.factor

Hi all, +1 (non-binding) for KIP-115. On Thu, Jan 26, 2017, at 04:26, Stevo Slavić wrote: > If I understood well, this KIP is trying to solve for the problem of > offsets.topic.replication.factor not being enforced, particularly in > context of "when you have clients or tooling running as the cl

[jira] [Commented] (KAFKA-4647) Improve test coverage of GlobalStreamThread

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

[jira] [Updated] (KAFKA-4647) Improve test coverage of GlobalStreamThread

[ https://issues.apache.org/jira/browse/KAFKA-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4647: -- Status: Patch Available (was: Open) > Improve test coverage of GlobalStreamThread > ---

[GitHub] kafka pull request #2450: KAFKA-4647: Improve test coverage of GlobalStreamT...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2450 KAFKA-4647: Improve test coverage of GlobalStreamThread Add a test to ensure a `StreamsException` is thrown when an exception other than `StreamsException` is caught You can merge this pull request in

[jira] [Commented] (KAFKA-4676) Kafka consumers gets stuck for some partitions

[ https://issues.apache.org/jira/browse/KAFKA-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840024#comment-15840024 ] Ismael Juma commented on KAFKA-4676: [~hachikuji], is this something that we need to f

[jira] [Assigned] (KAFKA-4647) Improve test coverage of GlobalStreamThread

[ https://issues.apache.org/jira/browse/KAFKA-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-4647: - Assignee: Damian Guy > Improve test coverage of GlobalStreamThread >

[jira] [Work started] (KAFKA-4702) Parametrize streams benchmarks to run at scale

[ https://issues.apache.org/jira/browse/KAFKA-4702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4702 started by Eno Thereska. --- > Parametrize streams benchmarks to run at scale >

[jira] [Created] (KAFKA-4702) Parametrize streams benchmarks to run at scale

Eno Thereska created KAFKA-4702: --- Summary: Parametrize streams benchmarks to run at scale Key: KAFKA-4702 URL: https://issues.apache.org/jira/browse/KAFKA-4702 Project: Kafka Issue Type: Improv

[jira] [Commented] (KAFKA-4557) ConcurrentModificationException in KafkaProducer event loop

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

[GitHub] kafka pull request #2449: KAFKA-4557: Handle Producer.send correctly in expi...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/2449 KAFKA-4557: Handle Producer.send correctly in expiry callbacks When iterating deque for expiring record batches, delay the actual completion of the batch until iteration is complete since call

[jira] [Commented] (KAFKA-4644) Improve test coverage of StreamsPartitionAssignor

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

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

[ https://issues.apache.org/jira/browse/KAFKA-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska resolved KAFKA-4694. - Resolution: Fixed > Streams smoke tests fails when there is only 1 broker > --

[GitHub] kafka pull request #2448: KAFKA-4644: Improve test coverage of StreamsPartit...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2448 KAFKA-4644: Improve test coverage of StreamsPartitionAssignor Some exception paths not previously covered. Extracted `ensureCopartitioning` into a static class. You can merge this pull request into a

[jira] [Updated] (KAFKA-4644) Improve test coverage of StreamsPartitionAssignor

[ https://issues.apache.org/jira/browse/KAFKA-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4644: -- Status: Patch Available (was: Open) > Improve test coverage of StreamsPartitionAssignor > -

[jira] [Commented] (KAFKA-4569) Transient failure in org.apache.kafka.clients.consumer.KafkaConsumerTest.testWakeupWithFetchDataAvailable

[ https://issues.apache.org/jira/browse/KAFKA-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839945#comment-15839945 ] Ismael Juma commented on KAFKA-4569: [~umesh9...@gmail.com], have you tried running th

[jira] [Updated] (KAFKA-4569) Transient failure in org.apache.kafka.clients.consumer.KafkaConsumerTest.testWakeupWithFetchDataAvailable

[ https://issues.apache.org/jira/browse/KAFKA-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4569: --- Fix Version/s: (was: 0.10.2.0) 0.10.3.0 > Transient failure in > org.apache.ka

[jira] [Updated] (KAFKA-2334) Prevent HW from going back during leader failover

[ https://issues.apache.org/jira/browse/KAFKA-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2334: --- Labels: reliability (was: ) > Prevent HW from going back during leader failover > --

[jira] [Updated] (KAFKA-4637) Update system test(s) to use multiple listeners for the same security protocol

[ https://issues.apache.org/jira/browse/KAFKA-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4637: --- Fix Version/s: (was: 0.10.2.0) 0.10.3.0 > Update system test(s) to use multiple

[jira] [Updated] (KAFKA-2334) Prevent HW from going back during leader failover

[ https://issues.apache.org/jira/browse/KAFKA-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2334: --- Fix Version/s: (was: 0.10.2.0) 0.10.3.0 > Prevent HW from going back during lea

[jira] [Updated] (KAFKA-3779) Add the LRU cache for KTable.to() operator

[ https://issues.apache.org/jira/browse/KAFKA-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-3779: Fix Version/s: (was: 0.10.2.0) 0.10.3.0 > Add the LRU cache for KTable.to() o

[jira] [Commented] (KAFKA-3779) Add the LRU cache for KTable.to() operator

[ https://issues.apache.org/jira/browse/KAFKA-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839942#comment-15839942 ] Eno Thereska commented on KAFKA-3779: - [~ijuma] Done, thanks. > Add the LRU cache for

[jira] [Commented] (KAFKA-3429) Remove Serdes needed for repartitioning in KTable stateful operations

[ https://issues.apache.org/jira/browse/KAFKA-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839941#comment-15839941 ] Ismael Juma commented on KAFKA-3429: Should we move this to a future release version (

[jira] [Commented] (KAFKA-3779) Add the LRU cache for KTable.to() operator

[ https://issues.apache.org/jira/browse/KAFKA-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839939#comment-15839939 ] Ismael Juma commented on KAFKA-3779: Should we move this to a future release version (

[jira] [Updated] (KAFKA-4701) Allow kafka brokers to dynamically reload truststore without restarting.

[ https://issues.apache.org/jira/browse/KAFKA-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Xiang updated KAFKA-4701: --- Description: Right now in order to add SSL clients(update broker truststores), a rolling restart of al

[jira] [Assigned] (KAFKA-1368) Upgrade log4j

[ https://issues.apache.org/jira/browse/KAFKA-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison reassigned KAFKA-1368: - Assignee: Mickael Maison > Upgrade log4j > - > > Key: KAFKA-1

[jira] [Assigned] (KAFKA-4644) Improve test coverage of StreamsPartitionAssignor

[ https://issues.apache.org/jira/browse/KAFKA-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-4644: - Assignee: Damian Guy > Improve test coverage of StreamsPartitionAssignor > --

[jira] [Commented] (KAFKA-4646) Improve test coverage AbstractProcessorContext

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

[jira] [Updated] (KAFKA-4646) Improve test coverage AbstractProcessorContext

[ https://issues.apache.org/jira/browse/KAFKA-4646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4646: -- Status: Patch Available (was: Reopened) > Improve test coverage AbstractProcessorContext >

[GitHub] kafka pull request #2447: KAFKA-4646: Improve test coverage AbstractProcesso...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2447 KAFKA-4646: Improve test coverage AbstractProcessorContext Exception paths in `register()`, `topic()`, `partition()`, `offset()`, and `timestamp()`, were not covered by any existing tests You can merg

  1   2   >