garage block list-errors
shows errors after cluster layout change and node reboot
I noticed for all four blocks, garage block info $block_id still reports "Error: No matching block found" only if executed on node3. Is this expected to be a node-local command?
Yes, it's a…
garage block list-errors
shows errors after cluster layout change and node reboot
garage block list-errors
shows errors after cluster layout change and node reboot
I think this is mostly normal behavior of Garage, especially given that:
- no data that you stored in the S3 API was lost
- the situation normalized itself after some time
The block errors…
Yes, PRs are welcome. Make sure that the new behavior is well documented in the config file reference page.
garage status
keeps displaying old IP for itself
@vk, I would be interested if you could check if the undesirable behavior disappears in v1.0.0. In theory it should be fixed.
Reading this naively, it looks like we need to do BOTH launch garage server
and create the docker container, which is not the case. Maybe reword with something like:
content-length
on HEAD
object
Does this work correctly on older versions such as 0.9.0 and 0.8.6?
The code should return the size of the object as saved in the object's metadata, bit maybe that information is wrong,…
I'm having a hard time understanding exactly what is the request that your code makes.
Could you rather set your Garage daemon to debug mode (RUST_LOG=garage_api=debug
) and paste the log…