Project

General

Profile

Actions
Copy link

Bug #10405

closed

Bug #10373: Upgrading from 4.0 to 4.1 failed on Centos7.3, and purged LDAP directory

Bad way to calculate the size of mdb database for LDAP data

Added by François ARMAND about 7 years ago. Updated about 7 years ago.

Status:
Released
Priority:
N/A
Assignee:
Alexis Mousset
Category:
System integration
Target version:
4.1.0
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Small
Priority:
68
Name check:
Fix check:
Regression:

Description

With the parent task merged, we are now correctly setting the mdb database size during migration.

But we are not at all using the correct way to calculate it, because we are still using the old way which was for a cache, so depending on RAM, and not for a storage size.

The problem is that it is not trivial to update mdb storage size if limit is reached, and the consequences can be very grave (losing data).

So, we need to:

- find the normal database size for a set of production install,
- find a sufficiently high value so that, if possible, any installation can run a couple of thousand node without even knowing that that limit exists (tracked on that ticket)
- document all of that (tracked in #10404)

Actions
Copy link

Also available in: Atom PDF