-
Notifications
You must be signed in to change notification settings - Fork 43
Сonfusing wording in box.backup page #869
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
Comments
Changed description as intended. Consider review.
Suggested fix in English - please review. |
Reviewed – read comments.
My point at this ticket is |
I understand that and agree with your point, but my quote was an example of the same problem in other part of the documentation. I am suggesting we use this ticket to check all documentation for the same issue. |
Ok, I got it. It's really important issue and we should fix this mistake anywhere
27 авг. 2019 г., 10:46 AM +0300, izmalk <[email protected]>, писал:
… > Reviewed – read comments.
> > Also this issue might be mentioned in other parts of documentation: for example the very previous chapter has following text -
> > "Put all nodes in read-only mode and disable checkpointing with box.backup.start(). "
> > And in Russian -
> > "Переключите все узлы в режим только для чтения и отключите командой box.backup.start() создание контрольных точек."
> My point at this ticket is box.backup.start() doesn't put a node in read_only mode and doesn't disable checkpointing.
I understand that and agree with your point, but my quote was an example of the same problem in other part of the documentation. I am suggesting we use this ticket to check all documentation for the same issue.
But i feel like i need a permission to do that from @lenkis.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Fix gh-825 feedback: Submodule box.index Fix gh-857 feedback: Модель данных Fix gh-856 feedback: Access control Fix gh-853 feedback: Functions for transaction management Fix gh-848 feedback: Submodule box.index Fix gh-834 Использование бинарного пакета Fix gh-867 feedback: Access control Fix gh-866 feedback: Триггеры Fix gh-865 feedback: Триггеры Fix gh-864 feedback: Рекомендации по Lua-синтаксису Fix gh-861 feedback: Модуль http Fix gh-869 Сonfusing wording in box.backup page Fix gh-860 vshard.router/storage.sync miss return value documentation Fix gh-830 Improve documentation on fibers Fix gh-850 Add more info about connectors
@izmalk Please check all entries of read-only throughout the manual. Changes may be required. |
Fixed description regarding garbage collection in backup.start()
Fixed backup.start() use description in disaster recovery. Note the ref-link to box.backup.stop() is the same as the start().
I searched doc.po for all box.backup.start() mentions and checked them - made 2 adjustments to clarify the documentations. Applied all changes to Russian version too. |
Fixed description regarding garbage collection in backup.start()
Fixed backup.start() use description in disaster recovery. Note the ref-link to box.backup.stop() is the same as the start().
Fix gh-876 document reaction on error in replication configuration change Upd gh-868 Tarantool dependency list was changed Fix gh-869 Сonfusing wording in box.backup page Fix gh-893 feedback: Submodule box.info Fix gh-902 feedback: Сборка из исходных файлов Fix gh-915 feedback: Building from source Fix gh-920 feedback: Module vshard Fix gh-922 feedback: Module vshard
Uh oh!
There was an error while loading. Please reload this page.
It doesn't mean that instance turned into
read_only
mode by it self. It means that Tarantool snapshot garbage collector will not remove any checkpoints.It can also be noted that the creation of checkpoints in this case will occur by schedule.
The text was updated successfully, but these errors were encountered: