Re: [7.0.2] problems with spinlock under FreeBSD?
От | The Hermit Hacker |
---|---|
Тема | Re: [7.0.2] problems with spinlock under FreeBSD? |
Дата | |
Msg-id | Pine.BSF.4.21.0008241625080.801-100000@thelab.hub.org обсуждение исходный текст |
Ответ на | Re: [7.0.2] problems with spinlock under FreeBSD? (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [7.0.2] problems with spinlock under FreeBSD?
Re: [7.0.2] problems with spinlock under FreeBSD? |
Список | pgsql-hackers |
okay, I just doubled my FDs to 8192 from 4136 and will watch things ... anyone know of a way of telling how many are currently in use, and where they peaked? somethign similar to 'netstat -m' showing mbufs? thanks tom ... On Thu, 24 Aug 2000, Tom Lane wrote: > The Hermit Hacker <scrappy@hub.org> writes: > > you still have your account on that machine if you want to take a quick > > look around ... else, anything else I should be looking at? > > I poked around and couldn't learn much of anything --- the logfiles from > yesterday are already gone, apparently. I did find some interesting > entries in today's logfiles: > > %grep Lru * > 5432.61820:FATAL 1: ReleaseLruFile: No open files available to be closed > postmaster.5437.36290:FATAL 1: ReleaseLruFile: No open files available to be closed > postmaster.5437.62218:FATAL 1: ReleaseLruFile: No open files available to be closed > > What we see here are backends choking because there are no free kernel > file descriptor slots, even after they've closed *all* of their own > discretionary FDs. So you've definitely got a serious problem with > insufficient FD slots. Time to tweak those kernel parameters. > > I still don't see a linkage between too few FDs and the stuck-spinlock > crashes, but maybe there is one. > > regards, tom lane > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
В списке pgsql-hackers по дате отправления: