You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Bharath Kumarasubramanian (Jira)" <ji...@apache.org> on 2021/05/06 00:05:00 UTC

[jira] [Updated] (SAMZA-2633) Rolling deployment/upgrade causes downtime for processors for the entire deployment window

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

Bharath Kumarasubramanian updated SAMZA-2633:
---------------------------------------------
    Fix Version/s: 1.7

> Rolling deployment/upgrade causes downtime for processors for the entire deployment window
> ------------------------------------------------------------------------------------------
>
>                 Key: SAMZA-2633
>                 URL: https://issues.apache.org/jira/browse/SAMZA-2633
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Bharath Kumarasubramanian
>            Assignee: Bharath Kumarasubramanian
>            Priority: Major
>             Fix For: 1.7
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> *Problem*:
> At LinkedIn, we noticed several standalone users complained about lag/downtime during rolling deployments/upgrades.
> *Description*:
> During rolling upgrades, the current debounce timer gets extended every time when there is a quorum change notification. As a result, processors that were upgraded earlier in the deployment window remain unavailable waiting for work assignment. In some scenarios, this cause processors to be unavailable for 20 minutes or so depending on the size of the quorum and the debounce time configuration.
> *Impact*:
> Partitions that were stopped for initial processors as part of upgrade remain unassigned for the entire deployment window which can result in processing lag.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)