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.

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

Replication init fails with ASAN build #6632

Open
vashirov opened this issue Feb 25, 2025 · 0 comments · May be fixed by #6633
Open

Replication init fails with ASAN build #6632

vashirov opened this issue Feb 25, 2025 · 0 comments · May be fixed by #6633
Labels
needs triage The issue will be triaged during scrum

Comments

@vashirov
Copy link
Member

Issue Description
After the increase of DEFAULT_PBKDF2_ROUNDS to 100_000, bind operation on ASAN build takes more time. On some systems it's more time than the default timeouts for replication agreements, causing replication init to fail.

@vashirov vashirov added the needs triage The issue will be triaged during scrum label Feb 25, 2025
vashirov added a commit to vashirov/389-ds-base that referenced this issue Feb 25, 2025
Bug Description:
After the increase of DEFAULT_PBKDF2_ROUNDS to 100_000, bind operation
on ASAN build takes more time. On some systems it's more time than the
default timeouts for replication agreements, causing replication init
to fail.

Fix Description:
Introduce a new helper function `get_timeout_scale()` and update
hardcoded timeouts to use it for scaling. For ASAN builds it returns
2.0 instead of default 1.0.
Factor returned by `get_timeout_scale()` can be adjusted using
environment variable `DS_TIMEOUT_SCALE`.

Fixes: 389ds#6632
@vashirov vashirov linked a pull request Feb 25, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage The issue will be triaged during scrum
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant