[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[EP-tech] indexer stalls part 2



Hi all!

using this guide: 
http://unix.stackexchange.com/questions/116849/why-load-is-high-despite-the-fact-that-neither-cpu-or-disk-is-overused/116865#116865

I've found the problem:

top - 13:30:26 up 349 days, 17 min,  4 users,  load average: 2.01, 1.83, 
1.49
Tasks: 155 total,   2 running, 153 sleeping,   0 stopped,   0 zombie
Cpu(s):  3.0%us,  0.2%sy,  0.0%ni, 71.6%id, 25.3%wa,  0.0%hi, 0.0%si,  
0.0%st
Mem:   8388608k total,  8120380k used,   268228k free,    54460k buffers
Swap:  2093048k total,        0k used,  2093048k free,  5445200k cached

   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+ WCHAN     
COMMAND
  6514 mysql     17   0  608m 150m 5788 D  0.0  1.8   0:05.73 sync_page 
mysqld

this mysql thread stay blocked in D state forever (I don't know what is 
doing really), thus the high I/O.

More info when I'll find more infos.

Il 03/02/2016 22:29, yurj at alfa.it ha scritto:
> Il 2016-02-03 11:13 martin.braendle at id.uzh.ch ha scritto:
>> Hi Yuri,
>
>>   - Our experience is that the indexer rather is slowed down by too
>> many entries in the event table, especially if there are some which
>> are ancient (several weeks or months old). See Manage records > Tasks
>> . Removing old tasks will help a lot.
>>
> This really solved the problem, removing the queue of item to index lead
> to a normal load. I would like to know why :-D
>
> Thanks!
> *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
> *** Archive: http://www.eprints.org/tech.php/
> *** EPrints community wiki: http://wiki.eprints.org/
> *** EPrints developers Forum: http://forum.eprints.org/