Hi Anthony,
Looking at the linked issue it appears that the 503 response can be
returned erroneously when communication between a Riak CS and Riak
node has an error ("If the first member of the preflist is down").
Is there anything predictable about these errors? You say they come
from 1 client o
We are having a lot of 503 Service Unvailable errors for 1 particular
application client(s) when connecting to Riak-CS. Everything looks fine in
Riak/Riak-CS and when I check the Riak-CS access logs, I can see access from
other applications to other buckets before, during and after the reported
