-
Notifications
You must be signed in to change notification settings - Fork 56
Run LocalBackend on multiple nodes with :peer
#69
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
base: main
Are you sure you want to change the base?
Run LocalBackend on multiple nodes with :peer
#69
Conversation
|
As per #79 (comment) what are the requirements for this to be merged? |
|
This is something we would like to be in, as far as I know. So once it is ready for review, one of FLAME maintainers will review when they have time available. |
|
@lorrrrrrrenzo are you still active on Github? Wanted to know if it's ok to salvage for review. |
|
Hello @fire. Yes, I'm still active on GH and would prefer to keep this PR. I think the most helpful thing would be to clone it and check whether the behavior conforms to what you expect and need from the tool. Once I get a moment to review this, I'll upgrade it to a proper PR for review by the core team. Happy to collaborate. |
|
I'm interested in getting this across the line for a work project, so please let me know if there's anything I can do. In the meantime, I will do as @lorrrrrrrenzo suggested and clone the changes to test it out myself and report back! |
Per issue #3 we use Erlang's
:peerpackage to start anothererlprocess, enabling local FLAME workers to run code distinct from the parent process.