ceph/qa/cephfs/conf/mds.yaml

overrides:
  ceph:
    cluster-conf:
      mds:
        debug mds: 20
        debug mds balancer: 20
        debug ms: 2
        mds debug frag: true
        mds debug scatterstat: true
        mds op complaint time: 180
        mds verify scatter: true
        osd op complaint time: 180
        rados mon op timeout: 900
        rados osd op timeout: 900
qa: create common conf for all cephfs suites This will be followed by removing common CephFS configurations in the ceph.conf.template in teuthology. Signed-off-by: Patrick Donnelly <pdonnell@redhat.com> 2018-06-27 16:53:12 +00:00			`overrides:`
			`ceph:`
qa/cephfs: set confs using cluster-conf So that these configs can be easily overriden by tests. Signed-off-by: Patrick Donnelly <pdonnell@redhat.com> 2023-08-08 01:14:03 +00:00			`cluster-conf:`
qa: create common conf for all cephfs suites This will be followed by removing common CephFS configurations in the ceph.conf.template in teuthology. Signed-off-by: Patrick Donnelly <pdonnell@redhat.com> 2018-06-27 16:53:12 +00:00			`mds:`
qa: ignore normal slow IO warnings for cephfs Generally the slow warnings we get are just over the threshold. These warnings are related to deploying multiple Ceph daemons side-by-side. Let's see how we do with two minutes. Ignoring the warnings entirely is unsatisfactory as they serve as a useful canary in the coal mine when you see warnings for ops > some unreasonably large amount of time. Fixes: http://tracker.ceph.com/issues/26900 Signed-off-by: Patrick Donnelly <pdonnell@redhat.com> 2018-08-07 00:55:42 +00:00			`debug mds: 20`
qa: increase mds balancer debug Fixes: https://tracker.ceph.com/issues/55980 Signed-off-by: Patrick Donnelly <pdonnell@redhat.com> 2022-06-09 16:05:27 +00:00			`debug mds balancer: 20`
qa: set debug_ms=2 for cephfs tests Since we have hit this many times in cephfs tests, just increase the debug_ms log level for now. Related: https://tracker.ceph.com/issues/65309 Signed-off-by: Xiubo Li <xiubli@redhat.com> 2024-06-04 01:36:14 +00:00			`debug ms: 2`
qa: ignore normal slow IO warnings for cephfs Generally the slow warnings we get are just over the threshold. These warnings are related to deploying multiple Ceph daemons side-by-side. Let's see how we do with two minutes. Ignoring the warnings entirely is unsatisfactory as they serve as a useful canary in the coal mine when you see warnings for ops > some unreasonably large amount of time. Fixes: http://tracker.ceph.com/issues/26900 Signed-off-by: Patrick Donnelly <pdonnell@redhat.com> 2018-08-07 00:55:42 +00:00			`mds debug frag: true`
qa: create common conf for all cephfs suites This will be followed by removing common CephFS configurations in the ceph.conf.template in teuthology. Signed-off-by: Patrick Donnelly <pdonnell@redhat.com> 2018-06-27 16:53:12 +00:00			`mds debug scatterstat: true`
qa: ignore normal slow IO warnings for cephfs Generally the slow warnings we get are just over the threshold. These warnings are related to deploying multiple Ceph daemons side-by-side. Let's see how we do with two minutes. Ignoring the warnings entirely is unsatisfactory as they serve as a useful canary in the coal mine when you see warnings for ops > some unreasonably large amount of time. Fixes: http://tracker.ceph.com/issues/26900 Signed-off-by: Patrick Donnelly <pdonnell@redhat.com> 2018-08-07 00:55:42 +00:00			`mds op complaint time: 180`
qa: create common conf for all cephfs suites This will be followed by removing common CephFS configurations in the ceph.conf.template in teuthology. Signed-off-by: Patrick Donnelly <pdonnell@redhat.com> 2018-06-27 16:53:12 +00:00			`mds verify scatter: true`
qa: ignore normal slow IO warnings for cephfs Generally the slow warnings we get are just over the threshold. These warnings are related to deploying multiple Ceph daemons side-by-side. Let's see how we do with two minutes. Ignoring the warnings entirely is unsatisfactory as they serve as a useful canary in the coal mine when you see warnings for ops > some unreasonably large amount of time. Fixes: http://tracker.ceph.com/issues/26900 Signed-off-by: Patrick Donnelly <pdonnell@redhat.com> 2018-08-07 00:55:42 +00:00			`osd op complaint time: 180`
qa: do not use any time related suffix for _op_timeouts When testing the upgration, for the old version the _op_timeouts options' type is TYPE_FLOAT, but when parsing them by strict_strtod it will failed with error: strict_strtod: garbage at end of string. got: '15m' This commit will remove the 'm' suffix by switch the time to 900, thus the old version still could parse it successfully. Introduced-by: d060c9a768c6974d3b68e4d408edf78bba9e0e85 https://tracker.ceph.com/issues/51705 Signed-off-by: Xiubo Li <xiubli@redhat.com> 2021-12-29 04:31:48 +00:00			`rados mon op timeout: 900`
			`rados osd op timeout: 900`