Bug #102509 TransactionMemory problem
Submitted: 6 Feb 2021 18:34 Modified: 14 Dec 2021 19:06
Reporter: Mikael Ronström Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:8.0.23 OS:Ubuntu
Assigned to: CPU Architecture:Any

[6 Feb 2021 18:34] Mikael Ronström 
Description:
    Fix a bug which meant that setting TransactionMemory prevented
    setting of MaxNoOfConcurrentOperations and MaxNoOfConcurrentScans.
    At the same it didn't prevent setting MaxNoOfLocalScans and
    MaxNoOfLocalOperations.

How to repeat:
Try setting TransactionMemory and MaxNoOfConcurrentOperations at the
same time
[7 Feb 2021 9:44] MySQL Verification Team 
Hello Mikael,

Thank you for the report and feedback.

Sincerely,
Umesh
[14 Dec 2021 19:06] Jon Stephens 
Documented fix as follows in the NDB 8.0.29 changelog:

    It was possible to set any of MaxNoOfFiredTriggers,
    MaxNoOfLocalScans, and MaxNoOfLocalOperations concurrently with
    TransactionMemory, although this should be disallowed.

    In addition, it was not possible to set any of
    MaxNoOfConcurrentTransactions, MaxNoOfConcurrentOperations, and
    MaxNoOfConcurrentScans concurrently with TransactionMemory,
    although there is no reason to prevent this.

    In both cases, the concurrent settings behavior now matches the
    documentation for the TransactionMemory parameter.

Closed.