ERROR value args count differs from table column count in BuildDMLUpdateQuery

hi shlomi noach
**Will this new error affect the integrity and consistency of the data?**
I have seen similar errors:
#442

2018-05-29 18:39:49 INFO Setting RENAME timeout as 3 seconds
2018-05-29 18:39:49 INFO Session renaming tables is 4837
2018-05-29 18:39:49 INFO Issuing and expecting this to block: rename /* gh-ost */ table db1.t1 to db1._t1_20180529174403_del, db1._t1_gho to db1.t1
2018-05-29 18:39:49 INFO Found atomic RENAME to be blocking, as expected. Double checking the lock is still in place (though I don't strictly have to)
2018-05-29 18:39:49 INFO Checking session lock: gh-ost.4832.lock
2018-05-29 18:39:49 INFO Connection holding lock on original table still exists
2018-05-29 18:39:49 INFO Will now proceed to drop magic table and unlock tables
2018-05-29 18:39:49 INFO Dropping magic cut-over table
2018-05-29 18:39:49 INFO Releasing lock from db1.t1, db1._t1_20180529174403_del
**2018-05-29 18:39:49 INFO Tables unlocked
2018-05-29 18:39:49 INFO Tables renamed
2018-05-29 18:39:49 INFO Lock & rename duration: 236.629407ms. During this time, queries on t1 were blocked
2018-05-29 18:39:49 INFO Looking for magic cut-over table
2018-05-29 18:39:50 ERROR value args count differs from table column count in BuildDMLUpdateQuery**
2018-05-29 18:39:51 ERROR value args count differs from table column count in BuildDMLUpdateQuery
2018-05-29 18:39:52 ERROR value args count differs from table column count in BuildDMLUpdateQuery
2018-05-29 18:39:53 ERROR value args count differs from table column count in BuildDMLUpdateQuery
Copy: 13490694/13490694 100.0%; Applied: 215167; Backlog: 254/1000; Time: 55m50s(total), 46m30s(copy); streamer: mysql-bin.000080:44713964; State: migrating; ETA: due
2018-05-29 18:39:54 ERROR value args count differs from table column count in BuildDMLUpdateQuery
2018-05-29 18:39:55 ERROR value args count differs from table column count in BuildDMLUpdateQuery
2018-05-29 18:39:56 ERROR value args count differs from table column count in BuildDMLUpdateQuery
2018/05/29 18:39:57 binlogsyncer.go:107: [info] syncer is closing...
2018/05/29 18:39:57 binlogstreamer.go:47: [error] close sync with err: sync is been closing...
2018-05-29 18:39:57 DEBUG done streaming events
2018-05-29 18:39:57 DEBUG Done streaming
2018/05/29 18:39:57 binlogsyncer.go:122: [info] syncer is closed
2018-05-29 18:39:57 INFO Closed streamer connection. err=
2018-05-29 18:39:57 INFO Dropping table db1._t1_ghc
2018-05-29 18:39:57 INFO Table dropped
2018-05-29 18:39:57 INFO Am not dropping old table because I want this operation to be as live as possible. If you insist I should do it, please add --ok-to-drop-table next time. But I prefer you do not. To drop the old table, issue:
2018-05-29 18:39:57 INFO -- drop table db1._t1_20180529174403_del
2018-05-29 18:39:57 INFO Done migrating db1.t1
2018-05-29 18:39:57 INFO Removing socket file: /tmp/gh-ost.db1.t1.sock
2018-05-29 18:39:57 INFO Tearing down inspector
2018-05-29 18:39:57 INFO Tearing down applier
2018-05-29 18:39:57 DEBUG Tearing down...
2018-05-29 18:39:57 INFO Tearing down streamer
2018-05-29 18:39:57 INFO Tearing down throttler
2018-05-29 18:39:57 DEBUG Tearing down...
Done

thanks shlomi noach

Inizia tracciando l’entry point BuildDMLUpdateQuery indicato nell’errore e confronta il numero di colonne della tabella e di argomenti di valore durante la sequenza di cut-over segnalata. Riproduci lo scenario di migrazione dai logs, se possibile, quindi identifica la condizione che causa la discrepanza e verifica che l’errore non si ripresenti senza influire sul risultato della migrazione.

Scritto dal modello di indicizzazione a partire dal testo della issue.