Skip to content

Commit 2ea3348

Browse files
committed
msg: decrease the level to print the sending msgs from the protocol
We have hitting the issue, which is the messages are stuck in the sender queue, many times. We just suspect it's a bug of the protocol code and we need to know exactly whether the msgs are sent out or not. Related: https://tracker.ceph.com/issues/65309 Signed-off-by: Xiubo Li <[email protected]>
1 parent ec0f9cc commit 2ea3348

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

src/msg/async/ProtocolV1.cc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1173,8 +1173,8 @@ ssize_t ProtocolV1::write_message(Message *m, ceph::buffer::list &bl, bool more)
11731173
}
11741174

11751175
m->trace.event("async writing message");
1176-
ldout(cct, 20) << __func__ << " sending " << m->get_seq() << " " << m
1177-
<< dendl;
1176+
ldout(cct, 2) << __func__ << " sending message m=" << m
1177+
<< " seq=" << m->get_seq() << " " << *m << dendl;
11781178
ssize_t total_send_size = connection->outgoing_bl.length();
11791179
ssize_t rc = connection->_try_send(more);
11801180
if (rc < 0) {

src/msg/async/ProtocolV2.cc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -551,7 +551,7 @@ ssize_t ProtocolV2::write_message(Message *m, bool more) {
551551
return -EILSEQ;
552552
}
553553

554-
ldout(cct, 5) << __func__ << " sending message m=" << m
554+
ldout(cct, 2) << __func__ << " sending message m=" << m
555555
<< " seq=" << m->get_seq() << " " << *m << dendl;
556556

557557
m->trace.event("async writing message");

0 commit comments

Comments
 (0)