Re: [ceph-users] failed lossy con, dropping message

2017-04-13 Thread Gregory Farnum
On Thu, Apr 13, 2017 at 9:27 AM, Laszlo Budai wrote: > Hello Greg, > > Thank you for the clarification. One last thing: can you point me to some > documents that describes these? I would like to better understand what's > going on behind the curtains ... Unfortunately I don't think anything like

Re: [ceph-users] failed lossy con, dropping message

2017-04-13 Thread Laszlo Budai
Hello Greg, Thank you for the clarification. One last thing: can you point me to some documents that describes these? I would like to better understand what's going on behind the curtains ... Kind regards, Laszlo On 13.04.2017 16:22, Gregory Farnum wrote: On Thu, Apr 13, 2017 at 2:17 AM Las

Re: [ceph-users] failed lossy con, dropping message

2017-04-13 Thread Gregory Farnum
On Thu, Apr 13, 2017 at 2:17 AM Laszlo Budai wrote: > Hello Greg, > > Thank you for the answer. > I'm still in doubt with the "lossy". What does it mean in this context? I > can think of different variants: > 1. The designer of the protocol from start is considering the connection > to be "lossy"

Re: [ceph-users] failed lossy con, dropping message

2017-04-13 Thread Laszlo Budai
Hello Greg, Thank you for the answer. I'm still in doubt with the "lossy". What does it mean in this context? I can think of different variants: 1. The designer of the protocol from start is considering the connection to be "lossy" so the connection errors are handled in a higher layer. So the

Re: [ceph-users] failed lossy con, dropping message

2017-04-12 Thread Gregory Farnum
On Wed, Apr 12, 2017 at 3:00 AM, Laszlo Budai wrote: > Hello, > > yesterday one of our compute nodes has recorded the following message for > one of the ceph connections: > > submit_message osd_op(client.28817736.0:690186 > rbd_data.15c046b11ab57b7.00c4 [read 2097152~380928] 3.6f81364a

Re: [ceph-users] failed lossy con, dropping message

2017-04-12 Thread Laszlo Budai
Hi Alex, I saw your thread, but I think mine is a little bit different. I have only one message so far, and I want to better understand the issue. I would like to see whether there are any tunable parameters that could be adjusted to have an influence on this behavior. Kind regards, Laszlo On

Re: [ceph-users] failed lossy con, dropping message

2017-04-12 Thread Alex Gorbachev
Hi Laszlo, On Wed, Apr 12, 2017 at 6:26 AM Laszlo Budai wrote: > Hello, > > yesterday one of our compute nodes has recorded the following message for > one of the ceph connections: > > submit_message osd_op(client.28817736.0:690186 > rbd_data.15c046b11ab57b7.00c4 [read 2097152~380928

[ceph-users] failed lossy con, dropping message

2017-04-12 Thread Laszlo Budai
Hello, yesterday one of our compute nodes has recorded the following message for one of the ceph connections: submit_message osd_op(client.28817736.0:690186 rbd_data.15c046b11ab57b7.00c4 [read 2097152~380928] 3.6f81364a ack+read+known_if_redirected e3617) v5 remote, 10.12.68.71:68

Re: [ceph-users] Failed lossy con, dropping message

2014-12-04 Thread Gregory Farnum
It means that the connection from the client to the osd went away. This could happen just because the client shut down, but if so it quit before it had gotten commits from all its disk writes, which seems bad. It could also mean there was a networking problem of some kind. -Greg On Thu, Dec 4, 2014

[ceph-users] Failed lossy con, dropping message

2014-12-04 Thread Andrei Mikhailovsky
Hello guys, I am seeing about a dozen or so messages like these on a daily basis. Was wondering if this is something I should worry about? 2014-12-04 06:51:14.639833 7fb3ea615700 0 -- 192.168.168.200:6815/3326 submit_message osd_op_reply(175402 rbd_data.1bb23193a95f874.2c08 [set-