Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-70

Data node should shutdown when a "critical" error is returned by the name node

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      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.

        Attachments

          Activity

            People

            • Assignee:
              sameerp Sameer Paranjpye
              Reporter:
              shv Konstantin Shvachko
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: