Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/10794#discussion_r57732142
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedClusterMessage.scala
---
@@ -30,6 +30,8 @@ private[spark] object CoarseGrainedClusterMessages {
case object RetrieveSparkProps extends CoarseGrainedClusterMessage
+ case object RetrieveMaxExecutorId extends CoarseGrainedClusterMessage
--- End diff --
we seem to be intermixing current and Max. Max makes me think that this is
some limit so can we change things to be consistent and perhaps use
CurrentExecutorId or LargestAllocated
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
