Project

General

Profile

Activity

From 11/22/2011 to 12/21/2011

12/21/2011

09:10 AM Feature #1851 (Rejected): SimpleMessenger: use non-blocking io
This will allow some great stuff, like doing a revoke on sending messages. And decoupling threads from sockets. Etc.
...
Greg Farnum

12/14/2011

11:26 AM Bug #1829 (Resolved): SimpleMessenger tries to shut down threads that aren't running
Oh, even simpler than I expected. Fixed in commit:55639dcd87fe985059355afe5fab787e4d139b11 (compile tested). Greg Farnum
11:12 AM Bug #1829 (Resolved): SimpleMessenger tries to shut down threads that aren't running
Saw this on benjamin yesterday. Looks like the OSD repeatedly restarted its messengers and was eventually unable to r... Greg Farnum

12/12/2011

04:45 PM Bug #1803: msgr: behave better when ending TCP connections
And I've flipped back and forth umpteen times today about what's going on. At this point I can conclude that nobody o... Greg Farnum
10:49 AM Bug #1803 (In Progress): msgr: behave better when ending TCP connections
From the little I'm reading in Unix Network Programming, it looks like we're just doing this wrong — we call shutdown... Greg Farnum

12/09/2011

11:18 AM Bug #1803: msgr: behave better when ending TCP connections
I'm going to see if I can handle this in userspace today — fixing it in the kernel client will be another ticket. Greg Farnum
11:13 AM Feature #1809 (New): msgr: limit simultaneous connections
Right now SimpleMessenger has no mechanism for limiting the number of simultaneous connections it holds open. This is... Greg Farnum

12/07/2011

05:20 PM Bug #1803: msgr: behave better when ending TCP connections
This actually caused a deadlock with ffsb on the kernel client - ffsb ended up with 1006 connections in the CLOSING s... Josh Durgin
04:56 PM Bug #1803 (Won't Fix): msgr: behave better when ending TCP connections
TV is telling me that if we're not confirming that each side of the connection calls ::shutdown() on the socket, we'r... Greg Farnum

12/01/2011

05:40 PM Bug #1747 (Need More Info): msgr: osd connection originates from wrong port
The blank address isn't a problem; it's due to the in_hbmsgr not being bound (deliberately). Unfortunately I've been ... Greg Farnum

11/30/2011

02:20 PM Bug #1747 (In Progress): msgr: osd connection originates from wrong port
The problem here is somewhere on osd.2 — osd.1 is using the address that osd.2 is providing, and you can see that osd... Greg Farnum

11/22/2011

09:40 PM Bug #1747 (Resolved): msgr: osd connection originates from wrong port
osd.2 sends a couple messages to osd.1:... Sage Weil
 

Also available in: Atom