New nodes not used as storage nodes #698
Labels
No Label
AdminAPI
Bug
Check AWS
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#698
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Hi, I'm using garage as nextcloud storage and I start receiving 500 errors from the S3 API. I suspect it is due to insufficient free memory, as two nodes are full. Why are the other two free nodes not used as storage nodes? I have noticed before that only two nodes are used as storage nodes and I had the assumption that further nodes are only listed when data is actually stored on them. Unfortunately, I couldn't find anything about this in the documentation.
All nodes were assigned with the following command:
garage layout assign -c 150 -z <ZONE> <ID>
Kind regards
Tim
Hello @en0x , a first thing that stands out is that you shouldn't be using "150" as a capacity value, you should be using "150G" for "150 gigabytes", otherwise Garage will interpret it as "150 bytes".
Once you fix all your capacities to "150G", can you post the output of
garage layout show
before applying, and then after?Hello @lx , I tried
garage layout assign -c 150G -z fra1 d70bff9518aa1107 b2493052b3061fdd a13dc7533ad626bb 07531a39050119af
and
garage layout assign -c "150G" -z fra1 d70bff9518aa1107 b2493052b3061fdd a13dc7533ad626bb 07531a39050119af
but both return
error: Invalid value for '--capacity <capacity>': invalid digit found in string
Was this changed in a version newer than 0.8.2? Because the
garage status
in my initial post shows the 150 correct as GB.Sorry, I had not seen that you were using a v0.8. The layout algorithm in that version is broken, which probably explains the issues you are having. You should upgrade to v0.9 if possible.
Yes, the update to v0.9.1 fixed the issue. After applying the new layout the data was rebalanced. Thanks for your help.