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

Posted to dev@twill.apache.org by "Terence Yim (JIRA)" <ji...@apache.org> on 2017/12/04 18:24:00 UTC

[jira] [Resolved] (TWILL-250) On restarting the TwillRunnerService process, it can causes running apps unable to spin up new container

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

Terence Yim resolved TWILL-250.
-------------------------------
    Resolution: Not A Problem

Turns out it has been handled by checking against running applications

> On restarting the TwillRunnerService process, it can causes running apps unable to spin up new container
> --------------------------------------------------------------------------------------------------------
>
>                 Key: TWILL-250
>                 URL: https://issues.apache.org/jira/browse/TWILL-250
>             Project: Apache Twill
>          Issue Type: Bug
>          Components: core, yarn
>    Affects Versions: 0.10.0, 0.11.0, 0.12.0
>            Reporter: Terence Yim
>            Assignee: Terence Yim
>            Priority: Blocker
>
> A new TwillRunnerService instance will have a different sessionId (timestamp) and the `LocationCacheCleaner` just remove older version blindly, causing existing application fail to localize files when launch new container.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)