For replication we don't additionally warn when we get 404s from the object server.
The request is logged by the object server, so you could easily track replicator requests that end with 404.
I'd say it's not optimal to get 404s, but it's certainly not "unexpected".
Every time someone changes their storage, we'll just fill up the logs with these until reconstruction stabilizes.
For replication we don't additionally warn when we get 404s from the object server.
The request is logged by the object server, so you could easily track replicator requests that end with 404.
I'd say it's not optimal to get 404s, but it's certainly not "unexpected".
Every time someone changes their storage, we'll just fill up the logs with these until reconstruction stabilizes.