Skip to content
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

[Epic: Status] Sharding peer management and discovery hardening #1231

Closed
3 tasks done
Tracked by #172
chair28980 opened this issue Jun 18, 2024 · 5 comments
Closed
3 tasks done
Tracked by #172

[Epic: Status] Sharding peer management and discovery hardening #1231

chair28980 opened this issue Jun 18, 2024 · 5 comments
Assignees
Labels
epic Tracks a yearly team epic (only for waku-org/pm repo)

Comments

@chair28980
Copy link
Contributor

chair28980 commented Jun 18, 2024

@chaitanyaprem
Copy link
Collaborator

status-im/status-go#5171 may not be needed to be part of this deliverable.
Since to achieve static sharding of communities with 100 shards , the existing fleet (maybe additional nodes) is going to support all shards (100 + 2 common) along with store nodes in the fleet.

@fryorcraken can you confirm?

@fryorcraken
Copy link
Collaborator

status-im/status-go#5171 may not be needed to be part of this deliverable. Since to achieve static sharding of communities with 100 shards , the existing fleet (maybe additional nodes) is going to support all shards (100 + 2 common) along with store nodes in the fleet.

@fryorcraken can you confirm?

Correct.

Fo rMilestone Static Sharding - dedicated shards we assume up to 100 shards/communities, all hosted by Status. Hence no need to remove hardcoding of store node.

Removal of hardcoding would be needed for Milestone Scale up number of Communities](https://github.com/waku-org/pm/milestone/32) but we have not yet scheduled this milestone.

@chaitanyaprem
Copy link
Collaborator

removed #1156 as per #1156 (comment)

@chaitanyaprem
Copy link
Collaborator

Nothing else pending in this milestone , so we can close it.

cc @chair28980 @fryorcraken

@fryorcraken
Copy link
Collaborator

Epics can be closed by CC or leads

@chair28980 chair28980 transferred this issue from waku-org/pm Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Tracks a yearly team epic (only for waku-org/pm repo)
Projects
Status: Done
Development

No branches or pull requests

4 participants