From 4e64e045a2e61e2a5dbc5065b0cee2f50e0f2a2d Mon Sep 17 00:00:00 2001 From: Anirban Pal Date: Thu, 31 Oct 2024 04:49:07 +0700 Subject: [PATCH] updated formatting of tasks.rst --- .../concepts/main_concepts/tasks.rst | 22 +++++++++---------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/docs/user_guide/concepts/main_concepts/tasks.rst b/docs/user_guide/concepts/main_concepts/tasks.rst index 035957587ee..90d3e1f750d 100644 --- a/docs/user_guide/concepts/main_concepts/tasks.rst +++ b/docs/user_guide/concepts/main_concepts/tasks.rst @@ -133,26 +133,26 @@ Tasks can define a retry strategy to handle different types of failures: - Network issues - Service unavailability - Hardware failures - - *Important*: When running on spot/interruptible instances, preemptions count against the system retry budget, not the user retry budget. The last retry attempt automatically runs on a non-preemptible instance to ensure task completion. -2. **User Retries**: Specified in the `@task` decorator (via `retries` parameter), used for: +*Important*: When running on spot/interruptible instances, preemptions count against the system retry budget, not the user retry budget. The last retry attempt automatically runs on a non-preemptible instance to ensure task completion. + +2. **User Retries**: Specified in the ``@task`` decorator (via ``retries`` parameter), used for: - Application-level errors - Invalid input handling - Business logic failures -```python -@task(retries=3) # Sets user retry budget to 3 -def my_task() -> None: - ... -``` +.. code-block:: python + + @task(retries=3) # Sets user retry budget to 3 + def my_task() -> None: + ... ### Alternative Retry Behavior -Starting with from 1.10.0, Flyte offers a simplified retry behavior where both system and user retries count towards a single retry budget defined in the task decorator. To enable this: +Starting from 1.10.0, Flyte offers a simplified retry behavior where both system and user retries count towards a single retry budget defined in the task decorator. To enable this: -1. Set `configmap.core.propeller.node-config.ignore-retry-cause` to `true` in helm values +1. Set ``configmap.core.propeller.node-config.ignore-retry-cause`` to ``true`` in helm values 2. Define retries in the task decorator to set the total retry budget 3. The last retries will automatically run on non-spot instances -This provides a simpler, more predictable retry behavior while maintaining reliability. \ No newline at end of file +This provides a simpler, more predictable retry behavior while maintaining reliability. \ No newline at end of file