Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.10.1
    • Fix Version/s: 0.11.0
    • Component/s: None
    • Labels:
      None

      Description

      A name node should ask a data node to re-register when
      1) the name node restarts; or
      2) the name node receives a heartbeat from an unregistered data node; or
      3) the name node recieves a heartbeat from a data node whose heart beat is lost.

      In response to the re-registration request, the data node sends a register request followed by a block report.

      1. register.patch
        6 kB
        Hairong Kuang

        Issue Links

          Activity

          Hide
          Hadoop QA added a comment -

          -1, because the patch command could not apply the latest attachment (http://issues.apache.org/jira/secure/attachment/12349950/register.patch</a> applied and successfully tested against trunk revision r501249. </div>) as a patch to trunk revision r501616. Please note that this message is automatically generated and may represent a problem with the automation system and not the patch.

          Show
          Hadoop QA added a comment - -1, because the patch command could not apply the latest attachment ( http://issues.apache.org/jira/secure/attachment/12349950/register.patch </a> applied and successfully tested against trunk revision r501249. </div>) as a patch to trunk revision r501616. Please note that this message is automatically generated and may represent a problem with the automation system and not the patch.
          Hide
          Doug Cutting added a comment -

          I just committed this. Thanks, Hairong!

          Show
          Doug Cutting added a comment - I just committed this. Thanks, Hairong!
          Hide
          Hadoop QA added a comment -

          +1, because http://issues.apache.org/jira/secure/attachment/12349950/register.patch applied and successfully tested against trunk revision r501249.

          Show
          Hadoop QA added a comment - +1, because http://issues.apache.org/jira/secure/attachment/12349950/register.patch applied and successfully tested against trunk revision r501249.
          Hide
          Hairong Kuang added a comment -

          Although the patch does not change the format of the datanode protocol, it changes its sematics. So I bumped up its version number.

          Show
          Hairong Kuang added a comment - Although the patch does not change the format of the datanode protocol, it changes its sematics. So I bumped up its version number.
          Hide
          Doug Cutting added a comment -

          Do you think this change to the protocol is entirely back-compatible, or should we also increment the version number of DataNode protocol?

          Show
          Doug Cutting added a comment - Do you think this change to the protocol is entirely back-compatible, or should we also increment the version number of DataNode protocol?
          Hide
          Hadoop QA added a comment -

          +1, because http://issues.apache.org/jira/secure/attachment/12349749/register.patch applied and successfully tested against trunk revision r500415.

          Show
          Hadoop QA added a comment - +1, because http://issues.apache.org/jira/secure/attachment/12349749/register.patch applied and successfully tested against trunk revision r500415.

            People

            • Assignee:
              Hairong Kuang
              Reporter:
              Hairong Kuang
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development