From 8787a0ac384e77b9cc785d978283c08e97c1be43 Mon Sep 17 00:00:00 2001 From: Sameer Raheja Date: Wed, 29 Jul 2020 22:18:08 -0700 Subject: [PATCH] fix broken link Signed-off-by: Sameer Raheja --- docs/get-started/getting-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/get-started/getting-started.md b/docs/get-started/getting-started.md index ed80cbf50ac..e3b3b6907c7 100644 --- a/docs/get-started/getting-started.md +++ b/docs/get-started/getting-started.md @@ -497,7 +497,7 @@ file. To make sure your hs_err_pid.log file goes into the YARN application log d the config: `--conf spark.executor.extraJavaOptions="-XX:ErrorFile=/hs_err_pid_%p.log"` If you want to see why an operation did not run on the GPU you can turn on the configuration: -[`--conf spark.rapids.sql.explain=NOT_ON_GPU`](configs.md#sql.explain). A log message will then +[`--conf spark.rapids.sql.explain=NOT_ON_GPU`](../configs.md#sql.explain). A log message will then be emitted to the driver log as to why a Spark operation is not able to run on the GPU. ## Out of GPU Memory