Re: Timeout not getting applied on KafkaAdminClient.create

Hi, Tuning SOCKET_CONNECTION_SETUP_TIMEOUT_MAX_MS_CONFIG / SOCKET_CONNECTION_SETUP_TIMEOUT_MS_CONFIG didn't helped, what i fail to understand is why timeout is not happening after 30seconds. These are the properties i have configured. {ssl.protocol=TLSv1.2, request.timeout.ms=1000, acks=0,

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #1582

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.4 #80

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #1581

See

Re: [VOTE] KIP-889 Versioned State Stores

Hi everyone, I have just pushed two minor amendments to KIP-889: - Updated the versioned store specification to clarify that the *"history retention" parameter is also used as "grace period,"* which means that writes (including inserts, updates, and deletes) to the store will not be

Re: [VOTE] KIP-903: Replicas with stale broker epoch should not be allowed to join the ISR

Hi, Calvin, Thanks for the KIP. +1 Jun On Fri, Feb 10, 2023 at 11:03 AM Alexandre Dupriez < alexandre.dupr...@gmail.com> wrote: > +1 (non-binding). > > Le ven. 10 févr. 2023 à 19:02, Calvin Liu a > écrit : > > > > Hi all, > > > > I'd like to call for a vote on KIP-903, which proposes a fix to

[jira] [Resolved] (KAFKA-14711) kafaka-metadata-quorum.sh does not honor --command-config

[ https://issues.apache.org/jira/browse/KAFKA-14711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino resolved KAFKA-14711. --- Resolution: Fixed > kafaka-metadata-quorum.sh does not honor --command-config >

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #1580

See

Re: [DISCUSS] KIP-894: Use incrementalAlterConfigs API for syncing topic configurations

Hi Chris My comment on the second point is not correct. Please ignore the part about the config source (config source does set back to DEFAULT_CONFIG when deleting a config). I got diverted off the issue a little bit. With the legacy API, we do propagate deletion due to resetting all the configs

Re: [DISCUSS] KIP-894: Use incrementalAlterConfigs API for syncing topic configurations

Hi Tina, Thanks for the updates! RE item 1: Ah, to be clear, I wasn't suggesting that we retry with the incremental API for every request, just wondering about whether we'd want to block on the very first request completing before we issue subsequent requests, since otherwise we might send

Re: [DISCUSS] KIP-900: KRaft kafka-storage.sh API additions to support SCRAM

Comments below. On Wed, Feb 1, 2023 at 2:24 PM Proven Provenzano wrote: > The following are also acceptable from your example. I changed the ordering > because it does't matter. > > --add-config entity-type brokers entity-name 0 foo=bar > --add-config default-entity entity-type broker baaz=quux

Re: [DISCUSS] KIP-900: KRaft kafka-storage.sh API additions to support SCRAM

Comments below. On Mon, Feb 13, 2023 at 11:44 AM Proven Provenzano wrote: > > Hi Jose > > I want to clarify that the file parsing that Argparse4j provides is just a > mechanism for > taking command line args and putting them in a file. It doesn't > actually change what the > command line args

Re:Timeout not getting applied on KafkaAdminClient.create

If the broker connection is timing out then see if tuning SOCKET_CONNECTION_SETUP_TIMEOUT_MAX_MS_CONFIG / SOCKET_CONNECTION_SETUP_TIMEOUT_MS_CONFIG helps. The MAX defaults to 30 seconds. From: dev@kafka.apache.org At: 02/13/23 08:46:12 UTC-5:00To: dev@kafka.apache.org Subject: Timeout not

[jira] [Created] (KAFKA-14712) Confusing error when writing downgraded FeatureImage

David Arthur created KAFKA-14712: Summary: Confusing error when writing downgraded FeatureImage Key: KAFKA-14712 URL: https://issues.apache.org/jira/browse/KAFKA-14712 Project: Kafka Issue

Re: [DISCUSS] KIP-903: Replicas with stale broker epoch should not be allowed to join the ISR

Hi David. Thanks for the feedback. I have updated the KIP as you suggested. On Mon, Feb 13, 2023 at 7:34 AM David Jacot wrote: > Hi Calvin, > > 01. Should we update the KIP to mention this? > > 09. The upgrade part is still not very clear in my opinion. It would be > good to clearly mention how

Re: [DISCUSS] KIP-900: KRaft kafka-storage.sh API additions to support SCRAM

Hi Jose I want to clarify that the file parsing that Argparse4j provides is just a mechanism for taking command line args and putting them in a file. It doesn't actually change what the command line args are for processing the file. So I can add any kafka-storage command line arg into the file

Re: [DISCUSS] KIP-793: Sink Connectors: Support topic-mutating SMTs for async connectors (preCommit users)

Hi Yash, I think the key difference between adding methods/overloads related to SinkTask::open/SinkTask::close and SinkTask::put is that this isn't auxiliary information that may or may not be useful to connector developers. It's actually critical for them to understand the difference between the

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #1579

See

Re: [DISCUSS] KIP-900: KRaft kafka-storage.sh API additions to support SCRAM

Thanks for the discussion Colin and Proven. CLIs can be difficult to design when there are complicated use cases. Did we consider having CLI flags only for the common case? I would think that the common case is SCRAM for one user. For the complicated and less common cases they have to provide a

[jira] [Resolved] (KAFKA-6793) Unnecessary warning log message

[ https://issues.apache.org/jira/browse/KAFKA-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6793. Fix Version/s: 3.5.0 Resolution: Fixed We resolved this by changing the logging to

[jira] [Created] (KAFKA-14711) kafaka-metadata-quorum.sh does not honor --command-config

Ron Dagostino created KAFKA-14711: - Summary: kafaka-metadata-quorum.sh does not honor --command-config Key: KAFKA-14711 URL: https://issues.apache.org/jira/browse/KAFKA-14711 Project: Kafka

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #1578

See Changes: -- [...truncated 472247 lines...] [2023-02-13T11:01:05.891Z] [INFO] Changes detected - recompiling the module! [2023-02-13T11:01:05.891Z] [INFO] Compiling 3

Re: [DISCUSS] KIP-793: Sink Connectors: Support topic-mutating SMTs for async connectors (preCommit users)

Hi Chris, > especially if connectors are intentionally designed around > original topic partitions instead of transformed ones. Ha, that's a good point and reminds me of Hyrum's Law [1] :) > I think we have to provide connector developers with some > way to differentiate between the two, but

Re: [DISCUSS] KIP-903: Replicas with stale broker epoch should not be allowed to join the ISR

Hi Calvin, 01. Should we update the KIP to mention this? 09. The upgrade part is still not very clear in my opinion. It would be good to clearly mention how we are going to handle the upgrade of the AlterPartition API and the Fetch API. For the former, the broker uses the ApiVersions API to

[GitHub] [kafka-site] C0urante commented on pull request #491: MINOR: Fix anchor links in Connect docs

C0urante commented on PR #491: URL: https://github.com/apache/kafka-site/pull/491#issuecomment-1428125181 Thanks Bill! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

[GitHub] [kafka-site] C0urante merged pull request #491: MINOR: Fix anchor links in Connect docs

C0urante merged PR #491: URL: https://github.com/apache/kafka-site/pull/491 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Timeout not getting applied on KafkaAdminClient.create

Hi, I want to add timeout for KafkaAdminClient creation. AdminClient admin1 = KafkaAdminClient.create(properties); I have thread which gets killed after 10seconds. I want that if KafkaAdminClient creation is taking more time it should timeout. But when kafka-broker is not present my code gets

[jira] [Created] (KAFKA-14710) KRaft cannot initialise storage for valid UUID

Tristan Stevens created KAFKA-14710: --- Summary: KRaft cannot initialise storage for valid UUID Key: KAFKA-14710 URL: https://issues.apache.org/jira/browse/KAFKA-14710 Project: Kafka Issue

[jira] [Created] (KAFKA-14709) Move content in connect/mirror/README.md to the docs

Mickael Maison created KAFKA-14709: -- Summary: Move content in connect/mirror/README.md to the docs Key: KAFKA-14709 URL: https://issues.apache.org/jira/browse/KAFKA-14709 Project: Kafka

Re: [DISCUSS] KIP-894: Use incrementalAlterConfigs API for syncing topic configurations

Hi Chris and Luke, Thank you very much for your feedback. I have addressed some of the suggestions and would like to clarify a few things on the others: > 1) The current logic for syncing topic configs in MM2 is basically fire-and-forget; all we do is log a warning message [1] if an attempt