Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@giraph.apache.org
Date: Tue, 11 Feb 2014 23:04:20 +0000 (UTC)
From: "Roman Shaposhnik (JIRA)" <jira@apache.org>
To: giraph-dev@incubator.apache.org
Message-ID: <JIRA.12665157.1377217995357.27088.1392159860212@arcas>
In-Reply-To: <JIRA.12665157.1377217995357@arcas>
References: <JIRA.12665157.1377217995357@arcas>
Subject: [jira] [Commented] (GIRAPH-747) BspServiceMaster finishes ZooKeeper
 cleanup without waiting for all workers to complete
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/GIRAPH-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898460#comment-13898460 ] 

Roman Shaposhnik commented on GIRAPH-747:
-----------------------------------------

[~initialcontext] any chance we can fix this for 1.1.0? I guess you're the resident Giraph-on-YARN expert ;-)

> BspServiceMaster finishes ZooKeeper cleanup without waiting for all workers to complete
> ---------------------------------------------------------------------------------------
>
>                 Key: GIRAPH-747
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-747
>             Project: Giraph
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Chuan Lei
>            Assignee: Chuan Lei
>             Fix For: 1.1.0
>
>         Attachments: GIRAPH-747.v1.patch
>
>
> In BspServiceMaster, the function cleanUpZooKeeper should wait for the number of workers and masters to complete. However, it appears that maxTasks only takes workers into consideration. Consequently, the worker straggler may fail to report to the ZooKeeper due to the path gets removed too early. This will cause No lease on path File does not exist exception at runtime.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)