RGW has numerous pool creation calls, one of which utilizes
an async interface. This adds support for RGW's use-case.
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
rgw: use a namespace for rgw reshard pool for upgrades as well
Reviewed-by: Casey Bodley <cbodley@redhat.com>
Reviewed-by: Orit Wasserman <owasserm@redhat.com>
The output of ceph osd stat has changed,
It printed:
cluster b370a29d-9287-4ca3-ab57-3d824f65e339
health HEALTH_OK
monmap e1: 1 mons at {ceph1=10.0.0.8:6789/0}, election epoch 2, quorum 0 ceph1
osdmap e63: 2 osds: 2 up, 2 in
pgmap v41338: 952 pgs, 20 pools, 17130 MB data, 2199 objects
115 GB used, 167 GB / 297 GB avail
952 active+clean
but now the osdmap line has gone and thus this no longer works:
qa/workunits/cephtool/test.sh:1944:
old_pgs=$(ceph osd pool get $TEST_POOL_GETSET pg_num | sed -e 's/pg_num: //')
new_pgs=$(($old_pgs+$(ceph osd stat | grep osdmap | awk '{print $3}')*32))
4: qa/workunits/cephtool/test.sh: line 1945: 10+*32: syntax errotoken is "*32")
- And parse the output in json , with jq, for better reliability
Signed-off-by: Willem Jan Withagen <wjw@digiware.nl>
we encode the payload w/o the writelock even can_write == NOWRITE, if
the message "can_fast_prepare". in that case, the "feature" of the
connection is 0, as no handshake happens yet. so the header.version is
always set to a version compatible with pre-luminous. but when the
message is re-encoded when the connection is re-established with feature
with luminous, the header.version is not set back to HEADER_VERSION.
that's why the message's encoding is not consistent with header.version
sometimes.
in this change, we always set the header.version in encode_payload(), so
it's consistent even after connection reset and message re-encoding.
Fixes: http://tracker.ceph.com/issues/19939
Signed-off-by: Kefu Chai <kchai@redhat.com>
This closes a window between mkfs and when the first mgr goes active
where *no* mgr commands are defined, and things like 'pg dump' fail. We
do not get the default set of commands defined by modules, but we get
everything else.
Signed-off-by: Sage Weil <sage@redhat.com>
So that the list of commands includes python modules,
thus allowing python-provided commands to be invoked
by the CLI with out a `tell mgr` prefix.
Signed-off-by: John Spray <john.spray@redhat.com>
The mgr already sends a beacon to the mon immediately
after loading python modules in Mgr::init, to indicate
that it is now available. Use that beacon to transmit
the command descriptions.
The monitor should handle this beacon by persisting
the command descriptions before persisting the updated
mgrmap that indicates that the mgr is now active.
Signed-off-by: John Spray <john.spray@redhat.com>
This was just a for loop. No longer needed for
MonCommands, and the usage in memstore/PageSet
was just iterating over char* and should never have
been there to begin with.
Signed-off-by: John Spray <john.spray@redhat.com>
- factor out install and ceph into ceph/ceph.yaml
- pg_num thrashing + 20 minute health timeout for thrashosds
- common thrashosds-health.yaml whitelist
- drop iozone workload
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
And the output is wrong...
cluster:
id: b979e20d-6441-46b4-8663-954e1e8ce01d
health: HEALTH_WARN
1 osds down
mon %names has mon_osd_down_out_interval set to 0
Now:
health: HEALTH_WARN
mon a is low on available space
mon a has mon_osd_down_out_interval set to 0
Signed-off-by: xie xingguo <xie.xingguo@zte.com.cn>