You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Konstantin Shvachko (JIRA)" <ji...@apache.org> on 2007/07/18 03:27:04 UTC
[jira] Created: (HADOOP-1624) Unknown op code exception in
DataXceiver.
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
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.
[jira] Updated: (HADOOP-1624) Unknown op code exception in
DataXceiver.
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Cutting updated HADOOP-1624:
---------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this. Thanks, Raghu!
> 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.
[jira] Commented: (HADOOP-1624) Unknown op code exception in
DataXceiver.
Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513787 ]
Konstantin Shvachko commented on HADOOP-1624:
---------------------------------------------
+1
> 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
>
>
> 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.
[jira] Updated: (HADOOP-1624) Unknown op code exception in
DataXceiver.
Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raghu Angadi updated HADOOP-1624:
---------------------------------
Attachment: HADOOP-1624.patch
Updated the patch. Forgot to remove the unused import that Konstantin mentioned.
> 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.
[jira] Updated: (HADOOP-1624) Unknown op code exception in
DataXceiver.
Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raghu Angadi updated HADOOP-1624:
---------------------------------
Attachment: HADOOP-1624.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
>
>
> 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.
[jira] Updated: (HADOOP-1624) Unknown op code exception in
DataXceiver.
Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raghu Angadi updated HADOOP-1624:
---------------------------------
Status: Patch Available (was: Open)
> 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
>
>
> 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.
[jira] Commented: (HADOOP-1624) Unknown op code exception in
DataXceiver.
Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513710 ]
Raghu Angadi commented on HADOOP-1624:
--------------------------------------
'break' is missing. This causes exception to be thrown once, not in a loop. This gets triggered when a datanode joins after block-crc upgrade is completed on the cluster.
will attach a patch that includes other modifications Konstantin suggested (these were not part of 1134).
> 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
>
>
> 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.
[jira] Commented: (HADOOP-1624) Unknown op code exception in
DataXceiver.
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (HADOOP-1624) Unknown op code exception in
DataXceiver.
Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513411 ]
Konstantin Shvachko commented on HADOOP-1624:
---------------------------------------------
Also a redundant import
import org.apache.hadoop.dfs.FSConstants.StartupOption;
> 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
>
>
> 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.