Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 798C1200B17 for ; Mon, 6 Jun 2016 23:08:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 77012160A56; Mon, 6 Jun 2016 21:08:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E4F34160A24 for ; Mon, 6 Jun 2016 23:08:21 +0200 (CEST) Received: (qmail 68555 invoked by uid 500); 6 Jun 2016 21:08:21 -0000 Mailing-List: contact dev-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list dev@flink.apache.org Received: (qmail 68534 invoked by uid 99); 6 Jun 2016 21:08:21 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Jun 2016 21:08:21 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id E56E62C033A for ; Mon, 6 Jun 2016 21:08:20 +0000 (UTC) Date: Mon, 6 Jun 2016 21:08:20 +0000 (UTC) From: "Elias Levy (JIRA)" To: dev@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (FLINK-4027) FlinkKafkaProducer09 sink can lose messages MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 06 Jun 2016 21:08:22 -0000 Elias Levy created FLINK-4027: --------------------------------- Summary: FlinkKafkaProducer09 sink can lose messages Key: FLINK-4027 URL: https://issues.apache.org/jira/browse/FLINK-4027 Project: Flink Issue Type: Bug Components: Kafka Connector Affects Versions: 1.0.3 Reporter: Elias Levy Priority: Critical The FlinkKafkaProducer09 sink appears to not offer at-least-once guarantees. The producer is publishing messages asynchronously. A callback can record publishing errors, which will be raised when detected. But as far as I can tell, there is no barrier to wait for async errors from the sink when checkpointing or to track the event time of acked messages to inform the checkpointing process. If a checkpoint occurs while there are pending publish requests, and the requests return a failure after the checkpoint occurred, those message will be lost as the checkpoint will consider them processed by the sink. -- This message was sent by Atlassian JIRA (v6.3.4#6332)