From: Michał B. <mic...@co...> - 2012-04-20 19:07:34
|
Do you have this problem with only one chunk server or with each of them? If with one you should check its performance, charts, hard disk operation times, etc. in the CGI monitor. You may experiment with CHUNKS_WRITE_REP_LIMIT and CHUNKS_READ_REP_LIMIT options. Kind regards Michał Borychowski MooseFS Support Manager -----Original Message----- From: Elliot Finley [mailto:efi...@gm...] Sent: Thursday, April 19, 2012 12:57 AM To: moo...@li... Subject: [Moosefs-users] write to chunkservers timing out - too much load? I get a steady stream of: 'file: NNN, index: NNN, chunk: NNN, version: NNN - writeworker: connection with (XXXXXXXX:PPPP) was timed out (unfinished writes: Y; try counter: Z)' Where Y is usually 1 or 2 and Z is almost always 1. From the FAQ, I know this is informational and not an error. My question is: If I'm getting a steady stream of these, is it because I've got too much load on my chunkservers (i.e. too many network connections, too many pending writes?) Would adding more chunkservers alleviate this situation? MFS seems to only use 10 write threads on a chunkserver. Would it make sense to increase the number of write threads to equal the number of disks on the chunkserver? Most of my chunkservers have 16 disks. One of them has 36 disks. TIA, Elliot ---------------------------------------------------------------------------- -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ moosefs-users mailing list moo...@li... https://lists.sourceforge.net/lists/listinfo/moosefs-users |