allan bailey

Could workers just read from a queue and not be attached to a specific primary?

> additionally, the mounted logs never produce. Looking at the docker compose, we're not teeing the log output to a file, perhaps that's why? the logs are going to stdout/stderr...

Is this still a problem? The initial reported error seems to have been related to disk issues. Did you try `docker compose down -v` to delete the volumes before bringing...

Could workers just read from a queue and not be attached to a specific primary?

It seems to me that somehow the 'size' spec is being ignored for the default value of '10Gi'. I have not yet found a way to override that.