kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-5913) Add RecordMetadataNotAvailableException to indicate that ProduceResponse did not contain offset and timestamp information
Date Sat, 16 Sep 2017 01:18:00 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168748#comment-16168748
] 

ASF GitHub Bot commented on KAFKA-5913:
---------------------------------------

GitHub user apurvam opened a pull request:

    https://github.com/apache/kafka/pull/3878

    KAFKA-5913: Add the RecordMetadataNotAvailableException

    We return this exception from `RecordMetadata.offset()` or `RecordMetadata.timestamp()`
if these pieces of metadata were not returned by the broker. 
    
    This will happen, for instance, when the broker returns a `DuplicateSequenceException`.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apurvam/kafka KAFKA-5913-add-record-metadata-not-available-exception

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/3878.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 #3878
    
----
commit e9770a65203f7bdcea8c25a5fbaaa9366d12851c
Author: Apurva Mehta <apurva@confluent.io>
Date:   2017-09-16T01:15:15Z

    Initial commit

----


> Add RecordMetadataNotAvailableException to indicate that ProduceResponse did not contain
offset and timestamp information
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-5913
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5913
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Apurva Mehta
>            Assignee: Apurva Mehta
>             Fix For: 1.0.0
>
>
> One of the changes in KIP-192 is to send a {{DUPLICATE_SEQUENCE}} error code with a {{ProduceResponse}}
when we detect a duplicate on the broker but don't have the batch metadata for the sequence
in question in memory.
> To handle this on the client, we mark the batch as successful, but cannot return the
offset and timestamp information in the {{RecordMetadata}} returned in the produce future.
Instead of returning implicit invalid values (like -1), we should throw a {{RecordMetadataNotAvailableException}}
to ensure that applications don't suffer from faulty processing.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message