|
David to answer your Q , the idea is to have the www existing idle connections being reused, so I think the access analyzer(logconv) advice to increase the idle timeout ldap may be misleading in this case and we are debating if we should turn off in and only cfg idle timeout on www pool side . From: Ghiurea, Isabella
Sent: Wednesday, June 27, 2018 12:50 PM To: 389-users@xxxxxxxxxxxxxxxxxxxxxxx Subject: tunning DS for idle timeout exceeded Hi List we are running 389-ds-base-1.3.5.15-1.fc24.x86_64 ( OS -FC24) analyzing access log file today , I am seeing for each of the client T1 msg, our applications are using www pools connection to ldap we have a large number of hosts cfg for min and max pools size , most of connections are always in a open/idle state
to be reused by the client. Initial I had nssldap-idletimeout set to 120 sec, but today I went and increase by factor of 2 in hope to eliminate this T1 msg but no luck so far , the number of file descriptor is set to 4096. Here is one sample from access log output, I 'm looking to get some input how to tune DS to eliminate T1 message Client 6:...... 88 - Connections
|
_______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx/message/PRKD5RYGXBLQXCIDFNXH5WODZQNV46NU/
