You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Jake Maes (JIRA)" <ji...@apache.org> on 2017/12/22 18:38:00 UTC
[jira] [Resolved] (SAMZA-1539) KafkaProducer potential hang on
close() when task.drop.producer.errors==true
[ https://issues.apache.org/jira/browse/SAMZA-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jake Maes resolved SAMZA-1539.
------------------------------
Resolution: Fixed
Issue resolved by pull request 390
[https://github.com/apache/samza/pull/390]
> KafkaProducer potential hang on close() when task.drop.producer.errors==true
> ----------------------------------------------------------------------------
>
> Key: SAMZA-1539
> URL: https://issues.apache.org/jira/browse/SAMZA-1539
> Project: Samza
> Issue Type: Bug
> Reporter: Jake Maes
> Assignee: Jake Maes
> Fix For: 0.15.0
>
>
> The issue is caused by 2 bad behaviors:
> 1. KafkaProducer.close() does an unbounded thread.join() even when a force close (timeout == 0 ms) is specified.
> 2. KafkaSystemProducer.handleSendException() has a synchronized block to recreate the producer when task.drop.producer.errors==true. When the IO thread is waiting on the synchronized block, it prevents the KafkaProducer from joining the IO thread.
> Fixing either one will fix the issue, but we will close this ticket as soon as the Samza side is tested and committed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)