Thread: Strange/random overload of the server
Hi,
I have some strange problems with my server.
Randomly the server gets overloaded with queries.
Queries are accepted and never executed, thus reaching max_connections limit .
This I/O wait in top command reaches up to 90%
Couple of restarts (and sometimes vacuum and reindex of my biggest tables) fix it for a while (about a week or so).
I suspected full-text indexes going wild, but after i dropping indexes i had same issues again.
I found that file system have errors. Can this lead to this kind of behavior ?
I am planning downtime to fix the FS errors since this can't be done on mounted file systems.
Any ideas ?
I have some strange problems with my server.
Randomly the server gets overloaded with queries.
Queries are accepted and never executed, thus reaching max_connections limit .
This I/O wait in top command reaches up to 90%
Couple of restarts (and sometimes vacuum and reindex of my biggest tables) fix it for a while (about a week or so).
I suspected full-text indexes going wild, but after i dropping indexes i had same issues again.
I found that file system have errors. Can this lead to this kind of behavior ?
I am planning downtime to fix the FS errors since this can't be done on mounted file systems.
Any ideas ?
On Thu, Sep 2, 2010 at 8:14 AM, Georgi Ivanov <georgi.r.ivanov@gmail.com> wrote: > Hi, > I have some strange problems with my server. > > Randomly the server gets overloaded with queries. > Queries are accepted and never executed, thus reaching max_connections limit > . > This I/O wait in top command reaches up to 90% > Couple of restarts (and sometimes vacuum and reindex of my biggest tables) > fix it for a while (about a week or so). > I suspected full-text indexes going wild, but after i dropping indexes i had > same issues again. > I found that file system have errors. Can this lead to this kind of behavior > ? Yes. > I am planning downtime to fix the FS errors since this can't be done on > mounted file systems. Sounds like you're headed in the right direction. Note that it's possible your db is corrupted and you'll need to restore from a previous known good backup if you've been having file system problems. -- To understand recursion, one must first understand recursion.
On Thu, Sep 2, 2010 at 5:25 PM, Scott Marlowe <scott.marlowe@gmail.com> wrote: > On Thu, Sep 2, 2010 at 8:14 AM, Georgi Ivanov <georgi.r.ivanov@gmail.com> wrote: >> Hi, >> I have some strange problems with my server. >> >> Randomly the server gets overloaded with queries. >> Queries are accepted and never executed, thus reaching max_connections limit >> . >> This I/O wait in top command reaches up to 90% >> Couple of restarts (and sometimes vacuum and reindex of my biggest tables) >> fix it for a while (about a week or so). >> I suspected full-text indexes going wild, but after i dropping indexes i had >> same issues again. >> I found that file system have errors. Can this lead to this kind of behavior >> ? > > Yes. Your disk might be broken. Check the SMART status. Groeten, Arjen Nienhuis