Hey team, I added a new column and then clicked re...
# troubleshooting
a
Hey team, I added a new column and then clicked reload all segments. But still got the following error when running queries. Any idea how to fix it?
There are 330 invalid segment/s. This usually means that they were created with an older schema. Please reload the table in order to refresh these segments to the new schema.
m
How long before did you run the reload, was it completed? If so, try to reset the segments.
a
more than 10 hours.
But how to check if it’s completed?🤣 Table status is good. How to locate these invalid segments?
m
Hmm, that doesn’t make sense. If table status is good, all segments should have been reloaded.
a
I tried reset this table, run query again and “errorCode”: 305 occured.
m
Any issues reported by table debug endpoint? cc: @Rong R to help debug
r
did you fix your previous multi-value non-dict column issue? if so you might need to delete the table and restart from scratch.
a
It’s another table without multi-value column.
r
oh. i see. i was confused with "still got error". is it possible to share the controller logs.
h
Hi @Mayank, @Rong R, Is there any configuration that influences the speed of reloading? For example, the reloading is conducted in a batch way, each batch only loads a max/certain number of segments, and a new batch will be triggered every some time.
m
I think there is a setting for that, let me find. However you don’t want to increase parallelism too much.
h
I see the warned un-reloaded segment number decreases by 9 each time, from 195 to 186 to 177. The number decreased feel like because I triggered reloading from API several times, at 195, at 186 … If I don’t trigger the reloading again, the number stays the same even after many hours.