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

Posted to issues@tez.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2015/01/15 00:50:35 UTC

[jira] [Created] (TEZ-1950) Incorrect handling of counters in TaskAttemptImpl

Hitesh Shah created TEZ-1950:
--------------------------------

             Summary: Incorrect handling of counters in TaskAttemptImpl
                 Key: TEZ-1950
                 URL: https://issues.apache.org/jira/browse/TEZ-1950
             Project: Apache Tez
          Issue Type: Bug
            Reporter: Hitesh Shah


To maintain task attempt counters, we are using TaskAttempt.TaskAttemptStatus.counters

Now, counters is not accessed in a thread safe manner. 

Counters are updated in either StatusUpdaterTransition or modified as part of
TaskAttempt.TaskAttemptStatus::setLocalityCounter(). 

In a scenario, where TaskAttempt::getCounters() is called before any status update transition comes back, the locality counter will get lost because the atomic boolean flag is never reset.





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