Bug 1170706
| Summary: | cos_cache_build_definition_list does not stop during server shutdown | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | mreynolds |
| Component: | 389-ds-base | Assignee: | Noriko Hosoi <nhosoi> |
| Status: | CLOSED ERRATA | QA Contact: | Viktor Ashirov <vashirov> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.6 | CC: | amsharma, jgalipea, nkinder, rmeggins |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 389-ds-base-1.2.11.15-51.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: The COS cache rebuild process does not check for a server shutdown.
Consequence: The server can take a very long time to shutdown depending on how many COS templates/definitions there are.
Fix: Check for shutdown and abort the COS cache rebuild.
Result: The server shutsdown in a reasonable amount of time even if the cache is being rebuilt.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-07-22 06:36:25 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
mreynolds
2014-12-04 16:19:44 UTC
Fixed upstream. Verification is a little tricky, this was originally reproduced with customer specific data that had over 4500 COS templates. [1] Setup DS [2] Add 4500 COS templates [3] Modify 1 template [4] Stop the server. The server should stop with 30 seconds /usr/lib64/mozldap/ldapmodify -a -p 389 -h localhost -D cn=directory manager -w Secret123 -f /export/cos1.ldif
adding new entry cn=cosTemplateExample6,ou=People,dc=example,dc=com
/usr/lib64/mozldap/ldapmodify -a -p 389 -h localhost -D cn=directory manager -w Secret123 -f /export/cos1.ldif
adding new entry cn=cosTemplateExample5,ou=People,dc=example,dc=com
/usr/lib64/mozldap/ldapmodify -a -p 389 -h localhost -D cn=directory manager -w Secret123 -f /export/cos1.ldif
adding new entry cn=cosTemplateExample4,ou=People,dc=example,dc=com
/usr/lib64/mozldap/ldapmodify -a -p 389 -h localhost -D cn=directory manager -w Secret123 -f /export/cos1.ldif
adding new entry cn=cosTemplateExample3,ou=People,dc=example,dc=com
/usr/lib64/mozldap/ldapmodify -a -p 389 -h localhost -D cn=directory manager -w Secret123 -f /export/cos1.ldif
adding new entry cn=cosTemplateExample2,ou=People,dc=example,dc=com
/usr/lib64/mozldap/ldapmodify -a -p 389 -h localhost -D cn=directory manager -w Secret123 -f /export/cos1.ldif
adding new entry cn=cosTemplateExample1,ou=People,dc=example,dc=com
/usr/lib64/mozldap/ldapmodify -a -p 389 -h localhost -D cn=directory manager -w Secret123 -f /export/cos1.ldif
[root@qe-blade-09 export]# ldapmodify -x -D "cn=Directory Manager" -w Secret123 -p 389 -h localhost << EOF
> dn: cn=cosTemplateExample4000,ou=People,dc=example,dc=com
> changetype: modify
> replace: st
> st: AND
> EOF
modifying entry "cn=cosTemplateExample4000,ou=People,dc=example,dc=com"
[root@qe-blade-09 export]# time service dirsrv stop
Shutting down dirsrv:
qe-blade-09...[ OK ]
real 0m1.051s
user 0m0.018s
sys 0m0.024s
Hence VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-1326.html |