as new as the map epoch indicated on the message. If not, the message is
queued in OSD::waiting_for_osdmap via OSD::wait_for_new_map. Note, this
cannot violate the above conditions since any two messages will be queued
-in order of receipt and if a message is recieved with epoch e0, a later message
+in order of receipt and if a message is received with epoch e0, a later message
from the same source must be at epoch at least e0. Note that two PGs from
the same OSD count for these purposes as different sources for single PG
messages. That is, messages from different PGs may be reordered.
The test mode will use the input crush map ( as specified with **-i
map** ) and perform a dry run of CRUSH mapping or random placement (
if **--simulate** is set ). On completion, two kinds of reports can be
-created. The **--show-...** options output human readable informations
+created. The **--show-...** options output human readable information
on stderr. The **--output-csv** option creates CSV files that are
documented by the **--help-output** option.
``mon_status`` can be obtained through the ``ceph`` tool when you have
a formed quorum, or via the admin socket if you don't. This command will
-output a multitude of informations about the monitor, including the same
+output a multitude of information about the monitor, including the same
output you would get with ``quorum_status``.
Take the following example of ``mon_status``::
Scrap the monitor and create a new one
You should only take this route if you are positive that you won't
- lose the informations kept by that monitor; that you have other monitors
+ lose the information kept by that monitor; that you have other monitors
and that they are running just fine so that your new monitor is able
to synchronize from the remaining monitors. Keep in mind that destroying
a monitor, if there are no other copies of its contents, may lead to
The test mode will use the input crush map ( as specified with \fB\-i
map\fP ) and perform a dry run of CRUSH mapping or random placement (
if \fB\-\-simulate\fP is set ). On completion, two kinds of reports can be
-created. The \fB\-\-show\-...\fP options output human readable informations
+created. The \fB\-\-show\-...\fP options output human readable information
on stderr. The \fB\-\-output\-csv\fP option creates CSV files that are
documented by the \fB\-\-help\-output\fP option.
.INDENT 0.0
/*
- current crop of tunables are all now "safe". reenable this when we
+ current crop of tunables are all now "safe". re-enable this when we
add new ones that are ... new.
if (!unsafe_tunables) {
* onto the original Paxos' Prepare phase. Basically, we'll generate a
* Proposal Number, taking @p oldpn into consideration, and we will send
* it to a quorum, along with our first and last committed versions. By
- * sending these informations in a message to the quorum, we expect to
+ * sending these information in a message to the quorum, we expect to
* obtain acceptances from a majority, allowing us to commit, or be
* informed of a higher Proposal Number known by one or more of the Peons
* in the quorum.
* accordingly.
*
* Once a Peon receives a collect message from the Leader it will reply
- * with its first and last committed versions, as well as informations so
+ * with its first and last committed versions, as well as information so
* the Leader may know if his Proposal Number was, or was not, accepted by
* the Peon. The Peon will accept the Leader's Proposal Number iif it is
* higher than the Peon's currently accepted Proposal Number. The Peon may
cluster_messenger->send_message(m, con.get());
} else {
dout(7) << "do_notify osd " << it->first
- << " sending seperate messages" << dendl;
+ << " sending separate messages" << dendl;
for (vector<pair<pg_notify_t, pg_interval_map_t> >::iterator i =
it->second.begin();
i != it->second.end();
cluster_messenger->send_message(m, con.get());
} else {
dout(7) << "do_queries querying osd." << who
- << " sending seperate messages "
+ << " sending saperate messages "
<< " on " << pit->second.size() << " PGs" << dendl;
for (map<spg_t, pg_query_t>::iterator i = pit->second.begin();
i != pit->second.end();
<< "non-auth_log_shard osd." << logevt.from << dendl;
return discard_event();
}
- dout(10) << "GetLog: recieved master log from osd"
+ dout(10) << "GetLog: received master log from osd"
<< logevt.from << dendl;
msg = logevt.msg;
post_event(GotLog());
Ping a monitor to assess liveness
May be used as a simply way to assess liveness, or to obtain
- informations about the monitor in a simple way even in the
+ information about the monitor in a simple way even in the
absence of quorum.
:param mon_id: the ID portion of the monitor's name (i.e., mon.<ID>)
cerr << " user info get user info\n";
cerr << " user rm remove user\n";
cerr << " user suspend suspend a user\n";
- cerr << " user enable reenable user after suspension\n";
+ cerr << " user enable re-enable user after suspension\n";
cerr << " user check check user info\n";
cerr << " user stats show user stats as accounted by quota subsystem\n";
cerr << " caps add add user capabilities\n";
user info get user info
user rm remove user
user suspend suspend a user
- user enable reenable user after suspension
+ user enable re-enable user after suspension
user check check user info
user stats show user stats as accounted by quota subsystem
caps add add user capabilities