CEPH filesystem development
 help / color / mirror / Atom feed
From: Noah Watkins <jayhawk@cs.ucsc.edu>
To: ceph-devel@vger.kernel.org
Subject: Re: Client receives 'connection refused' only after heavy use
Date: Sun, 04 Dec 2011 17:03:15 -0800	[thread overview]
Message-ID: <4EDC1853.5080405@cs.ucsc.edu> (raw)
In-Reply-To: <4EDC0ECF.60805@cs.ucsc.edu>

Yikes, I think this was actually the problem. nm

# ulimit -n
1024

-----

root@issdm-23:/var/log/ceph# grep -n  "Too many" full_conn_refused.log
2417924:2011-12-04 14:52:15.289873 7f1406ecb700 -- 
192.168.141.123:6800/1325 accepter no incoming connection?  sd = -1 
errno 24 Too many open files
2417925:2011-12-04 14:52:15.289923 7f1406ecb700 -- 
192.168.141.123:6800/1325 accepter no incoming connection?  sd = -1 
errno 24 Too many open files
2417926:2011-12-04 14:52:15.289952 7f1406ecb700 -- 
192.168.141.123:6800/1325 accepter no incoming connection?  sd = -1 
errno 24 Too many open files
2417927:2011-12-04 14:52:15.289970 7f1406ecb700 -- 
192.168.141.123:6800/1325 accepter no incoming connection?  sd = -1 
errno 24 Too many open files
2417928:2011-12-04 14:52:15.290002 7f1406ecb700 -- 
192.168.141.123:6800/1325 accepter no incoming connection?  sd = -1 
errno 24 Too many open files

On 12/04/2011 04:22 PM, Noah Watkins wrote:
> We are experiencing client connection problems that occur only after 
> some period of heavy use. Prior to the 'connection refused' error in 
> the client log the cluster behaves as normal. Restarting Ceph solves 
> the problem but we are not able to finish long jobs.
>
> Logs attached. I have the full 1 GB MDS log if needed, and included 
> only the portition of the log in which the client had problems plus 
> about 5 seconds of context on either side of the test.
>
> Thanks,
> Noah
>
> Client
> ====
> ...
> 2011-12-04 16:07:58.154523 7f4458314700 -- 192.168.141.123:0/1009375 
> >> 192.168.141.123:6800/1325 pipe(0x7f445437d020 sd=55 pgs=0 cs=0 
> l=0).connect 0
> 2011-12-04 16:07:58.154562 7f4458314700 -- 192.168.141.123:0/1009375 
> >> 192.168.141.123:6800/1325 pipe(0x7f445437d020 sd=55 pgs=0 cs=0 
> l=0).connecting to 192.168.141.123:6800/1325
> 2011-12-04 16:07:58.154605 7f4458314700 -- 192.168.141.123:0/1009375 
> >> 192.168.141.123:6800/1325 pipe(0x7f445437d020 sd=55 pgs=0 cs=0 
> l=0).connect error 192.168.141.123:6800/1325, 111: Connection refused
> 2011-12-04 16:07:58.154620 7f4458314700 -- 192.168.141.123:0/1009375 
> >> 192.168.141.123:6800/1325 pipe(0x7f445437d020 sd=55 pgs=0 cs=0 
> l=0).fault 111: Connection refused
> 2011-12-04 16:07:58.154635 7f4458314700 -- 192.168.141.123:0/1009375 
> >> 192.168.141.123:6800/1325 pipe(0x7f445437d020 sd=55 pgs=0 cs=0 
> l=0).fault waiting 3.200000
>
> Full logs attached.


  reply	other threads:[~2011-12-05  1:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-05  0:22 Client receives 'connection refused' only after heavy use Noah Watkins
2011-12-05  1:03 ` Noah Watkins [this message]
2011-12-05  4:47   ` Sage Weil
2011-12-05  6:22     ` Noah Watkins
2011-12-05 18:57     ` Noah Watkins
2011-12-05 19:03       ` Tommi Virtanen
2011-12-05 19:05         ` Noah Watkins
2011-12-05 19:11           ` Sage Weil
2011-12-05 19:36           ` Tommi Virtanen
2011-12-07  5:49             ` Gregory Farnum
2011-12-07 22:33               ` Gregory Farnum
2011-12-09  0:40                 ` Noah Watkins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EDC1853.5080405@cs.ucsc.edu \
    --to=jayhawk@cs.ucsc.edu \
    --cc=ceph-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox