Skip to content

[0pt] Clarify tarantool update process to a newer major version #836

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

Closed
Tracked by #2572
Totktonada opened this issue Jul 23, 2019 · 5 comments · Fixed by #3080
Closed
Tracked by #2572

[0pt] Clarify tarantool update process to a newer major version #836

Totktonada opened this issue Jul 23, 2019 · 5 comments · Fixed by #3080
Labels
feature A new functionality

Comments

@Totktonada
Copy link
Member

Totktonada commented Jul 23, 2019

Our guarantee is that Nth major version can be upgraded to (N+1)th one, but we does not guarantee the same for (N+2)th version.

Say, to update 1.7 to 2.1 we need to update it first to 1.9, then to 1.10 and only then to 2.1.

We should clarify also what is a major version of tarantool: 1.7, 1.9, 1.10, 2. The way to enumarate versions was changed since 2.*.

@lenkis lenkis self-assigned this Jul 25, 2019
@lenkis
Copy link
Contributor

lenkis commented Jul 25, 2019

we need to revise the entire release policy doc then: https://www.tarantool.io/en/doc/2.1/dev_guide/release_management/#release-policy

@lenkis lenkis added 1.10 feature A new functionality need feedback [special status] On hold, awaiting feedback user_guide [location] Tarantool manual, User's Guide part labels Jul 25, 2019
@printercu
Copy link
Contributor

Actually upgrading to 1.9 is not required, 1.7 -> 1.10 -> 2.1 works fine.

It's quite easy to migrate using docker

$ docker run --volume /path/to/workdir:/tnt -it tarantool/tarantool:1 sh
  sh> tarantool
    tnt> box.cfg{work_dir = '/tnt'}
    tnt> box.snapshot()
$ docker run --volume /path/to/workdir:/tnt -it tarantool/tarantool:2.1 sh
  sh> tarantool
    tnt> box.cfg{work_dir = '/tnt'}
    tnt> box.snapshot()

@Totktonada
Copy link
Member Author

I would add to the Max's message: using box.snapshot() is important here. Otherwise you can receive the following errors:

E> ER_ACCESS_DENIED: Usage access to universe '' is denied for user 'admin'
F> can't initialize storage: Usage access to universe '' is denied for user 'admin'

@Totktonada
Copy link
Member Author

The issue related to ER_ACCESS_DENIED: tarantool/tarantool#4606.

@lenkis lenkis assigned Onvember and unassigned kyukhin and lenkis May 7, 2020
@lenkis lenkis added S (small) and removed need feedback [special status] On hold, awaiting feedback user_guide [location] Tarantool manual, User's Guide part labels May 7, 2020
@lenkis lenkis assigned lenkis and unassigned Onvember Oct 29, 2020
@veod32
Copy link
Collaborator

veod32 commented Dec 16, 2020

If we are not going to revise the entire release policy and its documentation as @lenkis mentioned above, then the estimation of the issue can be 8pt.

@veod32 veod32 changed the title Clarify tarantool update process to a newer major version [8pt] Clarify tarantool update process to a newer major version Dec 16, 2020
@veod32 veod32 changed the title [8pt] Clarify tarantool update process to a newer major version [0pt] Clarify tarantool update process to a newer major version Apr 23, 2021
@veod32 veod32 removed 1.10 labels Apr 28, 2021
@xuniq xuniq removed the dev label Sep 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature A new functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants