BestHub
Sign in
Tagged articles
107 articles
Page 2 of 2
21CTO
21CTO
Nov 28, 2015 · Databases

Why MySQL Key Partition Queries Fail After Upgrade and How to Fix Them

This article examines several MySQL issues—including key partition hash algorithm changes causing data loss after upgrades, a client crash triggered by misdirected dump output, GTID_PURGED interactions that break AUTO_POSITION replication, and replicate‑do‑db filtering effects on GTID continuity—and provides concrete compatibility fixes and troubleshooting steps.

Database UpgradeGTIDReplication
0 likes · 18 min read
Why MySQL Key Partition Queries Fail After Upgrade and How to Fix Them
Qunar Tech Salon
Qunar Tech Salon
Oct 30, 2015 · Databases

MySQL Partitioning Hash Changes, GTID Replication Bugs, Client Crash, and TokuDB Optimize Table Analysis

This article examines how differing key‑hash algorithms in MySQL 5.1 versus 5.5/5.6 cause data loss in partitioned tables, describes compatibility fixes with ALTER TABLE … ALGORITHM=1, analyzes a MySQL client crash caused by mis‑redirected dump output, explores GTID_PURGED replication issues and replicate‑do‑db filtering gaps, and evaluates the behavior of OPTIMIZE TABLE on TokuDB tables.

BackendGTIDOptimizeTable
0 likes · 18 min read
MySQL Partitioning Hash Changes, GTID Replication Bugs, Client Crash, and TokuDB Optimize Table Analysis
21CTO
21CTO
Oct 20, 2015 · Databases

Deep Dive into MySQL Partitioning, GTID Bugs, and TokuDB Optimize Table Anomalies

This article examines why MySQL 5.5/5.6 fails to retrieve non‑null partitioned rows after a physical upgrade, how the ALTER TABLE … PARTITION BY KEY ALGORITHM=1 fix works, the cause of MySQL client crashes when dump output mixes warnings, GTID_PURGED replication bugs, replicate‑filter side effects, and the behavior of TokuDB’s OPTIMIZE TABLE.

GTIDPartitioningReplication
0 likes · 19 min read
Deep Dive into MySQL Partitioning, GTID Bugs, and TokuDB Optimize Table Anomalies
21CTO
21CTO
Oct 13, 2015 · Databases

How Group Commit, DDL Fast Fail, and GTID Optimizations Boost MySQL Performance

This article explains MySQL's evolution from serialized binlog writes to group commit, introduces DDL fast‑fail and GTID allocation improvements, analyzes InnoDB auto‑increment duplication after restart, and details replication performance gains from multi‑threaded and seqno‑based parallel execution, providing code examples and benchmark results.

DDL Fast FailGTIDGroup Commit
0 likes · 22 min read
How Group Commit, DDL Fast Fail, and GTID Optimizations Boost MySQL Performance
Architect
Architect
Aug 31, 2015 · Databases

MySQL High Availability: Replication, Monitoring, and Failover Strategies

This article discusses MySQL high‑availability solutions, covering asynchronous and semi‑synchronous replication, monitoring with keepalived, Zookeeper, and custom agents, failover procedures using binlog positions, GTID and pseudo‑GTID techniques, and the author's practical experiences and future plans.

GTIDReplicationdatabase
0 likes · 17 min read
MySQL High Availability: Replication, Monitoring, and Failover Strategies