Any tips on debugging issues where , in this case,...
# troubleshoot
h
Any tips on debugging issues where , in this case, a dataFlow exists in the GMS database, but does not show up in the UI?
Maybe a
RestoreIndices
would help? But I'm also wondering how this could happen, or if there's a way of detecting the issue without randomly stumbling on it in the UI?
Is there any risk in running the restore-indices job without nuking the elasticsearch content first?
b
cc @early-lamp-41924
There shouldn't be risk
My guess is this is indeed indexing related. But strange that it's happening - have you had any downtime on the index side?
e
There is no risk. It is only if the local db is behind search index (for example backing up old snapshot)
h
Nice to know! I can vaguely recall some downtime with our Kafka/Opensearch provider, which might cause this I guess, but then both the MCE and MAE topics would have been down 🤔 Another option is a short downtime due to upgrading our Opensource instance. Putting too much effort into "at-least-once" delivery might be overkill, but how much work would it be to write a verification job to make sure the main DB and the search index are in sync? This might become more relevant with the Lineage Impact Analysis (if the feature is what I hope it is 😄 ).