You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Shanthoosh Venkataraman (JIRA)" <ji...@apache.org> on 2018/02/16 18:24:00 UTC
[jira] [Updated] (SAMZA-1587) Switch from infinite to bounded
retries in ExponentialBackOffStrategy usage within samza
[ https://issues.apache.org/jira/browse/SAMZA-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shanthoosh Venkataraman updated SAMZA-1587:
-------------------------------------------
Description:
ExponentialStrategy is used for multiple scenarios within samba such as fetching metadata of input stream, fetching messages from input stream, creating intermediate streams etc.
In all these scenarios, some failures are irrecoverable and retrying it indefinitely will prevent the exception propagation to samza users.
Creating this ticket for book-keeping purposes.
was:
ExponentialStrategy is used for multiple scenarios within samba such as fetching metadata of input stream, fetching messages from input stream, creating intermediate streams etc.
In all these scenarios, some failures are irrecoverable and blocking it indefinitely will prevent the exception propagation to samza users.
Creating this ticket for book-keeping purposes.
> Switch from infinite to bounded retries in ExponentialBackOffStrategy usage within samza
> ----------------------------------------------------------------------------------------
>
> Key: SAMZA-1587
> URL: https://issues.apache.org/jira/browse/SAMZA-1587
> Project: Samza
> Issue Type: Bug
> Reporter: Shanthoosh Venkataraman
> Assignee: Shanthoosh Venkataraman
> Priority: Major
>
> ExponentialStrategy is used for multiple scenarios within samba such as fetching metadata of input stream, fetching messages from input stream, creating intermediate streams etc.
> In all these scenarios, some failures are irrecoverable and retrying it indefinitely will prevent the exception propagation to samza users.
> Creating this ticket for book-keeping purposes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)