Skip to content

Commit 4c6b30c

Browse files
jiangzhodongjoon-hyun
authored andcommitted
[SPARK-52774] Fix resourceRetentionPolicy typo to resourceRetainPolicy in docs
### What changes were proposed in this pull request? This fixes typo in docs regarding resourceRetainPolicy ### Why are the changes needed? For docs sanity ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? pass CIs ### Was this patch authored or co-authored using generative AI tooling? No Closes apache#284 from jiangzho/typofix. Authored-by: Zhou JIANG <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
1 parent 198e3c8 commit 4c6b30c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/spark_custom_resources.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -289,11 +289,11 @@ On the other hand, when developing an application, it's possible to configure
289289
```yaml
290290
applicationTolerations:
291291
# Acceptable values are 'Always', 'OnFailure', 'Never'
292-
resourceRetentionPolicy: OnFailure
292+
resourceRetainPolicy: OnFailure
293293
```
294294

295295
to avoid operator attempt to delete driver pod and driver resources if app fails. Similarly,
296-
if resourceRetentionPolicy is set to `Always`, operator would not delete driver resources
296+
if resourceRetainPolicy is set to `Always`, operator would not delete driver resources
297297
when app ends. Note that this applies only to operator-created resources (driver pod, SparkConf
298298
configmap .etc). You may also want to tune `spark.kubernetes.driver.service.deleteOnTermination`
299299
and `spark.kubernetes.executor.deleteOnTermination` to control the behavior of driver-created

0 commit comments

Comments
 (0)