-
Notifications
You must be signed in to change notification settings - Fork 96
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
Japanese translation of Releasenote 2.1.0 #1270
Conversation
|
||
Additional storage usage metrics are also available. . These metrics are gathered during storage calculation. Gathering these metrics is off by default, but you can turn it on by setting `detailed_storage_calc` to `true` in advanced.config. When you enable this option, you have access to information about how many manifests are `writing`, `pending_delete`, `scheduled_delete` and `active` which is not visible via the API. | ||
|
||
追加でストレージ使用量メトリクスも利用できるようになりました。このメトリクスはストレージ集計中に収集されます。デフォルトでメトリクス収集は無効化されていますが、advanced.config で `detailed_storage_calc` を `true` へ変更すると有効化できます。 このオプションを有効化すると、APIからは見えないマニフェストデータの情報にアクセスできます。これは`writing`、`pending_delete`、`scheduled_delete`、`active`の各状態にいくつのマニフェストが属しているか、という情報です。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
この「追加」は、既存の使用量メトリクスへの追加の意味なので、「これまでのメトリクスに加え、新しいストレージ使用量メトリクスも」とくどいくらいに書いた方が日本語としては自然かも
Good work. Once my comments are addressed and original English deleted, I'll throw my cents. |
Thanks. Updated. |
* `--leeway` has been added to create a temporary leeway period whose values are used only once and not repeated at the next run, and `--max-workers` has been added to allow you to override the concurrency value temporarily for a single run of garbage collector. [[PR 1147 ](https://github.com/basho/riak_cs/pull/1147)] | ||
* `--leeway` は猶予期間(leeway period)の値を一時的に設定します。これは一度だけ利用され、繰返して次の実行で利用されることはありません。そして、`--max-workers` はガベージコレクタ実行の並列度を一時的に変更します。[[PR 1147 ](https://github.com/basho/riak_cs/pull/1147)] | ||
* Riak S2 2.0 (and older) has a race condition where fullsync replication and garbage collection may resurrect deleted blocks without any way to delete them again. When real-time replication and replication of a garbage collection bucket entry object being dropped from the real-time queue are combined, blocks may remain on the sink side without being collected. Riak S2 2.1 introduces deterministic garbage collection to avoid fullsync replication. Additionally, garbage collection and fullsync replication run concurrently, and work on the same blocks and manifests. You can now specify the range of time using the `--start` and `--end` flags with `riak-cs-admin gc batch` for garbage collector in order to collect deleted objects synchronously on both sink and source sides. [[PR 1147 ](https://github.com/basho/riak_cs/pull/1147)] | ||
* Riak S2 2.0 (とそれ以前は) Fullsyncレプリケーションとガベージコレクションの競合状態の問題があり、削除したブロックが一旦復活し、二度と削除できなくなる可能性がありました。Realtimeレプリケーションと、Realtimeレプリケーションのキューから溢れたGCバケット内エントリのレプリカが混在すると、sink側でブロックが収集されずに残るのです。他にも、GCとFullsyncレプリケーションが平行に動き、同時に同一のブロックやマニフェストを処理した場合にも、これが起こり得ます。Riak S2 2.1 ではFullsyncレプリケーションを避ける、決定論的ガベージコレクションを導入しました。そして、sink側、souce側の双方で同期したオブジェクトの収集、削除を実施するために、ガベージコレクションの `riak-cs-admin gc batch` で、 `--start` および `--end` フラグによる、期間指定ができるようになりました。 [[PR 1147 ](https://github.com/basho/riak_cs/pull/1147)] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/平行/並行/
Please address one more thing. |
Fixed ! 💣 |
Japanese translation of Releasenote 2.1.0 Reviewed-by: kuenishi
0c3e377
to
5338c83
Compare
oops. Although +1 comment became invisible on this view after squashing commits, I'll merge this. |
@borshop merge |
Japanese translation of Releasenote 2.1.0
No description provided.