Shut down FDB on dev
#2166
Merged
Shut down FDB on dev
#2166
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
Shut down FDB cluster in dev now that it is not used for the write path due to memory issues. Remove dependant services lik its dhstore. Remove corresponding indexers from the assigner. Assigner will have no indexers in its pool but it will continue to propagate requests over gossipsub which get picked up by ago since ago is peered to the assigner.
willscott
approved these changes
Jul 27, 2023
gammazero
approved these changes
Jul 27, 2023
I know.. we can revert this PR to bring it all back. No point keeping dead code in the repo |
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.
Shut down FDB cluster in dev now that it is not used for the write path due to memory issues. Remove dependant services lik its dhstore. Remove corresponding indexers from the assigner.
Assigner will have no indexers in its pool but it will continue to propagate requests over gossipsub which get picked up by ago since ago is peered to the assigner.