-
Notifications
You must be signed in to change notification settings - Fork 56
Improve ray actors resilience #195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
be47828
119dfcf
897e487
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -314,6 +314,7 @@ The following environment variables control Ray's logging behavior, task retry s | |
| | `RAY_ENABLE_RECORD_ACTOR_TASK_LOGGING` | `number` | `1` | Enables logs at task level in the Ray dashboard for better debugging and monitoring. | | ||
| | `RAY_task_retry_delay_ms` | `number` | `3000` | Delay (in milliseconds) before retrying a failed task. Controls the wait time between retry attempts. | | ||
| | `RAY_ENABLE_UV_RUN_RUNTIME_ENV` | `number` | `0` | Controls UV runtime environment integration. **Critical**: Must be set to `0` when using the newest version of UV to avoid compatibility issues. | | ||
| |`RAY_memory_monitor_refresh_ms`| `number` | 250 ms | To control the frequency of memory usage checks and task or actor termination if needed. If you set this value to 0, task killing is disabled. | | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can you make it in all capitalized letter? So be consistant with the other config variables (except for RAY_task_retry_delay_ms , that should be eventually changed as well)
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Also, I don't see how this env var is used?
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
It's an innate RAY variable so we don't have control over the naming. I didn't used anywhere in my code; i documented it here cause according to the RAY documentation it can help with memory issues for example disable actor killing.
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I find it a bit weird to add vars from external lib just to document it exists, but I don't have a strong opposition |
||
|
|
||
| #### Indexer Configuration | ||
|
|
||
|
|
@@ -330,6 +331,7 @@ Controls the maximum number of concurrent operations for different indexer tasks | |
| |----------|------|---------|-------------| | ||
| | `INDEXER_DEFAULT_CONCURRENCY` | int | 1000 | Default concurrency limit for general operations | | ||
| | `INDEXER_UPDATE_CONCURRENCY` | int | 100 | Maximum concurrent document update operations | | ||
| | `INDEXER_SERIALIZE_CONCURRENCY` | int | 50 | Maximum concurrent serialization operations | | ||
| | `INDEXER_SEARCH_CONCURRENCY` | int | 100 | Maximum concurrent search/retrieval operations | | ||
| | `INDEXER_DELETE_CONCURRENCY` | int | 100 | Maximum concurrent document deletion operations | | ||
| | `INDEXER_CHUNK_CONCURRENCY` | int | 1000 | Maximum concurrent document chunking operations | | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.