failed to get record hashes: no such column: ids

[zjshen14]

It's not blocking, but saw the error log like this:

{"level":"error","ts":1569886521.7687557,"caller":"committee/committee.go:231","msg":"failed to sync","ioAddr":"io1ph0u2psnd7muq5xv9623rmxdsxc4uapxhzpg02","networkAddr":"0.0.0.0:4689","error":"failed to get record hashes: no such column: ids","errorVerbose":"no such column: ids\nfailed to get record hashes\ngithub.com/iotexproject/iotex-election/committee.(*recordTableOperator).Put\n\t/go/pkg/mod/github.com/iotexproject/[email protected]/committee/recordtableoperator.go:140\ngithub.com/iotexproject/iotex-election/committee.(*archive).PutPoll\n\t/go/pkg/mod/github.com/iotexproject/[email protected]/committee/pollarchive.go:135\ngithub.com/iotexproject/iotex-election/committee.(*committee).storeInBatch\n\t/go/pkg/mod/github.com/iotexproject/[email protected]/committee/committee.go:349\ngithub.com/iotexproject/iotex-election/committee.(*committee).Sync\n\t/go/pkg/mod/github.com/iotexproject/[email protected]/committee/committee.go:273\ngithub.com/iotexproject/iotex-election/committee.(*committee).Start.func1\n\t/go/pkg/mod/github.com/iotexproject/[email protected]/committee/committee.go:230\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1337"}

[zjshen14]

I found the problem:

On our nightly cluster we start with iotex-core:latest image which is using election v0.2.2. And then we upgrade to a custom image, which uses v0.2.4. In between there's incompatible schema change to height_to_*: https://github.com/iotexproject/iotex-election/blob/v0.2.2/committee/archive.go#L38-L39. See there's not ids column there. After upgrade there's no logic to handle the schema difference