Description
Probably affects older versions too. The following REST API returns a 200 status code even though the bucket does not exist on this node. This is arguably misleading, and results in us making a request that gets as far as the stats_reader code which eventually returns this error when it cannot find a corresponding gen_server:
[stats:error,2024-04-16T15:18:03.861+01:00,n_1@127.0.0.1:<0.5815.0>:stats_reader:log_bad_responses:260]Some nodes didn't respond: ['n_1@127.0.0.1']
|