Bug #106907 Backup::get_total_memory returns incorrect result
| Submitted: | 4 Apr 2022 16:15 | Modified: | 23 Sep 2022 21:14 |
|---|---|---|---|
| Reporter: | Mikael Ronström | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
| Version: | 8.0.23 | OS: | Any |
| Assigned to: | CPU Architecture: | Any |
[4 Apr 2022 16:15]
Mikael Ronström
[5 Apr 2022 6:04]
MySQL Verification Team
Hello Mikael, Thank you for the report and feedback. Sincerely, Umesh
[23 Sep 2022 21:14]
Jon Stephens
Documented fix as follows in the NDB 8.0.32 changelog:
Backup::get_total_memory(), used to calculate proposed disk
write speeds for checkpoints, wrongly considered DataMemory that
may not have been used in the calculation of memory used by
LDMs.
We fix this by obtaining the total DataMemory used by
the LDM threads instead. as reported by DBTUP.
Closed.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.039 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.