Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Describe tarantool 1.10->2.x migration process #587

Closed
2 tasks
rosik opened this issue Feb 18, 2020 · 1 comment · Fixed by #1131
Closed
2 tasks

Describe tarantool 1.10->2.x migration process #587

rosik opened this issue Feb 18, 2020 · 1 comment · Fixed by #1131
Assignees
@Onvember
Labels
documentation Improvements or additions to documentation
Milestone
Documentation imp...

Comments

@rosik
Copy link
Contributor

rosik commented Feb 18, 2020 •
edited by artur-barsegyan

Suppose i'm a user, and I have cartridge (scm-1) + tarantool (1.10). How do I upgrade tarantool to 2.x?

Related: tarantool/tarantool#4691

  • Describe the process of migration
  • Choose a place for publishing this information
@rosik rosik added the documentation Improvements or additions to documentation label Feb 18, 2020
@olegrok
Copy link
Contributor

olegrok commented Feb 18, 2020

I think it could be useful - #253 (comment)

@DHorrible DHorrible mentioned this issue Mar 5, 2020
Closed
3 tasks
@olegrok olegrok self-assigned this Mar 19, 2020
@olegrok olegrok mentioned this issue Mar 27, 2020
Merged
3 tasks
rosik added a commit that referenced this issue Mar 27, 2020
@olegrok @rosik
Support automatic schema upgrade (#671)
cbabf82 
This patch introduces an option - `upgrade_schema` to perform an upgrade
procedure if we want to upgrade tarantool version. The main idea to
apply `box.schema.upgrade` on the leader (according to failover priority
in topology confgig). We can't do it on each instance - it lead to
replication conflicts if we have 2 or more writable instances.

We don't do it automatically to give an ability for user to check that
instances works fine with new tarantool version but old schema. This
thesis is not relevant just now because of "Space 277 doesn't exist"
error (tarantool/tarantool#4691). But I hope it will be solved soon.

Also introduce new type of tests - "upgrade". The main idea it to try to
bootstrap server from existing snapshots with older schema version.

See also #587 

Co-authored-by: Yaroslav Dynnikov <yaroslav.dynnikov@gmail.com>
@rosik rosik added this to the Documentation improvements milestone Apr 7, 2020
@lenkis lenkis self-assigned this Jul 7, 2020
@artur-barsegyan artur-barsegyan assigned Onvember and unassigned lenkis Nov 6, 2020
Onvember added a commit that referenced this issue Nov 16, 2020
@Onvember
gh-587 describe schema upgrading process
3146453
@Onvember Onvember mentioned this issue Nov 17, 2020
Closed
Onvember added a commit that referenced this issue Nov 19, 2020
@Onvember
gh-587 describe schema upgrading process
d7a0d31
@Onvember Onvember mentioned this issue Nov 19, 2020
Merged
rosik pushed a commit that referenced this issue Nov 20, 2020
@Onvember
Describe schema upgrading process (#1131)
87bb9f8 
Close #587
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Onvember Onvember

Labels
documentation Improvements or additions to documentation
Projects
None yet
Milestone
Documentation improvements
5 participants
@rosik @olegrok @lenkis @DHorrible @Onvember