Hadoop HDFS
  1. Hadoop HDFS
  2. HDFS-2891

Some times first DataNode detected as bad when we power off for the second DataNode.

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.1.0
    • Fix Version/s: None
    • Component/s: datanode, hdfs-client
    • Labels:
      None

      Description

      In one of my clusters, observed this situation.
      This issue looks to be due to time out in ResponseProcesser at client side, it is marking first DataNode as bad.
      This happens in 20.2 version. This can be there in branch-1 as well and will check for trunk.

        Activity

        Uma Maheswara Rao G created issue -
        Uma Maheswara Rao G made changes -
        Field Original Value New Value
        Affects Version/s 1.1.0 [ 12317959 ]
        Description In one of my clusters, observed this situation.
        This issue looks to be due to time out in ResponseProcesser at client side, it is marking first DataNode as bad.
        In one of my clusters, observed this situation.
        This issue looks to be due to time out in ResponseProcesser at client side, it is marking first DataNode as bad.
        This happens in 20.2 version. This can be there in branch-1 as well and will check for trunk.
        Component/s data-node [ 12312927 ]
        Component/s hdfs client [ 12312928 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Uma Maheswara Rao G
          • Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

            • Created:
              Updated:

              Development