aboutsummaryrefslogtreecommitdiff
path: root/math/py-fastcluster
diff options
context:
space:
mode:
authorChristos Chatzaras <chris@cretaforce.gr>2025-08-24 16:41:16 +0000
committerJochen Neumeister <joneum@FreeBSD.org>2025-08-24 16:42:53 +0000
commitba614a3b226631bf387d8066930f154a842f17eb (patch)
tree7d7968f5825eeadc58f77517ac9d3a3874cb67b6 /math/py-fastcluster
parentd770455da7c4a615f6ccf4b15b4aa6e29a64ae51 (diff)
databases/mysql80-{client, server}: Update to 8,0.43HEADmain
Bugs Fixed Important Note; Group Replication: The Group Communication System (GCS) handles Group Replication communication between members, and keeps track of the group membership and connections between all group members. Membership tracking includes the membership's current and previous two iterations. When a member leaves, the remaining members in the group keep a record of the departing member but stop communicating with it until it returns. For example: The group contains members M1, M2, and M3. M3 leaves the group; M1 and M2 stop communicating with M3. When a new member (M4) joins, it learns the previous iterations of this group's membership and attempts to communicate with all servers, including those from previous iterations (in this case, M3). In the event that some previous servers were gone and did not return, the new member continuously tried to connect to the missing servers; in some conditions, these ongoing connection attempts could introduce network latency affecting group member communication. In order to avoid this issue, connections to servers that belong to iterations of the group membership are now stopped after 5 minutes, which should be sufficient time to re-establish valid connections without imposing a continuing impact on group communication. (Bug NDB Cluster: Following an upgrade from NDB 8.0 to NDB 8.4, all data nodes in the cluster underwent an unexpected simultaneous restart. This occurred when the transaction coordinator had no scan state, leading to protocol timeout; the resulting misalignement in protocol states caused data nodes to shut down unexpectedly. This is fixed by extending existing handling of an unexpected SCAN_NEXTREQ signal to cover the case when the scan is already stateless. (Bug #37994985) References: This issue is a regression of: Bug #37022901. Full Changelog see: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-43.html PR: 288952 Sponsored by: Netzkommune GmbH
Diffstat (limited to 'math/py-fastcluster')
0 files changed, 0 insertions, 0 deletions