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/09/21 22:47:00 UTC
[jira] [Updated] (SAMZA-1411) Document SystemProducer changes in
Samza 0.14.0
[ https://issues.apache.org/jira/browse/SAMZA-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jake Maes updated SAMZA-1411:
-----------------------------
Description:
Document the producer changes in SAMZA-1392. Particularly:
0. MOST IMPORTANTLY: if users enable task.drop.producer.errors they should also alert on *producer-send-failed metric!
1. How are producer exceptions handled in general? How can the user configure them to be ignored? How can they tell if there was a producer exception (sendFail, flushFail metrics)?
2. How does the KafkaSystemProducer handle exceptions?
3. Retries and linger ms config defaults
4. Others TBD
was:
Document the producer changes in SAMZA-1392. Particularly:
1. How are producer exceptions handled in general? How can the user configure them to be ignored? How can they tell if there was a producer exception (sendFail, flushFail metrics)?
2. How does the KafkaSystemProducer handle exceptions?
3. Retries and linger ms config defaults
4. Others TBD
> Document SystemProducer changes in Samza 0.14.0
> -----------------------------------------------
>
> Key: SAMZA-1411
> URL: https://issues.apache.org/jira/browse/SAMZA-1411
> Project: Samza
> Issue Type: Bug
> Reporter: Jake Maes
> Assignee: Jake Maes
> Fix For: 0.14.0
>
>
> Document the producer changes in SAMZA-1392. Particularly:
> 0. MOST IMPORTANTLY: if users enable task.drop.producer.errors they should also alert on *producer-send-failed metric!
> 1. How are producer exceptions handled in general? How can the user configure them to be ignored? How can they tell if there was a producer exception (sendFail, flushFail metrics)?
> 2. How does the KafkaSystemProducer handle exceptions?
> 3. Retries and linger ms config defaults
> 4. Others TBD
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)