Since the Beast frontend uses boost::context which is not supported on
s390x.
Signed-off-by: Nathan Cutler <ncutler@suse.com>
Signed-off-by: Kefu Chai <kchai@redhat.com>
boost::context is currently (1.63) unsupported for s390x and anyway
it makes sense to conditionalize Boost components so they are only
built with the Ceph components that need them (like is already being
done for mgr).
Fixes: http://tracker.ceph.com/issues/20048
Signed-off-by: Nathan Cutler <ncutler@suse.com>
Signed-off-by: Tim Serong <tserong@suse.com>
Signed-off-by: Casey Bodley <cbodley@redhat.com>
Signed-off-by: Kefu Chai <kchai@redhat.com>
common/iso_8601.cc: Make return expression Clang compatible
Reviewed-By: Adam C. Emerson <aemerson@redhat.com>
Reviewed-by: Kefu Chai <kchai@redhat.com>
- Buffer.h is needed to prevent Clang seriously complaining
about missing and wrong forward declarations of
ceph::buffer:ptr
including buffer_fwd.h does not help.
Signed-off-by: Willem Jan Withagen <wjw@digiware.nl>
- During include cleanup just a too bit much was removed for FreeBSD
to get things compiled.
This redoes some of the includes.
Tracker: http://tracker.ceph.com/issues/19883
Signed-off-by: Willem Jan Withagen <wjw@digiware.nl>
We are soon going to use BlueStore as the default OS, and
hence "bluestore-kv" shall be the preferred option.
By applying this patch, the help message shall be slightly
nicer to newcomers to this tool now.
Signed-off-by: xie xingguo <xie.xingguo@zte.com.cn>
$ python test_multi.py --num-zonegroups=2 --num-zones 2 --gateways-per-zone 1
Traceback (most recent call last):
File "test_multi.py", line 315, in <module>
init(True)
File "test_multi.py", line 162, in init
path = tpath('test_multi.conf')
NameError: global name 'tpath' is not defined
Signed-off-by: Jiaying Ren <jiaying.ren@umcloud.com>
when the thread is calling AsyncConnection::handle_write, another thread may
replace it and requeue all messages. Because we remove the write_lock
protection for handle_write caller, it may happen sent racing with out_q
Fix: http://tracker.ceph.com/issues/20093
Signed-off-by: Haomai Wang <haomai@xsky.com>
This finisher thread has a lot of callbacks which can hold PGRefs. Make
sure we drain them out before checking that all the PGs have finished
and have no outstanding references.
Moving this should be safe; we've already stopped the op thread et al
and the only things still running are the OSDService's objecter_finisher,
recovery_request_timer, and snap_sleep_timer (which has definitely been emptied
by the time we get here as it's synchronously cleared out on PG shutdown).
Signed-off-by: Greg Farnum <gfarnum@redhat.com>
- put 'osd.NNN failed' at front
- drop the ip address
- include the crush location
- be consistent:
"osd.$id failed ($crush_location) ($reason)"
2017-05-26 16:05:21.573460 mon.0 [INF] osd.0 failed (root=default,host=gnit) (refused connection reported by osd.1)
2017-05-26 16:06:17.198225 mon.0 [INF] osd.1 failed (root=default,host=gnit) (2 reporters from different osd after 20.098778 >= grace 20.000000)
Signed-off-by: Sage Weil <sage@redhat.com>
1. normalize arg parsing for "bucket limit check"
1.1 s/buckets/bucket/
2. avoid dividing by num_shards when it is 0
Signed-off-by: Matt Benjamin <mbenjamin@redhat.com>
On the leader we cancel the mapping job in encode_pending. On a peon,
we don't cancel it at all! It is surprising this didn't already cause
problems, but with the PGtempMap is pretty reliably crashes with a
largish map.
Fixes: http://tracker.ceph.com/issues/20067
Signed-off-by: Sage Weil <sage@redhat.com>
Use a flat_map with pointers into a buffer with the actual data. For a
decoded mapping, we have just two allocations (one for flat_map and one
for the encoded buffer).
This can get slow if you make lots of incremental changes after the fact
since flat_map is not efficient for modifications at large sizes. :/
Signed-off-by: Sage Weil <sage@redhat.com>
