You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Currently the logic for calculating the number of nodes used on a YARN cluster only looks at the active executors. This is an ok approximation but with dynamic allocation this number could change a lot over the lifetime of an application.
Our logic:
val activeExecInfo = executorIdToInfo.values.collect {
case execInfo if execInfo.isActive => (execInfo.host, execInfo.totalCores)
}
activeHosts.toSet.size
We should be looking at the maximum number of executor going at any point in time and then calculating the number of nodes needed.
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently the logic for calculating the number of nodes used on a YARN cluster only looks at the active executors. This is an ok approximation but with dynamic allocation this number could change a lot over the lifetime of an application.
Our logic:
We should be looking at the maximum number of executor going at any point in time and then calculating the number of nodes needed.
The text was updated successfully, but these errors were encountered: