I have verified trusty-proposed, it works good!
I used the second method (the gdb one) to verify it, below is the message I got:
231007:2018-12-04 13:54:53.828152 7ffa7658b700 10 -- 10.5.0.13:6801/15728 >> 10.5.0.20:6802/1017937 pipe(0x7ffa96c8a280 sd=146 :6801 s=2 pgs=3 cs=1 l=0 c=0x7ffa96f592e0).reader got message 4294967607 0x7ffa96c8ca80 osd_sub_op_reply(client.14165.0:26 2.36 b27bf2f6/benchmark_data_juju-13c929-ceph-trusty-0_21644_object25/head//2 [] ondisk, result = 0) v2
so we can see the osd_sub_op_reply was not been dropped even the message seq number has exceed the max value of unsigned 32 bit.
Hi Brian,
I have verified trusty-proposed, it works good! 13:6801/ 15728 >> 10.5.0. 20:6802/ 1017937 pipe(0x7ffa96c8a280 sd=146 :6801 s=2 pgs=3 cs=1 l=0 c=0x7ffa96f592e 0).reader got message 4294967607 0x7ffa96c8ca80 osd_sub_ op_reply( client. 14165.0: 26 2.36 b27bf2f6/ benchmark_ data_juju- 13c929- ceph-trusty- 0_21644_ object25/ head//2 [] ondisk, result = 0) v2
I used the second method (the gdb one) to verify it, below is the message I got:
231007:2018-12-04 13:54:53.828152 7ffa7658b700 10 -- 10.5.0.
so we can see the osd_sub_op_reply was not been dropped even the message seq number has exceed the max value of unsigned 32 bit.
Thanks,
Dongdong