Hi Ilya,
G'day.
We were seeing the rgw bucket creation failures if application is not enabled for the rgw control pool and ceph status was not reporting the warning message "x pool(s) do not have an application enabled (POOL_APP_NOT_ENABLED)". We also observed the RGW daemon crash in the absence of application was not enabled for the pool. There was no way to know the reason behind RGW bucket creation failure. This issue has been raised on BZ#2029585.
My opinion was that if we create a pool then we must specify the application for the pool even though the pool is not in use to avoid unnecessary creation of the pool.
Let me know your thoughts.
Regards,
Prashant
On Wed, Aug 23, 2023 at 12:52 PM Ilya Dryomov <idryomov@xxxxxxxxx> wrote:
Hello,
What was the motivation for the "issue pool application warning even if
pool is empty" change [1]? This didn't occur to me what I saw the PR, but
it basically makes it impossible to create a pool without HEALTH_WARN
popping up. The reason is that pool creation and pool application
enablement are separate monitor commands: there is no way to create
a pool and enable an application on a pool atomically. And this is why
this health check has always been limited to in-use pools (also pointed
out by Greg when it was being introduced [2]).
[1] https://github.com/ceph/ceph/pull/47560
[2] https://github.com/ceph/ceph/pull/15763#discussion_r123084421
Thanks,
Ilya
_______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
