Sur zimbra v8.8.10 (et 8.8.11) il existe un bug qui de mani\u00e8re \u00ab\u00a0al\u00e9atoire\u00a0\u00bb provoque une surcharge CPU sur les stores. Ensuite s’en suit un autre soucis sur les Proxy qui g\u00e8re mal la perte du sotre. Voici une correction au probl\u00e8me. <\/p>\n\n\n\n
Sur tous les Store : modification du fichier
\u201c\/opt\/zimbra\/common\/jetty_home\/etc\/jetty-monitor.xml\u201d en mettant tout en\u00a0
commentaire : <\/p>\n\n\n\n
<!–
<Call name=\u00a0\u00bbaddBean\u00a0\u00bb>
<Arg>
<New class=\u00a0\u00bborg.eclipse.jetty.monitor.ThreadMonitor\u00a0\u00bb>
<Set name=\u00a0\u00bbscanInterval\u00a0\u00bb>2000<\/Set>
<Set name=\u00a0\u00bbbusyThreshold\u00a0\u00bb>90<\/Set>
<Set name=\u00a0\u00bbstackDepth\u00a0\u00bb>3<\/Set>
<Set name=\u00a0\u00bbtrailLength\u00a0\u00bb>2<\/Set>
–>
<!– To enable logging CPU utilization for threads above specified\u00a0
threshold, –>
<!– uncomment the following lines, changing log interval (in\u00a0
milliseconds) –>
<!– and log threshold (in percent) as desired. –>
<!–
<Set name=\u00a0\u00bblogInterval\u00a0\u00bb>10000<\/Set>
<Set name=\u00a0\u00bblogThreshold\u00a0\u00bb>1<\/Set>
–>
<– To enable detail dump of the server whenever a thread is\u00a0
detected as spinning, –>
<– uncomment the following lines. –>
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<–
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<Set name=\u00a0\u00bbdumpable\u00a0\u00bb> <Ref refid=\u00a0\u00bbServer\u00a0\u00bb\/><\/Set>
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0–>
\u00a0 <\/p>\n\n\n\n
Restart du serveur. (zmcontrol restart suffit pas)<\/p>\n\n\n\n
Il faut aussi passer un hotfix pour les proxy : Sur zimbra v8.8.10 (et 8.8.11) il existe un bug qui de mani\u00e8re \u00ab\u00a0al\u00e9atoire\u00a0\u00bb provoque une surcharge CPU sur les stores.…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[6],"tags":[],"_links":{"self":[{"href":"http:\/\/blog.nosland.com\/index.php?rest_route=\/wp\/v2\/posts\/606"}],"collection":[{"href":"http:\/\/blog.nosland.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/blog.nosland.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/blog.nosland.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/blog.nosland.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=606"}],"version-history":[{"count":1,"href":"http:\/\/blog.nosland.com\/index.php?rest_route=\/wp\/v2\/posts\/606\/revisions"}],"predecessor-version":[{"id":607,"href":"http:\/\/blog.nosland.com\/index.php?rest_route=\/wp\/v2\/posts\/606\/revisions\/607"}],"wp:attachment":[{"href":"http:\/\/blog.nosland.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=606"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/blog.nosland.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=606"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/blog.nosland.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=606"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\u00a0\u00a0Sur les serveurs zproxy, installation via le yum d’un hotfix qui\u00a0
corrige les probl\u00e8mes de lenteurs sur les proxys quand un store est en\u00a0
carafe.
Explication du support Zimbra :
\u00ab\u00a0Fixed issue where Proxy does not failover to the next mailbox server if
the server is hung This issue is affecting Zimbra servers with\u00a0
zimbra-nginx version 1.7.1-1zimbra8.7b9. In a multiple node environment,\u00a0
proxy workers are getting stuck in a loop due to failure to connect to\u00a0
the lookup handler of a hung mailbox. This causes proxy to hang and it\u00a0
will not fallback to the next working mailbox server. After upgrading to\u00a0
zimbra-nginx version 1.7.1-1zimbra8.7b11, this issue will be resolved.\u00a0\u00bb<\/em> <\/p>\n","protected":false},"excerpt":{"rendered":"