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

See Changes: [me] KAFKA-7834: Extend collected logs in system test services to include -- [...truncated 2.29 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

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

See Changes: [manikumar] MINOR: release.py: fix some compatibility problems. [me] KAFKA-7834: Extend collected logs in system test services to include -- [...truncated

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

See

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

See Changes: [manikumar] KAFKA-7804: Update docs for topic-command related KIP-377 -- [...truncated 2.20 MB...] kafka.controller.PartitionLeaderElectionAlgorithmsTest >

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

See Changes: [me] MINOR: Upgrade ducktape to 0.7.5 (#6197) -- [...truncated 1.40 MB...] org.apache.kafka.common.security.scram.ScramCredentialUtilsTest > invalidCredential

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

See Changes: [manikumar] KAFKA-7804: Update docs for topic-command related KIP-377 [manikumar] MINOR: release.py: fix some compatibility problems. -- [...truncated 2.29

[jira] [Created] (KAFKA-7897) Invalid use of epoch cache following message format downgrade

Jason Gustafson created KAFKA-7897: -- Summary: Invalid use of epoch cache following message format downgrade Key: KAFKA-7897 URL: https://issues.apache.org/jira/browse/KAFKA-7897 Project: Kafka

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

See Changes: [manikumar] KAFKA-7804: Update docs for topic-command related KIP-377 -- [...truncated 2.30 MB...] org.apache.kafka.connect.json.JsonConverterTest >

[jira] [Resolved] (KAFKA-7834) Extend collected logs in system test services to include heap dumps

[ https://issues.apache.org/jira/browse/KAFKA-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-7834. -- Resolution: Fixed Fix Version/s: (was: 1.1.2)

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

"I think you are saying that this enables additional (potentially cheaper) storage options without *requiring* an existing ETL pipeline. “ Yes. " But it's not really a replacement for the sort of pipelines people build with Connect, Gobblin etc.” It is not. But also making an assumption that

Re: Request permission to create KIP for likan

Gave you permission. Please take a look. Thanks, Harsha On Feb 4, 2019, 3:13 PM -0800, Li Kan , wrote: > Hi Kafka Team, > > Would you please grant me permission to create KIP? I'd like to create a > KIP. Thanks. > My wiki ID is likan: https://cwiki.apache.org/confluence/display/~likan > > -- >

Request permission to create KIP for likan

Hi Kafka Team, Would you please grant me permission to create KIP? I'd like to create a KIP. Thanks. My wiki ID is likan: https://cwiki.apache.org/confluence/display/~likan -- Best, Kan

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

See Changes: [github] KAFKA-7832: Use automatic RPC generation in CreateTopics (#5972) -- [...truncated 4.58 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

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

Thanks Harsha, makes sense for the most part. > tiered storage is to get away from this and make this transparent to the user I think you are saying that this enables additional (potentially cheaper) storage options without *requiring* an existing ETL pipeline. But it's not really a replacement

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

See Changes: [github] KAFKA-7832: Use automatic RPC generation in CreateTopics (#5972) -- [...truncated 2.30 MB...]

[VOTE] KIP-425: Add some Log4J Kafka Appender Properties for Producing to Secured Brokers

Calling a vote for this since it's pretty trivial/non-controversial https://cwiki.apache.org/confluence/display/KAFKA/KIP-425%3A+Add+some+Log4J+Kafka+Appender+Properties+for+Producing+to+Secured+Brokers

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

Hi Eric, Thanks for your questions. Answers are in-line "The high-level design seems to indicate that all of the logic for when and how to copy log segments to remote storage lives in the RLM class. The default implementation is then HDFS specific with additional implementations being left

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

Harsha, Sriharsha, Suresh, a couple thoughts: - How could this be used to leverage fast key-value stores, e.g. Couchbase, which can serve individual records but maybe not entire segments? Or is the idea to only support writing and fetching entire segments? Would it make sense to support both? -

Re: [DISCUSS] KIP-415: Incremental Cooperative Rebalancing in Kafka Connect

Hi all, Thank you for your comments so far. Now that KIP freeze and feature freeze are behind us for version 2.2, I'd like to bring this thread back at the top of the email stack, with the following suggestion: I'll be changing KIP-415's description to include a serialization format that extends

[jira] [Resolved] (KAFKA-7883) Add schema.namespace support to SetSchemaMetadata SMT in Kafka Connect

[ https://issues.apache.org/jira/browse/KAFKA-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jérémy Thulliez resolved KAFKA-7883. Resolution: Workaround > Add schema.namespace support to SetSchemaMetadata SMT in Kafka

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

The high level design seems to indicate that all of the logic for when and how to copy log segments to remote storage lives in the RLM class. The default implementation is then HDFS specific with additional implementations being left to the community. This seems like it would require anyone

[DISCUSS] KIP-405: Kafka Tiered Storage

Hi All, We are interested in adding tiered storage to Kafka. More details about motivation and design are in the KIP. We are working towards an initial POC. Any feedback or questions on this KIP are welcome. Thanks, Harsha

Re: [DISCUSS] KIP-391: Allow Producing with Offsets for Cluster Replication

Hi Radai, thanks for the observation on the the kip-320 conflict. I would not have the destination broker treat the __consumer_offsets as a special case (if this is what you suggested). Rather in the replicator the __consumer_offsets topic could be treated as a special case where instead of just

Re: [DISCUSS] KIP-425: Add some Log4J Kafka Appender Properties for Producing to Secured Brokers

I've worked with the module a bit, a while ago. Overall, the proposal is simple and reasonable - just bring the Log4J appender up to the same configuration we already have elsewhere. So, I support this KIP. Thanks, Rohan :) On Mon, Feb 4, 2019 at 1:54 AM Dongjin Lee wrote: > > Hi Rohan, > >

[jira] [Resolved] (KAFKA-817) Implement a zookeeper path-based controlled shutdown tool

[ https://issues.apache.org/jira/browse/KAFKA-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sönke Liebau resolved KAFKA-817. Resolution: Won't Fix I'll close this for now as I've received no feedback to the contrary. >

[jira] [Resolved] (KAFKA-1015) documentation for inbuilt offset management

[ https://issues.apache.org/jira/browse/KAFKA-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sönke Liebau resolved KAFKA-1015. - Resolution: Fixed I'll close this as there was no conflicting feedback here or on the mailing

Re: metric for total volume of messages per topic over a period of time

Hi Stanislav, Thanks for the suggestions. I am looking for exactly what you suggested. My final objective: get the volume of data ingested in a day (or any such time frame). My approach: collect the bytes in per sec value and run an aggregate (sum) on the collected data to get the volume

[jira] [Resolved] (KAFKA-659) Support request pipelining in the network server

[ https://issues.apache.org/jira/browse/KAFKA-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sönke Liebau resolved KAFKA-659. Resolution: Fixed I'll close this for now since no-one objected here or on the mailing list, so

[jira] [Resolved] (KAFKA-217) Client test suite

[ https://issues.apache.org/jira/browse/KAFKA-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sönke Liebau resolved KAFKA-217. Resolution: Won't Fix I'll close this for now since no-one objected here or on the mailing list. If

Re: [DISCUSS] KIP-425: Add some Log4J Kafka Appender Properties for Producing to Secured Brokers

Hi Rohan, Thank you for your proposal. Since the release of 2.2.0 is imminent, most committers are on working frenzy now so don't be distressed if there are few responses for the discussion thread. Although I am not a committer, here are some notes I would like to share about submitting a KIP: