Mailing-List: contact jira-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@kafka.apache.org
Date: Tue, 27 Jun 2017 14:49:00 +0000 (UTC)
From: "Ismael Juma (JIRA)" <jira@apache.org>
To: jira@kafka.apache.org
Message-ID: <JIRA.13073323.1495167657000.115926.1498574940091@Atlassian.JIRA>
In-Reply-To: <JIRA.13073323.1495167657000@Atlassian.JIRA>
References: <JIRA.13073323.1495167657000@Atlassian.JIRA> <JIRA.13073323.1495167657452@jira-lw-us.apache.org>
Subject: [jira] [Updated] (KAFKA-5286) Producer should await transaction
 completion in close
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 27 Jun 2017 14:49:03 -0000


     [ https://issues.apache.org/jira/browse/KAFKA-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ismael Juma updated KAFKA-5286:
-------------------------------
    Parent Issue: KAFKA-5527  (was: KAFKA-4815)

> Producer should await transaction completion in close
> -----------------------------------------------------
>
>                 Key: KAFKA-5286
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5286
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: clients, core, producer 
>            Reporter: Jason Gustafson
>             Fix For: 0.11.0.1
>
>
> We should wait at least as long as the timeout for a transaction which has begun completion (commit or abort) to be finished. Tricky thing is whether we should abort a transaction which is in progress. It seems reasonable since that's the coordinator will either timeout and abort the transaction or the next producer using the same transactionalId will fence the producer and abort the transaction. In any case, the transaction will be aborted, so perhaps we should do it proactively.


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