You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/10/12 14:45:00 UTC
[jira] [Updated] (STORM-3254) Blob localization time-outs can cause
Slot to be stuck and leaked over time
[ https://issues.apache.org/jira/browse/STORM-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated STORM-3254:
----------------------------------
Labels: pull-request-available (was: )
> Blob localization time-outs can cause Slot to be stuck and leaked over time
> ---------------------------------------------------------------------------
>
> Key: STORM-3254
> URL: https://issues.apache.org/jira/browse/STORM-3254
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-server
> Reporter: Kishor Patil
> Assignee: Kishor Patil
> Priority: Major
> Labels: pull-request-available
>
> If Blobs requested by slot take forever to come back, the Slot could get stuck in _waiting-for-blob-localization_ state, even after release of slot or topology being killed making that slot unusable. So worker for next assignment will never be launched.
> The steps to reproduce this are:
> # Delay blob store localization.
> # kill topology and check jstack.
> # worker will not be scheduled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)