[RFC] Move multi-actors-per-process feature to a separate util lib
See original GitHub issueFor the purposes of:
- Improving some API’s semantics which based on one actor per process, such as kill(actor)…
- Clearing the gap and redundant codepath of PG and actors scheduling between Python and Java.
- Addressing other potential risks since the feature flag is off in opensource codebase currently.
- Speeding up the process to opensource gcs scheduling.
- Improving actor isolation.
We’d like to remove all code path of multi-actors-per-process and have not been support the feature. As an alternate, we’d like to support another parallel execution model based on concurrency group, which is as a separate util library of commonlibs. The new util is on the top of actor, hence it won‘t break the assumption of one actor per process
.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Track items of Removal about multiple core workers in one ...
Use case ; [RFC] Move multi-actors-per-process feature to a separate util lib #21547. Closed ; [Java] Remove RayRuntimeInternal class #25016.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
DONE
The plan should be:
num-java-workers-per-process
on 2.0 branch only. Because this is a huge breakage behavior. #24147