-
Notifications
You must be signed in to change notification settings - Fork 29.3k
[SPARK-28177][SQL] Adjust post shuffle partition number in adaptive execution #24978
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 3 commits
31756cb
54c8715
6f6bdaf
228ed58
7f0397a
b767977
65ea8f6
27a8180
4b001ca
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -293,27 +293,27 @@ object SQLConf { | |
| .bytesConf(ByteUnit.BYTE) | ||
| .createWithDefault(64 * 1024 * 1024) | ||
|
|
||
| val RUNTIME_REOPTIMIZATION_ENABLED = | ||
| buildConf("spark.sql.runtime.reoptimization.enabled") | ||
| .doc("When true, enable runtime query re-optimization.") | ||
| .booleanConf | ||
| .createWithDefault(false) | ||
|
|
||
| val ADAPTIVE_EXECUTION_ENABLED = buildConf("spark.sql.adaptive.enabled") | ||
| .doc("When true, enable adaptive query execution.") | ||
| .booleanConf | ||
| .createWithDefault(false) | ||
|
|
||
| val SHUFFLE_MIN_NUM_POSTSHUFFLE_PARTITIONS = | ||
| buildConf("spark.sql.adaptive.minNumPostShufflePartitions") | ||
| .internal() | ||
| .doc("The advisory minimal number of post-shuffle partitions provided to " + | ||
| "ExchangeCoordinator. This setting is used in our test to make sure we " + | ||
| "have enough parallelism to expose issues that will not be exposed with a " + | ||
| "single partition. When the value is a non-positive value, this setting will " + | ||
| "not be provided to ExchangeCoordinator.") | ||
| .doc("The advisory minimum number of post-shuffle partitions used in adaptive execution.") | ||
| .intConf | ||
| .createWithDefault(-1) | ||
| .checkValue(_ > 0, "The minimum shuffle partition number " + | ||
| "must be a positive integer.") | ||
| .createWithDefault(1) | ||
|
|
||
| val SHUFFLE_MAX_NUM_POSTSHUFFLE_PARTITIONS = | ||
| buildConf("spark.sql.adaptive.maxNumPostShufflePartitions") | ||
| .doc("The advisory maximum number of post-shuffle partitions used in adaptive execution. " + | ||
| "The by default equals to spark.sql.shuffle.partitions") | ||
| .intConf | ||
| .checkValue(_ > 0, "The maximum shuffle partition number " + | ||
| "must be a positive integer.") | ||
| .createOptional | ||
|
|
||
| val SUBEXPRESSION_ELIMINATION_ENABLED = | ||
| buildConf("spark.sql.subexpressionElimination.enabled") | ||
|
|
@@ -1911,14 +1911,14 @@ class SQLConf extends Serializable with Logging { | |
| def targetPostShuffleInputSize: Long = | ||
| getConf(SHUFFLE_TARGET_POSTSHUFFLE_INPUT_SIZE) | ||
|
|
||
| def runtimeReoptimizationEnabled: Boolean = getConf(RUNTIME_REOPTIMIZATION_ENABLED) | ||
|
|
||
| def adaptiveExecutionEnabled: Boolean = | ||
| getConf(ADAPTIVE_EXECUTION_ENABLED) && !getConf(RUNTIME_REOPTIMIZATION_ENABLED) | ||
| def adaptiveExecutionEnabled: Boolean = getConf(ADAPTIVE_EXECUTION_ENABLED) | ||
|
|
||
| def minNumPostShufflePartitions: Int = | ||
| getConf(SHUFFLE_MIN_NUM_POSTSHUFFLE_PARTITIONS) | ||
|
|
||
| def maxNumPostShufflePartitions: Int = | ||
| getConf(SHUFFLE_MAX_NUM_POSTSHUFFLE_PARTITIONS).getOrElse(numShufflePartitions) | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We may want to set the default value here to something much higher (Int.Max?). The upper bound here is determined by the shuffles for which we are trying to reduce the number of partitions.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We actually use this as the initial shuffle partition number, which will be set in the
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why would we have two confs for adaptive and non-adaptive execution?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. People usually already have tuned |
||
|
|
||
| def minBatchesToRetain: Int = getConf(MIN_BATCHES_TO_RETAIN) | ||
|
|
||
| def maxBatchesToRetainInMemory: Int = getConf(MAX_BATCHES_TO_RETAIN_IN_MEMORY) | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,195 @@ | ||
| /* | ||
| * Licensed to the Apache Software Foundation (ASF) under one or more | ||
| * contributor license agreements. See the NOTICE file distributed with | ||
| * this work for additional information regarding copyright ownership. | ||
| * The ASF licenses this file to You under the Apache License, Version 2.0 | ||
| * (the "License"); you may not use this file except in compliance with | ||
| * the License. You may obtain a copy of the License at | ||
| * | ||
| * http://www.apache.org/licenses/LICENSE-2.0 | ||
| * | ||
| * Unless required by applicable law or agreed to in writing, software | ||
| * distributed under the License is distributed on an "AS IS" BASIS, | ||
| * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
| * See the License for the specific language governing permissions and | ||
| * limitations under the License. | ||
| */ | ||
|
|
||
| package org.apache.spark.sql.execution.adaptive.rule | ||
|
|
||
| import scala.collection.mutable.ArrayBuffer | ||
| import scala.concurrent.duration.Duration | ||
|
|
||
| import org.apache.spark.MapOutputStatistics | ||
| import org.apache.spark.rdd.RDD | ||
| import org.apache.spark.sql.catalyst.InternalRow | ||
| import org.apache.spark.sql.catalyst.expressions.Attribute | ||
| import org.apache.spark.sql.catalyst.plans.physical.{Partitioning, UnknownPartitioning} | ||
| import org.apache.spark.sql.catalyst.rules.Rule | ||
| import org.apache.spark.sql.execution.{ShuffledRowRDD, SparkPlan, UnaryExecNode} | ||
| import org.apache.spark.sql.execution.adaptive.{QueryStageExec, ReusedQueryStageExec, ShuffleQueryStageExec} | ||
| import org.apache.spark.sql.internal.SQLConf | ||
| import org.apache.spark.util.ThreadUtils | ||
|
|
||
| /** | ||
| * A rule to adjust the post shuffle partitions based on the map output statistics. | ||
| * | ||
| * The strategy used to determine the number of post-shuffle partitions is described as follows. | ||
| * To determine the number of post-shuffle partitions, we have a target input size for a | ||
| * post-shuffle partition. Once we have size statistics of all pre-shuffle partitions, we will do | ||
| * a pass of those statistics and pack pre-shuffle partitions with continuous indices to a single | ||
| * post-shuffle partition until adding another pre-shuffle partition would cause the size of a | ||
| * post-shuffle partition to be greater than the target size. | ||
| * | ||
| * For example, we have two stages with the following pre-shuffle partition size statistics: | ||
| * stage 1: [100 MiB, 20 MiB, 100 MiB, 10MiB, 30 MiB] | ||
| * stage 2: [10 MiB, 10 MiB, 70 MiB, 5 MiB, 5 MiB] | ||
| * assuming the target input size is 128 MiB, we will have four post-shuffle partitions, | ||
| * which are: | ||
| * - post-shuffle partition 0: pre-shuffle partition 0 (size 110 MiB) | ||
| * - post-shuffle partition 1: pre-shuffle partition 1 (size 30 MiB) | ||
| * - post-shuffle partition 2: pre-shuffle partition 2 (size 170 MiB) | ||
| * - post-shuffle partition 3: pre-shuffle partition 3 and 4 (size 50 MiB) | ||
| */ | ||
| case class ReduceNumShufflePartitions(conf: SQLConf) extends Rule[SparkPlan] { | ||
|
|
||
| override def apply(plan: SparkPlan): SparkPlan = { | ||
| val shuffleMetrics: Seq[MapOutputStatistics] = plan.collect { | ||
| case stage: ShuffleQueryStageExec => | ||
| val metricsFuture = stage.mapOutputStatisticsFuture | ||
| assert(metricsFuture.isCompleted, "ShuffleQueryStageExec should already be ready") | ||
| ThreadUtils.awaitResult(metricsFuture, Duration.Zero) | ||
| case ReusedQueryStageExec(_, stage: ShuffleQueryStageExec, _) => | ||
| val metricsFuture = stage.mapOutputStatisticsFuture | ||
| assert(metricsFuture.isCompleted, "ShuffleQueryStageExec should already be ready") | ||
| ThreadUtils.awaitResult(metricsFuture, Duration.Zero) | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Here, the shuffle query stage is already ready, why we still call the
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. because we need to get the value from a
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Got it. Thanks for your explanation.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It is a scala Future and |
||
| } | ||
|
|
||
| if (!plan.collectLeaves().forall(_.isInstanceOf[QueryStageExec])) { | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. How about first collecting all the leaves, then checking if they are all
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. +1
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good point!
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. When the leaf node is
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We are ignoring
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We can have situations with BHJ where:
I believe scenario 2 may still be applicable here, so maybe we can change the condition to " isAllQueryStage && shuffleStageCount > 0"?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Obviously we don't want to adjust num shuffle partitions if there is no shuffle in this stage, so +1 to change the condition to
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I believe we are safe here. After checking |
||
| // If not all leaf nodes are query stages, it's not safe to reduce the number of | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Does this mean the case like https://github.com/Intel-bigdata/spark-adaptive/pull/54 ?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, that case is covered. There are many cases the leaves are not query stage, for example in the stage that does a table scan, the leaf is a table scan operator. The comment seems to cover these. |
||
| // shuffle partitions, because we may break the assumption that all children of a spark plan | ||
| // have same number of output partitions. | ||
| plan | ||
| } else { | ||
| // `ShuffleQueryStageExec` gives null mapOutputStatistics when the input RDD has 0 partitions, | ||
| // we should skip it when calculating the `partitionStartIndices`. | ||
| val validMetrics = shuffleMetrics.filter(_ != null) | ||
| if (validMetrics.nonEmpty) { | ||
| val partitionStartIndices = estimatePartitionStartIndices(validMetrics.toArray) | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We may need add a check of whether all the pre-shuffle partitions is same before calling the
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good catch. I'll add the check and the unit test. |
||
| // This transformation adds new nodes, so we must use `transformUp` here. | ||
| plan.transformUp { | ||
| // even for shuffle exchange whose input RDD has 0 partition, we should still update its | ||
| // `partitionStartIndices`, so that all the leaf shuffles in a stage have the same | ||
| // number of output partitions. | ||
| case stage: ShuffleQueryStageExec => | ||
| CoalescedShuffleReaderExec(stage, partitionStartIndices) | ||
| case reused: ReusedQueryStageExec if reused.plan.isInstanceOf[ShuffleQueryStageExec] => | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can we use pattern match here as in other places too?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good idea. |
||
| CoalescedShuffleReaderExec(reused, partitionStartIndices) | ||
| } | ||
| } else { | ||
| plan | ||
| } | ||
| } | ||
| } | ||
|
|
||
| /** | ||
| * Estimates partition start indices for post-shuffle partitions based on | ||
| * mapOutputStatistics provided by all pre-shuffle stages. | ||
| */ | ||
| // visible for testing. | ||
| private[sql] def estimatePartitionStartIndices( | ||
| mapOutputStatistics: Array[MapOutputStatistics]): Array[Int] = { | ||
| val minNumPostShufflePartitions = conf.minNumPostShufflePartitions | ||
| val advisoryTargetPostShuffleInputSize = conf.targetPostShuffleInputSize | ||
| // If minNumPostShufflePartitions is defined, it is possible that we need to use a | ||
| // value less than advisoryTargetPostShuffleInputSize as the target input size of | ||
| // a post shuffle task. | ||
| val totalPostShuffleInputSize = mapOutputStatistics.map(_.bytesByPartitionId.sum).sum | ||
| // The max at here is to make sure that when we have an empty table, we | ||
| // only have a single post-shuffle partition. | ||
| // There is no particular reason that we pick 16. We just need a number to | ||
| // prevent maxPostShuffleInputSize from being set to 0. | ||
| val maxPostShuffleInputSize = math.max( | ||
| math.ceil(totalPostShuffleInputSize / minNumPostShufflePartitions.toDouble).toLong, 16) | ||
| val targetPostShuffleInputSize = | ||
| math.min(maxPostShuffleInputSize, advisoryTargetPostShuffleInputSize) | ||
|
|
||
| logInfo( | ||
| s"advisoryTargetPostShuffleInputSize: $advisoryTargetPostShuffleInputSize, " + | ||
| s"targetPostShuffleInputSize $targetPostShuffleInputSize.") | ||
|
|
||
| // Make sure we do get the same number of pre-shuffle partitions for those stages. | ||
| val distinctNumPreShufflePartitions = | ||
| mapOutputStatistics.map(stats => stats.bytesByPartitionId.length).distinct | ||
| // The reason that we are expecting a single value of the number of pre-shuffle partitions | ||
| // is that when we add Exchanges, we set the number of pre-shuffle partitions | ||
| // (i.e. map output partitions) using a static setting, which is the value of | ||
| // spark.sql.shuffle.partitions. Even if two input RDDs are having different | ||
| // number of partitions, they will have the same number of pre-shuffle partitions | ||
| // (i.e. map output partitions). | ||
| assert( | ||
| distinctNumPreShufflePartitions.length == 1, | ||
| "There should be only one distinct value of the number pre-shuffle partitions " + | ||
| "among registered Exchange operator.") | ||
| val numPreShufflePartitions = distinctNumPreShufflePartitions.head | ||
|
|
||
| val partitionStartIndices = ArrayBuffer[Int]() | ||
| // The first element of partitionStartIndices is always 0. | ||
| partitionStartIndices += 0 | ||
|
|
||
| var postShuffleInputSize = 0L | ||
|
|
||
| var i = 0 | ||
| while (i < numPreShufflePartitions) { | ||
| // We calculate the total size of ith pre-shuffle partitions from all pre-shuffle stages. | ||
| // Then, we add the total size to postShuffleInputSize. | ||
| var nextShuffleInputSize = 0L | ||
| var j = 0 | ||
| while (j < mapOutputStatistics.length) { | ||
| nextShuffleInputSize += mapOutputStatistics(j).bytesByPartitionId(i) | ||
| j += 1 | ||
| } | ||
|
|
||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. =>
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This code was original there in |
||
| // If including the nextShuffleInputSize would exceed the target partition size, then start a | ||
| // new partition. | ||
| if (i > 0 && postShuffleInputSize + nextShuffleInputSize > targetPostShuffleInputSize) { | ||
| partitionStartIndices += i | ||
| // reset postShuffleInputSize. | ||
| postShuffleInputSize = nextShuffleInputSize | ||
| } else { | ||
| postShuffleInputSize += nextShuffleInputSize | ||
| } | ||
|
|
||
| i += 1 | ||
| } | ||
|
|
||
| partitionStartIndices.toArray | ||
| } | ||
| } | ||
|
|
||
| case class CoalescedShuffleReaderExec( | ||
| child: QueryStageExec, | ||
| partitionStartIndices: Array[Int]) extends UnaryExecNode { | ||
|
|
||
| override def output: Seq[Attribute] = child.output | ||
|
|
||
| override def doCanonicalize(): SparkPlan = child.canonicalized | ||
|
|
||
| override def outputPartitioning: Partitioning = { | ||
| UnknownPartitioning(partitionStartIndices.length) | ||
| } | ||
|
|
||
| private var cachedShuffleRDD: ShuffledRowRDD = null | ||
|
|
||
| override protected def doExecute(): RDD[InternalRow] = { | ||
| if (cachedShuffleRDD == null) { | ||
| cachedShuffleRDD = child match { | ||
| case stage: ShuffleQueryStageExec => | ||
| stage.plan.createShuffledRDD(Some(partitionStartIndices)) | ||
| case ReusedQueryStageExec(_, stage: ShuffleQueryStageExec, _) => | ||
| stage.plan.createShuffledRDD(Some(partitionStartIndices)) | ||
| } | ||
| } | ||
| cachedShuffleRDD | ||
| } | ||
| } | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an umbrella config, let's create a new config for
ReduceNumShufflePartitions. How aboutspark.sql.adaptive.reducePostShufflePartitions.enabled?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1. Being a bit pedantic here, but let's try to do orthogonal changes like removing the
RUNTIME_REOPTIMIZATION_ENABLEDflag in separate PRs. That makes the cognitive load of reviewing lower, and it also improves git blame.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree to add a config for
ReduceNumShufflePartitions. I was removingRUNTIME_REOPTIMIZATION_ENABLEDbecauseRUNTIME_REOPTIMIZATION_ENABLEDandADAPTIVE_EXECUTION_ENABLEDlook like the same config now. I didn't see a way to enableReduceNumShufflePartitionsbut disable runtime reoptimization.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The argument of not changing
RUNTIME_REOPTIMIZATION_ENABLEDtoADAPTIVE_EXECUTION_ENABLEDis just to keep this PR independent and smaller.Whatever name it is, we should have an umbrella flag that turns everything off. We could add another flag, though, just to turn off the SMJ -> BHJ runtime optimization, although we might have to do it in a slightly trickier way given that this opt comes naturally with the framework itself.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All right, I will use
RUNTIME_REOPTIMIZATION_ENABLEDas the umbrella flag in this PR.