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

ExternalShuffleBlockResolver should not block shuffle managers by name.

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.3.2
    • Fix Version/s: None
    • Component/s: Shuffle
    • Labels:
      None

      Description

      We configure a shuffle manager that is compatible with the original Spark shuffle manager (but with other network/storage implementation) in our environment.  It doesn't require any modification to Spark source code and It works fine until we enable dynamic allocation.  The problem is that in ExternalShuffleBlockResolver class it checks the name of the shuffle manager class and raise an UnsupportedOperationException if shuffle manager is not SortShuffleManager or UnsafeShuffleManager.
      Since shuffle manager is totally configurable, I think user should be able to decide which shuffle manager to use when dynamic allocation is enabled.
      Maybe we could change UnsupportedOperationException to a warning log telling user that the shuffle manager they are using may not be compatible with dynamic allocation and give them detail reasons why. On the other hand, user may still choose to use their own shuffle manager while knowing the risk behind it.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              jealous Peiyu Zhuang
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: