These are not used in Ceph code currently, and should not
be used in the future either, since any use will introduce
byte-order dependent behavior. Remove them to prevent
accidental use.
Signed-off-by: Ulrich Weigand <ulrich.weigand@de.ibm.com>
The integer bloom filter test cases do not really match typical usage
of the bloom filter in actual Ceph code. In particular:
- the tests use consecutive integer ranges, while Ceph code uses
hash values uniformly distributed over the uint32_t space;
- the tests pass "int" to the insert and contains functions, which
causes the generic C++ POD type overload to be selected instead
of the uint32_t overload that is used by Ceph code. The POD
overload is dependent on host byte order, and behaves actually
different from the uint32_t overload on little-endian systems.
To fix these issues, this patch changes the integer tests to
always pass in uint32_t (instead of int), and to use results
of a pseudo-random number generator instead of consecutive
sequences. (We assume the period of the generator is long
enough that all values generated within one test instance
are distinct.)
This not only makes the test pass on both big- and little-endian
hosts now, but it also allows tightening of the allowable actual
false positive rates, as they now match much closer the expected
values.
Signed-off-by: Ulrich Weigand <ulrich.weigand@de.ibm.com>
* refs/pull/30525/head:
qa/tasks/ceph.conf.template: disable power-of-2 warning
qa/standalone/mon/health-mute: use power of 2 for pg_num
osd/OSDMap: remove remaining g_conf() usage
PendingReleaseNotes: add note for 14.2.5 so we can backport this
osd/OSDMap: health alert for non-power-of-two pg_num
Reviewed-by: Kai Wagner <kwagner@suse.com>
Reviewed-by: Nathan Cutler <ncutler@suse.com>
Reviewed-by: xie xingguo <xie.xingguo@zte.com.cn>
* refs/pull/30431/head:
pybind/ceph_argparse: add :int or :float to numerical args
pybind/ceph_argparse: simplify osd name and target types
pybind/ceph_argparse: prefer field names to types in help output
pybind/ceph_argparse: more concise n=N '...'
pybind/ceph_argparse: [] (not {}) around optional args
Reviewed-by: Brad Hubbard <bhubbard@redhat.com>
Reviewed-by: Josh Durgin <jdurgin@redhat.com>
mgr/dashboard: Configuring an URL prefix does not work as expected
Reviewed-by: Ernesto Puerta <epuertat@redhat.com>
Reviewed-by: Stephan Müller <smueller@suse.com>
Add a new command-line switch to allow it to use the kernel client
instead, and add all of the machinery to handle local kcephfs mounts.
Document this in the developer guide, along with the appropriate scary
warnings about using this on a machine that you care about. While we're
in there, also correct a typo about FUSE configuration.
Fixes: https://tracker.ceph.com/issues/41910
Signed-off-by: Jeff Layton <jlayton@redhat.com>
osd: make osd recover more smoothly by avoiding failure peer info to resent
Reviewed-by: xie xingguo <xie.xingguo@zte.com.cn>
Reviewed-by: Sage Weil <sage@redhat.com>
* refs/pull/30297/head:
test_cephfs_shell: add note on how to run this testsuite
cephfs-shell: rewrite help text for put and get commands
Reviewed-by: Patrick Donnelly <pdonnell@redhat.com>
* refs/pull/29906/head:
vstart_runner: name booleans for options differently
qa/vstart_runner.py: add an option to remove old log
qa/vstart_runner.py: make log initialization code reusable
qa/vstart_runner.py: make printing of stdout of ps optional
qa/vstart_runner.py: add timeout for vstart.sh and stop.sh
qa/vstart_runner.py: add an option to teardown cluster
Reviewed-by: Jeff Layton <jlayton@redhat.com>
there is chance that the system already have epel-release-latest-7.noarch.rpm
installed, in that case, install-deps.sh should not fail.
Signed-off-by: Kefu Chai <kchai@redhat.com>
If we start a new interval and the prior interval may have OSDs that
are still readable, set the WAIT state bit and block operations until
sufficient time has elapsed.
Signed-off-by: Sage Weil <sage@redhat.com>
Before we share pg_history_t, refresh the prior_readable_until_ub to be
a simple duration from *now*, so that it is completely clock-independent.
The receiver can interpret it based on the receive time for the message,
which loses a bit of precision but is safe since this is an upper bound.
Signed-off-by: Sage Weil <sage@redhat.com>
