Even when there are enough other nodes available that can easily take the data
Garage partition allocation is static, so it cannot "reroute" files to other nodes dynamically, it would need a…
Garage 1.0.1 will definitely help with the layout issue you quoted above, an maybe as well with metadata performance depending on how much memory you have and how big your LMDB database is. So…
@Szetty can you give me the resync queue on garage node 6 and 7 between dec 18th and today? With the Y axis scaled to the graph (not set at zero, I want to see the variations). But my initial…
Nice! I'll take a look at the PR but if there is no breaking changes we should be good to go!
Sorry I somehow missed your last message, can you share a screenshot of the garage grafana dashboard if you have it setup? I'm especially interested on the evolution of the "Resync queue length"…
Replication set at 2 and 4 gateway would work, although it would not be ideal because if you want strong consistency, you'll need both nodes to be up, hence the recommandation to have at least 3…
@vk same as for github, you need to "fork" the repo under your own user, and push your code in a branch of your repo. You'll then be able to request a PR.
Garage does not have a central coordinator, and hence doesn't have a sense of "progress" at a cluster level for things such as layout migrations. The best way to monitor it is to setup [monitoring]…
Hello,
Thanks for considering Garage. A garage cluster can have "gateway" nodes that will not store data. But usually three data nodes is what we advice, and you seem to only have two. Are…
What is the version of garage you are using? Can you share what your garage status and layout look like? Can you also share the state of the works on a couple of nodes? Did you update the…
I would strongly encourage you at this cluster size to have the metadata on SSD (or metadata and data). Especially if you don't have enough RAM to keep around the data in the metadata database. I…
Based on your informations above I would say that garage is stalling because the disk is simply too slow to handle your cluster size. Could you get some telemetry from the OS to confirm that?…
Layout avant mise à jour :
[root@df-ykl:~]# docker exec -it 0bc65f9b208e /garage layout show
2024-11-28T21:05:45.674060Z INFO garage_net::netapp: Connected to [2a02:a03f:6510:5102:6e4b:9…
Vu les besoins en terme de latence qui doivent être relativement faible, je pense qu'il n'y a aucun prérequis à avoir woodpecker qui utilise forcément un postgres local.