[jira] [Commented] (KAFKA-4335) FileStreamSource Connector not working for large files (~ 1GB)

[ https://issues.apache.org/jira/browse/KAFKA-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15604115#comment-15604115 ] Rahul Shukla commented on KAFKA-4335: - It did not throw any exception but not producing content to the

[jira] [Commented] (KAFKA-4339) Failing ConsumerGroupCommand System Tests

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

[GitHub] kafka pull request #2061: KAFKA-4339: Update system tests to accommodate the...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/2061 KAFKA-4339: Update system tests to accommodate the new consumer group describe output You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-4339) Failing ConsumerGroupCommand System Tests

[ https://issues.apache.org/jira/browse/KAFKA-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15604019#comment-15604019 ] Vahid Hashemian commented on KAFKA-4339: Sure, I'll submit a PR shortly, and then kick off the

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

See Changes: [junrao] KAFKA-2089; Increase metadata wait time in unit test -- [...truncated 6388 lines...] kafka.api.AuthorizerIntegrationTest >

[GitHub] kafka pull request #1985: MINOR: A bunch of clean-ups related to usage of un...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1985 --- 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-4337) Create topic in multiple zookeepers with Kafka AdminUtils.CreateTopic JAVA API in Kafka 0.9.0.1 gives Error (Topic gets created in only one of the specified zookeeper)

[ https://issues.apache.org/jira/browse/KAFKA-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603917#comment-15603917 ] Ismael Juma commented on KAFKA-4337: Yes, this is not a valid bug. You can configure multiple

[jira] [Comment Edited] (KAFKA-4337) Create topic in multiple zookeepers with Kafka AdminUtils.CreateTopic JAVA API in Kafka 0.9.0.1 gives Error (Topic gets created in only one of the specified zookee

[ https://issues.apache.org/jira/browse/KAFKA-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603886#comment-15603886 ] huxi edited comment on KAFKA-4337 at 10/25/16 1:57 AM: --- Zookeeper client will try to

[jira] [Commented] (KAFKA-4337) Create topic in multiple zookeepers with Kafka AdminUtils.CreateTopic JAVA API in Kafka 0.9.0.1 gives Error (Topic gets created in only one of the specified zookeeper)

[ https://issues.apache.org/jira/browse/KAFKA-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603886#comment-15603886 ] huxi commented on KAFKA-4337: - After checking the source code, zookeeper client will try to connect to the

[jira] [Created] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

Jiangjie Qin created KAFKA-4340: --- Summary: Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms Key: KAFKA-4340 URL: https://issues.apache.org/jira/browse/KAFKA-4340

[jira] [Commented] (KAFKA-4099) Change the time based log rolling to only based on the message timestamp.

[ https://issues.apache.org/jira/browse/KAFKA-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603857#comment-15603857 ] Jiangjie Qin commented on KAFKA-4099: - [~junrao] Good point about making

[jira] [Updated] (KAFKA-4339) Failing ConsumerGroupCommand System Tests

[ https://issues.apache.org/jira/browse/KAFKA-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4339: --- Fix Version/s: 0.10.2.0 > Failing ConsumerGroupCommand System Tests >

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

Hi, Rajini, Thanks for the proposal. It looks very useful. Jun On Mon, Oct 24, 2016 at 6:27 AM, Rajini Sivaram < rajinisiva...@googlemail.com> wrote: > If there are no more comments or suggestions, I will start voting process > for this KIP later this week. > > Please feel free to add any

[jira] [Commented] (KAFKA-4339) Failing ConsumerGroupCommand System Tests

[ https://issues.apache.org/jira/browse/KAFKA-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603853#comment-15603853 ] Ismael Juma commented on KAFKA-4339: Expecting the topic name sounds good. It would be great to have a

[jira] [Commented] (KAFKA-4337) Create topic in multiple zookeepers with Kafka AdminUtils.CreateTopic JAVA API in Kafka 0.9.0.1 gives Error (Topic gets created in only one of the specified zookeeper)

[ https://issues.apache.org/jira/browse/KAFKA-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603845#comment-15603845 ] huxi commented on KAFKA-4337: - could you paste how you specify multiple zookeeper IPs? Those should be comma

[jira] [Commented] (KAFKA-4295) kafka-console-consumer.sh does not delete the temporary group in zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603797#comment-15603797 ] huxi commented on KAFKA-4295: - [~guozhang] Seems that pull request always got wrong due to failing to pass

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

See

Re: [VOTE] KIP-47 - Add timestamp-based log deletion policy

Hi Jun, Those are valid concerns. For our particular use case, application events triggering the timestamp update will never occur more than once an hour, and we maintain a sliding window so that we don't delete messages too close to what our consumers may be reading. For more general use cases,

[jira] [Commented] (KAFKA-4339) Failing ConsumerGroupCommand System Tests

[ https://issues.apache.org/jira/browse/KAFKA-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603683#comment-15603683 ] Vahid Hashemian commented on KAFKA-4339: [~hachikuji] This issue is very likely because we no

Re: [VOTE] KIP-47 - Add timestamp-based log deletion policy

Hi, Bill, Thanks for the proposal. Sorry for the late reply. The motivation of the proposal makes sense: don't delete the messages until the application tells you so. I am wondering if the current proposal is the best way to address the need though. There are couple of issues that I saw with

[jira] [Commented] (KAFKA-4339) Failing ConsumerGroupCommand System Tests

[ https://issues.apache.org/jira/browse/KAFKA-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603576#comment-15603576 ] Vahid Hashemian commented on KAFKA-4339: Thanks [~hachikuji]. I'll take a look. > Failing

[jira] [Updated] (KAFKA-4211) Change system tests to use the new consumer by default

[ https://issues.apache.org/jira/browse/KAFKA-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-4211: --- Status: Patch Available (was: In Progress) > Change system tests to use the new consumer by

[GitHub] kafka pull request #2060: KAFKA-4211: Update system tests to use the new con...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/2060 KAFKA-4211: Update system tests to use the new consumer by default Update system test method signatures and method calls to use the new consumer by default. You can merge this pull request

[jira] [Commented] (KAFKA-4339) Failing ConsumerGroupCommand System Tests

[ https://issues.apache.org/jira/browse/KAFKA-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603569#comment-15603569 ] Jason Gustafson commented on KAFKA-4339: [~vahid] I went ahead and assigned you since you are most

[jira] [Commented] (KAFKA-4211) Change system tests to use the new consumer by default

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

[jira] [Created] (KAFKA-4339) Failing ConsumerGroupCommand System Tests

Jason Gustafson created KAFKA-4339: -- Summary: Failing ConsumerGroupCommand System Tests Key: KAFKA-4339 URL: https://issues.apache.org/jira/browse/KAFKA-4339 Project: Kafka Issue Type: Bug

Re: [VOTE] KIP-73 - Replication Quotas

Yes, that sounds like a good idea. Updated the wiki for KIP-73. Thanks, Jun On Fri, Oct 21, 2016 at 4:26 PM, Joel Koshy wrote: > Thanks for catching that and the fix as well. Makes sense to me. > > We should consider adding an "amendments" section to KIPs - perhaps just a

[jira] [Commented] (KAFKA-2089) MetadataTest transient failure

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

[jira] [Updated] (KAFKA-4333) Report consumer group coordinator id when '--list' option is used

[ https://issues.apache.org/jira/browse/KAFKA-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-4333: --- Status: Patch Available (was: In Progress) > Report consumer group coordinator id when

[GitHub] kafka pull request #2057: KAFKA-2089: Increase metadata wait time in unit te...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2057 --- 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-2089) MetadataTest transient failure

[ https://issues.apache.org/jira/browse/KAFKA-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-2089. Resolution: Fixed Fix Version/s: (was: 0.9.0.0) 0.10.2.0 Issue resolved by

[GitHub] kafka pull request #2059: KAFKA-4333: Report coordinator id of the consumer ...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/2059 KAFKA-4333: Report coordinator id of the consumer group with '--list' option Enahnce the output of the consumer group commend and report the coordinator id of each group (for Java API based

[jira] [Commented] (KAFKA-4333) Report consumer group coordinator id when '--list' option is used

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

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

See

[GitHub] kafka pull request #2054: kafka-4295: ConsoleConsumer does not delete the te...

Github user amethystic closed the pull request at: https://github.com/apache/kafka/pull/2054 --- 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 #2058: kafka-4295: ConsoleConsumer does not delete the te...

GitHub user amethystic opened a pull request: https://github.com/apache/kafka/pull/2058 kafka-4295: ConsoleConsumer does not delete the temporary group in zookeeper ConsoleConsumer does not delete the temporary group in zookeeper Author: huxi...@hotmail.com Since consumer

[jira] [Updated] (KAFKA-4185) Abstract out password verifier in SaslServer as an injectable dependency

[ https://issues.apache.org/jira/browse/KAFKA-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4185: --- Fix Version/s: (was: 0.10.0.2) 0.10.2.0 > Abstract out password verifier in

[jira] [Updated] (KAFKA-3585) Shutdown slow when there is only one broker which is controller

[ https://issues.apache.org/jira/browse/KAFKA-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3585: --- Fix Version/s: (was: 0.10.0.2) 0.10.2.0 > Shutdown slow when there is only one

[jira] [Updated] (KAFKA-4116) Specifying 0.0.0.0 in "listeners" doesn't work

[ https://issues.apache.org/jira/browse/KAFKA-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4116: --- Fix Version/s: (was: 0.10.0.2) 0.10.2.0 > Specifying 0.0.0.0 in "listeners"

[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 ] Ismael Juma updated KAFKA-3994: --- Fix Version/s: (was: 0.10.1.1) (was: 0.10.0.2) 0.10.2.0

[jira] [Updated] (KAFKA-3986) completedReceives can contain closed channels

[ https://issues.apache.org/jira/browse/KAFKA-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3986: --- Fix Version/s: 0.10.1.1 > completedReceives can contain closed channels >

[jira] [Updated] (KAFKA-3493) Replica fetcher load is not balanced over fetcher threads

[ https://issues.apache.org/jira/browse/KAFKA-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3493: --- Fix Version/s: (was: 0.10.0.2) 0.10.2.0 > Replica fetcher load is not balanced

[jira] [Updated] (KAFKA-3135) Unexpected delay before fetch response transmission

[ https://issues.apache.org/jira/browse/KAFKA-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3135: --- Fix Version/s: (was: 0.10.0.2) 0.10.2.0 > Unexpected delay before fetch

[jira] [Updated] (KAFKA-3190) KafkaProducer should not invoke callback in send()

[ https://issues.apache.org/jira/browse/KAFKA-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3190: --- Fix Version/s: (was: 0.10.0.2) 0.10.2.0 > KafkaProducer should not invoke

[jira] [Updated] (KAFKA-3123) Follower Broker cannot start if offsets are already out of range

[ https://issues.apache.org/jira/browse/KAFKA-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3123: --- Fix Version/s: (was: 0.10.0.2) 0.10.2.0 > Follower Broker cannot start if

[jira] [Commented] (KAFKA-4099) Change the time based log rolling to only based on the message timestamp.

[ https://issues.apache.org/jira/browse/KAFKA-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603377#comment-15603377 ] Jun Rao commented on KAFKA-4099: [~becket_qin], thanks the explanation. What you described makes sense. So

Re: [DISCUSS] KIP-80: Kafka REST Server

If we want to start a vote on this, I suggest starting a [VOTE] thread instead of mentioning it in the middle of a very long [DISCUSS] thread. :) Ismael On Mon, Oct 24, 2016 at 9:46 PM, Ben Davison wrote: > This KIP has got muddy on differing opinions of what should

[jira] [Resolved] (KAFKA-4338) Release Kafka 0.10.1.0 on Maven Central

[ https://issues.apache.org/jira/browse/KAFKA-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emanuele Cesena resolved KAFKA-4338. Resolution: Invalid Omg, you're right! Sorry about that. > Release Kafka 0.10.1.0 on Maven

[jira] [Commented] (KAFKA-4338) Release Kafka 0.10.1.0 on Maven Central

[ https://issues.apache.org/jira/browse/KAFKA-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603250#comment-15603250 ] Stevo Slavic commented on KAFKA-4338: - It's already there. See

[jira] [Created] (KAFKA-4338) Release Kafka 0.10.1.0 on Maven Central

Emanuele Cesena created KAFKA-4338: -- Summary: Release Kafka 0.10.1.0 on Maven Central Key: KAFKA-4338 URL: https://issues.apache.org/jira/browse/KAFKA-4338 Project: Kafka Issue Type: Task

[GitHub] kafka pull request #2015: Small refactoring to improve readability and reduc...

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

This KIP has got muddy on differing opinions of what should be part of Kafka etc. I agree with Suresh, let's have a vote on if we actually want a REST client in Kafka core, and then we can work out what it actually looks like (personally I would like to reuse Confluents, great REST client if they

[jira] [Commented] (KAFKA-4331) Kafka Streams resetter is slow because it joins the same group for each topic

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

[GitHub] kafka pull request #2049: KAFKA-4331: Kafka Streams resetter is slow because...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2049 --- 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-4331) Kafka Streams resetter is slow because it joins the same group for each topic

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

Re: [DISCUSS] KIP-80: Kafka REST Server

Hey Suresh, I think we agree that REST apis are useful. I don't think we agree that they need to be part of the Kafka project. We've had this discussion a dozen odd times for different protocols---AMQP, REST, MQTT. Going back the last five years we've always rejected these. That doesn't mean they

Re: [DISCUSS] KIP-80: Kafka REST Server

I am dividing this discussion into two parts: 1. REST APIs as core Apache Kafka capability This should be a core Kafka functionality. Same view has been reflected by others (users and developers) as well. While we can debate whether other capabilities are core Kafka (Streams, Connect), it would be

[jira] [Commented] (KAFKA-4335) FileStreamSource Connector not working for large files (~ 1GB)

[ https://issues.apache.org/jira/browse/KAFKA-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15602851#comment-15602851 ] Ewen Cheslack-Postava commented on KAFKA-4335: -- Can you be more specific about what isn't

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

Overall I think the motivation is common and of interests to lots of users. Would like to throw my two cents on this discussion: 1. Kafka topics can be used in different ways. For some categories of topics (think: "pageView" event topics), it is a shared topic among different teams / apps within

Re: Kafka KIP meeting Oct 19 at 11:00am PST

I agree with Nacho. +1 for the KIP. Thanks, Mayuresh On Fri, Oct 21, 2016 at 11:46 AM, Nacho Solis wrote: > I think a separate KIP is a good idea as well. Note however that potential > decisions in this KIP could affect the other KIP. > > Nacho > > On Fri, Oct

[jira] [Created] (KAFKA-4337) Create topic in multiple zookeepers with Kafka AdminUtils.CreateTopic JAVA API in Kafka 0.9.0.1 gives Error (Topic gets created in only one of the specified zookeeper)

Bharat Patel created KAFKA-4337: --- Summary: Create topic in multiple zookeepers with Kafka AdminUtils.CreateTopic JAVA API in Kafka 0.9.0.1 gives Error (Topic gets created in only one of the specified zookeeper) Key: KAFKA-4337

[jira] [Commented] (KAFKA-4099) Change the time based log rolling to only based on the message timestamp.

[ https://issues.apache.org/jira/browse/KAFKA-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15602189#comment-15602189 ] Ismael Juma commented on KAFKA-4099: I filed KAFKA-4336 to make sure we don't lose track of this. It

[jira] [Created] (KAFKA-4335) FileStreamSource Connector not working for large files (~ 1GB)

Rahul Shukla created KAFKA-4335: --- Summary: FileStreamSource Connector not working for large files (~ 1GB) Key: KAFKA-4335 URL: https://issues.apache.org/jira/browse/KAFKA-4335 Project: Kafka

[jira] [Commented] (KAFKA-4336) Frequent log rolling when there's a mix of delayed and current data

[ https://issues.apache.org/jira/browse/KAFKA-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15602187#comment-15602187 ] Ismael Juma commented on KAFKA-4336: cc [~junrao] [~becket_qin] [~ewencp] [~norwood] > Frequent log

[jira] [Created] (KAFKA-4336) Frequent log rolling when there's a mix of delayed and current data

Ismael Juma created KAFKA-4336: -- Summary: Frequent log rolling when there's a mix of delayed and current data Key: KAFKA-4336 URL: https://issues.apache.org/jira/browse/KAFKA-4336 Project: Kafka

[jira] [Comment Edited] (KAFKA-4273) Streams DSL - Add TTL / retention period support for intermediate topics and state stores

[ https://issues.apache.org/jira/browse/KAFKA-4273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15602159#comment-15602159 ] Davor Poldrugo edited comment on KAFKA-4273 at 10/24/16 2:36 PM: - Is this

[jira] [Comment Edited] (KAFKA-4273) Streams DSL - Add TTL / retention period support for intermediate topics and state stores

[ https://issues.apache.org/jira/browse/KAFKA-4273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15602159#comment-15602159 ] Davor Poldrugo edited comment on KAFKA-4273 at 10/24/16 2:34 PM: - Is this

[jira] [Commented] (KAFKA-4273) Streams DSL - Add TTL / retention period support for intermediate topics and state stores

[ https://issues.apache.org/jira/browse/KAFKA-4273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15602159#comment-15602159 ] Davor Poldrugo commented on KAFKA-4273: --- Is this possibly resolved in 0.10.1.0 with streams config:

[jira] [Commented] (KAFKA-2089) MetadataTest transient failure

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

[GitHub] kafka pull request #2057: KAFKA-2089: Increase metadata wait time in unit te...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/2057 KAFKA-2089: Increase metadata wait time in unit test Increase timeout in test to avoid transient failures due to long GC or slow machine. You can merge this pull request into a Git

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

If there are no more comments or suggestions, I will start voting process for this KIP later this week. Please feel free to add any comments in the meantime. Thank you, Rajini On Fri, Oct 7, 2016 at 11:32 PM, Gwen Shapira wrote: > Huge +1. > > Thank you Rajini for all the

[jira] [Commented] (KAFKA-4311) Multi layer cache eviction causes forwarding to incorrect ProcessorNode

[ https://issues.apache.org/jira/browse/KAFKA-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15601431#comment-15601431 ] Frank Lyaruu commented on KAFKA-4311: - I'm also out at a conference most of this week. If I can find

[jira] [Updated] (KAFKA-4128) Kafka broker losses messages when zookeeper session times out

[ https://issues.apache.org/jira/browse/KAFKA-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mazhar Shaikh updated KAFKA-4128: - Attachment: log.tar.gz Attaching logs for this scenario: Total Brokers : 6 [b1-b6] Total

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

See Changes: [me] MINOR: Check for null timestamp rather than value in hashcode -- [...truncated 14166 lines...] org.apache.kafka.streams.kstream.JoinWindowsTest >

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

See Changes: [wangguoz] KAFAK-4058: Failure in -- [...truncated 14341 lines...] org.apache.kafka.streams.integration.KStreamKTableJoinIntegrationTest > shouldCountClicksPerRegion[0] STARTED

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

See