Conversation
tbordaz
left a comment
There was a problem hiding this comment.
Parts of the patch are related to LMDB. Do we need those parts in 2.4 ?
| #include "cl5_api.h" | ||
| #include "slapi-plugin.h" | ||
| #include "slap.h" | ||
| #include "../../slapd/back-ldbm/dbimpl.h" /* for dblayer_is_lmdb */ |
There was a problem hiding this comment.
lmdb definitions are not expected in 2.4
| Slapi_Backend *be = NULL; | ||
| const char *val = NULL; | ||
| int64_t ptimeout = 0; | ||
| int use_lmdb = 0; |
There was a problem hiding this comment.
There is no lmdb switch in 2.4
|
|
||
| /* flow control update window. */ | ||
| ra->flowControlWindow = DEFAULT_FLOWCONTROL_WINDOW; | ||
| use_lmdb = dblayer_is_lmdb(be); |
| return idl; | ||
| } | ||
|
|
||
| /* |
There was a problem hiding this comment.
I doubt those functions are needed in 2.4 as they are related to LMDB
tbordaz
left a comment
There was a problem hiding this comment.
If the tests fail because of missing fixture. Is it enough to backport the fixture in 2.4 in the tests but leave unchanged the core server ?
|
The test succeeds with just the fixture backported; I tested it manually previously. If the fixture alone is enough, I can amend this commit and remove the rest of it. |
d394190 to
cdfdb73
Compare
|
Removed all changes from commit other than the new fixture. Regression test confirmed successful.
Edit: Forgot to mention this, but I also kept four imports necessary for the test and the fixture. |
|
@abeisemb Hey, can you please rebase? Thanks! |
* Issue 6265 - lmdb - missing entries in range searches Several issues seen after generating ldif with 2000 users and importing it in a replica: 1. The entryid attribute in missing in the suffix entry. 2. Access log shows that the internal search looking for "(parentid>=1)" is not returning all entries but one. 3. When initializing a replica through a replication agreement some entries are missing (because of 2) 4. Once 2. get fixed, the bulk import still fails because the default values for nsds5ReplicaFlowControlWindow and nsds5ReplicaFlowControlPause are not adapted to lmdb (supplier sent the entry faster than bdb and the target replica import them slower. The fix is about: 1. Ensuring that the operational attribute are properly set when importing the suffix entry. 2. and 3. Avoid using database bulk operation when computing range unless we are sure that bdb is used. (rely instead on the generic dblayer database iterator - dblayer_cursor_iterate. 4. Change the default values for nsds5ReplicaFlowControlWindow and nsds5ReplicaFlowControlPause if agreement is on a lmdb backend. Issue: 389ds#6265 Reviewed by: @vashirov, @droideck (Thanks!)
cdfdb73 to
d35928c
Compare
|
@tbordaz Hi mate, can you please re-review this once? |
Commit in question is f75b5e2, meant to resolve issue #6265.
Resolves: #6827
Summary by Sourcery
Isolate multi-master replication regression tests by using temporary credentials and restoring each topology after execution.
Bug Fixes:
Enhancements:
Tests: