P2P Multiprocess Phase One [POC] #1161
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
glevco
force-pushed
the
glevco/p2p-mp-poc-2
branch
5 times, most recently
from
df2f44e to
bcab73b
Compare
glevco
force-pushed
the
glevco/p2p-mp-poc-2
branch
from
bcab73b to
5278c51
Compare
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the POC for the P2P Multiprocess Phase One project. For more information, read the RFC.
This is a working version that is able to perform a sync while running P2P components in a single separate subprocess. Run
poetry run hathor-cli run_node --testnet --data ./to verify it. Check that the full node responds to an API call to/v1a/versionin parallel to syncing, without being blocked.There are a few limitations, being a POC:
/v1a/status.