从服务器上MYI索引的大小较小

我最近通过在枚举字段中添加一个新值来更改一个巨大的MyISAM表（8000万条）。 在我这样做之后，我检查了用于复制主服务器的2个从服务器上的表的健康状况。 我注意到，在一台从服务器上MYI文件要小得多。 我已经用myisamchk和REPAIR修复了表，但索引的大小没有改变。

请在下面看到在这3台服务器上运行myisamchk -dvv返回的结果为“Keyfile length”：

 Master Server Auto increment key: 1 Last value: 80098340 Data records: 79375556 Deleted blocks: 0 Datafile parts: 79375556 Deleted data: 0 Datafile pointer (bytes): 6 Keyfile pointer (bytes): 6 Datafile length: 9635014668 **Keyfile length: 18945252352** Max datafile length: 281474976710654 Max keyfile length: 288230376151710719 Recordlength: 1110 Slave Server 1 Auto increment key: 1 Last value: 80097611 Data records: 79374828 Deleted blocks: 0 Datafile parts: 79394418 Deleted data: 0 Datafile pointer (bytes): 6 Keyfile pointer (bytes): 6 Datafile length: 9635788652 **Keyfile length: 18024821760** Max datafile length: 281474976710654 Max keyfile length: 288230376151710719 Recordlength: 1110 Slave Server 2 - Here the size of Keyfile is much smaller Auto increment key: 1 Last value: 80098312 Data records: 79375002 Deleted blocks: 0 Datafile parts: 79375002 Deleted data: 0 Datafile pointer (bytes): 6 Keyfile pointer (bytes): 6 Datafile length: 9634942908 **Keyfile length: 11092404224** Max datafile length: 281474976710654 Max keyfile length: 288230376151710719 

什么可能导致如此显着的差异？

• 添加一个pipe理员用户到MongoDB
• 连接到Windows 8.1 Azure VM上托pipe的Oracle数据库
• 部署开发数据库到现场系统的最佳实践是什么？
• 无法恢复托pipe在Azure VM上的Django应用程序的postgresql数据转储
• MySQL错误代码：1017权限被拒绝

 CREATE TABLE mytable ... LOCK TABLE mytable ... ALTER TABLE mytable DISABLE KEYS; (shuts off updates to non-unique indexes) INSERT INTO ... INSERT INTO ... . . . ALTER TABLE mytable ENABLE KEYS; (rebuild all indexes) UNLOCK TABLES;