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 13346200CB4 for ; Tue, 27 Jun 2017 16:49:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 11E9B160BC6; Tue, 27 Jun 2017 14:49:05 +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 EA0A8160BDC for ; Tue, 27 Jun 2017 16:49:03 +0200 (CEST) Received: (qmail 97034 invoked by uid 500); 27 Jun 2017 14:49:03 -0000 Mailing-List: contact jira-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@kafka.apache.org Delivered-To: mailing list jira@kafka.apache.org Received: (qmail 97023 invoked by uid 99); 27 Jun 2017 14:49:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jun 2017 14:49:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id B7526C24A5 for ; Tue, 27 Jun 2017 14:49:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.011 X-Spam-Level: X-Spam-Status: No, score=-100.011 tagged_above=-999 required=6.31 tests=[SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 8lYDK3nqUQXC for ; Tue, 27 Jun 2017 14:49:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 7260D5FD91 for ; Tue, 27 Jun 2017 14:49:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id B043CE0DAA for ; Tue, 27 Jun 2017 14:49:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1F7D124135 for ; Tue, 27 Jun 2017 14:49:00 +0000 (UTC) Date: Tue, 27 Jun 2017 14:49:00 +0000 (UTC) From: "Ismael Juma (JIRA)" To: jira@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (KAFKA-5342) Distinguish abortable failures in transactional producer MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 27 Jun 2017 14:49:05 -0000 [ https://issues.apache.org/jira/browse/KAFKA-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5342: ------------------------------- Parent Issue: KAFKA-5527 (was: KAFKA-4815) > Distinguish abortable failures in transactional producer > -------------------------------------------------------- > > Key: KAFKA-5342 > URL: https://issues.apache.org/jira/browse/KAFKA-5342 > Project: Kafka > Issue Type: Sub-task > Components: clients, core, producer > Reporter: Jason Gustafson > Assignee: Jason Gustafson > Fix For: 0.11.0.1 > > > The transactional producer distinguishes two classes of user-visible errors: > 1. Abortable errors: these are errors which are fatal to the ongoing transaction, but which can be successfully aborted. Essentially any error in which the producer can still expect to successfully send EndTxn to the transaction coordinator is abortable. > 2. Fatal errors: any error which is not abortable is fatal. For example, a transactionalId authorization error is fatal because it would also prevent the TC from receiving the EndTxn request. > At the moment, it's not clear how the user would know how they should handle a given failure. One option is to add an exception type to indicate which errors are abortable (e.g. AbortableKafkaException). Then any other exception could be considered fatal. -- This message was sent by Atlassian JIRA (v6.4.14#64029)