* refs/pull/27073/head:
qa/tasks: Check MDS failover during mon_thrash
qa/tasks: Compare two FSStatuses
qa/suites/fs: renamed default.yaml to mds.yaml
qa/suites/fs: mon_thrash test for fs
qa/tasks: Fix typo in the comment
Reviewed-by: Patrick Donnelly <pdonnell@redhat.com>
* refs/pull/28642/head:
mds: check last laggy before marking unresponsive client stale
mds: remove the code that skip evicting the only client
Reviewed-by: Patrick Donnelly <pdonnell@redhat.com>
If we allocate a new extent that is contiguous with the last extent,
just extend it. This avoids having long vectors of continguous extents
when a single large extent would suffice--especially with log files.
Signed-off-by: Sage Weil <sage@redhat.com>
Warning when there are already 2M omap keys does not help, reduce this
threshold so that preemptive measures can be taken based on this.
Fixes: https://tracker.ceph.com/issues/40583
Signed-off-by: Neha Ojha <nojha@redhat.com>
turns out the libstdc++ on fc30 does not include error_code.message() in
filesystem_error.what(). let's make it optional
Signed-off-by: Kefu Chai <kchai@redhat.com>
MemStore does not have this feature, but CyanStore needs it. because
`qa/tasks/ceph.py` uses following steps when creating/starting an OSD
1. ceph-osd --mkfs --mkkey -i <osd_id> --monmap <monmap>
2. read the osd_fsid of osd.<osd_id>
3. ceph osd new <osd_fsid> <osd_id>
when we mkfs for the OSD, the osd_fsid is still unknown. so we cannot
use the configured one, as it is always empty. in that case, we need to
use a random uuid, and persist it to both ${osd_data}/fsid and
superblock.osd_fsid
Signed-off-by: Kefu Chai <kchai@redhat.com>
so we can
* have access to the available command line options offered by Seastar.
* tell if the executable we are playing around is ceph-osd or crimson-osd.
Signed-off-by: Kefu Chai <kchai@redhat.com>
as crimson's logging levels are now connected those of ceph, there is no
need to note down the difference between them anymore.
Signed-off-by: Kefu Chai <kchai@redhat.com>
when the logging level of a subsys changes, update seastar accordingly
before this change, seastar logging levels of different logger are not
connected to ceph's logging levels of different subsystem.
after this change, they are connected. whenever a subsys's logging level
changes, the corresponding seastar logger is updated as well.
Signed-off-by: Kefu Chai <kchai@redhat.com>
The primary benefit is that the OSD doesn't need to keep a flood of
blocked heartbeat messages around in memory.
This prevents OSDs from accumulating heartbeat messages due to a
broken switch and then exhausting the whole node's memory:
Jun 11 04:19:26 host-192-168-9-12 kernel: [409881.137077] Out of memory:
Kill process 1471476 (ceph-osd) score 47 or sacrifice child
Jun 11 04:19:26 host-192-168-9-12 kernel: [409881.146054] Killed process
1471476 (ceph-osd) total-vm:4822548kB, anon-rss:3097860kB,
file-rss:2556kB, shmem-rss:0kB
Fixes: http://tracker.ceph.com/issues/40586
Signed-off-by: xie xingguo <xie.xingguo@zte.com.cn>
