You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tez.apache.org by "Zhiyuan Yang (JIRA)" <ji...@apache.org> on 2016/05/06 16:49:12 UTC

[jira] [Created] (TEZ-3245) Data race between addKnowInput and clearAndGetOnepartition of InputHost

Zhiyuan Yang created TEZ-3245:
---------------------------------

             Summary: Data race between addKnowInput and clearAndGetOnepartition of InputHost
                 Key: TEZ-3245
                 URL: https://issues.apache.org/jira/browse/TEZ-3245
             Project: Apache Tez
          Issue Type: Bug
            Reporter: Zhiyuan Yang
            Assignee: Zhiyuan Yang


In ShuffleManager::addKnownInput, InputHost::addKnowInput is invoked without locking. At the same time, InputHost::clearAndGetOnePartition can be invoked with lock(ShuffleManager.RunShuffleCallable::callInternal => ShuffleManager::constructFetcherForHost => InputHosst::clearAndGetOnePartition). The method clearAndGetOnePartition does two things: drain input attempt of a host and then delete the entry for this host. If addKnownInput happens between these two operation, the added input will be deleted without being handled.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)