[GitHub] kafka pull request #4032: MINOR: Fix typo

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4032 ---

Re: [DISCUSS] KIP-210: Provide for custom error handling when Kafka Streams fails to produce

Thanks for the KIP Matt. Regarding the handle interface of ProductionExceptionHandlerResponse, could you write it on the wiki also, along with the actual added config names (e.g. what https://cwiki.apache.org/confluence/display/KAFKA/KIP-161%3A+streams+deserialization+exception+handlers

[GitHub] kafka pull request #4096: HOTFIX: Poll with zero milliseconds during restora...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4096 ---

Re: [DISCUSS]: KIP-159: Introducing Rich functions to Streams

Thanks for the information Jeyhun. I had also forgot about KAFKA-3907 with this KIP.. Thinking a bit more, I'm now inclined to go with what we agreed before, to add the commit() call to `RecordContext`. A few minor tweaks on its implementation: 1. Maybe we can deprecate the `commit()` in

Re: [DISCUSS] KIP-205: Add getAllKeys() API to ReadOnlyWindowStore

Thanks Richard for updating the wiki. Made another pass over it, overall it LGTM. Just a few minor comments: 1) Could you update the title to reflect the function names accordingly? Generally I think having `all / range` is better in terms of consistency with key-value windows. I.e. queries with

Re: Requesting Wiki Comment Permissions

Hi Jordan, I'd recommend leaving comments or asking questions about a wiki page directly on the mailing list here, as it gets much faster. Guozhang On Mon, Oct 23, 2017 at 1:31 PM, Jordan Pilat wrote: > Hello, > > Would somebody please be so kind as to grant me "comment"

[jira] [Reopened] (KAFKA-5842) QueryableStateIntegrationTest may fail with JDK 7

[ https://issues.apache.org/jira/browse/KAFKA-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reopened KAFKA-5842: Happened again:

[GitHub] kafka pull request #4123: MINOR: reset state in cleanup, fixes jmx mixin fla...

GitHub user xvrl opened a pull request: https://github.com/apache/kafka/pull/4123 MINOR: reset state in cleanup, fixes jmx mixin flakiness @ewencp @ijuma You can merge this pull request into a Git repository by running: $ git pull https://github.com/xvrl/kafka

Re: Metadata class doesn't "expose" topics with errors

Hello Paolo, The reason we filtered the errors in the topics in the generated Cluster is that Metadata and its "fetch()" returned Cluster is a common class that is used among all clients (producer, consumer, connect, streams, admin), and is treated as a high-level representation of the current

Re: [DISCUSS] KIP-210: Provide for custom error handling when Kafka Streams fails to produce

Thanks for this feedback. I’m at a conference right now and am planning on updating the KIP again with details from this conversation later this week. I’ll shoot you a more detailed response then! :) On Mon, Oct 23, 2017 at 8:16 PM Guozhang Wang wrote: > Thanks for the KIP

[VOTE] 1.0.0 RC3

Hello Kafka users, developers and client-developers, This is the third candidate for release of Apache Kafka 1.0.0. The main PRs that gets merged in after RC1 are the following: https://github.com/apache/kafka/commit/dc6bfa553e73ffccd1e604963e076c 78d8ddcd69 It's worth noting that starting in

Re: [VOTE] 1.0.0 RC3

bq. Tag to be voted upon (off 1.0 branch) is the 1.0.0-rc2 tag: There seems to be a typo above: 1.0.0-rc3 tag FYI On Mon, Oct 23, 2017 at 6:00 PM, Guozhang Wang wrote: > Hello Kafka users, developers and client-developers, > > This is the third candidate for release of

[jira] [Created] (KAFKA-6111) Tests for KafkaControllerZkUtils

Ismael Juma created KAFKA-6111: -- Summary: Tests for KafkaControllerZkUtils Key: KAFKA-6111 URL: https://issues.apache.org/jira/browse/KAFKA-6111 Project: Kafka Issue Type: Sub-task

Re: [DISCUSS]: KIP-159: Introducing Rich functions to Streams

Hi Matthias, It is probably my bad, the discussion was a bit long in this thread. I proposed the related issue in the related KIP discuss thread [1] and got an approval [2,3]. Maybe I misunderstood. [1]

Re: [DISCUSS]: KIP-159: Introducing Rich functions to Streams

Fair point. This is a long discussion and I totally forgot that we discussed this. Seems I changed my opinion about including KAFKA-3907... Happy to hear what others think. -Matthias On 10/23/17 1:20 PM, Jeyhun Karimov wrote: > Hi Matthias, > > It is probably my bad, the discussion was a bit

[DISCUSS] KIP-212: Enforce set of legal characters for connector names

All, I've created a KIP to discuss enforcing of rules on what characters are allowed in connector names. Since this may break api calls that are currently working I figured a KIP is the better way to go than to just create a jira. I'd love to hear your input on this!

Build failed in Jenkins: kafka-trunk-jdk9 #149

See Changes: [wangguoz] KAFKA-5140: Fix reset integration test -- [...truncated 1.81 MB...] org.apache.kafka.streams.processor.FailOnInvalidTimestampTest >

[jira] [Created] (KAFKA-6107) SCRAM user add fails if Kafka has never been started

Dustin Cote created KAFKA-6107: -- Summary: SCRAM user add fails if Kafka has never been started Key: KAFKA-6107 URL: https://issues.apache.org/jira/browse/KAFKA-6107 Project: Kafka Issue Type:

[GitHub] kafka pull request #4095: KAFKA-5140: Fix reset integration test

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4095 ---

[jira] [Resolved] (KAFKA-5140) Flaky ResetIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-5140. -- Resolution: Fixed Fix Version/s: (was: 0.11.0.0) 0.11.0.2

Requesting Wiki Comment Permissions

Hello, Would somebody please be so kind as to grant me "comment" permissions on the Wiki? The page in question to which I'd like to add a comment is: https://cwiki.apache.org/confluence/display/KAFKA/Kafka+data+structures+in+Zookeeper My confluence username is jrpilat Thanks! - Jordan

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

See Changes: [wangguoz] KAFKA-5140: Fix reset integration test -- [...truncated 1.83 MB...] org.apache.kafka.streams.integration.RegexSourceIntegrationTest >

Build failed in Jenkins: kafka-0.11.0-jdk7 #323

See Changes: [jason] KAFKA-6042: Avoid deadlock between two groups with delayed operations -- [...truncated 2.45 MB...]

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

See Changes: [wangguoz] KAFKA-5140: Fix reset integration test -- [...truncated 1.78 MB...] org.apache.kafka.streams.integration.QueryableStateIntegrationTest >

[jira] [Created] (KAFKA-6109) ResetIntegrationTest may fail due to IllegalArgumentException

Ted Yu created KAFKA-6109: - Summary: ResetIntegrationTest may fail due to IllegalArgumentException Key: KAFKA-6109 URL: https://issues.apache.org/jira/browse/KAFKA-6109 Project: Kafka Issue Type:

Re: [DISCUSS] KIP-212: Enforce set of legal characters for connector names

Here's the link to KIP-212: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74684586 I do think it's worthwhile to define the rules for connector names. However, I think it would be better to describe the current restrictions for names outside of them appearing within URLs. For

[jira] [Created] (KAFKA-6108) Synchronizing on commits and StandbyTasks can be improved

Matthias J. Sax created KAFKA-6108: -- Summary: Synchronizing on commits and StandbyTasks can be improved Key: KAFKA-6108 URL: https://issues.apache.org/jira/browse/KAFKA-6108 Project: Kafka

Build failed in Jenkins: kafka-1.0-jdk7 #54

See Changes: [wangguoz] KAFKA-5140: Fix reset integration test -- [...truncated 1.82 MB...] org.apache.kafka.streams.kstream.WindowTest > shouldThrowIfStartIsNegative PASSED

[GitHub] kafka pull request #4122: KAFKA-6096: Add multi-threaded tests for group coo...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/4122 KAFKA-6096: Add multi-threaded tests for group coordinator, txn manager You can merge this pull request into a Git repository by running: $ git pull

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

See -- [...truncated 1.83 MB...] org.apache.kafka.streams.kstream.JoinWindowsTest > shouldUseWindowSizeForMaintainDurationWhenSizeLargerThanDefaultMaintainMs PASSED

Build failed in Jenkins: kafka-0.11.0-jdk7 #324

See Changes: [wangguoz] KAFKA-5140: Fix reset integration test -- [...truncated 2.09 MB...] org.apache.kafka.common.config.ConfigDefTest > testBaseConfigDefDependents

[GitHub] kafka pull request #4121: Kafka 6042: Use state write lock for delayed txn o...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/4121 Kafka 6042: Use state write lock for delayed txn operations You can merge this pull request into a Git repository by running: $ git pull https://github.com/rajinisivaram/kafka

[jira] [Created] (KAFKA-6110) Warning when running the broker on Windows

Vahid Hashemian created KAFKA-6110: -- Summary: Warning when running the broker on Windows Key: KAFKA-6110 URL: https://issues.apache.org/jira/browse/KAFKA-6110 Project: Kafka Issue Type: Bug

[GitHub] kafka pull request #4121: Kafka 6042: Use state write lock for delayed txn o...

Github user rajinisivaram closed the pull request at: https://github.com/apache/kafka/pull/4121 ---

[VOTE] KIP-205: Add all() and range() API to ReadOnlyWindowStore

Hi all, I want to propose KIP-205 for the addition of new API. It is about adding methods similar to those found in ReadOnlyKeyValueStore to the ReadOnlyWindowStore class. As it appears the discussion has reached a conclusion, I would like to start the voting process.

[GitHub] kafka pull request #3512: KAFKA-5574: add thread.id header in show-detailed-...

Github user cnZach closed the pull request at: https://github.com/apache/kafka/pull/3512 ---

Re: [DISCUSS] KIP-204 : adding records deletion operation to the new Admin Client API

Hi Colin, I was using the long primitive in the code but not updated the KIP yet, sorry ... now it's updated ! At same time I agree on using DeletionTarget ... KIP updated ! Regarding the deleteBefore factory method, it's a pattern already used witn NewPartitions.increaseTo which I think

[GitHub] kafka pull request #4102: MINOR: Update Scala to 2.12.4

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4102 ---

Jenkins build is back to normal : kafka-trunk-jdk9 #144

See

[GitHub] kafka pull request #4117: MINOR: Configure owasp.dependencycheck gradle plug...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/4117 MINOR: Configure owasp.dependencycheck gradle plugin It seems to output a few false positives, but still worth verifying. You can merge this pull request into a Git repository by running: $

Metadata class doesn't "expose" topics with errors

Hi devs, while developing the KIP-204 (having delete records operation in the "new" Admin Client) I'm facing with the following doubt (or maybe a lack of info) ... As described by KIP-107 (which implements this feature at protocol level and in the "legacy" Admin Client), the request needs to

[GitHub] kafka pull request #4104: MINOR: add hint for setting an uncaught exception ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4104 ---

Re: [DISCUSS] KIP-204 : adding records deletion operation to the new Admin Client API

At the risk of muddying the waters further, have you considered "RecordsToDelete" as the name of the class? It's both shorter and more descriptive imho. Also "deleteBefore()" as the factory method name isn't very future proof if we came to support time-based deletion. Something like

Re: Please subscribe me in your updates

As detailed at https://kafka.apache.org/contact, to subscribe, send an email to dev-subscr...@kafka.apache.org < dev-subscr...@kafka.apache.org>. On 22 October 2017 at 15:15, Veeramani S wrote: > >

Re: Metadata class doesn't "expose" topics with errors

I'd like just to add that in my specific case I could resolve creating a new NodeProvider implementation like LeaderForProvider in order to send the request to the right leader for each topic. The drawback of this solution is not grouping topics for the same leader so not having only one

Re: Metadata class doesn't "expose" topics with errors

Finally another plan could be to use nesting of runnable calls. The first one for asking metadata (using the MetadataRequest which provides us all the errors) and then sending the delete records requests in the handleResponse() of such metadata request. Paolo Patierno Senior Software Engineer

[GitHub] kafka pull request #4113: KAFKA-6104: Added unit tests for ClusterConnection...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4113 ---

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

See Changes: [damian.guy] MINOR: add hint for setting an uncaught exception handler to JavaDocs -- [...truncated 3.31 MB...] kafka.security.auth.SimpleAclAuthorizerTest

Request for Review: KAFKA-4930

Hi everybody, could one of the committers please have a quick look at my PR [1] for KAFKA-4930? I think I've addressed all comments I received so far and its been sitting for a while ready for review. Kind regards, Sönke [1] https://github.com/apache/kafka/pull/2755

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

See Changes: [ismael] MINOR: Update Scala to 2.12.4 -- [...truncated 381.29 KB...] kafka.security.auth.SimpleAclAuthorizerTest >

[GitHub] kafka pull request #4108: KAFKA-6101 Reconnecting to broker does not exponen...

Github user tedyu closed the pull request at: https://github.com/apache/kafka/pull/4108 ---

[GitHub] kafka pull request #4118: KAFKA-6101 Reconnecting to broker does not exponen...

GitHub user tedyu opened a pull request: https://github.com/apache/kafka/pull/4118 KAFKA-6101 Reconnecting to broker does not exponentially backoff You can merge this pull request into a Git repository by running: $ git pull https://github.com/tedyu/kafka trunk Alternatively

[GitHub] kafka pull request #4117: MINOR: Configure owasp.dependencycheck gradle plug...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4117 ---

[GitHub] kafka pull request #4119: MINOR: added -1 value description as "high waterma...

GitHub user ppatierno opened a pull request: https://github.com/apache/kafka/pull/4119 MINOR: added -1 value description as "high watermark" in the protocol delete records request You can merge this pull request into a Git repository by running: $ git pull

Jenkins build is back to normal : kafka-trunk-jdk9 #150

See

Re: [VOTE] 1.0.0 RC3

A minor request about the RC releases in context of Maven - Right now, these RC releases are being released into (Apache staging) Maven repository using the version number of the final release. So each RC1, RC2, RC3 and so on, all end up in Maven repo as 1.0.0 [1]. For using these as

Re: [kafka-clients] [VOTE] 1.0.0 RC2

1.0.0-RC2 passed all kafka-python integration tests. Excited for this release -- great work everyone! -Dana On Tue, Oct 17, 2017 at 9:47 AM, Guozhang Wang wrote: > Hello Kafka users, developers and client-developers, > > This is the third candidate for release of Apache

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

See

[GitHub] kafka pull request #4085: HOTFIX: poll with zero millis during restoration

Github user guozhangwang closed the pull request at: https://github.com/apache/kafka/pull/4085 ---

[GitHub] kafka pull request #4116: KAFKA-6105: load client properties in proper order...

Github user cnZach closed the pull request at: https://github.com/apache/kafka/pull/4116 ---

Jenkins build is back to normal : kafka-1.0-jdk7 #55

See

Re: [kafka-clients] [VOTE] 1.0.0 RC3

+1. passed kafka-python integration tests, and manually verified producer/consumer on both compressed and non-compressed data. -Dana On Mon, Oct 23, 2017 at 6:00 PM, Guozhang Wang wrote: > Hello Kafka users, developers and client-developers, > > This is the third candidate

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

See Changes: [wangguoz] HOTFIX: Poll with zero milliseconds during restoration phase [ismael] MINOR: Fix typo in ConsumerCoordinator comment -- [...truncated 3.80 MB...]

[GitHub] kafka pull request #4124: KAFKA-6074 Use ZookeeperClient in ReplicaManager a...

GitHub user tedyu opened a pull request: https://github.com/apache/kafka/pull/4124 KAFKA-6074 Use ZookeeperClient in ReplicaManager and Partition You can merge this pull request into a Git repository by running: $ git pull https://github.com/tedyu/kafka trunk Alternatively

[GitHub] kafka pull request #4085: HOTFIX: poll with zero millis during restoration

GitHub user guozhangwang reopened a pull request: https://github.com/apache/kafka/pull/4085 HOTFIX: poll with zero millis during restoration Mirror of #4096 for 0.11.01. During the restoration phase, when thread state is still in PARTITION_ASSIGNED not RUNNING yet, call

[GitHub] kafka pull request #4125: KAFKA-6105: load client properties in proper order...

GitHub user cnZach opened a pull request: https://github.com/apache/kafka/pull/4125 KAFKA-6105: load client properties in proper order for EndToEndLatency tool Currently, the property file is loaded first, and later a auto generated group.id is used:

Re: [VOTE] KIP-207:The Offsets which ListOffsetsResponse returns should monotonically increase even during a partition leader change

On Mon, Oct 23, 2017, at 10:29, Jason Gustafson wrote: > Thanks for the KIP. I'm assuming the new behavior only affects > ListOffsets requests from the consumer. That's a very good point. I will add a caveat that we only apply the KIP-207 behavior to requests from clients, not requests from

Re: [DISCUSS]: KIP-159: Introducing Rich functions to Streams

Interesting. I thought that https://issues.apache.org/jira/browse/KAFKA-4125 is the main motivation for this KIP :) I also think, that we should not expose the full ProcessorContext at DSL level. Thus, overall I am not even sure if we should fix KAFKA-3907 at all. Manual commits are something

[GitHub] kafka pull request #3885: MINOR: Added ">" prompt in examples where kafka-co...

Github user ppatierno closed the pull request at: https://github.com/apache/kafka/pull/3885 ---

Re: [VOTE] KIP-171 - Extend Consumer Group Reset Offset for Stream Application

Thanks Jorge for driving this KIP! +1 (binding). Guozhang On Mon, Oct 16, 2017 at 2:11 PM, Bill Bejeck wrote: > +1 > > Thanks, > Bill > > On Fri, Oct 13, 2017 at 6:36 PM, Ted Yu wrote: > > > +1 > > > > On Fri, Oct 13, 2017 at 3:32 PM, Matthias J. Sax

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

See

Request for access to the KIP wiki page

Hi all, could someone please grant my user (userid: soenkeliebau) permissions to the KIP page of the wiki, I'd like to create a proposal. Thanks! Sönke

Re: Request for access to the KIP wiki page

Hello Sönke, It's done. Cheers. Guozhang On Mon, Oct 23, 2017 at 11:08 AM, Sönke Liebau < soenke.lie...@opencore.com.invalid> wrote: > Hi all, > > could someone please grant my user (userid: soenkeliebau) permissions to > the KIP page of the wiki, I'd like to create a proposal. > > Thanks!

Re: [VOTE] 1.0.0 RC2

We (Heroku) have run our usual set of perf tests against 1.0 RC2 and found no notable issues so far. Once RC3 is out we will test that too. Thanks Tom Crayford Heroku Kafka On Tue, Oct 17, 2017 at 5:47 PM, Guozhang Wang wrote: > Hello Kafka users, developers and

[GitHub] kafka pull request #4120: Make CONSOLE_OUTPUT_FILE configurable

GitHub user rnpridgeon opened a pull request: https://github.com/apache/kafka/pull/4120 Make CONSOLE_OUTPUT_FILE configurable Even if Kafka is not configured without the console appender the CONSOLE_OUTPUT_FILE is generated. Allowing for this to be configurable offers more

Re: Before creating KIP : Kafka Connect / Add a configuration provider class

Very interesting. Would the proposed configuration provider be set at the connector level or the worker level? The latter would obviously be required to handle all/multiple connector configurations. Either way, the provider class(es) would need to be installed on the worker (really, every worker),

[GitHub] kafka pull request #4118: KAFKA-6101 Reconnecting to broker does not exponen...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4118 ---

Re: Before creating KIP : Kafka Connect / Add a configuration provider class

I agree, sounds like an intriguing idea. I think we could probably come up with a few common enough implementations that merit including in Kafka. FileConfigProvider for example, so you can distribute common configs throughout your cluster with some orchestration tool and users simply state the

Jenkins build is back to normal : kafka-trunk-jdk9 #148

See

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

See

[jira] [Created] (KAFKA-6105) group.id is not picked by kafka.tools.EndToEndLatency

Yuexin Zhang created KAFKA-6105: --- Summary: group.id is not picked by kafka.tools.EndToEndLatency Key: KAFKA-6105 URL: https://issues.apache.org/jira/browse/KAFKA-6105 Project: Kafka Issue

[GitHub] kafka pull request #4115: KAFKA-6105: load client properties in proper order...

GitHub user cnZach opened a pull request: https://github.com/apache/kafka/pull/4115 KAFKA-6105: load client properties in proper order for kafka.tools.EndToEndLatency Currently, the property file is loaded first, and later a auto generated group.id is used:

[GitHub] kafka pull request #4115: KAFKA-6105: load client properties in proper order...

Github user cnZach closed the pull request at: https://github.com/apache/kafka/pull/4115 ---

Re: [DISCUSS] KIP-204 : adding records deletion operation to the new Admin Client API

About the name I just started to have a doubt about DeletetionTarget because it could be bounded to any deletion operation (i.e. delete topic, ...) and not just what we want now, so records deletion. I have updated the KIP-204 using DeleteRecordsTarget so it's clear that it's related to the

[GitHub] kafka pull request #4116: KAFKA-6105: load client properties in proper order...

GitHub user cnZach opened a pull request: https://github.com/apache/kafka/pull/4116 KAFKA-6105: load client properties in proper order for EndToEndLatency tool Currently, the property file is loaded first, and later a auto generated group.id is used:

try to subscribe

Build failed in Jenkins: kafka-1.0-jdk7 #52

See Changes: [ismael] KAFKA-6101; Reconnecting to broker does not exponentially backoff -- [...truncated 372.24 KB...] kafka.server.ServerGenerateBrokerIdTest >

Re: [DISCUSS] KIP-204 : adding records deletion operation to the new Admin Client API

On Mon, Oct 23, 2017, at 01:37, Tom Bentley wrote: > At the risk of muddying the waters further, have you considered > "RecordsToDelete" as the name of the class? It's both shorter and more > descriptive imho. +1 for RecordsToDelete > > Also "deleteBefore()" as the factory method name isn't

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

See Changes: [ismael] KAFKA-6104; Added unit tests for ClusterConnectionStates -- [...truncated 2.92 MB...] org.apache.kafka.common.security.plain.PlainSaslServerTest >

[jira] [Resolved] (KAFKA-6101) Reconnecting to broker does not exponentially backoff

[ https://issues.apache.org/jira/browse/KAFKA-6101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6101. Resolution: Fixed Assignee: Ted Yu > Reconnecting to broker does not exponentially backoff >

[jira] [Resolved] (KAFKA-5743) All ducktape services should store their files in subdirectories of /mnt

[ https://issues.apache.org/jira/browse/KAFKA-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5743. Resolution: Fixed Fix Version/s: 1.0.0 > All ducktape services should store their files in

[GitHub] kafka pull request #4084: KAFKA-6070: add ipaddress and enum34 dependencies ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4084 ---

[jira] [Resolved] (KAFKA-5720) In Jenkins, kafka.api.SaslSslAdminClientIntegrationTest failed with org.apache.kafka.common.errors.TimeoutException

[ https://issues.apache.org/jira/browse/KAFKA-5720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5720. Resolution: Fixed Fix Version/s: (was: 1.1.0) 1.0.0 > In Jenkins,

[jira] [Resolved] (KAFKA-6070) ducker-ak: add ipaddress and enum34 dependencies to docker image

[ https://issues.apache.org/jira/browse/KAFKA-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6070. Resolution: Fixed Fix Version/s: 1.1.0 1.0.0 > ducker-ak: add ipaddress

Build failed in Jenkins: kafka-trunk-jdk9 #147

See Changes: [ismael] MINOR: Configure owasp.dependencycheck gradle plugin -- [...truncated 1.90 MB...] org.apache.kafka.connect.runtime.isolation.PluginUtilsTest >

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

See Changes: [ismael] MINOR: Configure owasp.dependencycheck gradle plugin -- [...truncated 1.84 MB...] org.apache.kafka.streams.KafkaStreamsTest >

[jira] [Created] (KAFKA-6106) Postpone normal processing of tasks within a thread until restoration of all tasks have completed

Guozhang Wang created KAFKA-6106: Summary: Postpone normal processing of tasks within a thread until restoration of all tasks have completed Key: KAFKA-6106 URL: https://issues.apache.org/jira/browse/KAFKA-6106

Jenkins build is back to normal : kafka-1.0-jdk7 #53

See

Re: [VOTE] KIP-207:The Offsets which ListOffsetsResponse returns should monotonically increase even during a partition leader change

Thanks for the KIP. I'm assuming the new behavior only affects ListOffsets requests from the consumer. Might be worth mentioning that in the KIP. Also, does it affect all ListOffsets requests, or only those that specify the latest offset? -Jason On Wed, Oct 18, 2017 at 9:15 AM, Colin McCabe