[HDFS-70] Data node should shutdown when a "critical" error is returned by the name node

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Assignee: Sameer Paranjpye
• Reporter: Konstantin Shvachko
• Created: 01/Jun/06 09:38
• Updated: 17/Jul/11 18:26
• Resolved: 17/Jul/11 18:26

Description

Currently data node does not distinguish between critical and non critical exceptions.
Any exception is treated as a signal to sleep and then try again. See
org.apache.hadoop.dfs.DataNode.run()
This is happening because RPC always throws the same RemoteException.
In some cases (like UnregisteredDatanodeException, IncorrectVersionException) the data
node should shutdown rather than retry.
This logic naturally belongs to the
org.apache.hadoop.dfs.DataNode.offerService()
but can be reasonably implemented (without examining the RemoteException.className
field) after HADOOP-266 (2) is fixed.