Re: [DISCUSS] KIP-572: Improve timeouts and retires in Kafka Streams

Thanks for the feedback Bruno. I updated the KIP (I thought the info was there, but it seems it was too implicit). 1) Each time a client TimeoutException happens, we would log a WARN message. If `task.timeout.ms` expires, we would rethrow the last client `TimeoutException` to stop processing.

[DISCUSS] KIP-609: Use Pre-registration and Blocking Calls for Better Transaction Efficiency

Hey all, I would like to start the discussion for KIP-609: https://cwiki.apache.org/confluence/display/KAFKA/KIP-609%3A+Use+Pre-registration+and+Blocking+Calls+for+Better+Transaction+Efficiency This KIP aims to improve the current EOS semantic which makes the processing more efficient and

Jenkins build is back to normal : kafka-trunk-jdk11 #1457

See

[jira] [Resolved] (KAFKA-8311) Better consumer timeout exception handling

[ https://issues.apache.org/jira/browse/KAFKA-8311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-8311. Resolution: Duplicate Closing this ticket – KIP-572 / KAFKA-9274 does subsume it. >

Re: [DISCUSS] KIP-613: Add end-to-end latency metrics to Streams

Thanks for the KIP Sophie. I think it's not useful to record the avg/mean; it sensitive to outliers. We should rather track the median (50th percentile). Not sure if tracking min is useful, but I am also ok to track it. However, I find it odd to track 75th percentile. Standard measures would

Build failed in Jenkins: kafka-trunk-jdk14 #84

See Changes: [github] MINOR: Handle task migrated inside corruption path (#8667) -- [...truncated 3.09 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

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

See Changes: [github] MINOR: Handle task migrated inside corruption path (#8667) -- [...truncated 6.14 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

Re: KAFKA-10000

Hey Matthias, thanks for calling this out in the community. Maybe one way to do this is to encourage everyone who read this thread to browse over "tickets created by me" and see if some of those are already fixed / not an issue any more :)

Re: KAFKA-10000

Thanks a lot for starting this initiative Matthias! I guess I will start from closing my open tickets first :) On Thu, May 14, 2020 at 9:02 PM Matthias J. Sax wrote: > Hi, > > today, KAFKA-1 was created, marking quite a milestone for the > project. This milestone made me look into our

KAFKA-10000

Hi, today, KAFKA-1 was created, marking quite a milestone for the project. This milestone made me look into our backlog and there are many old and outdated tickets. The oldest ticket I found was KAFKA-10 (closed it already)... Cleaning up the backlog is quite tedious, and I took the liberty

[jira] [Resolved] (KAFKA-7985) Cleanup AssignedTasks / AbstractTask logic

[ https://issues.apache.org/jira/browse/KAFKA-7985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-7985. Resolution: Abandoned Given that this ticket is old and the code was refactored multiple

[jira] [Resolved] (KAFKA-7708) [kafka-streams-scala] Invalid signature for KTable join in 2.12

[ https://issues.apache.org/jira/browse/KAFKA-7708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-7708. Resolution: Abandoned > [kafka-streams-scala] Invalid signature for KTable join in 2.12 >

[jira] [Resolved] (KAFKA-7445) Branch one Stream in multiple Streams

[ https://issues.apache.org/jira/browse/KAFKA-7445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-7445. Resolution: Not A Problem > Branch one Stream in multiple Streams >

[jira] [Resolved] (KAFKA-7203) Improve Streams StickyTaskAssingor

[ https://issues.apache.org/jira/browse/KAFKA-7203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-7203. Resolution: Fixed > Improve Streams StickyTaskAssingor >

[jira] [Resolved] (KAFKA-7209) Kafka stream does not rebalance when one node gets down

[ https://issues.apache.org/jira/browse/KAFKA-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-7209. Resolution: Abandoned > Kafka stream does not rebalance when one node gets down >

[jira] [Resolved] (KAFKA-7133) DisconnectException every 5 minutes in single restore consumer thread

[ https://issues.apache.org/jira/browse/KAFKA-7133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-7133. Resolution: Abandoned > DisconnectException every 5 minutes in single restore consumer

[jira] [Resolved] (KAFKA-7035) Kafka Processor's init() method sometimes is not called

[ https://issues.apache.org/jira/browse/KAFKA-7035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-7035. Resolution: Abandoned > Kafka Processor's init() method sometimes is not called >

[jira] [Resolved] (KAFKA-7015) Enhance RecordCollectorImpl exceptions with more context information

[ https://issues.apache.org/jira/browse/KAFKA-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-7015. Resolution: Not A Problem We should actually not log sensitive information like key and

[jira] [Resolved] (KAFKA-7004) Support configurable restore consumer poll timeout

[ https://issues.apache.org/jira/browse/KAFKA-7004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-7004. Resolution: Fixed > Support configurable restore consumer poll timeout >

[jira] [Resolved] (KAFKA-6977) Kafka Streams - java.lang.IllegalStateException: Unexpected error code 2 while fetching data

[ https://issues.apache.org/jira/browse/KAFKA-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6977. Resolution: Abandoned > Kafka Streams - java.lang.IllegalStateException: Unexpected error

[jira] [Resolved] (KAFKA-6888) java.lang.UnsatisfiedLinkError: librocksdbjni4271925274440341234.dll: âÑX

[ https://issues.apache.org/jira/browse/KAFKA-6888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6888. Resolution: Abandoned > java.lang.UnsatisfiedLinkError:

[jira] [Resolved] (KAFKA-6822) Kafka Consumer 0.10.2.1 can not normally read data from Kafka 1.0.0

[ https://issues.apache.org/jira/browse/KAFKA-6822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6822. Resolution: Abandoned > Kafka Consumer 0.10.2.1 can not normally read data from Kafka

[jira] [Resolved] (KAFKA-6821) The producer attempted to use a producer id which is not currently assigned to its transactional id

[ https://issues.apache.org/jira/browse/KAFKA-6821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6821. Resolution: Cannot Reproduce A lot of work on EOS was done recently. Closing this ticket

[jira] [Resolved] (KAFKA-6804) Event values should not be included in log messages

[ https://issues.apache.org/jira/browse/KAFKA-6804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6804. Resolution: Fixed I believe this is fixed via KAFKA-8501. > Event values should not be

[jira] [Resolved] (KAFKA-6461) TableTableJoinIntegrationTest is unstable if caching is enabled

[ https://issues.apache.org/jira/browse/KAFKA-6461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6461. Resolution: Cannot Reproduce > TableTableJoinIntegrationTest is unstable if caching is

[jira] [Resolved] (KAFKA-6237) stream stopped working after exception: Cannot execute transactional method because we are in an error state

[ https://issues.apache.org/jira/browse/KAFKA-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6237. Resolution: Cannot Reproduce There was a lot of EOS work recently. Closing this ticket.

[jira] [Resolved] (KAFKA-6182) Automatic co-partitioning of topics via automatic intermediate topic with matching partitions

[ https://issues.apache.org/jira/browse/KAFKA-6182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6182. Resolution: Fixed KIP-221 is implemented now. Closing this ticket. > Automatic

[jira] [Resolved] (KAFKA-6125) Avoid third party exception to flow through streams code base

[ https://issues.apache.org/jira/browse/KAFKA-6125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6125. Resolution: Not A Problem > Avoid third party exception to flow through streams code base

[jira] [Resolved] (KAFKA-6124) Revisit default config for internal client with regard to resilience

[ https://issues.apache.org/jira/browse/KAFKA-6124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6124. Resolution: Abandoned We changed couple of default values (also in consumer/producer/admin

Re: [DISCUSS] KIP-613: Add end-to-end latency metrics to Streams

Hi Sophie, It seems like there would still be plenty of use cases for recording this metric at all processors and not just stateful ones, but I'm happy to suspend my arguments for now. Since you're proposing to keep them at the processor-node level, it will be seamless later to add in the

[jira] [Resolved] (KAFKA-6000) streams 0.10.2.1 - kafka 0.11.0.1 state restore not working

[ https://issues.apache.org/jira/browse/KAFKA-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6000. Resolution: Abandoned > streams 0.10.2.1 - kafka 0.11.0.1 state restore not working >

[jira] [Resolved] (KAFKA-5625) Invalid subscription data may cause streams app to throw BufferUnderflowException

[ https://issues.apache.org/jira/browse/KAFKA-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-5625. Resolution: Abandoned > Invalid subscription data may cause streams app to throw >

[jira] [Resolved] (KAFKA-5581) Avoid creating changelog topics for state stores that are materialized from a source topic

[ https://issues.apache.org/jira/browse/KAFKA-5581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-5581. Resolution: Fixed > Avoid creating changelog topics for state stores that are materialized

[jira] [Resolved] (KAFKA-5393) in-memory state store memory issue

[ https://issues.apache.org/jira/browse/KAFKA-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-5393. Resolution: Abandoned > in-memory state store memory issue >

[jira] [Resolved] (KAFKA-5240) Make persistent checkpointedOffsets optionable

[ https://issues.apache.org/jira/browse/KAFKA-5240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-5240. Resolution: Fixed > Make persistent checkpointedOffsets optionable >

Re: [DISCUSS] KIP-614: Add Prefix Scan support for State Stores

Hi, Sagar! Thanks for this KIP. I'm sorry it took me so long to reply. I'll number my points differently to avoid confusion. I can provide some additional context on the difficulties we previously faced in KIP-213 (which you and Adam have already discussed). J1) In your KIP, you propose the

[jira] [Resolved] (KAFKA-5071) ERROR StreamThread:783 StreamThread-128 - stream-thread [StreamThread-128] Failed to commit StreamTask 0_304 state: org.apache.kafka.streams.errors.ProcessorStateExcept

[ https://issues.apache.org/jira/browse/KAFKA-5071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-5071. Resolution: Abandoned > ERROR StreamThread:783 StreamThread-128 - stream-thread

[jira] [Resolved] (KAFKA-4934) Add streams test with RocksDb failures

[ https://issues.apache.org/jira/browse/KAFKA-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-4934. Resolution: Abandoned > Add streams test with RocksDb failures >

[jira] [Resolved] (KAFKA-4887) Enabling caching on a persistent window store breaks support for duplicate insertion

[ https://issues.apache.org/jira/browse/KAFKA-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-4887. Resolution: Fixed > Enabling caching on a persistent window store breaks support for

[jira] [Resolved] (KAFKA-4778) OOM on kafka-streams instances with high numbers of unreaped Record classes

[ https://issues.apache.org/jira/browse/KAFKA-4778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-4778. Resolution: Abandoned Does not seem to be an issue in newer released any more? > OOM on

[jira] [Resolved] (KAFKA-4742) ResetTool does not commit offsets correclty

[ https://issues.apache.org/jira/browse/KAFKA-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-4742. Resolution: Abandoned This ticket only affect 0.10.0.x and 0.10.1.x and it's very unlikely

[jira] [Resolved] (KAFKA-4697) Simplify Streams Reset Tool

[ https://issues.apache.org/jira/browse/KAFKA-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-4697. Resolution: Abandoned This tickets only affect 0.10.0.x and 0.10.1.x versions and it's

[jira] [Resolved] (KAFKA-7566) Add sidecar job to leader (or a random single follower) only

[ https://issues.apache.org/jira/browse/KAFKA-7566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-7566. Resolution: Won't Fix > Add sidecar job to leader (or a random single follower) only >

Re: KIP-560 Discuss

Hey Sang, seems this thread has been quiet, are you still working on this KIP? On Sat, Mar 7, 2020 at 3:54 PM Matthias J. Sax wrote: > Thanks for the KIP Sang! > > I have a couple of more comments about the wiki page: > > (1) The "Public Interface" section should only list the new stuff. This >

[jira] [Resolved] (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 ] Matthias J. Sax resolved KAFKA-3779. Resolution: Won't Fix `KTable#to()` was removed from the API. > Add the LRU cache for

[jira] [Resolved] (KAFKA-10) Kafka deployment on EC2 should be WHIRR based, instead of current contrib/deploy code based solution

[ https://issues.apache.org/jira/browse/KAFKA-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-10. -- Resolution: Won't Fix (was: Abandoned) Apache Whirr has been retired. > Kafka deployment on

Re: [DISCUSS] KIP-610: Error Reporting in Sink Connectors

Hi Randall, Thanks for the feedback. 1. This is a great suggestion, but I find that adding an overloaded put(...) which essentially deprecates the old put(...) to only be used when a connector is deployed on older versions of Connect adds enough of a complication that could cause connectors to

[jira] [Created] (KAFKA-10001) Store's own restore listener should be triggered in store changelog reader

Guozhang Wang created KAFKA-10001: - Summary: Store's own restore listener should be triggered in store changelog reader Key: KAFKA-10001 URL: https://issues.apache.org/jira/browse/KAFKA-10001

Re: [DISCUSS] KIP-601: Configurable socket connection timeout

Hi Rajini, Thanks for the reply. > Not sure 10s is a good default because it unnecessarily times out > connections, only to attempt re-connecting to the same broker (except in > the leastLoadedNode case where it would be useful to have a lower timeout). The underlying logic for a connection

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

See Changes: [github] MINOR: skip listOffsets request for newly created changelog topics [github] KAFKA-9984 Should fail the subscription when pattern is empty (#8665)

Re: [DISCUSS] KIP-610: Error Reporting in Sink Connectors

Hi Andrew, Thanks for your comments. Based on my understanding from https://kafka.apache.org/25/javadoc/org/apache/kafka/connect/sink/SinkTask.html, put(...) can be asynchronous but not necessarily should be, specifically in: "As records are fetched from Kafka, they will be passed to the sink

Need help regarding missing kafka producer metrics while upgrade from 1.1.0 to 2.0.0

Hi Kafka community, we are currently using kafka client version 1.1.0 in our production. I'm working on upgrade it to kafka version 2.0.0. I see there are some metrics which are present in version 1.1.1 are removed in kafka version 2.0.0. S# version 1.1.1 2.0.0 1

Re: [VOTE] KIP-586: Deprecate commit records without record metadata

+1 (binding) Makes a lot of sense :) Thanks, Mario. On Mon, Apr 27, 2020 at 12:05 PM Mario Molina wrote: > Hi all, > > I'd like to start a vote for KIP-586. You can find the link for this KIP > here: > >

Re: [DISCUSS] KIP-610: Error Reporting in Sink Connectors

Hi Aakash, Responding to your question from a separate KIP-610 discussion thread here, with my comments: > 4. Great point about the addition of the extra configuration properties. By "If we decide to include these properties, we should also update the "Synchrony" section to be agnostic about

Re: [DISCUSS] KIP-610: Error Reporting in Sink Connectors

Hi Randall, I think I prefer the method originally specified in the KIP. A separate method can come with a contract about if/when it's called so that tasks can assume that it's only invoked once over their lifetime, and allows connector developers to separate the logic for storing (and possibly

[jira] [Created] (KAFKA-10000) Atomic commit of source connector records and offsets

Chris Egerton created KAFKA-1: - Summary: Atomic commit of source connector records and offsets Key: KAFKA-1 URL: https://issues.apache.org/jira/browse/KAFKA-1 Project: Kafka

Re: [DISCUSS] KIP-610: Error Reporting in Sink Connectors

Hi, Aakash. Thanks for the KIP. Connect does need an improved ability for sink connectors to report individual records as being problematic, and this integrates nicely with the existing DLQ feature. I also appreciate the desire to maintain compatibility so that connectors can take advantage of

Re: [VOTE]: KIP-604: Remove ZooKeeper Flags from the Administrative Tools

+1. Thanks Colin! Guozhang On Tue, May 12, 2020 at 3:45 PM Colin McCabe wrote: > Hi all, > > I'd like to start a vote on KIP-604: Remove ZooKeeper Flags from the > Administrative Tools. > > As a reminder, this KIP is for the next major release of Kafka, the 3.0 > release. So it won't go

Re: [DISCUSS] KIP-596 Safely abort Producer transactions during application shutdown

Hey Xiang, since Matthias is agreeing, do you want to kick off the vote? Boyang On Fri, May 8, 2020 at 4:20 PM Matthias J. Sax wrote: > >> I'm not sure I follow your question, the producer will not automatically > >> close when there is fatal error IIUC. > > Correct. I found the code example

Re: [VOTE] KIP-606: Add Metadata Context to MetricsReporter

+1 (binding) Thanks for the proposal, Xavier. On Wed, May 13, 2020 at 4:10 PM Gwen Shapira wrote: > +1 (binding) > Thanks for the proposal, Xavier. > > On Wed, May 13, 2020 at 11:54 AM Xavier Léauté wrote: > > > Hi everyone, > > > > Folks seem happy with the state of the KIP, so I'd like to

Re: [DISCUSS] KIP-554: Add Broker-side SCRAM Config API

Hi Cheng, Good point. I updated the KIP to include the same information that is currently returned. best, Colin On Sun, May 10, 2020, at 22:40, Cheng Tan wrote: > Hi Colin, > > > If I understood correctly, in your design, listScramUsers will return > the mechanism and iteration. Let’s use

Re: [DISCUSS] KIP-554: Add Broker-side SCRAM Config API

On Tue, May 12, 2020, at 06:43, Tom Bentley wrote: > Hi Colin, > > It's not clear whether users of the Java API would need to supply the salt > and salted password directly, or whether the constructor of ScramCredential > would take the password and perform the hashing itself. > Hi Tom, The

Build failed in Jenkins: kafka-trunk-jdk11 #1456

See Changes: [github] MINOR: skip listOffsets request for newly created changelog topics [github] KAFKA-9984 Should fail the subscription when pattern is empty (#8665)

[jira] [Resolved] (KAFKA-9984) Should fail the subscription when pattern is empty

[ https://issues.apache.org/jira/browse/KAFKA-9984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-9984. Fix Version/s: 2.6.0 Resolution: Fixed > Should fail the subscription when pattern

Re: [DISCUSS] KIP-614: Add Prefix Scan support for State Stores

Whoops, I guess I didn't finish reading the KIP all the way to the end earlier. Thanks for including the link to the RocksDB PR in the KIP! I have one additional question about the proposal: do you plan to also add this prefix seek API to the dual column family iterators? These are used by

[jira] [Created] (KAFKA-9999) Topic description should be triggered after each failed topic creation iteration

Boyang Chen created KAFKA-: -- Summary: Topic description should be triggered after each failed topic creation iteration Key: KAFKA- URL: https://issues.apache.org/jira/browse/KAFKA- Project:

[jira] [Created] (KAFKA-9998) KafkaProducer.close(timeout) still may block indefinitely

radai rosenblatt created KAFKA-9998: --- Summary: KafkaProducer.close(timeout) still may block indefinitely Key: KAFKA-9998 URL: https://issues.apache.org/jira/browse/KAFKA-9998 Project: Kafka

Build failed in Jenkins: kafka-trunk-jdk11 #1455

See Changes: [github] KAFKA-9650: include human readable units in ms and bytes configs (#8222) -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node

[jira] [Created] (KAFKA-9997) upgrade log4j lib to address CVE-2020-9488

Emanuele Maccherani created KAFKA-9997: -- Summary: upgrade log4j lib to address CVE-2020-9488 Key: KAFKA-9997 URL: https://issues.apache.org/jira/browse/KAFKA-9997 Project: Kafka Issue

[jira] [Created] (KAFKA-9996) upgrade zookeeper to 3.5.8 to address security vulnerabilities

Emanuele Maccherani created KAFKA-9996: -- Summary: upgrade zookeeper to 3.5.8 to address security vulnerabilities Key: KAFKA-9996 URL: https://issues.apache.org/jira/browse/KAFKA-9996 Project:

Re: [DISCUSS] KIP-613: Add end-to-end latency metrics to Streams

Hey all, After discussing with Bruno I'd like to propose a small amendment, which is to record the processor-node-level metrics only for *stateful* *operators*. They would still be considered a "processor-node-level" metric and not a "state-store-level" metric as the staleness is still a property

Re: [DISCUSS] KIP-614: Add Prefix Scan support for State Stores

Hey @Adam, Thanks for sharing your experience with using prefix seek. I did look at your code for RocksDBPrefixIterator, infact I have repurposed that class itself since it wasn't being used else where. Regarding how I plan to expose them through-out the state stores, what I have tried to do is

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

See

Re: [DISCUSS] KIP-405: Kafka Tiered Storage

Hi Jun, Thanks for your comments. We updated the KIP with more details. >100. For each of the operations related to tiering, it would be useful to provide a description on how it works with the new API. These include things like consumer fetch, replica fetch, offsetForTimestamp, retention

[jira] [Created] (KAFKA-9995) IllegalStateException when offsets not found

James Hay created KAFKA-9995: Summary: IllegalStateException when offsets not found Key: KAFKA-9995 URL: https://issues.apache.org/jira/browse/KAFKA-9995 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-9994) Catch TaskMigrated exception in task corruption code path

Boyang Chen created KAFKA-9994: -- Summary: Catch TaskMigrated exception in task corruption code path Key: KAFKA-9994 URL: https://issues.apache.org/jira/browse/KAFKA-9994 Project: Kafka Issue

[jira] [Created] (KAFKA-9993) Think about inheritance in the protocol generation framework

Boyang Chen created KAFKA-9993: -- Summary: Think about inheritance in the protocol generation framework Key: KAFKA-9993 URL: https://issues.apache.org/jira/browse/KAFKA-9993 Project: Kafka

Re: [DISCUSS] KIP-572: Improve timeouts and retires in Kafka Streams

Thanks for the update, Matthias! Other than Bruno’s good points, this proposal looks good to me. Thanks, John On Thu, May 14, 2020, at 07:17, Bruno Cadonna wrote: > Hi Matthias, > > Thank you for the KIP. I like your KIP. > > Here my feedback: > > 1. The KIP is not clear about what should

Re: [VOTE] KIP-577: Allow HTTP Response Headers Configured for Kafka Connect

All, Vote for this KIP has been passed. This KIP is accepted with 3 +1 binding votes (Randall, Manikumar, Konstantine) and 1 +1 non-binding vote (Aneel) Thanks to all who made suggestion and ideas. Jeff Huang. On 2020/04/17 18:28:20, Zhiguo Huang wrote: > Thanks to everyone for their

Re: [DISCUSS] KIP-612: Ability to Limit Connection Creation Rate on Brokers

Hi Anna, Thanks for your answers and the updated KIP. Looks good to me! Best, David On Thu, May 14, 2020 at 12:54 AM Anna Povzner wrote: > I updated the KIP to add a new broker configuration to limit connection > creation rate per IP: max.connection.creation.rate.per.ip. Once the limit > is

Re: KIP Request

Hi David, Thanks for your interest. You're all set now. -Bill On Thu, May 14, 2020 at 10:43 AM David Mollitor wrote: > Hello, > > I would like to create a KIP in regards to: > > https://github.com/apache/kafka/pull/7944 > > Can you please add my Apache ID (dmollitor) to the access list? > >

Kafka Integration with Microsoft Dynamics 365 CE

Hi team, We are looking for the SCADA integration with Dynamics 356 CE w Kafka. We already have SCADA and Kafka integration in place. Just wanted to understand if there are readymade connector available for Kafka and Dynamics 365 integration. Any support is appreciated. Regards Vrushali

KIP Request

Hello, I would like to create a KIP in regards to: https://github.com/apache/kafka/pull/7944 Can you please add my Apache ID (dmollitor) to the access list? Thanks. -- *David A. Mollitor* | Principal Customer Operations Engineer cloudera.com [image: Cloudera]

Build failed in Jenkins: kafka-trunk-jdk11 #1454

See Changes: [github] KAFKA-6145: KIP-441: Improve assignment balance (#8588) -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment

Re: [DISCUSS] KIP-601: Configurable socket connection timeout

Hi Cheng, 1) Thanks for the update, the KIP now says ` socket.connections.setup.timeout.ms*`*, which sounds good. 2) Not sure 10s is a good default because it unnecessarily times out connections, only to attempt re-connecting to the same broker (except in the leastLoadedNode case where it would

Re: [DISCUSS] KIP-585: Conditional SMT

Hi Konstantine, Thanks very much for your input. It's helpful to have a steer from a committer on the syntax point especially. I've made all those changes and added a note about compatibility. Cheers, Tom On Thu, May 14, 2020 at 6:00 AM Konstantine Karantasis < konstant...@confluent.io> wrote:

[jira] [Created] (KAFKA-9992) EmbeddedKafka not working with kafka_2.13

Andras Katona created KAFKA-9992: Summary: EmbeddedKafka not working with kafka_2.13 Key: KAFKA-9992 URL: https://issues.apache.org/jira/browse/KAFKA-9992 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP-572: Improve timeouts and retires in Kafka Streams

Hi Matthias, Thank you for the KIP. I like your KIP. Here my feedback: 1. The KIP is not clear about what should happen when task.timeout.ms expires. To facilitate the mapping from the error users might encounter due to timeouts to this KIP, it would be good to state the error that will be

Re: [DISCUSS] KIP-613: Add end-to-end latency metrics to Streams

Hi Sophie, Thank you for the KIP. The KIP looks good to me. 50th percentile: I think we do not need it now. If we need it, we can add it. Here the old truism applies: Adding is always easier than removing. processor-node-level metrics: I think it is good to have the staleness metrics also on

[jira] [Resolved] (KAFKA-7965) Flaky Test ConsumerBounceTest#testRollingBrokerRestartsWithSmallerMaxGroupSizeConfigDisruptsBigGroup

[ https://issues.apache.org/jira/browse/KAFKA-7965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-7965. Resolution: Fixed > Flaky Test >

[jira] [Resolved] (KAFKA-9676) Add test coverage for new ActiveTaskCreator and StandbyTaskCreator

[ https://issues.apache.org/jira/browse/KAFKA-9676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-9676. Resolution: Fixed The current unit test coverage is pretty good now, closing the ticket. > Add