Activity log for bug #1896125

Date Who What changed Old value New value Message
2020-09-17 21:12:56 Lance Bragstad bug added bug
2020-09-17 21:13:02 Lance Bragstad tags ldap
2020-09-17 21:24:31 Lance Bragstad description If you're using page_size [0] and are integrating keystone with an LDAP server that supports paging (like Active Directory), it's possible to see keystone memory footprint slowly increase over time. The problem isn't as noticable with large page sizes (e.g., page_size = 10000). But it's noticable when you use small page sizes (e.g., page_size = 5). I hit this issue using Active Directory with 10,000 users. I set my page_size to 5 and listed users continuously for an hour. During that time I noticed keystone's total memory consumption on the host increase from 5% to 14%. Additionally, the problem is exacerbated using page_size = 1. I was unsuccessful in reproducing this issue with FreeIPA, which is another LDAP implementation that doesn't support paging. Keystone automatically disables paging if the LDAP server doesn't support it. It seems there is a memory leak somewhere in keystone's LDAP paging implementation. [0] https://docs.openstack.org/keystone/latest/configuration/config-options.html#ldap.page_size If you're using page_size [0] and are integrating keystone with an LDAP server that supports paging (like Active Directory), it's possible to see keystone memory footprint slowly increase over time. The problem isn't as noticable with large page sizes (e.g., page_size = 10000). But it's noticable when you use small page sizes (e.g., page_size = 5). I hit this issue using Active Directory with 10,000 users. I set my page_size to 5 and listed users continuously for an hour. During that time I noticed keystone's total memory consumption on the host increase from 5% to 14%. Additionally, the problem is exacerbated using page_size = 1. I was unsuccessful in reproducing this issue with FreeIPA, which is another LDAP implementation, but it doesn't support paging. Keystone automatically disables paging if the LDAP server doesn't support it. It seems there is a memory leak somewhere in keystone's LDAP paging implementation. [0] https://docs.openstack.org/keystone/latest/configuration/config-options.html#ldap.page_size
2020-09-26 01:50:29 OpenStack Infra keystone: status New In Progress
2020-09-26 01:50:29 OpenStack Infra keystone: assignee Lance Bragstad (lbragstad)
2020-10-15 19:55:29 OpenStack Infra keystone: status In Progress Fix Released
2020-10-21 19:07:56 OpenStack Infra tags ldap in-stable-victoria ldap
2020-10-21 23:33:04 OpenStack Infra tags in-stable-victoria ldap in-stable-ussuri in-stable-victoria ldap
2020-11-17 01:54:01 OpenStack Infra tags in-stable-ussuri in-stable-victoria ldap in-stable-train in-stable-ussuri in-stable-victoria ldap