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.

Sign up for GitHub

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

Jump to bottom

Posibility to set our own shardlList for client. #1385

Open
pauldb09 opened this issue Jun 7, 2022 · 2 comments · May be fixed by #1389
Open

Posibility to set our own shardlList for client. #1385

pauldb09 opened this issue Jun 7, 2022 · 2 comments · May be fixed by #1389
Labels
enhancement

Comments

@pauldb09
Copy link

pauldb09 commented Jun 7, 2022

It could be interessting to set our own shard list so we have more controll on the sharding. We could also use different modules and implement clustering
@DonovanDMC
Copy link
Contributor

DonovanDMC commented Jun 7, 2022 •
edited
Loading

The possibility of providing specific shard ids has been planned by a community member, and we've declined to integrate clustering into eris

@DonovanDMC DonovanDMC closed this as not planned Won't fix, can't repro, duplicate, stale Jun 7, 2022
@abalabahaha abalabahaha reopened this Jun 8, 2022
@abalabahaha
Copy link
Owner

We generally don't take suggestions in the form of issues

Errrr yes we do, it helps track things.

@HcgRandon HcgRandon linked a pull request Jun 17, 2022 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(shards): Support Non-Sequential Shard IDs HcgRandon/eris
3 participants
@abalabahaha @DonovanDMC @pauldb09