[
https://issues.apache.org/jira/browse/IMPALA-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v resolved IMPALA-3613.
-------------------------------
Resolution: Fixed
Fix Version/s: Impala 2.11.0
https://gerrit.cloudera.org/#/c/8449/
> Statestore should not update reconnected subscribers repeatedly
> ---------------------------------------------------------------
>
> Key: IMPALA-3613
> URL: https://issues.apache.org/jira/browse/IMPALA-3613
> Project: IMPALA
> Issue Type: Bug
> Components: Distributed Exec
> Affects Versions: Impala 2.5.0
> Reporter: Huaisi Xu
> Assignee: bharath v
> Fix For: Impala 2.11.0
>
>
> Subscriber normally will re-register when it thinks it gets disconnected from
> statestore in its own perspective. So it will register again. And statestore
> will push a new update for the newly subscribed clients without cleaning
> previous already scheduled(queued) one.
> If heart beat failed to catch up. those two queues will be filled full and
> may cause IMPALA-2642 (this can lead to dead lock).
> Essentially every new register will have one more update in queue. So we may
> end up with repeated scheduling for the same subscriber without notice.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
