Sure
Can we get a backport and start testing today?
On Mon, Apr 18, 2022 at 10:30 AM Cory Snyder <csnyder@xxxxxxxxx> wrote:
Hey Yuri,
We were hoping to get the following fix merged and backported before
the next pacific release:
https://github.com/ceph/ceph/pull/45904
There is a bug in current versions of Pacific that prevents dynamic
RGW bucket resharding from working on versioned buckets [1]. That bug
was fixed and is included in the changes staged for 16.2.8. An upgrade
to 16.2.8 could be painful for some RGW users if the aforementioned
fix isn't included, because dynamic resharding will start working
again, and could create exceptionally large range deletion tombstones.
Without this fix, large range deletion tombstones can have
catastrophic effects on cluster throughput under some workloads.
Is it still possible to include it at this point?
[1] https://tracker.ceph.com/issues/51429
Thanks,
Cory
On Mon, Apr 18, 2022 at 12:03 PM Yuri Weinstein <yweinste@xxxxxxxxxx> wrote:
>
> We merged all PRs known to be included into the next pacific and are ready to merge the repo later today and start QE validation.
>
> Thx
> YuriW
>
> On Thu, Mar 31, 2022 at 3:51 AM Ilya Dryomov <idryomov@xxxxxxxxx> wrote:
>>
>> On Thu, Mar 31, 2022 at 12:15 AM Yuri Weinstein <yweinste@xxxxxxxxxx> wrote:
>> >
>> > We tested and merged many PRs in the last week and again want to start testing the next pacific ASAP.
>> >
>> > I see no new issues in the queue (is:open is:pr milestone:pacific label:needs-qa)
>> >
>> > Please let me know what is still planned, otherwise, the repo will be locked and we will start QE validation.
>>
>> For RBD:
>>
>> - https://github.com/ceph/ceph/pull/45638
>> labeled with wip-yuri2-testing, should be OK to merge once that
>> branch goes through
>>
>> - https://github.com/ceph/ceph/pull/45184
>> already tested but can't be merged yet due to a unit test issue,
>> Chris is looking into it
>>
>> Thanks,
>>
>> Ilya
>>
> _______________________________________________
> Dev mailing list -- dev@xxxxxxx
> To unsubscribe send an email to dev-leave@xxxxxxx
_______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
