Skip to content

Kafka 2761#445

Closed
SinghAsDev wants to merge 1 commit intoapache:trunkfrom
SinghAsDev:KAFKA-2761
Closed

Kafka 2761#445
SinghAsDev wants to merge 1 commit intoapache:trunkfrom
SinghAsDev:KAFKA-2761

Conversation

@SinghAsDev
Copy link
Copy Markdown
Contributor

#412 is a pre-req.

@SinghAsDev
Copy link
Copy Markdown
Contributor Author

@guozhangwang this should take care of your concern on KAFKA-2734. I like to keep separate concerns in separate commits, as it makes it easier to cherry-pick and follow. I hope it makes sense. Also, note that this branch already has KAFKA-2734, which is a pre-req to this PR, cherry-picked to help reviewers try out the changes locally.

@guozhangwang
Copy link
Copy Markdown
Contributor

@SinghAsDev Could you rebase?

@SinghAsDev
Copy link
Copy Markdown
Contributor Author

@guozhangwang done

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this happen with the check in ConsoleConsumer?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This check is actually redundant, as it is also happening in ConsoleConsumer. However, the check just seemed to be natural here. Let me know if you are in favor of removing it.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was originally thinking if it should not ever happen let's remove it, after another thought I feel it may be OK to leave it as is.

@guozhangwang
Copy link
Copy Markdown
Contributor

LGTM, thanks.

@asfgit asfgit closed this in 34d9976 Nov 8, 2015
granders referenced this pull request in confluentinc/kafka Nov 18, 2015
…onsoleConsumer

#412 is a pre-req.

Author: Ashish Singh <asingh@cloudera.com>

Reviewers: Guozhang Wang

Closes #445 from SinghAsDev/KAFKA-2761
hachikuji added a commit to hachikuji/kafka that referenced this pull request Dec 8, 2020
…ng loop (apache#445)

This patch does the following:

1) Events are handled in order. The previous logic attempted to route the out-of-band registration/fencing messages to the front of the queue, but it seems simpler to let them be handled in order. I am not sure it is worthwhile optimizing for the case when there is a backlog of events to be processed.
2) Event failures are propagated. Previously we incremented an error counter, but an event failure leaves the broker state machine in an indeterminate state and it seems dangerous to try and continue. 
3) Simplify processor API. Rather than overloading `process`, we can use a single method and let the processor `match` on the events it wants to handle.
4) Hook up `MetaLogManager.Listener`. The only real change here is that I preferred to retain the java List type since it awkwardly converts to the `Buffer` type with the scala collection converters.
wyuka pushed a commit to wyuka/kafka that referenced this pull request Mar 22, 2023
…plicas on parition assignment cancellation (apache#445)

This should be a direct fix-up to the commit 
- 28cca3e Cancellation of reassignments allowed if the resulting ISR is at min-ISR (apache#442)
davide-armand pushed a commit to aiven/kafka that referenced this pull request Dec 1, 2025
…e#445)

* feat(inkless): support loading google access token credentials

If service account impersonation is used, then a plain access token is
used for authentication.

* fix(inkless): fix reloading Gcs credentials

GoogleCredentials.equals returned true by comparing only public
fields. Simply always reset Storage instance with given credentials.
jeqo pushed a commit to aiven/kafka that referenced this pull request Jan 16, 2026
…e#445)

* feat(inkless): support loading google access token credentials

If service account impersonation is used, then a plain access token is
used for authentication.

* fix(inkless): fix reloading Gcs credentials

GoogleCredentials.equals returned true by comparing only public
fields. Simply always reset Storage instance with given credentials.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants