[
https://issues.apache.org/jira/browse/HADOOP-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated HADOOP-4671:
----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
{noformat}
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] -1 tests included. The patch doesn't appear to include any new
or modified tests.
[exec] Please justify why no tests are needed for
this patch.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath
integrity.
{noformat}
I just committed this.
> Make some "flag" booleans volatile because they are set/read in different
> threads
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-4671
> URL: https://issues.apache.org/jira/browse/HADOOP-4671
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/chukwa, dfs, mapred
> Reporter: Owen O'Malley
> Assignee: Chris Douglas
> Priority: Minor
> Fix For: 0.20.0
>
> Attachments: 4671-0.patch
>
>
> Peter Veentjer has identified the following variables as being tracked
> in a loop without assignments or synchronization.
> AgentControllerSocketListener.closing
> HttpConnector.stopMe
> IndexUpdateReducer.closed
> SecundaryNodeName.shouldRun
> voTask.hasNext
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
