-
Notifications
You must be signed in to change notification settings - Fork 43
feedback: Submodule box.info #893
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
Added follow status. Will need a translation.
Added follow status as per tarantool/tarantool#3904.
which means there is additional |
Fixed status name and some wording in description.
See tarantool/tarantool@a4a7744 It is a current time minus a time when a last row was sent by a relay. |
Is it time of "sent" by other server (so additional time sync issues possible) or local time the moment it has been received? |
As I see it is pure local value: when a relay sends a row it updates |
This is the same fix as with v. 1.10 but with added downstream.idle description. Translation needed
Updated the example to represent features, relevant to version 2.2
* Fix gh-893 (v.2.2 specific) feedback: Submodule box.info This is the same fix as with v. 1.10 but with added downstream.idle description. Translation needed * Update gh-893 feedback: Submodule box.info Updated the example to represent features, relevant to version 2.2 * Fix gh-899 feedback: Module key_def Added round brackets and pretify the text description. Translation needed for this page.
Added follow status. Will need a translation.
Fixed status name and some wording in description.
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
https://www.tarantool.io/en/doc/2.2/book/box/box_info/
This sentence is whong and should be re-checked
The text was updated successfully, but these errors were encountered: