[
https://issues.apache.org/jira/browse/HADOOP-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513804
]
Hadoop QA commented on HADOOP-1624:
-----------------------------------
-1, build or testing failed
2 attempts failed to build and test the latest attachment
http://issues.apache.org/jira/secure/attachment/12362103/HADOOP-1624.patch
against trunk revision r557118.
Test results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/432/testReport/
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/432/console
Please note that this message is automatically generated and may represent a
problem with the automation system and not the patch.
> Unknown op code exception in DataXceiver.
> -----------------------------------------
>
> Key: HADOOP-1624
> URL: https://issues.apache.org/jira/browse/HADOOP-1624
> Project: Hadoop
> Issue Type: Bug
> Affects Versions: 0.14.0
> Reporter: Konstantin Shvachko
> Assignee: Raghu Angadi
> Priority: Blocker
> Fix For: 0.14.0
>
> Attachments: HADOOP-1624.patch, HADOOP-1624.patch
>
>
> There is a missing break statement in DataNode.DataXceiver.run() which sends
> DataXceiver into an infinite loop printing
> Faulty op: 82
> 07/07/17 17:52:04 ERROR dfs.DataNode: DataXCeiver
> java.io.IOException: Unknown opcode 82in data stream
> at org.apache.hadoop.dfs.DataNode$DataXceiver.run(DataNode.java:742)
> at java.lang.Thread.run(Thread.java:595)
> Consequence of HADOOP-1134.
> Also a printout two lines below seems unnecessary.
> And another three lines below
> LOG.error("DataXCeiver", t);
> should be spelled DataXceiver
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
