Is there any risk in using Garage at a large scale? #812
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#812
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Is there any risk in using Garage at a large scale? Currently, I'm using Garage to manage 5 servers node, each with 1TB of data per node, and haven't encountered any issues. However, I'm planning to use Garage to manage 300 servers node, each with around 22 disks totaling about 250TB capacity per server node. The data will be replication_factor =2, and there will be a large number of 4k small files. Can Garage support such a large scale? What are the potential risks?
There's a max node limit right now of 256:
pub const MAX_NODE_NUMBER: usize = 256;Besides that; there's risk involved with everything in life - you'll have to test the deployment at a small scale, test your workload, gather metrics, and evaluate and repeat with larger scale.