Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

After a failed online import the next imports are very slow #4432

Closed
mreynolds389 opened this issue Nov 11, 2020 · 2 comments
Closed

After a failed online import the next imports are very slow #4432

mreynolds389 opened this issue Nov 11, 2020 · 2 comments
Assignees
@mreynolds389
Milestone
1.4.3

Comments

@mreynolds389
Copy link
Contributor

Issue Description

If you attempt to do an online import and entert he wrong LDIF name that import will fail. When you try it again with the correct LDIF name the import becomes very slow.

Reproducible steps:

[1] Attempt an import with a typo in the LDIF file name so that the import fails:

     # dsconf slapd-localhost backend import userroot 1mil-typo.ldif

[2] Fix the typo and do the import:

     # dsconf localhost backend import userroot 1mil.ldif

[02/Nov/2020:16:44:06.244158418 -0500] - INFO - import_monitor_threads - import userroot: Processed 58 entries -- average rate 2.9/sec, recent rate 2.9/sec, hit ratio 0%
[02/Nov/2020:16:44:26.281630749 -0500] - INFO - import_monitor_threads - import userroot: Processed 108 entries -- average rate 2.7/sec, recent rate 2.7/sec, hit ratio 100%
[02/Nov/2020:16:44:46.314696042 -0500] - INFO - import_monitor_threads - import userroot: Processed 158 entries -- average rate 2.6/sec, recent rate 2.5/sec, hit ratio 100%
...

[3] Restart the server, and try the import again:

[02/Nov/2020:16:51:19.259511417 -0500] - INFO - import_monitor_threads - import userroot: Processed 85095 entries -- average rate 4254.8/sec, recent rate 4254.7/sec, hit ratio 0%
[02/Nov/2020:16:51:39.516911186 -0500] - INFO - import_monitor_threads - import userroot: Processed 153041 entries -- average rate 3825.9/sec, recent rate 3825.9/sec, hit ratio 97%
[02/Nov/2020:16:51:59.708787576 -0500] - INFO - import_monitor_threads - import userroot: Processed 217130 entries -- average rate 3618.8/sec, recent rate 3300.9/sec, hit ratio 96%
@mreynolds389 mreynolds389 added this to the 1.4.3 milestone Nov 11, 2020
@mreynolds389 mreynolds389 self-assigned this Nov 11, 2020
@mreynolds389 mreynolds389 mentioned this issue Nov 11, 2020
Merged
mreynolds389 added a commit to mreynolds389/389-ds-base that referenced this issue Nov 12, 2020
@mreynolds389
Issue 4432 - After a failed online import the next imports are very slow
ecf3b07 
Bug Description:  When an online import fails the entry and DN caches are
                  "reset", but we use the wrong "new maxsize" which was
                  setting the entry cache maxsize to zero which killed the
                  import performance.

Fix Description:  When resetting the caches use the previous cache maxsize.

Relates: 389ds#4432

Reviewed by: firstyear & progier(Thanks!!)
mreynolds389 added a commit that referenced this issue Nov 12, 2020
@mreynolds389
Issue 4432 - After a failed online import the next imports are very slow
4e99d89 
Bug Description:  When an online import fails the entry and DN caches are
                  "reset", but we use the wrong "new maxsize" which was
                  setting the entry cache maxsize to zero which killed the
                  import performance.

Fix Description:  When resetting the caches use the previous cache maxsize.

Relates: #4432

Reviewed by: firstyear & progier(Thanks!!)
mreynolds389 added a commit that referenced this issue Nov 12, 2020
@mreynolds389
Issue 4432 - After a failed online import the next imports are very slow
6233c04 
Bug Description:  When an online import fails the entry and DN caches are
                  "reset", but we use the wrong "new maxsize" which was
                  setting the entry cache maxsize to zero which killed the
                  import performance.

Fix Description:  When resetting the caches use the previous cache maxsize.

Relates: #4432

Reviewed by: firstyear & progier(Thanks!!)
mreynolds389 added a commit that referenced this issue Nov 12, 2020
@mreynolds389
Issue 4432 - After a failed online import the next imports are very slow
ef8241e 
Bug Description:  When an online import fails the entry and DN caches are
                  "reset", but we use the wrong "new maxsize" which was
                  setting the entry cache maxsize to zero which killed the
                  import performance.

Fix Description:  When resetting the caches use the previous cache maxsize.

Relates: #4432

Reviewed by: firstyear & progier(Thanks!!)
@mreynolds389
Copy link
Contributor Author

9c7d590..6233c04 389-ds-base-1.4.4 -> 389-ds-base-1.4.4
174b3cd..ef8241e 389-ds-base-1.4.3 -> 389-ds-base-1.4.3

@mreynolds389
Copy link
Contributor Author

https://bugzilla.redhat.com/show_bug.cgi?id=1837982

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mreynolds389 mreynolds389

Labels
None yet
Projects
None yet
Milestone
1.4.3
Development

No branches or pull requests
1 participant
@mreynolds389