-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
7.1 with tenanting upgrade to 7.3 crash #11292
Comments
Tenant is an experimental feature in 7.1 and 7.3. Since Apple is not planning to use this feature, we'll rely on community support to bring this feature to a mature state, including fixing such upgrade issues. |
What we did was migrate everything to 7.3 before introducing tenanting in production. |
Good to know. However, you may run into issues upgrading from 7.3 to future releases again. We recently noticed that there are data format changes between 7.3 and 7.3: tenants.results[0].getInt(1) == updatedTenantEntry.id main: tenantsInGroup.results[0].getInt(2) == tenantId So we have disabled tenant for upgrading tests from 7.3 to |
I’ve been testing 7.1 → 7.3 upgrades with tenanted data due to a discussion in Tenants & golang - #8 by newhook which lead to Tenant feature metadata changes in 7.2 release.
I've been testing:
foundationdb-clients_7.1.40-1_amd64.deb foundationdb-server_7.1.40-1_amd64.deb
upgrading to:
foundationdb-clients_7.3.36-1_amd64.deb foundationdb-server_7.3.36-1_amd64.deb
What I discovered was if I have tenanted data in the 7.1 database I end up crashing a 7.3 server on startup. I get one of two crashes:
or when I was running in memory mode, which I guess is occurring in log replay.
Are these expected? Anyway around them? Any advice?
The text was updated successfully, but these errors were encountered: