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

See Changes: [mjsax] MINOR: Fix line break issue in upgrade notes (#6320) -- [...truncated 2.31 MB...] org.apache.kafka.trogdor.workload.PayloadGeneratorTest >

[jira] [Resolved] (KAFKA-7845) Kafka clients do not re-resolve ips when a broker is replaced.

[ https://issues.apache.org/jira/browse/KAFKA-7845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jennifer Thompson resolved KAFKA-7845. -- Resolution: Fixed Fix Version/s: 2.1.1 > Kafka clients do not re-resolve ips

Re: [VOTE] 2.2.0 RC0

@Stephane Thanks! You are right (I copied the list from an older draft without double checking). On the release Wiki page, it's correctly listed as postponed: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100827512 @Viktor Thanks. This will not block the release, but I'll

[jira] [Created] (KAFKA-8002) Replica reassignment to new log dir may not complete if future and current replicas segment files have different base offsets

Anna Povzner created KAFKA-8002: --- Summary: Replica reassignment to new log dir may not complete if future and current replicas segment files have different base offsets Key: KAFKA-8002 URL:

[jira] [Created] (KAFKA-8001) Fetch from future replica stalls when local replica becomes a leader

Anna Povzner created KAFKA-8001: --- Summary: Fetch from future replica stalls when local replica becomes a leader Key: KAFKA-8001 URL: https://issues.apache.org/jira/browse/KAFKA-8001 Project: Kafka

Re: Statestore restoration & scaling questions - possible KIP as well.

1) you are right, a thread's restoration phase will not interfere will any other threads' normal processing collocated within the same JVM / machine etc at all. So you may have a Streams instance which contains some threads already finished restoring and started processing tasks, while other

Re: [DISCUSS] KIP-433: Provide client API version to authorizer

Hi Ying, I think the question is can we add a module in the core which can take up the dynamic config and does a block certain APIs. This module will be called in each of the APIs like the authorizer does today to check if the API is supported for the client. Instead of throwing

Re: [DISCUSS] KIP-433: Provide client API version to authorizer

If you guys don't like the extension of authorizer interface, I will just propose a single broker dynamic configuration: client.min.api.version, to keep things simple. What do you think? On Mon, Feb 25, 2019 at 2:23 PM Ying Zheng wrote: > @Viktor Somogyi-Vass, @Harsha, It seems the biggest

Re: [DISCUSS] KIP-424: Allow suppression of intermediate events based on wall clock time

On 2019/02/21 02:19:27, "Matthias J. Sax" wrote: > thanks for the KIP. Corner case question: > > What happens if an application is stopped an restarted? > > - Should suppress() flush all records (would be _before_ the time elapsed)? > - Or should it preserve buffered records and reload on

Re: [DISCUSS] KIP-433: Provide client API version to authorizer

@Viktor Somogyi-Vass, @Harsha, It seems the biggest concern is the backward-compatibility to the existing authorizers. We can put the new method into a new trait / interface: trait AuthorizerEx extends Authorizer { def authorize(session: Session, operation: Operation, resource: Resource,

Re: Statestore restoration & scaling questions - possible KIP as well.

Hi Guozhang - Thanks for the replies, and directing me to the existing JIRAs. I think that a two-phase rebalance will be quite useful. 1) For clarity's sake, I should have just asked: When a new thread / node is created and tasks are rebalanced, are the state stores on the new threads/nodes

I am not able to authenticate kafka using ssl

I am getting the following Bad file descriptor error (Full error given below) if I try to create an SSL certificate following the instructions in the link given below. http://kafka.apache.org/documentation/#security_ssl ERROR [root@x certificate]# openssl s_client -debug -connect

Re: [DISCUSS] KIP-236 Interruptible Partition Reassignment

Hi Viktor,  Thanks for the response.  Good questions!  answers below:  > A few questions regarding the rollback algorithm:> 1. At step 2 how do you > elect the leader?  The step 2 code is in https://github.com/apache/kafka/pull/6296   core/src/main/scala/kafka/controller/KafkaController.scala 

Re: [DISCUSS] KIP-433: Provide client API version to authorizer

I think the motivation of the KIP is to configure which API we want to allow for a broker. This is challenging for a hosted service where you have customers with different versions of clients. It's not just about down conversion but for example transactions, there is a case where we do not want

[jira] [Created] (KAFKA-7999) Flaky Test ExampleConnectIntegrationTest#testProduceConsumeConnector

Matthias J. Sax created KAFKA-7999: -- Summary: Flaky Test ExampleConnectIntegrationTest#testProduceConsumeConnector Key: KAFKA-7999 URL: https://issues.apache.org/jira/browse/KAFKA-7999 Project:

TSU NOTIFICATION - Encryption

SUBMISSION TYPE: TSU SUBMITTED BY: Rajini Sivaram SUBMITTED FOR:The Apache Software Foundation POINT OF CONTACT: Secretary, The Apache Software Foundation FAX: +1-919-573-9199 MANUFACTURER(S): The Apache Software Foundation, Oracle PRODUCT

[jira] [Created] (KAFKA-7998) Windows Quickstart script fails

Dieter De Paepe created KAFKA-7998: -- Summary: Windows Quickstart script fails Key: KAFKA-7998 URL: https://issues.apache.org/jira/browse/KAFKA-7998 Project: Kafka Issue Type: Bug

[jira] [Resolved] (KAFKA-7268) Review Handling Crypto Rules and update ECCN page if needed

[ https://issues.apache.org/jira/browse/KAFKA-7268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri Yandell resolved KAFKA-7268. -- Resolution: Fixed > Review Handling Crypto Rules and update ECCN page if needed >

Re: [VOTE] KIP-131 - Add access to OffsetStorageReader from SourceConnector

+1 (binding) On Mon, Feb 25, 2019 at 4:32 AM Florian Hussonnois wrote: > Hi Kafka Team, > > I'd like to bring this thread back at the top of the email stack to get a > chance to see this KIP merge in the next minor/major release. > > Thanks. > > Le ven. 18 janv. 2019 à 01:20, Florian Hussonnois

Re: [VOTE] KIP-430 - Return Authorized Operations in Describe Responses

Hi, Thanks for the KIP. +1( binding). Thanks, On Mon, Feb 25, 2019 at 6:28 PM Rajini Sivaram wrote: > Thanks Mickael. > > I thought I had to list the type only once when the same field appears > twice (the field itself is listed both for cluster and topic). But you are > the second person

Re: [VOTE] 2.2.0 RC0

Hi Matthias, I've noticed a minor line break issue in the upgrade docs. I've created a small PR for that: https://github.com/apache/kafka/pull/6320 Best, Viktor On Sun, Feb 24, 2019 at 10:16 PM Stephane Maarek wrote: > Hi Matthias > > Thanks for this > Running through the list of KIPs. I

Re: [VOTE] KIP-430 - Return Authorized Operations in Describe Responses

Thanks Mickael. I thought I had to list the type only once when the same field appears twice (the field itself is listed both for cluster and topic). But you are the second person who brought this up, so I must be mistaken. I have added the type in both places to avoid confusion. On Mon, Feb 25,

Re: [VOTE] KIP-430 - Return Authorized Operations in Describe Responses

+1 (non binding) In the Metadata v8 section, it looks like the "authorized_operations" field is missing under "topic_metadata". There's only the top-level "authorized_operations" field. On Mon, Feb 25, 2019 at 12:11 PM Rajini Sivaram wrote: > > Hi Colin, > > Yes, it makes sense to reduce

Re: [VOTE] KIP-430 - Return Authorized Operations in Describe Responses

Hi Colin, Yes, it makes sense to reduce response size by using bit fields. Updated the KIP. I have also updated the KIP to say that clients will ignore any bits set by the broker that are unknown to the client, so there will be no UNKNOWN operations in the set returned by AdminClient. Brokers

Re: [DISCUSS] KIP-236 Interruptible Partition Reassignment

Hey George, Thanks for the prompt response, it makes sense. I'll try to keep your code changes on top of my list and help reviewing that. :) Regarding the incremental reassignment: I don't mind either to discuss it as part of this or in a separate conversation but I think a separate one could be

[jira] [Created] (KAFKA-7997) Replace SaslAuthenticate request/response with automated protocol

Mickael Maison created KAFKA-7997: - Summary: Replace SaslAuthenticate request/response with automated protocol Key: KAFKA-7997 URL: https://issues.apache.org/jira/browse/KAFKA-7997 Project: Kafka

Re: [VOTE] KIP-131 - Add access to OffsetStorageReader from SourceConnector

Hi Kafka Team, I'd like to bring this thread back at the top of the email stack to get a chance to see this KIP merge in the next minor/major release. Thanks. Le ven. 18 janv. 2019 à 01:20, Florian Hussonnois a écrit : > Hey folks, > > This KIP has start since a while but has never been

Re: [DISCUSS] KIP-434: Add Replica Fetcher and Log Cleaner Count Metrics

Hi Stanislav, Thanks for the feedback and sharing that discussion thread. I read your KIP and the discussion on it too and it seems like that'd cover the same motivation I had with the log-cleaner-thread-count metric. This supposed to tell the count of the alive threads which might differ from

Re: [DISCUSS] KIP-307: Allow to define custom processor names with KStreams DSL

Hi Matthias, Bill, I've updated the KIP with your last feedbacks. However, you have suggested to rename : `Suppressed#withName(String)` withName is not a static method like Joined.named was. withName method is part of the new interface NameOperation. In addition, I've split the PR in 5 commits

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

See Changes: [manikumar] KAFKA-7972: Use automatic RPC generation in SaslHandshake -- [...truncated 4.63 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

[jira] [Created] (KAFKA-7996) KafkaStreams does not pass timeout when closing Producer

Patrik Kleindl created KAFKA-7996: - Summary: KafkaStreams does not pass timeout when closing Producer Key: KAFKA-7996 URL: https://issues.apache.org/jira/browse/KAFKA-7996 Project: Kafka