rgw/bucket-logging: support EC pools#65900
Conversation
655c5cc to
07d68e1
Compare
|
@yuvalif , please take a look at the approach and let me know what you think. Pending tasks:
|
07d68e1 to
a77a07d
Compare
|
Pending tasks:
|
9192f62 to
44c07a6
Compare
|
Please select a line under the Tracker section of the checklist. |
01997e0 to
defee46
Compare
a6c7445 to
490c4fe
Compare
490c4fe to
fa10b55
Compare
Log buckets can now be created within erasure-coded (EC) pools. To support append operations, a temporary log record object is initially created in the replicated default.rgw.log pool. This object is then copied to the EC pool upon log record commitment. All implicit log commit operations will execute asynchronously. A new BucketLoggingManager class is responsible for processing these pending commits at set intervals. Explicit commit operations, however, will continue to be performed synchronously. Fixes: https://tracker.ceph.com/issues/71365 Signed-off-by: Nithya Balachandran <nithya.balachandran@ibm.com>
Run the rgw bucket logging teuthology tests on an erasure coded pool. Signed-off-by: Nithya Balachandran <nithya.balachandran@ibm.com>
fa10b55 to
cb825ef
Compare
|
jenkins test submodules |
|
followup work (to be done in other PRs):
|
|
bucket logging tests are passing: https://pulpito.ceph.com/nithyab-2025-12-01_15:29:39-rgw:bucket-logging-wip-nbalacha-71365-distro-default-smithi/
|
|
This is an automated message by src/script/redmine-upkeep.py. I found one or more
The referenced tickets are: Those tickets do not reference this merged Pull Request. If this Pull Request merge resolves any of those tickets, please update the "Pull Request ID" field on each ticket. A future run of this script will appropriately update them. Update Log: https://github.com/ceph/ceph/actions/runs/19858758035 |
Log buckets can now be created within erasure-coded (EC) pools.
To support append operations, a temporary log record object is initially
created in the replicated default.rgw.log pool. This object is then copied
to the EC pool upon log record commitment.
All implicit log commit operations will execute asynchronously. A new
BucketLoggingManager class is responsible for processing these pending
commits at set intervals. Explicit commit operations, however, will
continue to be performed synchronously.
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an
xbetween the brackets:[x]. Spaces and capitalization matter when checking off items this way.Checklist
Show available Jenkins commands
jenkins test classic perfJenkins Job | Jenkins Job Definitionjenkins test crimson perfJenkins Job | Jenkins Job Definitionjenkins test signedJenkins Job | Jenkins Job Definitionjenkins test make checkJenkins Job | Jenkins Job Definitionjenkins test make check arm64Jenkins Job | Jenkins Job Definitionjenkins test submodulesJenkins Job | Jenkins Job Definitionjenkins test dashboardJenkins Job | Jenkins Job Definitionjenkins test dashboard cephadmJenkins Job | Jenkins Job Definitionjenkins test apiJenkins Job | Jenkins Job Definitionjenkins test docsReadTheDocs | Github Workflow Definitionjenkins test ceph-volume allJenkins Jobs | Jenkins Jobs Definitionjenkins test windowsJenkins Job | Jenkins Job Definitionjenkins test rook e2eJenkins Job | Jenkins Job DefinitionYou must only issue one Jenkins command per-comment. Jenkins does not understand
comments with more than one command.