[jira] [Updated] (KAFKA-14167) Unexpected UNKNOWN_SERVER_ERROR raised from kraft controller
[
https://issues.apache.org/jira/browse/KAFKA-14167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson updated KAFKA-14167:
Priority: Blocker (was: Major)
> Unexpected UNKNOWN_SERVER_ERROR raised from kraft controller
>
>
> Key: KAFKA-14167
> URL: https://issues.apache.org/jira/browse/KAFKA-14167
> Project: Kafka
> Issue Type: Bug
>Reporter: Jason Gustafson
>Priority: Blocker
> Fix For: 3.3.0
>
>
> In `ControllerApis`, we have callbacks such as the following after completion:
> {code:java}
> controller.allocateProducerIds(context, allocatedProducerIdsRequest.data)
> .handle[Unit] { (results, exception) =>
> if (exception != null) {
> requestHelper.handleError(request, exception)
> } else {
> requestHelper.sendResponseMaybeThrottle(request, requestThrottleMs
> => {
> results.setThrottleTimeMs(requestThrottleMs)
> new AllocateProducerIdsResponse(results)
> })
> }
> } {code}
> What I see locally is that the underlying exception that gets passed to
> `handle` always gets wrapped in a `CompletionException`. When passed to
> `getErrorResponse`, this error will get converted to `UNKNOWN_SERVER_ERROR`.
> For example, in this case, a `NOT_CONTROLLER` error returned from the
> controller would be returned as `UNKNOWN_SERVER_ERROR`. It looks like there
> are a few APIs that are potentially affected by this bug, such as
> `DeleteTopics` and `UpdateFeatures`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (KAFKA-14167) Unexpected UNKNOWN_SERVER_ERROR raised from kraft controller
[
https://issues.apache.org/jira/browse/KAFKA-14167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson updated KAFKA-14167:
Fix Version/s: 3.3.0
> Unexpected UNKNOWN_SERVER_ERROR raised from kraft controller
>
>
> Key: KAFKA-14167
> URL: https://issues.apache.org/jira/browse/KAFKA-14167
> Project: Kafka
> Issue Type: Bug
>Reporter: Jason Gustafson
>Priority: Major
> Fix For: 3.3.0
>
>
> In `ControllerApis`, we have callbacks such as the following after completion:
> {code:java}
> controller.allocateProducerIds(context, allocatedProducerIdsRequest.data)
> .handle[Unit] { (results, exception) =>
> if (exception != null) {
> requestHelper.handleError(request, exception)
> } else {
> requestHelper.sendResponseMaybeThrottle(request, requestThrottleMs
> => {
> results.setThrottleTimeMs(requestThrottleMs)
> new AllocateProducerIdsResponse(results)
> })
> }
> } {code}
> What I see locally is that the underlying exception that gets passed to
> `handle` always gets wrapped in a `CompletionException`. When passed to
> `getErrorResponse`, this error will get converted to `UNKNOWN_SERVER_ERROR`.
> For example, in this case, a `NOT_CONTROLLER` error returned from the
> controller would be returned as `UNKNOWN_SERVER_ERROR`. It looks like there
> are a few APIs that are potentially affected by this bug, such as
> `DeleteTopics` and `UpdateFeatures`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
