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
Signed-off-by: Ahmed Hussein (amahussein) <a@ahussein.me>
FixesNVIDIA#1550
For dataproc GPU clusters, the Autotuner should set the following 2
properties to false. In addition, the autotuner appends a comment to
warn the user that those properties might be problematic to the GPU run.
- "spark.dataproc.enhanced.optimizer.enabled": "false"
- "spark.dataproc.enhanced.execution.enabled": "false"
The autotuner output will add a message stating that:
"should be disabled. WARN: Turning this property on might case the GPU
accelerated Dataproc cluster to hang."
Signed-off-by: Ahmed Hussein (amahussein) <a@ahussein.me>
Fixes#1550
For dataproc GPU clusters, the Autotuner should set the following 2
properties to false. In addition, the autotuner appends a comment to
warn the user that those properties might be problematic to the GPU run.
- "spark.dataproc.enhanced.optimizer.enabled": "false"
- "spark.dataproc.enhanced.execution.enabled": "false"
The autotuner output will add a message stating that:
"should be disabled. WARN: Turning this property on might case the GPU
accelerated Dataproc cluster to hang."
Describe the bug
After we merged #1539
GPU clusters had problems after setting those two properties.
We either need to disable those two properties or explicitly set them to false until we investigate them on GPUs.
The text was updated successfully, but these errors were encountered: