Hello, On Fri, Apr 15, 2022 at 7:39 AM 刘孟 <liumeng@xxxxxxxxxxxxxx> wrote: > > During the peak hours of the company's internal servers, the number of sub processes(hpptd) of > each server is about 1000,[Maxconnectionsperchild] is currently set to 0. In order to be able to > resolve the access target regularlyIn DNS, we plan to adjust the value of [maxconnectionsperchild] > to make each child process in half a day that It can be restarted once. > > My question is After setting this parameter, if it is possible that 1000 processes are arrive at the same time > resulting in service interruption? I suppose that you worry about 1000 processes restarting at the same time hence all issuing DNS requests (which could disrupt the DNS service)? If so it is very unlikely that MaxConnectionsPerChild triggers at the same time on all the children processes because the clients connections themselves will not have the same lifetime (including keep-alive in between requests). In my opinion the risk is negligible. > > Current server setting of [maxsparechlid = 20] and [minspareechlid = 10] > If [maxconnectionsperchild] is set, should the settings of these two values be adjusted synchronously (I suppose you are referring to MaxSpareServers and MinSpareServers here) If the peak is around 1000 connections then MaxSpareServers 20 is probably to low, if the load fluctuates a little httpd will keep stopping and recreating the processes all the peak time (there are 980 processes above the limit from its point of vue..). I don't think MaxSpareServers is a good fit for your goal of restarting processes at least twice a day anyway, you probably should raise it to something more close to MaxRequestWorkers for efficiency. While MaxConnectionsPerChild can help in lowering/restoring the number of processes after the peak, it's not ideal either for restarting processes in synchronization with your DNS because there can still be processes that are restarted just before the DNS have switched and they will not work until MaxConnectionsPerChild have failed.. Did you think of a cron job (or a trigger) that explicitely restart httpd (gracefuly) just after the DNS have switched? Regards; Yann. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|