I am running lakefs version 0.63.0 which is running on Postgres DB, but we switched to Yugabyte DB for some reason. Now when I try to start lakefs I keep getting this error

" schema version not compatible with the latest version"

Hi Jude, Some lakeFS releases contain mandatories migrations in order to run. You may want to run

lakefs migrate up

before running the new version.

Okay let me try that. Thanks

No problem

@Idan Novogroder I got this error after I ran the lakefs migrate up command

Failed to setup DB: get migrate database driver: dial tcp 159.89.247.141:5432: connect: connection timed ou

Do you know what could be the cause?

Hi Jude, Did you check that the DB you configured to work with is alive and serve with the IP, port and credentials you supplied?

Okay, let me clarify what I did. I had postgres connection string initially which was working, and can be found in the config.yaml file. Then I needed to use YugabyteDB which has been deployed already. I just modified the CONNECTION STRING in the config.yaml file and ran this migrate command.

I see, it looks like there's a connectivity issue with the DB you are trying to work with. It might be caused by many different reasons- wrong IP address, wrong IP, wrong username and password (all of these are part of the connection string). It may caused by downtime of the DB. Some DBs also work with block/allow lists in case you are using a managed version of YugabyteDB. Did you try to connect to your DB from the server/container that runs your lakeFS installation?

No I have not done that yet. Let me look at it. Thanks for the update

Sure 🙂 Let me know how it worked for you

Hi, @Idan Novogroder so we have been able to fix the issue on the cluster running our Yugabyte DB. But for some reason, I am still not able to run the migration. pops up with this error when I try to.

Failed to setup DB: get migrate database driver: pq: Timed out: Perform RPC (request call id 3) to 10.244.0.4:9100 timed out after 120.000s

Hi Jude, I'm looking into it. BTW, can you share what was the issue with cluster?

Okay, I will get that info from our DevOps team. I tried the update again and got this

Failed to setup DB: Dirty database version 1. Fix and force version

I don't know if this is useful

Meanwhile, can you please run this query on your DB in order to get which version of postgeSQL it runs?

*select* rpad(*version*(), 18)||'...' *as* v;

https://docs.yugabyte.com/preview/api/ysql/

Alright

About the

Failed to setup DB: Dirty database version 1. Fix and force version

error- It probably happens because you had a timeout in the middle of the migration run. This comment gives a good example (IMO) of how to fix this kind of issue: https://github.com/golang-migrate/migrate/issues/282#issuecomment-530732246 LT; DR- you should run something like:

migrate -path <PATH_TO_MIGRATIONS_FOLDER/ -database <CONNECTION_STRING_TO_YOUR_DB> force 0

Hi Jude, It seems like lakFS doesn't support Yugabyte DB at the moment. I thought there's maybe some way to make it work, but it seems like there are some Postgres syntax that Yugabyte doesn't support. I'll open an issue in the lakeFS project to support Yugabyte DB and will share it with you.

Hi Jude, Here's the issue I opened for supporting YugabyteDB in the future: https://github.com/treeverse/lakeFS/issues/3731