From: Eduardo K. <edu...@do...> - 2015-04-01 19:45:39
|
To make changes to the configuration file on the parameters mfsmaster.conf CHUNKS_SOFT_DEL_LIMIT CHUNKS_HARD_DEL_LIMIT these are not reflected in the graphs. Anyone have idea about it. -- ------------------------------------------------- Eduardo Kellenberger Departamento de Infraestructura Tecnológica DonWeb "La actitud es todo" Donweb.com Nota de confidencialidad: Este mensaje y archivos adjuntos al mismo son confidenciales, de uso exclusivo para el destinatario del mismo. La divulgación y/o uso del mismo sin autorización por parte de DonWeb.com queda prohibida. DonWeb.com no se hace responsable del mensaje por la falsificación y/o alteración del mismo. De no ser Ud el destinatario del mismo y lo ha recibido por error, por favor, notifique al remitente y elimínelo de su sistema. Confidentiality Note: This message and any attachments (the message) are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited by DonWeb.com. DonWeb.com shall not be liable for the message if altered or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender Nota de Confidencialidade: Esta mensagem e seus eventuais anexos podem conter dados confidenciais ou privilegiados. Se você os recebeu por engano ou não é um dos destinatários aos quais ela foi endereçada, por favor destrua-a e a todos os seus eventuais anexos ou copias realizadas, imediatamente. É proibida a retenção, distribuição, divulgação ou utilização de quaisquer informações aqui contidas. Por favor, informenos sobre o recebimento indevido desta mensagem, retornando-a para o autor. |
From: Aleksander W. <ale...@mo...> - 2015-04-02 08:33:43
|
Hello First of all I would like to explain what these parameters mean and how does it work: CHUNKS_SOFT_DEL_LIMIT - Soft maximum number of chunks being simultaneously deleted on one chunkserver (default is 10) CHUNKS_HARD_DEL_LIMIT - Hard maximum number of chunks being simultaneously deleted on one chunkserver (default is 25) MooseFS mainly uses the soft delete limit. If the system is able to remove all "to delete" chunks in one loop run, deletion limit will not be changed. But if the number of chunks to delete increase after a loop run, deletion limit will be increased by factor of 1.5 but never to a value higher than CHUNKS_HARD_DEL_LIMIT. This mechanism was implemented to prevent MooseFS cluster from freezing because of too many delete operations. So if you have small number of delete operations in your system hard limit will never be reached. How many files are you deleting in your system? Best regards Aleksander Wieliczko Technical Support Engineer MooseFS.com <moosefs.com> On 04/01/2015 09:48 PM, Eduardo Kellenberger wrote: > > To make changes to the configuration file on the parameters mfsmaster.conf > > CHUNKS_SOFT_DEL_LIMIT > CHUNKS_HARD_DEL_LIMIT > > these are not reflected in the graphs. > > Anyone have idea about it. > > > > |
From: Eduardo K. <edu...@do...> - 2015-04-06 11:58:12
|
Hi, thanks for your answer. The number of erasure is variable, I neesito is that from 8am to 11pm files are not deleted, or the least amount is removed to prevent overloading of chunckserver and between 11pm and 8am deletion rise. This I could control with version 1.6 but with the 2 EC no. best regard, Eduardo Kellenberger El Jueves 02 abril 2015 10:33:34 Aleksander Wieliczko escribió: > Hello > First of all I would like to explain what these parameters mean and how > does it work: > > CHUNKS_SOFT_DEL_LIMIT - Soft maximum number of chunks being > simultaneously deleted on one chunkserver (default is 10) > CHUNKS_HARD_DEL_LIMIT - Hard maximum number of chunks being > simultaneously deleted on one chunkserver (default is 25) > > MooseFS mainly uses the soft delete limit. If the system is able to > remove all "to delete" chunks in one loop run, deletion limit will not > be changed. > But if the number of chunks to delete increase after a loop run, > deletion limit will be increased by factor of 1.5 but never to a value > higher than CHUNKS_HARD_DEL_LIMIT. > > This mechanism was implemented to prevent MooseFS cluster from freezing > because of too many delete operations. > So if you have small number of delete operations in your system hard > limit will never be reached. > > How many files are you deleting in your system? -- ------------------------------------------------- Eduardo Kellenberger Departamento de Infraestructura Tecnológica DonWeb "La actitud es todo" Donweb.com Nota de confidencialidad: Este mensaje y archivos adjuntos al mismo son confidenciales, de uso exclusivo para el destinatario del mismo. La divulgación y/o uso del mismo sin autorización por parte de DonWeb.com queda prohibida. DonWeb.com no se hace responsable del mensaje por la falsificación y/o alteración del mismo. De no ser Ud el destinatario del mismo y lo ha recibido por error, por favor, notifique al remitente y elimínelo de su sistema. Confidentiality Note: This message and any attachments (the message) are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited by DonWeb.com. DonWeb.com shall not be liable for the message if altered or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender Nota de Confidencialidade: Esta mensagem e seus eventuais anexos podem conter dados confidenciais ou privilegiados. Se você os recebeu por engano ou não é um dos destinatários aos quais ela foi endereçada, por favor destrua-a e a todos os seus eventuais anexos ou copias realizadas, imediatamente. É proibida a retenção, distribuição, divulgação ou utilização de quaisquer informações aqui contidas. Por favor, informenos sobre o recebimento indevido desta mensagem, retornando-a para o autor. |
From: Steve W. <st...@pu...> - 2015-04-06 12:21:33
|
Perhaps you could have a cron job that would run every day at 8 a.m. and another one at 11 p.m. The 8 a.m. cron job would create a symbolic link from /etc/mfs/mfsmaster.cfg to /etc/mfs/mfsmaster-day.cfg and then send a signal to the mfsmaster to reload its configuration. And similarly, the 11 p.m. cron job would create a symbolic link from /etc/mfs/mfsmaster.cfg to /etc/mfs/mfsmaster-night.cfg and send a reload signal to mfsmaster. The two different config files would, of course, have the two different settings that you want, one for the daytime hours and another for the nighttime hours. Steve On 04/06/2015 08:01 AM, Eduardo Kellenberger wrote: > Hi, thanks for your answer. > > The number of erasure is variable, I neesito is that from 8am to 11pm files are not deleted, or the least amount is removed to prevent overloading of chunckserver and between 11pm and 8am deletion rise. > > This I could control with version 1.6 but with the 2 EC no. > > > best regard, > > Eduardo Kellenberger > > > > > > El Jueves 02 abril 2015 10:33:34 Aleksander Wieliczko escribió: >> Hello >> First of all I would like to explain what these parameters mean and how >> does it work: >> >> CHUNKS_SOFT_DEL_LIMIT - Soft maximum number of chunks being >> simultaneously deleted on one chunkserver (default is 10) >> CHUNKS_HARD_DEL_LIMIT - Hard maximum number of chunks being >> simultaneously deleted on one chunkserver (default is 25) >> >> MooseFS mainly uses the soft delete limit. If the system is able to >> remove all "to delete" chunks in one loop run, deletion limit will not >> be changed. >> But if the number of chunks to delete increase after a loop run, >> deletion limit will be increased by factor of 1.5 but never to a value >> higher than CHUNKS_HARD_DEL_LIMIT. >> >> This mechanism was implemented to prevent MooseFS cluster from freezing >> because of too many delete operations. >> So if you have small number of delete operations in your system hard >> limit will never be reached. >> >> How many files are you deleting in your system? |
From: Krzysztof K. <krz...@mo...> - 2015-04-06 17:33:22
|
Dear Eduardo, We'll look at this issue definitely tomorrow. It should be possible to change those parameters in MooseFS version 2.0. Best Regards, Krzysztof Kielak Director of Operations and Customer Support Mobile: +48 601 476 440 -----Original Message----- From: Eduardo Kellenberger [mailto:edu...@do...] Sent: Monday, April 6, 2015 2:02 PM To: Aleksander Wieliczko Cc: moo...@li... Subject: Re: [MooseFS-Users] CHUNKS_SOFT_DEL_LIMIT and CHUNKS_HARD_DEL_LIMIT on moosefs ce Hi, thanks for your answer. The number of erasure is variable, I neesito is that from 8am to 11pm files are not deleted, or the least amount is removed to prevent overloading of chunckserver and between 11pm and 8am deletion rise. This I could control with version 1.6 but with the 2 EC no. best regard, Eduardo Kellenberger El Jueves 02 abril 2015 10:33:34 Aleksander Wieliczko escribió: > Hello > First of all I would like to explain what these parameters mean and > how does it work: > > CHUNKS_SOFT_DEL_LIMIT - Soft maximum number of chunks being > simultaneously deleted on one chunkserver (default is 10) > CHUNKS_HARD_DEL_LIMIT - Hard maximum number of chunks being > simultaneously deleted on one chunkserver (default is 25) > > MooseFS mainly uses the soft delete limit. If the system is able to > remove all "to delete" chunks in one loop run, deletion limit will not > be changed. > But if the number of chunks to delete increase after a loop run, > deletion limit will be increased by factor of 1.5 but never to a value > higher than CHUNKS_HARD_DEL_LIMIT. > > This mechanism was implemented to prevent MooseFS cluster from > freezing because of too many delete operations. > So if you have small number of delete operations in your system hard > limit will never be reached. > > How many files are you deleting in your system? -- ------------------------------------------------- Eduardo Kellenberger Departamento de Infraestructura Tecnológica DonWeb "La actitud es todo" Donweb.com Nota de confidencialidad: Este mensaje y archivos adjuntos al mismo son confidenciales, de uso exclusivo para el destinatario del mismo. La divulgación y/o uso del mismo sin autorización por parte de DonWeb.com queda prohibida. DonWeb.com no se hace responsable del mensaje por la falsificación y/o alteración del mismo. De no ser Ud el destinatario del mismo y lo ha recibido por error, por favor, notifique al remitente y elimínelo de su sistema. Confidentiality Note: This message and any attachments (the message) are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited by DonWeb.com. DonWeb.com shall not be liable for the message if altered or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender Nota de Confidencialidade: Esta mensagem e seus eventuais anexos podem conter dados confidenciais ou privilegiados. Se você os recebeu por engano ou não é um dos destinatários aos quais ela foi endereçada, por favor destrua-a e a todos os seus eventuais anexos ou copias realizadas, imediatamente. É proibida a retenção, distribuição, divulgação ou utilização de quaisquer informações aqui contidas. Por favor, informenos sobre o recebimento indevido desta mensagem, retornando-a para o autor. ---------------------------------------------------------------------------- -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _________________________________________ moosefs-users mailing list moo...@li... https://lists.sourceforge.net/lists/listinfo/moosefs-users |
From: Eduardo K. <edu...@do...> - 2015-04-06 17:43:48
|
Krzysztof Kielak, thank you!! Best Regards, Eduardo Kellenberger El Lunes 06 abril 2015 19:33:17 Krzysztof Kielak escribió: > Dear Eduardo, > > We'll look at this issue definitely tomorrow. It should be possible to > change those parameters in MooseFS version 2.0. > > Best Regards, > Krzysztof Kielak > Director of Operations and Customer Support > Mobile: +48 601 476 440 > > -----Original Message----- > From: Eduardo Kellenberger [mailto:edu...@do...] > Sent: Monday, April 6, 2015 2:02 PM > To: Aleksander Wieliczko > Cc: moo...@li... > Subject: Re: [MooseFS-Users] CHUNKS_SOFT_DEL_LIMIT and CHUNKS_HARD_DEL_LIMIT > on moosefs ce > > Hi, thanks for your answer. > > The number of erasure is variable, I neesito is that from 8am to 11pm files > are not deleted, or the least amount is removed to prevent overloading of > chunckserver and between 11pm and 8am deletion rise. > > This I could control with version 1.6 but with the 2 EC no. > > > best regard, > > Eduardo Kellenberger > > > > > > El Jueves 02 abril 2015 10:33:34 Aleksander Wieliczko escribió: > > Hello > > First of all I would like to explain what these parameters mean and > > how does it work: > > > > CHUNKS_SOFT_DEL_LIMIT - Soft maximum number of chunks being > > simultaneously deleted on one chunkserver (default is 10) > > CHUNKS_HARD_DEL_LIMIT - Hard maximum number of chunks being > > simultaneously deleted on one chunkserver (default is 25) > > > > MooseFS mainly uses the soft delete limit. If the system is able to > > remove all "to delete" chunks in one loop run, deletion limit will not > > be changed. > > But if the number of chunks to delete increase after a loop run, > > deletion limit will be increased by factor of 1.5 but never to a value > > higher than CHUNKS_HARD_DEL_LIMIT. > > > > This mechanism was implemented to prevent MooseFS cluster from > > freezing because of too many delete operations. > > So if you have small number of delete operations in your system hard > > limit will never be reached. > > > > How many files are you deleting in your system? > > -- > ------------------------------------------------- > Eduardo Kellenberger > Departamento de Infraestructura Tecnológica DonWeb "La actitud es todo" > Donweb.com > > Nota de confidencialidad: Este mensaje y archivos adjuntos al mismo son > confidenciales, de uso exclusivo para el destinatario del mismo. La > divulgación y/o uso del mismo sin autorización por parte de DonWeb.com queda > prohibida. > DonWeb.com no se hace responsable del mensaje por la falsificación y/o > alteración del mismo. > De no ser Ud el destinatario del mismo y lo ha recibido por error, por > favor, notifique al remitente y elimínelo de su sistema. > > Confidentiality Note: This message and any attachments (the message) are > confidential and intended solely for the addressees. Any unauthorised use or > dissemination is prohibited by DonWeb.com. > DonWeb.com shall not be liable for the message if altered or falsified. > If you are not the intended addressee of this message, please cancel it > immediately and inform the sender > > Nota de Confidencialidade: Esta mensagem e seus eventuais anexos podem > conter dados confidenciais ou privilegiados. > Se você os recebeu por engano ou não é um dos destinatários aos quais ela > foi endereçada, por favor destrua-a e a todos os seus eventuais anexos ou > copias realizadas, imediatamente. > É proibida a retenção, distribuição, divulgação ou utilização de quaisquer > informações aqui contidas. > > Por favor, informenos sobre o recebimento indevido desta mensagem, > retornando-a para o autor. > > > ---------------------------------------------------------------------------- > -- > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your > own process in accordance with the BPMN 2 standard Learn Process modeling > best practices with Bonita BPM through live exercises > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF > > _________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users > -- ------------------------------------------------- Eduardo Kellenberger Departamento de Infraestructura Tecnológica DonWeb "La actitud es todo" Donweb.com Nota de confidencialidad: Este mensaje y archivos adjuntos al mismo son confidenciales, de uso exclusivo para el destinatario del mismo. La divulgación y/o uso del mismo sin autorización por parte de DonWeb.com queda prohibida. DonWeb.com no se hace responsable del mensaje por la falsificación y/o alteración del mismo. De no ser Ud el destinatario del mismo y lo ha recibido por error, por favor, notifique al remitente y elimínelo de su sistema. Confidentiality Note: This message and any attachments (the message) are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited by DonWeb.com. DonWeb.com shall not be liable for the message if altered or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender Nota de Confidencialidade: Esta mensagem e seus eventuais anexos podem conter dados confidenciais ou privilegiados. Se você os recebeu por engano ou não é um dos destinatários aos quais ela foi endereçada, por favor destrua-a e a todos os seus eventuais anexos ou copias realizadas, imediatamente. É proibida a retenção, distribuição, divulgação ou utilização de quaisquer informações aqui contidas. Por favor, informenos sobre o recebimento indevido desta mensagem, retornando-a para o autor. |
From: Krzysztof K. <krz...@mo...> - 2015-04-07 21:00:47
|
Dear Eduardo, We have tested to confirm that both parameters (CHUNKS_SOFT_DEL_LIMIT and CHUNKS_HARD_DEL_LIMIT) work as expected in MooseFS 2.0, but by design it works quite different than it was in MooseFS 1.6. * in MooseFS 1.6.x defined limits define how many deletions per second might be performed by any chunkserver * in MooseFS 2.0.x and above the limits define how many concurrent deletions might be running by chunkserver The tests that we have performed show that even with the parameters set to the lowest values (CHUNKS_SOFT_DEL_LIMIT=1, CHUNKS_HARD_DEL_LIMIT=2) we were able to see almost 17k deletions per minute on a three node MooseFS 2.0 instance. This translates to ~95 deletions per second per chunkserver in MooseFS 1.6.x. world - probably you don’t have so much deletions and that’s why you don’t see the difference when changing the profiles. MooseFS 2.0.x changed the way it interprets the parameters and the way it handles deletions. At the moment it’s not event possible to limit deletions as in MooseFS 1.6.x. Generally speaking MooseFS 2.0 employs improved algorithms for chunks deletions and can handle much more deletions without significant impact on overall system performance. Do you see any performance problems with deletions on your MooseFS 2.0.x system or you are just concerned that the behaviour changed after the upgrade? Best Regards, Krzysztof Kielak Director of Operations and Customer Support Mobile: +48 601 476 440 |
From: Eduardo K. <edu...@do...> - 2015-04-30 17:38:56
|
Dear Krzysztof Kielak, I do not have performance problems, I've only seen the change and caught my attention. Best Regards, Eduardo El Martes 07 abril 2015 23:00:36 Krzysztof Kielak escribió: > Do you see any performance problems with deletions on your MooseFS 2.0.x system or you are just concerned that the behaviour changed after the upgrade? -- ------------------------------------------------- Eduardo Kellenberger Departamento de Infraestructura Tecnológica DonWeb "La actitud es todo" Donweb.com Nota de confidencialidad: Este mensaje y archivos adjuntos al mismo son confidenciales, de uso exclusivo para el destinatario del mismo. La divulgación y/o uso del mismo sin autorización por parte de DonWeb.com queda prohibida. DonWeb.com no se hace responsable del mensaje por la falsificación y/o alteración del mismo. De no ser Ud el destinatario del mismo y lo ha recibido por error, por favor, notifique al remitente y elimínelo de su sistema. Confidentiality Note: This message and any attachments (the message) are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited by DonWeb.com. DonWeb.com shall not be liable for the message if altered or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender Nota de Confidencialidade: Esta mensagem e seus eventuais anexos podem conter dados confidenciais ou privilegiados. Se você os recebeu por engano ou não é um dos destinatários aos quais ela foi endereçada, por favor destrua-a e a todos os seus eventuais anexos ou copias realizadas, imediatamente. É proibida a retenção, distribuição, divulgação ou utilização de quaisquer informações aqui contidas. Por favor, informenos sobre o recebimento indevido desta mensagem, retornando-a para o autor. |