Hi,
during code profiling using LTTng, I encounter that during
processing of write requests to the cluster, the ceph-osd
spends a lot of time in the ReplicatedPG::log_operation
before the the actual writes to journal and object
in the FileStore are triggered.
This happens in ReplicatedBackend::submit_transaction.
What I wonder is
- what is the purpose of the log_operation?
If I am not mistaken, then it is neither the write-to-journal
nor the write-to-object; both of these are triggered from
the queue_operation following that log_operation.
- can the sequence between the log_operation and
the actual queue_operation be reversed in
ReplicatedBackend::submit_transaction?
Regards
Andreas Bluemle
--
Andreas Bluemle mailto:[email protected]
ITXperts GmbH http://www.itxperts.de
Balanstrasse 73, Geb. 08 Phone: (+49) 89 89044917
D-81541 Muenchen (Germany) Fax: (+49) 89 89044910
Company details: http://www.itxperts.de/imprint.htm
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
