https://flyte.org logo
#ask-the-community
Title
# ask-the-community
n

Nandakumar Raghu

01/19/2024, 3:58 PM
Hi All, We are planning to switch to flyte-core from flyte-binary. Since we have already run workflows on flyte-binary there is history in the DB of these runs. We would like to retain that, however, we are not sure if there are any changes in the DB schemas of flyte-binary and core. We wanted to do a clean install of core, i.e destroy the DB, S3 etc so that there are no compatibility issues, however if we can retain the history it would be great. What do you suggest? Clean install or install over existing flyte-binary DB. If you recommend clean install, is there a way to transfer run history?
d

David Espejo (he/him)

01/19/2024, 4:20 PM
I don't think theres a difference on the DB schema connected to the Helm chart you use
y

Yee

01/19/2024, 4:33 PM
there is no difference in the db schemas, you just have to make sure you hit the right helm variables to make sure it finds the db/s3 buckets correctly.
definitely save a backup of the db first just in case.
just curious though, what’s your motivation for doing this?
n

Nandakumar Raghu

01/19/2024, 4:40 PM
@Yee - We want to have more than 1 replica for the pod that supports the UI so it is always available. We have seen the flyte-binary pod crashing sometimes leading to downtime. Flyte binary does not support multiple replicas and when we did it (by modifying the charts), we started getting webhook errors, for which again the solution provided was to have multiple replicas.
y

Yee

01/19/2024, 4:56 PM
flyte-binary pod crashing is not good. do you remember the reasons why?
n

Nandakumar Raghu

01/19/2024, 5:00 PM
We couldn't identify the reasons, it used to crash at random times and we would find out only when we go to the UI and get a 503. Logs were not very useful.
4 Views