<html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">On 22/07/15 16:52, Ludwig Krispenz wrote: </div> <blockquote cite="mid:55AFAE46.4000008@redhat.com" type="cite"> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> <div class="moz-cite-prefix">On 07/22/2015 03:56 PM, Martin Basti wrote: </div> <blockquote cite="mid:55AFA115.2050404@redhat.com" type="cite">Hello all, I attached WIP patch to solve <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://fedorahosted.org/freeipa/ticket/4949">https://fedorahosted.org/freeipa/ticket/4949</a> I received several suggestions: 1) (implemented in patch) is to add the option --db-locks to installer (maybe as hidden option) 2) Configure the nsslapd-db-locks to higher value as default (what is the right value?) </blockquote> this is a good question, I just looked into the ticket and the BZ, but don't understand WHY it is running out of locks. I think adding the option is ok to be prepared, but I would not change the default before undestanding the reason for the lock consumtion and a relation to the data. Maybe we can also reduce the number of locks needed - do you have a setup to show this failure ? </blockquote> I don't have any setup, Petr1 did any testing with huge amount of user, he may have got some VMs. <blockquote cite="mid:55AFAE46.4000008@redhat.com" type="cite"> <blockquote cite="mid:55AFA115.2050404@redhat.com" type="cite"> 3) Combination of 1and 2: set default higher value and also have hidden option to allow configure higher number of locks during install Comments are more than welcome :-) <fieldset class="mimeAttachmentHeader"></fieldset> </blockquote> <fieldset class="mimeAttachmentHeader"></fieldset> </blockquote> <pre class="moz-signature" cols="72">-- Martin Basti</pre> </body> </html>