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

Hi Viktor, "Now, will the consumer be able to consume a remote segment if: - the remote segment is stored in the remote storage, BUT - the leader broker failed right after this AND - the follower which is to become a leader didn't scan yet for a new segment?" If I understand correctly,

[jira] [Created] (KAFKA-8188) Zookeeper Connection Issue Take Down the Whole kafka cluster

Candice Wan created KAFKA-8188: -- Summary: Zookeeper Connection Issue Take Down the Whole kafka cluster Key: KAFKA-8188 URL: https://issues.apache.org/jira/browse/KAFKA-8188 Project: Kafka

Re: [VOTE] KIP-422: Use the default value of max.poll.interval in Streams

Thanks all. The KIP-442 vote has passed with 3 binding votes (Guozhang, Bill, and Damian) and one non-binding vote (me) in favor and none against. I'll update the KIP page. -John On Fri, Mar 29, 2019 at 10:29 AM Damian Guy wrote: > +1 > > On Wed, 27 Mar 2019 at 21:38, John Roesler wrote: > >

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

See Changes: [rhauch] KAFKA-8126: Flaky Test -- [...truncated 2.73 MB...] kafka.coordinator.group.GroupCoordinatorTest > testValidJoinGroup STARTED

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

See Changes: [rhauch] KAFKA-8126: Flaky Test -- [...truncated 899.79 KB...] kafka.server.ServerGenerateBrokerIdTest > testConsistentBrokerIdFromUserConfigAndMetaProps

Re: [DISCUSS] KIP-411: Add option to make Kafka Connect task client ID values unique

Thanks Randall, I updated the proposal as suggested. Let me know if any other changes need to be made, otherwise I think the KIP-411 proposal is ready to finalize. I will aim to call a vote on Friday. On Mon, Mar 25, 2019 at 7:12 AM Ryanne Dolan wrote: > Randall, Paul, the proposal looks

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

See Changes: [rhauch] KAFKA-8126: Flaky Test -- [...truncated 1.90 MB...] ^

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

See Changes: [rhauch] KAFKA-8126: Flaky Test -- [...truncated 2.36 MB...] org.apache.kafka.connect.runtime.distributed.DistributedHerderTest > testUnknownConnectorPaused

[jira] [Created] (KAFKA-8187) State store record loss across multiple reassignments when using standby tasks

William Greer created KAFKA-8187: Summary: State store record loss across multiple reassignments when using standby tasks Key: KAFKA-8187 URL: https://issues.apache.org/jira/browse/KAFKA-8187

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

See Changes: [rhauch] KAFKA-8126: Flaky Test -- [...truncated 2.35 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

Kafka Jenkins not showing recent builds in history

Hi everybody, I looked through recent Jenkins builds for a while today and it somehow looks off to me. Both jobs [1] [2] don't show any builds that are more recent than March 19th in the "build history". Only the "last failed" and "last unsuccessful" permalinks show recent dates. Build pages can

[jira] [Resolved] (KAFKA-5141) WorkerTest.testCleanupTasksOnStop transient failure due to NPE

[ https://issues.apache.org/jira/browse/KAFKA-5141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-5141. -- Resolution: Fixed > WorkerTest.testCleanupTasksOnStop transient failure due to NPE >

[jira] [Resolved] (KAFKA-8126) Flaky Test org.apache.kafka.connect.runtime.WorkerTest.testAddRemoveTask

[ https://issues.apache.org/jira/browse/KAFKA-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-8126. -- Resolution: Fixed > Flaky Test org.apache.kafka.connect.runtime.WorkerTest.testAddRemoveTask >

[jira] [Resolved] (KAFKA-8063) Flaky Test WorkerTest#testConverterOverrides

[ https://issues.apache.org/jira/browse/KAFKA-8063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-8063. -- Resolution: Fixed > Flaky Test WorkerTest#testConverterOverrides >

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

See

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

See

Re: [VOTE] KIP-443: Return to default segment.ms and segment.index.bytes in Streams repartition topics

Hello Sönke, Thanks for the quick catch! I've fixed the test with this change. Guozhang On Wed, Apr 3, 2019 at 5:53 AM Sönke Liebau wrote: > Hi Guozhang, > > I've left a comment on the merged pull request, but not sure if you'll get > notified about that since the PR was already merged, so

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

Harsha, can you comment on this alternative approach: instead of fetching directly from remote storage via a new API, implement something like paging, where segments are paged-in and out of cold storage based on access frequency/recency? For example, when a remote segment is accessed, it could be

Re: [DISCUSS] KIP-252: Extend ACLs to allow filtering based on ip ranges and subnets

Hi Sönke, Maybe a reasonable design here would be to not allow creating ACLs based on ip ranges and subnets unless the inter-broker protocol setting has been upgraded. If an upgrade is done correctly, the IBP should not be upgraded until all the brokers have been upgraded, so there shouldn't

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

Hi Harsha, Thanks for the answer, makes sense. In the meantime one edge case popped up in my mind but first let me summarize what I understand if I interpret your KIP correctly. So basically whenever the leader RSM copies over a segment to the remote storage, the leader RLM will append an entry

Re: [VOTE] KIP-443: Return to default segment.ms and segment.index.bytes in Streams repartition topics

Hi Guozhang, I've left a comment on the merged pull request, but not sure if you'll get notified about that since the PR was already merged, so I'll write here as well. Setting this to -1 needs to be reflected in the test shouldAddInternalTopicConfigForRepartitionTopics as well, as this currently

Re: [DISCUSS] KIP-252: Extend ACLs to allow filtering based on ip ranges and subnets

All, as this thread has now been dormant for about three months again I'll am willing to consider the attempt at looking at a larger versioning scheme for ACLs as failed. I am away for a long weekend tomorrow and will start a [VOTE] thread on implementing this as is on Monday, as I personally

[jira] [Created] (KAFKA-8186) Apply for translation of the Chinese version, I hope to get authorization!

Yuan Yifan created KAFKA-8186: - Summary: Apply for translation of the Chinese version, I hope to get authorization! Key: KAFKA-8186 URL: https://issues.apache.org/jira/browse/KAFKA-8186 Project: Kafka

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

See Changes: [github] KAFKA-7190: KIP-443; Remove streams overrides on repartition topics -- [...truncated 2.35 MB...] org.apache.kafka.streams.test.OutputVerifierTest >