Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
Chapter 6. Known issues
This section documents known issues found in this release of Red Hat Ceph Storage.
6.1. The Cephadm utility
Some NFS daemons may not produce logs
Currently, in a cephadm-deployed NFS service with multiple NFS daemons, only one would be serving IO, causing the user to come across NFS daemons that produce no logs. There is no workaround for this as of now.
Prevent Mutex from failing when unlocking.
Previously, when a Mutex that was not locked was attempted to be unlocked, the Mutex crashed.
As a workaround, verify if the Mutex is locked in the first place before unlocking.
ceph orch ps command does not display a version for monitoring stack daemons
In cephadm, due to the version grabbing code currently being incompatible with the downstream monitoring stack containers, version grabbing fails for monitoring stack daemons, such as node-exporter, prometheus, and alertmanager.
Encryption of multipart uploads requires special handling around the part boundaries because each part is uploaded and encrypted separately. In multi-site, objects are encrypted, and multipart uploads are replicated as a single part. As a result, the replicated copy loses its knowledge about the original part boundaries required to decrypt the data correctly, which causes this corruption.
As a workaround, if the user needs to find the version, the daemons' container names include the version.
6.2. Ceph Dashboard
Ceph Object Gateway page does not load after a multi-site configuration
The Ceph Object Gateway page does not load because the dashboard cannot find the correct access key and secret key for the new realm during multi-site configuration.
As a workaround, use the ceph dashboard set-rgw-credentials command to manually update the keys.
6.3. Ceph Object Gateway
JSON select count() from S3Object[]; queries are lagging and cause high CPU usage
When running the select count() from S3Object[]; query, the time lapse and radosgw CPU utilization are very high compared to CSV object queries.
As a workaround, when running the JSON query, use count() instead of count(*) query.
s3select and Trino fail when processing JSON object using s3select
When Trino processes a JSON object using the s3select request, the request fails causing Trino to fail too. This emits the wrong json dataType should use DOCUMENT error message in the Ceph Object Gateway logs.
As a workaround, it is sometimes possible to use the s3select request directly, not using Trino.
