GET 24/7 LIVE HELP NOW

Announcement

Announcement Module
Collapse
No announcement yet.

mk_table_checksum Warning: WHERE clause too large for boundaries column

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • mk_table_checksum Warning: WHERE clause too large for boundaries column

    hi

    running mk_table_checksum is returning warnings while checking one of our large tables in a master-master (passive master) replication set up.

    Does anyone know what these mean and and what the implications are? are we ok to proceed? is the checksum working, will we actually be able to use this check at the end of the day for comparing replication. thanks.

    -- maatkit command used
    nohup mk-table-checksum --replicate=mysql.checksum --empty-replicate-table --chunk-size=500000 --databases==production -u root -p h=123.123123 -P 3306 &

    -- table structure
    Create Table: CREATE TABLE `change_event` (
    `change_event_id` bigint(20) NOT NULL DEFAULT '0',
    `timestamp` datetime NOT NULL,
    `change_type` enum('create','update','delete','noop') DEFAULT NULL,
    `changed_object_type` varchar(100) NOT NULL,
    `changed_object_id` varchar(255) DEFAULT NULL,
    `changed_object_modified` datetime NOT NULL DEFAULT '1000-01-01 00:00:00',
    `modified` datetime NOT NULL DEFAULT '1000-01-01 00:00:00',
    `created` datetime NOT NULL DEFAULT '1000-01-01 00:00:00',
    `pid` char(15) DEFAULT NULL,
    `episode_pid` char(15) DEFAULT NULL,
    `import_id` int(11) NOT NULL,
    `status` enum('success','failure') NOT NULL,
    `xml_diff` text,
    `node_digest` char(32) DEFAULT NULL,
    `version_pid` char(15) DEFAULT NULL,
    PRIMARY KEY (`change_event_id`),
    KEY `idx_change_events_changed_object_id` (`changed_object_id`),
    KEY `idx_change_events_episode_pid` (`episode_pid`),
    KEY `fk_import_id` (`import_id`),
    KEY `idx_change_event_timestamp_ce_id` (`timestamp`,`change_event_id`),
    KEY `idx_change_event_status` (`status`),
    KEY `idx_change_event_node_digest` (`node_digest`),
    KEY `idx_change_event_id` (`change_event_id`),
    KEY `changed_object_id_status` (`changed_object_id`,`status`),
    KEY `fk_change_event_changed_object_type` (`changed_object_type`),
    CONSTRAINT `fk_change_event_changed_object_type` FOREIGN KEY (`changed_object_type`) REFERENCES `entity_type` (`public_id`)
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8
    1 row in set (0.00 sec)

    -- number or rows
    37million rows in the table.

    --example warnings from log
    # mk_table_checksum:5454 14339 Warning: WHERE clause too large for boundaries column; mk-table-sync may fail; value: `change_event_id` >= 1218326621901402 AND `change_event_id` < 1220090368349034
    pips3_production change_event 22 123.123.123.123InnoDB 208508 6feb172 87 NULL NULL NULL
    # mk_table_checksum:5454 14339 Warning: WHERE clause too large for boundaries column; mk-table-sync may fail; value: `change_event_id` >= 1220090368349034 AND `change_event_id` < 1221854114796666
    pips3_production change_event 23 123.123.123.123InnoDB 235442 c3cf04aa 70 NULL NULL NULL
    # mk_table_checksum:5454 14339 Warning: WHERE clause too large for boundaries column; mk-table-sync may fail; value: `change_event_id` >= 1221854114796666 AND `change_event_id` < 1223617861244298
    pips3_production change_event 24 123.123.123.123InnoDB 252054 947d801e 69 NULL NULL NULL
    # mk_table_checksum:5454 14339 Warning: WHERE clause too large for boundaries column; mk-table-sync may fail; value: `change_event_id` >= 1223617861244298 AND `change_event_id` < 1225381607691930
    pips3_production change_event 25 123.123.123.123InnoDB 339493 42ca8089 89 NULL NULL NULL
    # mk_table_checksum:5454 14339 Warning: WHERE clause too large for boundaries column; mk-table-sync may fail; value: `change_event_id` >= 1225381607691930 AND `change_event_id` < 1227145354139562
    pips3_production change_event 26 123.123.123.123InnoDB 396065 2bd47bb4 130 NULL NULL NULL
    # mk_table_checksum:5454 14339 Warning: WHERE clause too large for boundaries column; mk-table-sync may fail; value: `change_event_id` >= 1227145354139562 AND `change_event_id` < 1228909100587194
    pips3_production change_event 27 123.123.123.123InnoDB 408512 dc843c3 233 NULL NULL NULL

  • #2
    The tool will work okay, but mk-table-sync might not be able to use the information in the --replicate table for syncing more efficiently. You can increase the size of the "boundaries" column to avoid this problem.

    Comment

    Working...
    X