Build failed in Jenkins: kafka-2.1-jdk8 #6

See Changes: [matthias] KAFKA-7484: fix suppression integration tests (#5748) -- [...truncated 884.26 KB...] kafka.cluster.ReplicaTest >

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

See Changes: [github] MINOR: Ensure consumers are closed in DynamicBrokerReconfigurationTest [ismael] MINOR: Add topic config to PartitionsSpec (#5523) [jason] KAFKA-7467; NoSuchElementException is raised

Jenkins build is back to normal : kafka-trunk-jdk10 #571

See

Jenkins build is back to normal : kafka-2.0-jdk8 #164

See

Build failed in Jenkins: kafka-2.1-jdk8 #5

See Changes: [jason] MINOR: Ensure consumers are closed in DynamicBrokerReconfigurationTest [jason] KAFKA-7467; NoSuchElementException is raised because controlBatch is [jason] KAFKA-6914; Set parent classloader of

Build failed in Jenkins: kafka-trunk-jdk10 #570

See Changes: [github] MINOR: Ensure consumers are closed in DynamicBrokerReconfigurationTest [ismael] MINOR: Add topic config to PartitionsSpec (#5523) [jason] KAFKA-7467; NoSuchElementException is raised

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

See

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

See Changes: [wangguoz] MINOR: Clarify usage of stateful processor node (#5740) [me] MINOR: Switch to use AWS spot instances -- [...truncated 2.72 MB...]

Build failed in Jenkins: kafka-2.0-jdk8 #163

See Changes: [me] MINOR: Switch to use AWS spot instances -- [...truncated 883.22 KB...] kafka.server.epoch.LeaderEpochFileCacheTest >

[jira] [Created] (KAFKA-7488) Controller not recovering after disconnection to zookeeper

Luigi Tagliamonte created KAFKA-7488: Summary: Controller not recovering after disconnection to zookeeper Key: KAFKA-7488 URL: https://issues.apache.org/jira/browse/KAFKA-7488 Project: Kafka

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

See Changes: [me] MINOR: Switch to use AWS spot instances -- [...truncated 1.33 MB...] org.apache.kafka.streams.processor.internals.MinTimestampTrackerTest >

Re: [DISCUSS] KIP-378: Enable Dependency Injection for Kafka Streams handlers

Hi Wladimir, Thanks for the KIP! As I mentioned in the PR discussion, I personally prefer not to recommend overriding StreamsConfig for this purpose. It seems like a person wishing to create a DI shim would have to acquire quite a deep understanding of the class and its usage to figure out what

[jira] [Resolved] (KAFKA-6880) Zombie replicas must be fenced

[ https://issues.apache.org/jira/browse/KAFKA-6880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6880. Resolution: Fixed Fix Version/s: (was: 2.2.0) 2.1.0 This was

[jira] [Resolved] (KAFKA-7395) Add fencing to replication protocol (KIP-320)

[ https://issues.apache.org/jira/browse/KAFKA-7395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7395. Resolution: Fixed Fix Version/s: 2.1.0 > Add fencing to replication protocol

Re: [DISCUSS] KIP-378: Enable Dependency Injection for Kafka Streams handlers

Hi Guozhang, I'm going to drop in a little extra context from the preliminary PR discussion (https://github.com/apache/kafka/pull/5344). The issue isn't that it's impossible to use Streams within a Spring app, just that the interplay between our style of construction/configuration and Spring's

[jira] [Created] (KAFKA-7487) DumpLogSegments reports mismatches for indexed offsets which are not at the start of a record batch

Michael Bingham created KAFKA-7487: -- Summary: DumpLogSegments reports mismatches for indexed offsets which are not at the start of a record batch Key: KAFKA-7487 URL:

Re: [VOTE] KIP-291: Have separate queues for control requests and data requests

Thanks for the suggestion, Ismael. I like it. Jun, I'm excited to get the +1, thanks a lot! Meanwhile what do you feel about renaming the metrics and config to ControlPlaneRequestQueueSize ControlPlaneNetworkProcessorIdlePercent ControlPlaneRequestHandlerIdlePercent

Re: New release branch 2.1.0

Hi When are we planning on releasing the bugfix version 2.0.1 ? On Thu, Oct 4, 2018 at 5:22 PM Dong Lin wrote: > Hello Kafka developers and users, > > As promised in the release plan > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554044, > we now have a release branch for

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

See Changes: [me] MINOR: Switch to use AWS spot instances -- [...truncated 376.02 KB...] kafka.controller.ZookeeperClientTest > testGetChildrenExistingZNodeWithChildren

Re: [VOTE] KIP-376: Implement AutoClosable on appropriate classes that want to be used in a try-with-resource statement

Hi, I think we have discussed this well enough to put this into a vote. Suggestions are welcome! Best, Yishun On Wed, Oct 3, 2018, 2:30 PM Yishun Guan wrote: > Hi All, > > I want to start a voting on this KIP: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=93325308 > >

[jira] [Resolved] (KAFKA-6914) Kafka Connect - Plugins class should have a constructor that can take in parent ClassLoader

[ https://issues.apache.org/jira/browse/KAFKA-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6914. Resolution: Fixed Fix Version/s: 2.1.0 2.0.1

[jira] [Resolved] (KAFKA-7467) NoSuchElementException is raised because controlBatch is empty

[ https://issues.apache.org/jira/browse/KAFKA-7467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7467. Resolution: Fixed Fix Version/s: 2.1.0 2.0.1

[jira] [Resolved] (KAFKA-6990) CommitFailedException; this task may be no longer owned by the thread

[ https://issues.apache.org/jira/browse/KAFKA-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryanne Dolan resolved KAFKA-6990. - Resolution: Not A Bug > CommitFailedException; this task may be no longer owned by the thread >

Re: [DISCUSS] Replacing EasyMock with Mockito in Kafka

+1 to moving to Mockito On Fri, Oct 5, 2018 at 12:11 PM Ron Dagostino wrote: > I have used Mockito and am a big fan -- I had never used EasyMock until > recently. The concept of record vs. replay mode in EasyMock really annoyed > me -- I'm a fan of the "NO MODES" idea ( >

Re: [DISCUSS] Replacing EasyMock with Mockito in Kafka

Agreed, I really liked the fact that Mockito has no "replay" concept. Ismael On Fri, 5 Oct 2018, 12:11 Ron Dagostino, wrote: > I have used Mockito and am a big fan -- I had never used EasyMock until > recently. The concept of record vs. replay mode in EasyMock really annoyed > me -- I'm a fan

Re: [DISCUSS] Replacing EasyMock with Mockito in Kafka

I have used Mockito and am a big fan -- I had never used EasyMock until recently. The concept of record vs. replay mode in EasyMock really annoyed me -- I'm a fan of the "NO MODES" idea ( https://en.wikipedia.org/wiki/Larry_Tesler), and when I encountered it in EasyMock in the context of Kafka

Jenkins build is back to normal : kafka-0.11.0-jdk7 #406

See

Re: [EXTERNAL] Incremental Cooperative Rebalancing

Hello Konstantine, Thanks for the great write-up! Here are a few quick comments I have about the proposals: 1. For "Kubernetes process death" and "Rolling bounce" case, there is another parallel work on KIP-345 [1] (cc'ed contributor) that is aimed to mitigate these two issues, but it is relying

[jira] [Created] (KAFKA-7486) Flaky test `DeleteTopicTest.testAddPartitionDuringDeleteTopic`

Jason Gustafson created KAFKA-7486: -- Summary: Flaky test `DeleteTopicTest.testAddPartitionDuringDeleteTopic` Key: KAFKA-7486 URL: https://issues.apache.org/jira/browse/KAFKA-7486 Project: Kafka

Re: [VOTE] KIP-349 Priorities for Source Topics

On Fri, Oct 5, 2018, at 10:58, Thomas Becker wrote: > Colin, > Would you mind sharing your vision for how this looks with multiple > consumers? I'm still getting my bearings with the new consumer but it's > not immediately obvious to me how this would work. Hi Thomas, I was just responding to

Re: [VOTE] KIP-349 Priorities for Source Topics

On Wed, Oct 3, 2018, at 16:01, n...@afshartous.com wrote: > > > > On Oct 3, 2018, at 12:41 PM, Colin McCabe wrote: > > > > Will there be a separate code path for people who don't want to use this > > feature? > > > Yes, I tried to capture this in the KIP by indicating that this API >

[jira] [Created] (KAFKA-7485) Flaky test `DyanamicBrokerReconfigurationTest.testTrustStoreAlter`

Jason Gustafson created KAFKA-7485: -- Summary: Flaky test `DyanamicBrokerReconfigurationTest.testTrustStoreAlter` Key: KAFKA-7485 URL: https://issues.apache.org/jira/browse/KAFKA-7485 Project: Kafka

Re: [VOTE] KIP-349 Priorities for Source Topics

Colin, Would you mind sharing your vision for how this looks with multiple consumers? I'm still getting my bearings with the new consumer but it's not immediately obvious to me how this would work. In particular, it doesn't seem particularly easy to know when you are at the high watermark of a

Re: [VOTE] KIP-291: Have separate queues for control requests and data requests

Hi, Lucas, Thanks for the updated KIP. About the name of the metric, since it's tagged by type=RequestChannel, it's probably fine to use the proposed name. So, +1 for the KIP. Jun On Thu, Oct 4, 2018 at 10:31 AM, Lucas Wang wrote: > Thanks Jun. I've changed the KIP with the suggested 2 step

[jira] [Resolved] (KAFKA-5117) Kafka Connect REST endpoints reveal Password typed values

[ https://issues.apache.org/jira/browse/KAFKA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5117. -- Resolution: Duplicate Assignee: Ewen Cheslack-Postava Fix

Re: [DISCUSS]KIP-216: IQ should throw different exceptions for different errors

Thanks for the explanation, that makes sense. Guozhang On Mon, Jun 25, 2018 at 2:28 PM, Matthias J. Sax wrote: > The scenario I had I mind was, that KS is started in one thread while a > second thread has a reference to the object to issue queries. > > If a query is issue before the "main

[jira] [Resolved] (KAFKA-7266) Fix MetricsTest test flakiness

[ https://issues.apache.org/jira/browse/KAFKA-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-7266. Resolution: Fixed Fix Version/s: 2.1.0 > Fix MetricsTest test flakiness >

Re: [DISCUSS] Replacing EasyMock with Mockito in Kafka

So far, it seems like people are in favour. If no objections are presented in the next couple of days, we will go ahead with the change. Ismael On Sun, 30 Sep 2018, 20:32 Ismael Juma, wrote: > Hi all, > > As described in KAFKA-7438 > ,

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

See Changes: [me] KAFKA-7476: Fix Date-based types in SchemaProjector -- [...truncated 2.72 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

Build failed in Jenkins: kafka-2.1-jdk8 #3

See -- [...truncated 417.35 KB...] kafka.controller.PartitionLeaderElectionAlgorithmsTest > testPreferredReplicaPartitionLeaderElectionPreferredReplicaNotInIsrNotLive PASSED

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

See Changes: [me] KAFKA-7476: Fix Date-based types in SchemaProjector -- [...truncated 152.01 KB...] kafka.api.SaslSslAdminClientIntegrationTest > testInvalidAlterConfigs

Re: [DISCUSS]KIP-216: IQ should throw different exceptions for different errors

Matthias, > Sorry to hear! Get well soon! I'm back! :) Base on many suggestion and discussion, I already rewrite the KIP. Please take a look: https://cwiki.apache.org/confluence/display/KAFKA/KIP-216%3A+IQ+should+throw+different+exceptions+for+different+errors > I see. If this is the

Build failed in Jenkins: kafka-2.0-jdk8 #162

See Changes: [me] KAFKA-7476: Fix Date-based types in SchemaProjector -- [...truncated 434.11 KB...] kafka.controller.ControllerIntegrationTest > testEmptyCluster STARTED

Build failed in Jenkins: kafka-2.1-jdk8 #2

See Changes: [me] KAFKA-7476: Fix Date-based types in SchemaProjector -- [...truncated 418.04 KB...] kafka.cluster.BrokerEndPointTest > testEndpointFromUri PASSED

[jira] [Created] (KAFKA-7484) Fix test SuppressionDurabilityIntegrationTest.shouldRecoverBufferAfterShutdown()

Dong Lin created KAFKA-7484: --- Summary: Fix test SuppressionDurabilityIntegrationTest.shouldRecoverBufferAfterShutdown() Key: KAFKA-7484 URL: https://issues.apache.org/jira/browse/KAFKA-7484 Project: Kafka

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

See Changes: [me] KAFKA-7476: Fix Date-based types in SchemaProjector -- [...truncated 1.31 MB...] org.apache.kafka.streams.processor.internals.StateConsumerTest >

Re: [DISCUSSION] KIP-376: Implement AutoClosable on appropriate classes that has close()

> However, it's a good hint, that `AutoClosable#close()` declares `throws > Exception` and thus, it seems to be a backward incompatible change. > Hence, I am not sure if we can actually move forward easily with this KIP. It is legal to remove declaration of "throwing Exception" from a class which

Jenkins build is back to normal : kafka-0.10.1-jdk7 #141

See

Build failed in Jenkins: kafka-2.1-jdk8 #1

See -- [...truncated 2.51 MB...] org.apache.kafka.streams.kstream.internals.KGroupedTableImplTest > shouldNotAllowInvalidStoreNameOnReduce STARTED

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

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-eu2 (ubuntu trusty) in workspace

Build failed in Jenkins: kafka-2.0-jdk8 #161

See -- Started by an SCM change Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H29 (ubuntu xenial) in workspace

Jenkins build is back to normal : kafka-1.1-jdk7 #217

See