orch approved
On Mon, Aug 5, 2024 at 4:33 PM Yuri Weinstein wrote:
> Details of this release are summarized here:
>
> https://tracker.ceph.com/issues/67340#note-1
>
> Release Notes - N/A
> LRC upgrade - N/A
> Gibba upgrade -TBD
>
> Seeking approvals/reviews for:
>
> rados - Radek, Laura (https:/
I forgot to add this one to get the info from any admin node:
ceph log last 10 warn cluster
2024-08-09T11:21:23.949916+ osd.1 (osd.1) 6 : cluster [WRN] Large
omap object found. Object: 3:592df674:::file:head PG: 3.2e6fb49a (3.0)
Key count: 363 Size (bytes): 2070
2024-08-09T11:21:27.723959
Hi,
I don't have much to comment about logging, I feel you though. I just
wanted to point out that the details about the large omap object
should be in the (primary) OSD log, not in the MON log:
grep -i "large omap"
/var/log/ceph/bce93c48-5552-11ef-8ba9-fa163e2ad8c5/ceph-osd.*
/var/log/ce
Hi,
I have a bunch of long-standing struggles with the way Ceph handles
logging and I cannot figured out how to solve them. These issues are
basically the following:
- The log config options are utterly confusing and very badly documented
- Mon file logs are spammed with DBG-level cluster log
Hi Chulin,
When it comes to data consistency, it's generally admitted that Ceph is an
undefeated master.
Considering the very few (~100) rados objects that were completely lost (data
and metadata) and the fact that you're using colocated HDD OSDs with volatile
disk buffers caching rocksdb meta
That's interesting, thanks for the link to the tracker issue. There's
definitely a chance that it could have been deleted (by the
application), but we don't have enough logs right now to confirm. They
don't have many insights into the application, so it can be difficult
to get to the bottom
Hello,
Did the customer deleted the object by any chance? If yes, could this be
related to https://tracker.ceph.com/issues/63935 ?
We got a scenario where an application was doing some DELETE and then listing
bucket entries.
It was able to find objects that should have been deleted and then was
