Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-36700

BlockManager re-registration is broken due to deferred removal of BlockManager

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 3.0.3, 3.1.2, 3.2.0, 3.3.0
    • Fix Version/s: 3.2.0, 3.1.3, 3.0.4, 3.3.0
    • Component/s: Spark Core
    • Labels:
      None

      Description

      Due to the deferred removal of BlockManager (introduced in SPARK-35011), an expected BlockManager re-registration could be refused as the inactive BlockManager still exists in the map `blockManagerInfo`:

      https://github.com/apache/spark/blob/9cefde8db373a3433b7e3ce328e4a2ce83b1aca2/core/src/main/scala/org/apache/spark/storage/BlockManagerMasterEndpoint.scala#L551

        Attachments

          Activity

            People

            • Assignee:
              Ngone51 wuyi
              Reporter:
              Ngone51 wuyi
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: