[
https://issues.apache.org/jira/browse/KAFKA-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16199004#comment-16199004
]
ASF GitHub Bot commented on KAFKA-6046:
---------------------------------------
GitHub user tedyu opened a pull request:
https://github.com/apache/kafka/pull/4052
KAFKA-6046 DeleteRecordsRequest to a non-leader should give proper error
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tedyu/kafka trunk
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/4052.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4052
----
commit 4f25a3e9ef5cc079ca1ea549787d75f7ca6f8940
Author: tedyu <[email protected]>
Date: 2017-10-10T17:17:13Z
KAFKA-6046 DeleteRecordsRequest to a non-leader should give proper error
----
> DeleteRecordsRequest to a non-leader
> ------------------------------------
>
> Key: KAFKA-6046
> URL: https://issues.apache.org/jira/browse/KAFKA-6046
> Project: Kafka
> Issue Type: Bug
> Reporter: Tom Bentley
> Fix For: 1.1.0
>
>
> When a `DeleteRecordsRequest` is sent to a broker that's not the leader for
> the partition the `DeleteRecordsResponse` returns
> `UNKNOWN_TOPIC_OR_PARTITION`. This is ambiguous (does the topic not exist on
> any broker, or did we just sent the request to the wrong broker?), and
> inconsistent (a `ProduceRequest` would return `NOT_LEADER_FOR_PARTITION`).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
