| Commit message (Collapse) | Author | Files | Lines |
|---|
|
Edit the seventh and final section of
doc/cephfs/disaster-recovery-experts.rst in preparation for adding
deeper explanations of the contexts in which one should use the various
commands listed on that page.
The section edited in this commit is
* Using an alternate metadata pool for recovery
A future commit might beneficially put this section into the format of
an ordered list. If so, such a commit should only reformat the
content and should not make any changes to the English. It's enough to
verify content or format. Let's not overload our editorial faculties by
forcing ourselves to walk and chew gum at the same time.
Follows https://github.com/ceph/ceph/pull/61442
https://tracker.ceph.com/issues/69557
Signed-off-by: Zac Dover <zac.dover@proton.me>
|
|
Signed-off-by: Ali Masarwa <amasarwa@redhat.com>
|
|
Edit the fifth and sixth sections of
doc/cephfs/disaster-recovery-experts.rst in preparation for adding
deeper explanations of the contexts in which one should use the various
commands listed on that page.
The sections edited in this commit are
- MDS Map Reset
- Recovery From Mission Metadata Objects
Follows https://github.com/ceph/ceph/pull/61427
https://tracker.ceph.com/issues/69557
Signed-off-by: Zac Dover <zac.dover@proton.me>
|
|
With commit#8c025045332a8005c6e82308fc17a33d38058734, changes
were made to call put_info while erasing bucket attrs. But
DBStore wasn't updating attrs as part of put_info operation.
This commit addresses the same.
Signed-off-by: Soumya Koduri <skoduri@redhat.com>
|
|
Properly wrap a poorly-formatted paragraph that looks just awful in an
80-column viewport and change MDS to "MDS daemons" where the latter
makes the sentence a lot clearer.
Signed-off-by: Zac Dover <zac.dover@proton.me>
|
|
These changes improve the robustness and reliability of Lua script execution in the RADOS Gateway by enforcing configurable limit on execution time.
- Enhanced `lua_state_guard` to support configurable runtime limits for Lua scripts.
- Updated rgw.yaml.in to include new configuration options for Lua runtime limits.
- Added tests in `test_rgw_lua.cc` to verify Lua script execution with different runtime constraints.
- Updated Lua scripting documentation to reflect the new runtime limit configuration.
Signed-off-by: Oshry Avraham <oshryabiz@gmail.com>
|
|
Edit the third and fourth sections of
doc/cephfs/disaster-recovery-experts.rst in preparation for adding
deeper explanations of the contexts in which one should use the various
commands listed on that page.
Follows https://github.com/ceph/ceph/pull/61426
https://tracker.ceph.com/issues/69557
Co-authored-by: Anthony D'Atri <anthony.datri@gmail.com>
Signed-off-by: Zac Dover <zac.dover@proton.me>
|
|
Even though we opt in right away after upgrading, which minimizes the chance
of this warning coming up, the cluster log still detects it sometimes and
fails the test. So, we can ignore it since it's expected for the warning
to come up for a few seconds in some cases.
Signed-off-by: Laura Flores <lflores@ibm.com>
|
|
1. For the telemetry upgrade tests, we want to
make sure we enable the perf channel before we
upgrade to test that out.
2. We also want to be sure to set up ident information.
in the workunits used before the upgrade.
3. We can remove the "opt out" commands in the before-upgrade
workunits since we want to stay opted in during the upgrade.
We only opt out after all the checks are complete.
4. We mistakenly test "ceph telemetry show" twice when one
of then should be "ceph telemetry show-all".
Signed-off-by: Laura Flores <lflores@ibm.com>
|
|
Rephrase the balancer-related warning issued to people upgrading to
Ceph 19.2.0.
Follows https://github.com/ceph/ceph/pull/61429
Co-authored-by: Anthony D'Atri <anthony.datri@gmail.com>
Signed-off-by: Zac Dover <zac.dover@proton.me>
|
|
Since main is now pre-Tentacle, we should replace the quincy upgrade
path with squid.
I have kept the quincy workunits since they are still
referenced in the overall upgrade suite. I will remove these
in a separate PR since changing the overall upgrade tests reaches
beyond the scope of just telemetry.
Signed-off-by: Laura Flores <lflores@ibm.com>
|
|
This comment was mistakenly carried over in
https://github.com/ljflores/ceph/commit/6d25c053127f6aaaf942e674dca30ffd42658b9d.
Signed-off-by: Laura Flores <lflores@ibm.com>
|
|
This commit changes the workunit that tests the upgrade path from
reef to x.
The logic to verify collections is now much more robust. Previously,
the test relied on developers to make it aware of any new collections
it needed to verify. Now, I have added logic to check that the # of
known collections matches the # of reported collections. If it does not,
the test errors out, which will force developers to add any new
collections to the upgrade test along with adding it to the telemetry
code.
The test also verifies all collections instead of focusing only on new
collections that were added after the base collections.
Signed-off-by: Laura Flores <lflores@ibm.com>
|
|
Add the API `process_expired_objects` which is used to process and
delete the expired objects (swift or temporarily restored from cloud)
to the Zipper interface.
Signed-off-by: Soumya Koduri <skoduri@redhat.com>
|
|
This change is to update 19.2.0 Squid release documentation with a warning for users regarding potential placement group balancer issues.
Signed-off-by: Laimis Juzeliunas <laimis.juzeliunas@oxylabs.io>
|
|
Remove a link to a tracker for a planned-but-never-developed tool that
would have facilitated the importation or exportation of a RADOS pool to
a file. This is a part of a project to improve the CephFS Disaster
Recovery documentation, which was requested by Eugen Block. See the
tracker issue below for more on this project.
Follows https://github.com/ceph/ceph/pull/61411
See https://github.com/ceph/ceph/pull/61411#discussion_r1918525109
https://tracker.ceph.com/issues/69557
Signed-off-by: Zac Dover <zac.dover@proton.me>
|
|
Fixes https://tracker.ceph.com/issues/69554
Signed-off-by: Gil Bregman <gbregman@il.ibm.com>
|
|
since it is only a suggestion for debian.
this is a regression from: https://github.com/ceph/ceph/pull/60666
Fixes: https://tracker.ceph.com/issues/69473
Signed-off-by: Yuval Lifshitz <ylifshit@ibm.com>
|
|
Edit the first two sections of doc/cephfs/disaster-recovery-experts.rst
in preparation for adding deeper explanations of the contexts in which
one should use the various commands listed on that page.
https://tracker.ceph.com/issues/69557
Signed-off-by: Zac Dover <zac.dover@proton.me>
|
|
Signed-off-by: abhishek-kane <abhishek.kane@ibm.com>
|
|
NVMeoF gateway version is independent of ceph version
so 'ceph version' shows wrong nvmeof version in output
(i.e. instead of gateway version, it shows Ceph version).
Hence, remove nvmeof in 'ceph versions' output.
To check for gateway version, use 'gw info' command.
Signed-off-by: Vallari Agrawal <vallari.agrawal@ibm.com>
|
|
In handle_replication_status_header() when the COMPLETED status is
being set to object's attr, it needs to be reflected to the current
live attrs for the corresponding request so it can be reflected in
the first try than the second.
Fixes: https://tracker.ceph.com/issues/69549
Signed-off-by: Seena Fallah <seenafallah@gmail.com>
|
|
bucket_source_sync_checkpoint() requires bucket id to lookup for
full-sync object and the dest pipe doesn't have it. by replcaning
the bucket key in the pipe with the bucket info we will ensure the
bucket id is set.
Fixes: https://tracker.ceph.com/issues/69548
Signed-off-by: Seena Fallah <seenafallah@gmail.com>
|
|
Signed-off-by: Ali Masarwa <amasarwa@redhat.com>
|
|
Currently, RGW returns a 200 on a successful DELETE on a bucket policy but
the S3 API expects a 204:
https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketPolicy.html
The sample response in the example above is a 204.
This patch checks the op_ret in `RGWDeleteBucketPolicy::send_response()`
and on a success we turn it to a 204 (or STATUS_NO_CONTENT).
Fixes: https://tracker.ceph.com/issues/69539
Signed-off-by: Simon Jürgensmeyer <simon.juergensmeyer@hetzner-cloud.de>
|
|
Signed-off-by: Anthony D'Atri <anthonyeleven@users.noreply.github.com>
|
|
Make sure that first_in_ceph_log() doesn't return None (which is
treated as success/"no badness" by the caller) if the cluster log file
is missing.
Fixes: https://tracker.ceph.com/issues/57864
Co-authored-by: Ilya Dryomov <idryomov@gmail.com>
Signed-off-by: Christopher Hoffman <choffman@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
|
|
Fixes: https://tracker.ceph.com/issues/69536
Signed-off-by: Yehuda Sadeh <ysadehwe@ibm.com>
|
|
This commit updates RGW Config Reference - Lifecycle Settings section. In particular it changes the section where two different tunings for two different workloads are suggested. It aims for a more understandable description as asked by the contributors.
Signed-off-by: Laimis Juzeliunas <laimis.juzeliunas@oxylabs.io>
|
|
Signed-off-by: Ronen Friedman <rfriedma@redhat.com>
|
|
currently, the dependency logic is duplicated between the different Service
classes and the module.py::_calc_daemon_deps function, which can lead
to issues such as BUGSs, difficulty in maintenance, and other problems
associated with duplicated code. In this change, we are consolidating
all the dependency logic into the Service subclasses to eliminate this
duplication. This way, we also force anybody creating a new Service to
think about its potential dependencies.
Fixes: https://tracker.ceph.com/issues/69021
Signed-off-by: Redouane Kachach <rkachach@ibm.com>
|
|
moved out of the main commit to
facilitate backporting it to pre-C++20.
Signed-off-by: Ronen Friedman <rfriedma@redhat.com>
|
|
Signed-off-by: Ronen Friedman <rfriedma@redhat.com>
|
|
In its get_tracked_conf_keys() member function, the
cacher (in the existing code) initializes a static
function-block variable ('keys'), and uses it for
registering the observer.
But the cacher is instantiated on the type of
the configuration value. Thus, multiple cacher
objects for which the configuration values are
of the same type - share the static 'keys'. Only
one of the observers is registered.
Note that the code could have been simplified
somewhat, if the signature of the
get_tracked_conf_keys() function
was changed to return 'const char* const *'.
Fixes: https://tracker.ceph.com/issues/69236
Signed-off-by: Ronen Friedman <rfriedma@redhat.com>
|
|
Signed-off-by: Samuel Just <sjust@redhat.com>
|
|
Add the actual EOL date for the Quincy release (it's 2025-01-13).
Signed-off-by: Zac Dover <zac.dover@proton.me>
|
|
Signed-off-by: Jon Bailey <jonathan.bailey1@ibm.com>
|
|
`beast::ssl_stream` is deprecated as of 1.86, and its loss of the move
constructor keeps it from compiling on that version.
Hopefully this passes tests on 1.85, too, or it will have to wait
until the boost bump.
Signed-off-by: Adam Emerson <aemerson@redhat.com>
|
|
Ensures the stringstream is empty before sending a command in the RadosIO class
Signed-off-by: Jon Bailey <jonathan.bailey1@ibm.com>
|
|
In `struct bluefs_fnode_t` there is a vector `extents` and
the vector `extents_index` that is a log2 seek cache.
Until modifications to truncate() we never removed extents from files.
Modified truncate() did not update extents_index.
For example 10 extents long files when truncated to 0 will have:
0 extents, 10 extents_index.
After writing some data to file:
1 extents, 11 extents_index.
Now, `bluefs_fnode_t::seek` will binary search extents_index,
lets say it located seek at item #3.
It will then jump up from #0 extent (that exists) to #3 extent which
does not exist at.
The worst part is that code is now broken, as #3 != extent.end().
There are 3 parts of the fix:
1) assert in `bluefs_fnode_t::seek` to protect against
jumping outside extents
2) code in BlueFS::truncate to sync up `extents_index` with `extents`
3) dampening down assert in _replay to give a way out of cases
where incorrect "offset 12345" (12345 is file size) instead of
"offset 20000" (allocations occupied) was written to log.
Fixes: https://tracker.ceph.com/issues/69481
Signed-off-by: Adam Kupczyk <akupczyk@ibm.com>
|
|
* when source bucket is deleted
* when logging is disabled
* when logging conf changes
* when target bucket is deleted
also add "bucket logging info" admin command
returning logging conf for source bucket, and list
of source buckets for log bucket
Signed-off-by: Yuval Lifshitz <ylifshit@ibm.com>
|
|
Signed-off-by: Yuval Lifshitz <ylifshit@ibm.com>
|
|
Signed-off-by: Yuval Lifshitz <ylifshit@ibm.com>
|
|
Signed-off-by: Yuval Lifshitz <ylifshit@ibm.com>
|
|
Signed-off-by: Yuval Lifshitz <ylifshit@ibm.com>
|
|
Thanks to the maintainers of the Arch User Repository Ceph PKGBUILD
for this fix.
Signed-off-by: Adam Emerson <aemerson@redhat.com>
|
|
Help from Pritha and Casey appreciated
Plus, fix 3 explicit mapping tests in test_rgw_iam_policy.cc.
Signed-off-by: Matt Benjamin <mbenjamin@redhat.com>
|
|
This commit adds:
1. workflow summary in the first section along with an image.
2. sub-section "Pushing to ceph-ci repository" to second section.
3. file doc/dev/developer_guide/testing_integration_tests/workflow.png
Signed-off-by: Vallari Agrawal <vallari.agrawal@ibm.com>
|
|
Unittest showing 2 different flavours of problems:
1) bluefs log corruption
2) bluefs sigsegv
Signed-off-by: Adam Kupczyk <akupczyk@ibm.com>
|
|
So that PhyscalNodeMapping doesn't contain LBAMapping specific
interfaces
Signed-off-by: Xuehan Xu <xuxuehan@qianxin.com>
|
