Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
Elixir
-
None
-
None
-
7.5.0-3081
-
Untriaged
-
-
1
-
Unknown
Description
When a rebalance being triggered immediately after the bucket creation which is trying to load sample data, sample data loading for that bucket fails.
Steps to reproduce:
- Create 10 databases with a pause of 1sec between each database creation.
- Create another database and immediately trigger rebalance by let's say updating the width for any existing database or set balance=False by changing weights.
Attachments
Activity
James Lee why do we need to update the bucket?
Ah, I should remember which MBs I've created. Yes, we do already plan to remove this functionality for Elixir (MB-54268) so this issue will disappear with that.
I would still like to see what Steve says about the endpoints when getting 503 status though as this would apply to 'cbimport' and 'cbbackpumgr restore' in other use-cases; I'd be good to see if we could make them more resilient in general.
Sorry James Lee I didn't see your prior update. An update to a bucket via the REST endpoint should be idempotent. Otherwise the bucket might be left in some unknown, inconsistent state.
That's perfect, thanks Steve Watanabe I'll get that updated in MB-54325.
Marking this issue as a duplicate of MB-54268 since we'll be removing the functionality to modify the bucket for Elixir in that ticket.
On our end, things are behaving as defined (although perhaps not as desired).
2022-10-19T22:41:22.072+00:00 WARN: (REST) (Attempt 1) (POST) Request to endpoint '/pools/default/buckets/volumetestbucket-3-xk5r37' failed with status code 503 -- logging.(*ToolsCommonLogger).Log() at tools_common.go:28We're failing to perform a POST with a 503 (service unavailable). Our REST client is correctly not retrying this request because POST requests aren't idempotent (as they can have side-effects).
Steve Watanabe are POST requests for bucket update idempotent (e.g. we could force retries on our end)?