On Fri, 2018-08-03 at 13:53 -0400, David Turner wrote:
> I came across you mentioning bucket check --fix before, but I totally
> forgot that I should be passing --bucket=mybucket with the command to
> actually do anything. I'm running this now and it seems to actually
> be doing something. My
I came across you mentioning bucket check --fix before, but I totally
forgot that I should be passing --bucket=mybucket with the command to
actually do anything. I'm running this now and it seems to actually be
doing something. My guess was that it was stuck in the state and now that
I can clean
Oh, also -- one thing that might work is running bucket check --fix on
the bucket. That should overwrite the reshard status field in the
bucket index.
Let me know if it happens to fix the issue for you.
Yehuda.
On Fri, Aug 3, 2018 at 9:46 AM, Yehuda Sadeh-Weinraub wrote:
> Is it actually
Is it actually resharding, or is it just stuck in that state?
On Fri, Aug 3, 2018 at 7:55 AM, David Turner wrote:
> I am currently unable to write any data to this bucket in this current
> state. Does anyone have any ideas for reverting to the original index
> shards and cancel the reshard
I am currently unable to write any data to this bucket in this current
state. Does anyone have any ideas for reverting to the original index
shards and cancel the reshard processes happening to the bucket?
On Thu, Aug 2, 2018 at 12:32 PM David Turner wrote:
> I upgraded my last cluster to
I upgraded my last cluster to Luminous last night. It had some very large
bucket indexes on Jewel which caused a couple problems with the upgrade,
but finally everything finished and we made it to the other side, but now
I'm having problems with [1] these errors populating a lot of our RGW logs
