[close #610] [to #590] add docs for api v2 and tls reload#611
[close #610] [to #590] add docs for api v2 and tls reload#611iosmanthus merged 6 commits intotikv:masterfrom
Conversation
Signed-off-by: iosmanthus <myosmanthustree@gmail.com>
Codecov Report
@@ Coverage Diff @@
## master #611 +/- ##
============================================
- Coverage 34.67% 34.65% -0.03%
+ Complexity 1419 1417 -2
============================================
Files 278 278
Lines 17352 17352
Branches 1971 1971
============================================
- Hits 6017 6013 -4
- Misses 10718 10728 +10
+ Partials 617 611 -6
Continue to review full report at Codecov.
|
| - default: null | ||
|
|
||
| #### tikv.tls.reload_interval | ||
| - The interval in seconds to poll the change of SSL context, if a change detected, the SSL context will be rebuilded. |
There was a problem hiding this comment.
Maybe it is always watching the change of cert file rather than SSL context.
There was a problem hiding this comment.
The SSL context includes certificate files and private key files.
Signed-off-by: iosmanthus <myosmanthustree@gmail.com>
Signed-off-by: iosmanthus <myosmanthustree@gmail.com>
docs/src/examples/rawkv.md
Outdated
|
|
||
|
|
||
| ## API V2 | ||
| With TiKV version >= 6.1.0, we release a new feature that allows the coexistence of transcation data and raw data. This feature could allow the [TiCDC](https://github.com/tikv/migration/tree/main/cdc) to capture the change of the data, and these events could be consumed by the downstream infrastructure like Kafka or another TiKV cluster for backup. |
There was a problem hiding this comment.
CDC feature is not released in v6.1.0, and we will not implement cdc with TiCDC. Suggest just to refer to v6.1.0 release notes as:
| With TiKV version >= 6.1.0, we release a new feature that allows the coexistence of transcation data and raw data. This feature could allow the [TiCDC](https://github.com/tikv/migration/tree/main/cdc) to capture the change of the data, and these events could be consumed by the downstream infrastructure like Kafka or another TiKV cluster for backup. | |
| With TiKV version >= 6.1.0, we release a new feature called "TiKV API V2", which provides a new Raw Key Value storage format and access interface. Please refer to [v6.10 release notes](https://docs.pingcap.com/tidb/stable/release-6.1.0#ease-of-use) for detail. |
There was a problem hiding this comment.
a new Raw Key-Value storage format is a too general description of this feature, how about keeping the statement of the coexistence of transaction data and raw data.
There was a problem hiding this comment.
a new Raw Key-Value storage formatis a too general description of this feature, how about keeping the statement of the coexistence of transaction data and raw data.
LGTM.
There was a problem hiding this comment.
I mean:
| With TiKV version >= 6.1.0, we release a new feature that allows the coexistence of transcation data and raw data. This feature could allow the [TiCDC](https://github.com/tikv/migration/tree/main/cdc) to capture the change of the data, and these events could be consumed by the downstream infrastructure like Kafka or another TiKV cluster for backup. | |
| With TiKV version >= 6.1.0, we release a new feature called "TiKV API V2" which provides a new raw key-value storage format allowing the coexistence of transaction data and raw data. Please refer to [v6.10 release notes](https://docs.pingcap.com/tidb/stable/release-6.1.0#ease-of-use) for detail. |
Signed-off-by: iosmanthus <myosmanthustree@gmail.com>
f8258de to
2691bca
Compare
|
@zhangyangyu, Thanks for your review. The bot only counts LGTMs from Reviewers and higher roles, but you're still welcome to leave your comments. You are not a reviewer or committer or co-leader or leader. |
| - default: null | ||
|
|
||
| #### tikv.tls.reload_interval | ||
| - The interval in seconds to poll the change of TLS context, if a change detected, the SSL context will be rebuilded. |
There was a problem hiding this comment.
if a change detected -> if a change is detected
| - default: `"10s"`, `"0s"` means disable TLS context reload. | ||
|
|
||
| #### tikv.conn.recycle_time | ||
| - After `tikv.conn.recycle_time` (in seconds) with a TLS context reloading, the old connections will be forced to shutdown preventing channel leak. |
There was a problem hiding this comment.
will be forced to shutdown after recycle time to prevent channel leak.
docs/src/examples/rawkv.md
Outdated
|
|
||
|
|
||
| ## API V2 | ||
| With TiKV version >= 6.1.0, we release a new feature called "TiKV API V2" which provides a new raw key-value storage format allowing the coexistence of transaction data and raw data. Please refer to [v6.10 release notes](https://docs.pingcap.com/tidb/stable/release-6.1.0#ease-of-use) for detail. |
There was a problem hiding this comment.
transaction data and raw data -> TxnKV and RawKV
I personally think the latter is more familiar to TiKV developers.
Signed-off-by: iosmanthus <myosmanthustree@gmail.com>
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
|
cherry pick to release-3.3 in PR #614 |
Signed-off-by: iosmanthus myosmanthustree@gmail.com
What problem does this PR solve?
Issue Number: close #610, to #590
Related changes