From: Markus K. <mar...@tu...> - 2020-09-10 05:51:14
|
On Tuesday, 8 September 2020 09:04:50 CEST Agata Kruszona-Zawadzka wrote: > W dniu 07.09.2020 o 15:17, Markus Köberl pisze: > > On Monday, 7 September 2020 12:19:42 CEST Agata Kruszona-Zawadzka wrote: > >> > >> W dniu 04.09.2020 o 15:22, Markus Köberl pisze: > >>> Since some time (last few versions of MooseFS) on a few chunkservers the used space grows above the default ACCEPTABLE_PERCENTAGE_DIFFERENCE = 1.0 till I restart the affected chunkserver. > >>> On the webinterface i see huge numbers for overgoal (even 4 extra copies). After the restart of the chunkserver the overgoal goes down but starts growing again after some time. > >> > >> We have an issue in MooseFS currently, where on disks with I/O errors in > >> certain circustances some chunks get locked and cannot be deleted until > >> the whole chunk server process is restarted. We introduced a fix for > >> that, it's gonna be available in version 3.0.115. The issue does not > >> affect disks without I/O errors. > > > > Thanks good to hear that a fix might be on the way. > > > > Could it be that instead of "some chunks get locked and cannot be deleted" that there a no deletes at all on this chunk server, or might that be a different problem? > > Yes, that's exactly it. By "some chunks" I meant that not every chunk is > able to trigger the problem, but once it happens so that enough chunks > do, then, due to operation limits (specifically deletions limit in this > instance), the system won't attempt to delete any more chunks. Thank you for confirming that it is the same problem and the good explanation. regards Markus Köberl -- Markus Koeberl Graz University of Technology Signal Processing and Speech Communication Laboratory E-mail: mar...@tu... |