Skip to content

Commit

Permalink
doc grndb: add --force-lock-clear option's information
Browse files Browse the repository at this point in the history
  • Loading branch information
komainu8 committed Jan 11, 2018
1 parent 8e8c3e8 commit 32c5ef9
Show file tree
Hide file tree
Showing 2 changed files with 55 additions and 0 deletions.
34 changes: 34 additions & 0 deletions doc/locale/ja/LC_MESSAGES/reference.po
Expand Up @@ -16626,6 +16626,40 @@ msgstr ""
"に存在するデータベースのオブジェクトファイルの情報が食い違っているときです。 "
"他にデータベースを復旧する方法がないときのみ使うべきです。"

msgid "``--force-lock-clear``"
msgstr ""

msgid ""
"It forces to clear lock of locked objects (database, table, column). You can "
"use if you want to database recover even if remain locked of database."
msgstr ""
"ロックされているオブジェクト(データベース、テーブル、カラム)のロックを強制的"
"に解除します。データベースにロックが残留していてもデータベースを復旧させたい"
"場合に使えます。"

msgid "Here is example that specifies ``--force-lock-clear`` option::"
msgstr "以下は ``--force-lock-clear`` オプションを指定する例です。"

msgid "check whether there are locked objects (database, table, column)"
msgstr ""
"ロックされたオブジェクト(データベース、テーブル、カラム)がないかチェックしま"
"す。"

msgid "clear lock of locked objects (database, table, column)"
msgstr ""
"ロックされたオブジェクト(データベース、テーブル、カラム)のロックを解除しま"
"す。"

msgid ""
"You must use this option only when necessary. Because can not the safty "
"recover database if remain locked of database. This option should be used "
"when even if you can't recover the safety database, you want to recover the "
"database and operating it."
msgstr ""
"このオプションは必要なときのみ使用します。ロックが残留しているデータベースは"
"安全に復旧できないからです。このオプションは、安全にデータベースを復旧できな"
"い場合でも、データベースを復旧して操作したい場合に使用してください。"

msgid "grnslap"
msgstr ""

Expand Down
21 changes: 21 additions & 0 deletions doc/source/reference/executables/grndb.rst
Expand Up @@ -169,6 +169,27 @@ against truncated tables or columns to recreate database.

You must use this option only when necessary. It means that you use it when there is a mismatch between database meta information and database object files which exists actually. This options should be used when there is no other way to recover database.

``--force-lock-clear``
""""""""""""""""""""""

.. versionadded:: 7.1.1

It forces to clear lock of locked objects (database, table, column).
You can use if you want to database recover even if remain locked of database.

Here is example that specifies ``--force-lock-clear`` option::

% grndb recover --force-lock-clear --log-level info --log-path /var/log/groonga/grndb.log /var/lib/groonga/db/db

When this option is specified, ``grndb`` does the following:

* check whether there are locked objects (database, table, column)
* clear lock of locked objects (database, table, column)

.. note::

You must use this option only when necessary. Because can not the safty recover database if remain locked of database. This option should be used when even if you can't recover the safety database, you want to recover the database and operating it.

``--log-level``
"""""""""""""""

Expand Down

0 comments on commit 32c5ef9

Please sign in to comment.