profile
viewpoint
Calvin Weng dcalvin PingCAP Beijing

dcalvin/artwork 0

🖌CNCF related logos and artwork

dcalvin/cncf.io 0

Rebuild of cncf.io site

dcalvin/community 0

TiKV community content

dcalvin/community-1 0

TiDB community content

dcalvin/community-2 0

Kubernetes community content

dcalvin/docker.github.io 0

Source repo for Docker's Documentation

dcalvin/docs 0

TiDB/TiKV/PD documents.

dcalvin/docs-1 0

CockroachDB user documentation

Pull request review commenttikv/community

sig: refine some info of transaction SIG

 Covers transaction related work in TiKV, including improve transaction in TiKV a  ## Meetings -* Regular SIG Meeting: -     * Bi-weekly on Wed 10am, Beijing Time (Tue 6pm PST) starting from 2020/02/12. -     * Meeting Notes-     * Meeting Link+- Regular SIG Meeting:+  - Weekly on Fri 11am, Beijing Time starting from 2020/05/15.
  - Weekly at 11 a.m. Friday (Beijing Time), starting from 2020/05/15.
jackysp

comment created time in 9 hours

push eventanotherrachel/chaos-mesh

Ben Ye

commit sha bf8d82f323eed3ddbe0c206a1d1b245be11f5a94

support experiment deletion (#524) Signed-off-by: yeya24 <yb532204897@gmail.com>

view details

Calvin Weng

commit sha b8091f8f6789a5cba05ed4c3a7f302571711daa3

Merge branch 'master' into update-docs

view details

push time in 4 days

Pull request review commentpingcap/chaos-mesh

Refine docs

 Description:  ## Limitation -* Time modification will only be injected into the main process of container-* Time chaos has no effect on pure syscall `clock_gettime`-* All injected vdso call will use pure syscall to get realtime, so clock related function call will be much slower.\ No newline at end of file+* Time modification only can be injected into the main process of container.+* Time chaos has no effect on pure syscall `clock_gettime`.+* All injected vdso call use pure syscall to get realtime, so clock-related function call becomes much slower.

Do we need to explain vDSO? Also what do we mean by realtime?

anotherrachel

comment created time in 5 days

Pull request review commentpingcap/chaos-mesh

Refine docs

 Description:  ## Limitation -* Time modification will only be injected into the main process of container-* Time chaos has no effect on pure syscall `clock_gettime`-* All injected vdso call will use pure syscall to get realtime, so clock related function call will be much slower.\ No newline at end of file+* Time modification only can be injected into the main process of container.+* Time chaos has no effect on pure syscall `clock_gettime`.+* All injected vdso call use pure syscall to get realtime, so clock-related function call becomes much slower.
* All injected vDSO calls use pure system calls to get realtime, so clock-related function call can be much slower.
anotherrachel

comment created time in 5 days

Pull request review commentpingcap/chaos-mesh

Refine docs

 Description:  ## Limitation -* Time modification will only be injected into the main process of container-* Time chaos has no effect on pure syscall `clock_gettime`-* All injected vdso call will use pure syscall to get realtime, so clock related function call will be much slower.\ No newline at end of file+* Time modification only can be injected into the main process of container.
* Time modification can only be injected into the main process of container.
anotherrachel

comment created time in 5 days

pull request commenttikv/website

correct path to client docs

I merged it. Thanks for your contribution. @FlorianLudwig

FlorianLudwig

comment created time in 5 days

push eventtikv/website

Florian Ludwig

commit sha e2b3f04af91364cff34f8b75991724db48b8ccc9

correct path to client docs (#124)

view details

push time in 5 days

PR merged tikv/website

correct path to client docs

<!--Thanks for your contribution to TiKV documentation. -->

What is changed?

https://tikv.org/docs/3.0/tasks/try/ has to dead links that should point to the client docs.

Which version does your change affect?

+2 -2

1 comment

1 changed file

FlorianLudwig

pr closed time in 5 days

push eventtikv/website

Yu

commit sha d34077f314c93aa2367479bebe741a6d5c52ac3c

Remove 'a' to fix a grammar mistake (#150) Signed-off-by: Youwithouto <youwithouto.z@gmail.com>

view details

push time in 5 days

PR merged tikv/website

Remove 'a' to fix a grammar mistake

Signed-off-by: Youwithouto youwithouto.z@gmail.com

<!--Thanks for your contribution to TiKV documentation. -->

What is changed?

Remove 'a' from the sentence "Raft is generally seen as a more understandable and simpler to implement than Paxos." in the Consensus algorithm section of the doc website.

Any related PRs or issues?

<!--Provide a reference link that is related to your change. -->

Which version does your change affect?

+1 -2

0 comment

1 changed file

youwithouto

pr closed time in 5 days

Pull request review commentcncf/sig-network

Draft: SIG Network - Chaos Mesh Review

+# SIG Network Chaos Mesh Project Review++# Background++**[TOC PR](https://github.com/cncf/toc/pull/367)** ++**[Presentation Slide](https://docs.google.com/presentation/d/115QvSCnT6ROwwV1lK-R10d4MW54fQhtVM2uZDGscpEk/edit#slide=id.g80f082b201_0_0)**++**[Presentation Link](https://www.youtube.com/watch?v=SuRUtlSQbm4)**++**[GitHub](https://github.com/pingcap/chaos-mesh)**++**Name of Project:** Chaos Mesh  ++**Project Goal:**++Chaos Mesh is a versatile Chaos Engineering platform that orchestrates chaos experiments on Kubernetes environments. It features all-around fault injection methods for complex systems on Kubernetes, covering faults in Pod, network, file system, and even the kernel.++Chaos Mesh was originated from the internal chaos engineering platform at PingCAP to ensure the resilience of TiDB, its distributed database system. As the system evolves and testing requirements multiply, the team realized that they need an easy to use, scalable and universal chaos testing platform. The combination of chaos and Kubernetes became the natural choice.  Chaos Mesh uses CRD to define chaos objects, which makes it naturally integrate with the Kubernetes ecosystem. ++At the current stage, it supports the following fault injection types:++- pod-kill: Simulates Kubernetes Pods being killed+- pod-failure: Simulates Kubernetes Pods being continuously unavailable+- container-kill: Simulates Kubernetes Pod’s container being killed+- network-delay: Simulates network delay+- network-loss: Simulates network packet loss+- network-duplication: Simulates network packet duplication+- network-corrupt: Simulates network packet corruption+- network-partition: Simulates network partition+- I/O delay: Simulates file system I/O delay+- I/O errno: Simulates file system I/O errors+- Time skew: Simulates time jumping forward or backward++Besides the versatile chaos types, it also offers Chaos Dashboard (under development), a visualized panel that shows the impacts of chaos experiments on the online services of the system, which makes chaos tests easily observable and manageable. ++**Current Status:**++* Stars: 1500++* Contributors: 23+* Commits: 240++* Forks: 88+++** Future Plans: ** ++**Roadmap**:++See [https://github.com/pingcap/chaos-mesh/blob/master/ROADMAP.md](https://github.com/pingcap/chaos-mesh/blob/master/ROADMAP.md)+++## Project Scope ++## Clear project definition+Does the project have a clear and well defined scope?++SIG Network agrees that Chaos Mesh has a well defined scope. ++Value-add to the CNCF ecosystem+Does the project have a clear value add to the current project ecosystem? How does it relate to other projects with overlapping capabilities? ++ChaosMesh is a universally applicable Chaos Engineering platform and would allow for further resiliency in CNCF projects. +++## Alignment with other CNCF projects+Does the project align and actively collaborate with other CNCF projects? ++##### Put other projects here ########++## Alignment with SIG-Network+++## High level architecture:+https://docs.google.com/presentation/d/115QvSCnT6ROwwV1lK-R10d4MW54fQhtVM2uZDGscpEk/edit#slide=id.g80deb1f634_0_331 ++# Formal Requirements++Document that the project fulfills the requirements as documented in the (CNCF graduation criteria)[https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc]+Sandbox Stage+As ChaosMesh is submitted at the sandbox stage it needs to meet the following criteria.++*   ChaosMesh is requesting 3 TOC sponsors+*   ChaosMesh will adopt the CNCF [Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md) -- this has not yet been done +*   ChaosMesh will adhere to CNCF [IP Policy](https://github.com/cncf/foundation/blob/master/charter.md#11-ip-policy) (including trademark transferred)
*   Chaos Mesh is requesting 3 TOC sponsors
*   Chaos Mesh will adopt the CNCF [Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md) -- this has not yet been done 
*   Chaos Mesh will adhere to CNCF [IP Policy](https://github.com/cncf/foundation/blob/master/charter.md#11-ip-policy) (including trademark transferred)
leecalcote

comment created time in 5 days

Pull request review commentcncf/sig-network

Draft: SIG Network - Chaos Mesh Review

+# SIG Network Chaos Mesh Project Review++# Background++**[TOC PR](https://github.com/cncf/toc/pull/367)** ++**[Presentation Slide](https://docs.google.com/presentation/d/115QvSCnT6ROwwV1lK-R10d4MW54fQhtVM2uZDGscpEk/edit#slide=id.g80f082b201_0_0)**++**[Presentation Link](https://www.youtube.com/watch?v=SuRUtlSQbm4)**++**[GitHub](https://github.com/pingcap/chaos-mesh)**++**Name of Project:** Chaos Mesh  ++**Project Goal:**++Chaos Mesh is a versatile Chaos Engineering platform that orchestrates chaos experiments on Kubernetes environments. It features all-around fault injection methods for complex systems on Kubernetes, covering faults in Pod, network, file system, and even the kernel.++Chaos Mesh was originated from the internal chaos engineering platform at PingCAP to ensure the resilience of TiDB, its distributed database system. As the system evolves and testing requirements multiply, the team realized that they need an easy to use, scalable and universal chaos testing platform. The combination of chaos and Kubernetes became the natural choice.  Chaos Mesh uses CRD to define chaos objects, which makes it naturally integrate with the Kubernetes ecosystem. ++At the current stage, it supports the following fault injection types:++- pod-kill: Simulates Kubernetes Pods being killed+- pod-failure: Simulates Kubernetes Pods being continuously unavailable+- container-kill: Simulates Kubernetes Pod’s container being killed+- network-delay: Simulates network delay+- network-loss: Simulates network packet loss+- network-duplication: Simulates network packet duplication+- network-corrupt: Simulates network packet corruption+- network-partition: Simulates network partition+- I/O delay: Simulates file system I/O delay+- I/O errno: Simulates file system I/O errors+- Time skew: Simulates time jumping forward or backward++Besides the versatile chaos types, it also offers Chaos Dashboard (under development), a visualized panel that shows the impacts of chaos experiments on the online services of the system, which makes chaos tests easily observable and manageable. ++**Current Status:**++* Stars: 1500++* Contributors: 23+* Commits: 240++* Forks: 88+++** Future Plans: ** ++**Roadmap**:++See [https://github.com/pingcap/chaos-mesh/blob/master/ROADMAP.md](https://github.com/pingcap/chaos-mesh/blob/master/ROADMAP.md)+++## Project Scope ++## Clear project definition+Does the project have a clear and well defined scope?++SIG Network agrees that Chaos Mesh has a well defined scope. ++Value-add to the CNCF ecosystem+Does the project have a clear value add to the current project ecosystem? How does it relate to other projects with overlapping capabilities? ++ChaosMesh is a universally applicable Chaos Engineering platform and would allow for further resiliency in CNCF projects. 
Chaos Mesh is a universally applicable Chaos Engineering platform and would allow for further resiliency in CNCF projects. 
leecalcote

comment created time in 5 days

Pull request review commentcncf/sig-network

Draft: SIG Network - Chaos Mesh Review

+# SIG Network Chaos Mesh Project Review++# Background++**[TOC PR](https://github.com/cncf/toc/pull/367)** ++**[Presentation Slide](https://docs.google.com/presentation/d/115QvSCnT6ROwwV1lK-R10d4MW54fQhtVM2uZDGscpEk/edit#slide=id.g80f082b201_0_0)**++**[Presentation Link](https://www.youtube.com/watch?v=SuRUtlSQbm4)**++**[GitHub](https://github.com/pingcap/chaos-mesh)**++**Name of Project:** Chaos Mesh  ++**Project Goal:**++Chaos Mesh is a versatile Chaos Engineering platform that orchestrates chaos experiments on Kubernetes environments. It features all-around fault injection methods for complex systems on Kubernetes, covering faults in Pod, network, file system, and even the kernel.++Chaos Mesh was originated from the internal chaos engineering platform at PingCAP to ensure the resilience of TiDB, its distributed database system. As the system evolves and testing requirements multiply, the team realized that they need an easy to use, scalable and universal chaos testing platform. The combination of chaos and Kubernetes became the natural choice.  Chaos Mesh uses CRD to define chaos objects, which makes it naturally integrate with the Kubernetes ecosystem. ++At the current stage, it supports the following fault injection types:++- pod-kill: Simulates Kubernetes Pods being killed+- pod-failure: Simulates Kubernetes Pods being continuously unavailable+- container-kill: Simulates Kubernetes Pod’s container being killed+- network-delay: Simulates network delay+- network-loss: Simulates network packet loss+- network-duplication: Simulates network packet duplication+- network-corrupt: Simulates network packet corruption+- network-partition: Simulates network partition+- I/O delay: Simulates file system I/O delay+- I/O errno: Simulates file system I/O errors+- Time skew: Simulates time jumping forward or backward++Besides the versatile chaos types, it also offers Chaos Dashboard (under development), a visualized panel that shows the impacts of chaos experiments on the online services of the system, which makes chaos tests easily observable and manageable. ++**Current Status:**++* Stars: 1500++* Contributors: 23+* Commits: 240++* Forks: 88+++** Future Plans: ** ++**Roadmap**:++See [https://github.com/pingcap/chaos-mesh/blob/master/ROADMAP.md](https://github.com/pingcap/chaos-mesh/blob/master/ROADMAP.md)+++## Project Scope ++## Clear project definition+Does the project have a clear and well defined scope?++SIG Network agrees that Chaos Mesh has a well defined scope. ++Value-add to the CNCF ecosystem
## Value-add to the CNCF ecosystem
leecalcote

comment created time in 5 days

Pull request review commentcncf/sig-network

Draft: SIG Network - Chaos Mesh Review

+# SIG Network Chaos Mesh Project Review++# Background++**[TOC PR](https://github.com/cncf/toc/pull/367)** ++**[Presentation Slide](https://docs.google.com/presentation/d/115QvSCnT6ROwwV1lK-R10d4MW54fQhtVM2uZDGscpEk/edit#slide=id.g80f082b201_0_0)**++**[Presentation Link](https://www.youtube.com/watch?v=SuRUtlSQbm4)**++**[GitHub](https://github.com/pingcap/chaos-mesh)**++**Name of Project:** Chaos Mesh  ++**Project Goal:**++Chaos Mesh is a versatile Chaos Engineering platform that orchestrates chaos experiments on Kubernetes environments. It features all-around fault injection methods for complex systems on Kubernetes, covering faults in Pod, network, file system, and even the kernel.++Chaos Mesh was originated from the internal chaos engineering platform at PingCAP to ensure the resilience of TiDB, its distributed database system. As the system evolves and testing requirements multiply, the team realized that they need an easy to use, scalable and universal chaos testing platform. The combination of chaos and Kubernetes became the natural choice.  Chaos Mesh uses CRD to define chaos objects, which makes it naturally integrate with the Kubernetes ecosystem. ++At the current stage, it supports the following fault injection types:++- pod-kill: Simulates Kubernetes Pods being killed+- pod-failure: Simulates Kubernetes Pods being continuously unavailable+- container-kill: Simulates Kubernetes Pod’s container being killed+- network-delay: Simulates network delay+- network-loss: Simulates network packet loss+- network-duplication: Simulates network packet duplication+- network-corrupt: Simulates network packet corruption+- network-partition: Simulates network partition+- I/O delay: Simulates file system I/O delay+- I/O errno: Simulates file system I/O errors+- Time skew: Simulates time jumping forward or backward++Besides the versatile chaos types, it also offers Chaos Dashboard (under development), a visualized panel that shows the impacts of chaos experiments on the online services of the system, which makes chaos tests easily observable and manageable. ++**Current Status:**++* Stars: 1500++* Contributors: 23+* Commits: 240++* Forks: 88+
* Stars: 1700+
* Contributors: 33
* Commits: 330+
* Forks: 128
* Releases: 1 (V1.0 coming soon)
leecalcote

comment created time in 5 days

issue commenttikv/website

Sticky nav wastes 1/3 of the screen on mobile

This is also included in our refactored plan which will be rolled out soon. Thanks @de-sh and @focusaurus

focusaurus

comment created time in 9 days

issue commenttikv/website

Broken link to Community on Deep Dive page

Thanks @de-sh. Actually we have plan to refactor the website recently, which including a re-purposed community page.

james-jra

comment created time in 9 days

issue commenttikv/website

Broken link from Tikv Ansible Deployment

Close as solved.

liuhao2050

comment created time in 9 days

issue closedtikv/website

Page not found about Key Metrics

The Overview of the TiKV Monitoring Framework in Key Metrics is not found.

Please fix it. Thanks

closed time in 9 days

yufeiminds

issue commenttikv/website

Page not found about Key Metrics

Close this as solved

yufeiminds

comment created time in 9 days

push eventtikv/website

Devdutt Shenoi

commit sha 725134c67b9605492d01a7bc0d9c3c378fb3bb7f

Correct links (#161) * Correct links in talent-plan article Signed-off-by: Devdutt Shenoi <devdutt@outlook.in> * Correct links including solution to #146 Signed-off-by: Devdutt Shenoi <devdutt@outlook.in> * Correct links mentioned in key metrics solving #158 Signed-off-by: Devdutt Shenoi <devdutt@outlook.in>

view details

push time in 9 days

PR merged tikv/website

Correct links

<!--Thanks for your contribution to TiKV documentation. -->

What is changed?

Correct links as they caused a bit of confusion. <!--Tell us what you did and why.-->

Any related PRs or issues?

Solved #146 and #158 <!--Provide a reference link that is related to your change.

Which version does your change affect?-->

+6 -6

0 comment

3 changed files

de-sh

pr closed time in 9 days

issue commenttikv/tikv

Add vulnerability disclosure documentation and link it to the “Community” menu

Vulnerability disclosure process as included https://github.com/tikv/tikv/issues/7008.

shafreeck

comment created time in 11 days

push eventpingcap/community

WT

commit sha a0cd4c832a8de96f745bc5843dfe46d491e5ea55

Create bug-hunting-program.md (#200)

view details

Yue Yang

commit sha 0d4ffda0af957c4dcd8d1d982cd400fa6d723e11

rfc: add discourse theme asktug into incubator programs (#202)

view details

Soline

commit sha 392ce16e677fae2649a3ab30167c227db840d66a

governance: add SIG governance and charter template (#150)

view details

notginger

commit sha 8e8314cf333a97b4c8394ba7b086d5654a48c483

update rules (#205) Co-authored-by: Calvin Weng <wenghao@pingcap.com>

view details

Calvin Weng

commit sha f11eb00671900374e4c303646910dc6ad3fa0753

update rules (#208)

view details

winkyao

commit sha 812c03645380714eb348cdde7217dd42a2864e48

README: clarify that AskTUG is using Chinese

view details

sykp241095

commit sha 13586a5936e5a1ca1ed489538be37d95f533ec90

SIG: add sig-web (#204) * Add new sig: sig-web * Typo fix Co-authored-by: Shirly <wuxuelian@pingcap.com>

view details

Ran

commit sha d3d80473d2592fff22c07c400a71f569c2987fd3

sig-docs: add new contributors (#209) * sig-docs: add new contributors * add PR numbers

view details

Yecheng Fu

commit sha 4edce3fe3683a0a0f3393e36723b3e8ff5d1edb0

[sig-k8s] rename K8S to K8s (#210)

view details

Lilian Lee

commit sha b8caee692f45693fa23e869eabae28e2f9a8ee0e

sig: update #sig-docs Slack link (#214)

view details

Ran

commit sha 78750aaaa0ad98c8f1a59cd73b991d6410cb04f0

sig: update #sig-docs slack link (#215)

view details

bb7133

commit sha 88953701aec9872a51739aef0ba832f0d03c7581

sig: update #sig-ddl slack invitation link (#218)

view details

ShuNing

commit sha 28c3aee45eafe23babbf278615fb36fad40a8ad4

sig: update the link of sig-scheduling (#213) * sig: update the link of sig-scheduling Signed-off-by: nolouch <nolouch@gmail.com>

view details

zhouqiang

commit sha 27e284161290792c22af60f722e70ab4d2445daa

add release checker doc (#217) * add release checker doc

view details

Ran

commit sha 3a0788700083fb372c48b0c0864a191b9ae9180f

sig-docs: update slack link for sig-docs (#220)

view details

Ran

commit sha feb7757802b9464d55974f91f82da44b644ce0a6

sig-docs: update contributor list (#219) Update the contributor list of May 8th. Co-authored-by: Lilian Lee <lilin@pingcap.com>

view details

Yecheng Fu

commit sha dd68b2e1e161f0a2837b1b6665f1f52218dc941f

[sig-k8s] use sig-k8s as the channel name (#211)

view details

Ran

commit sha c1f1b66df1932688158e106e2352f0d4f52a39fe

sig-docs: add the member list for all roles (#225)

view details

kennytm

commit sha 09faacf68257b6f27bb5ff7edcb52b01e9bee71d

sig-tools: update member list and meeting info (#224)

view details

Yecheng Fu

commit sha cd232920f05df1ed3b533bc1e05d2c57a50e9641

[sig-k8s] update member list (#223)

view details

push time in 12 days

pull request commentcncf/toc

add chaos mesh proposal for sandbox entry

Hi, @leecalcote @amye How are we going with SIG review? Is there something you need from our end?

dcalvin

comment created time in 12 days

push eventtikv/website

WT

commit sha 2b20d9bb66bae64a2950d028bbd9fe4ffd8ee9db

add implement raft in rust (#159) * add implement raft in rust Signed-off-by: Wenting Liu <liuwenting@pingcap.com>

view details

push time in 12 days

PR merged tikv/website

add implement raft in rust

Signed-off-by: Wenting Liu liuwenting@pingcap.com

<!--Thanks for your contribution to TiKV documentation. -->

What is changed?

add a blog Implement raft in rust

Any related PRs or issues?

N/A

<!--Provide a reference link that is related to your change. -->

Which version does your change affect?

N/A

+147 -0

0 comment

2 changed files

WT-Liu

pr closed time in 12 days

pull request commentcncf/toc

TiKV graduation proposal

Presented to SIG-Storage on May 13 call. Thanks @erinaboyd @chira001 for hosting us, and @saad-ali from TOC for stepping up to lead the DD review. TiKV maintainers and I are ready to address further comments.

dcalvin

comment created time in 13 days

pull request commentcncf/toc

TiKV graduation proposal

@erinaboyd This is the slide for SIG presentation:

https://docs.google.com/presentation/d/1c9ylDqv6b6I-LOyl-C-aqOibB9HjinM8ybTsOgtLrzE/edit#slide=id.g446c4deb4d_0_341

dcalvin

comment created time in 13 days

issue closedtikv/tikv

Add SECURITY.md

Feature Request

Is your feature request related to a problem? Please describe:

<!-- A description of what the problem is. -->

To ensure a secure and responsible disclosure of security vulnerabilities, it is important to have a dedicated point of contact. This person/team should be known, meaning that all necessary information such as an email address and preferably also encryption keys of that contact should be communicated appropriately. The MAINTAINERS.md file lists email addresses of project maintainers that can be contacted to report vulnerabilities. However, the document omits important details, such as the respective PGP keys and an outline of the disclosure process. The guideline on where to report security issues is quite hidden as it is part of the document that also explains how to set up certificates in TiKV. This is clearly not the appropriate place to present this kind of information. Instead, it is advised to put all details related to reporting

Describe the feature you'd like:

<!-- A description of what you want to happen. -->

Add SECURITY.md in the root repository.

Describe alternatives you've considered:

<!-- A description of any alternative solutions or features you've considered. -->

Teachability, Documentation, Adoption, Migration Strategy:

<!-- If you can, explain some scenarios how users might use this, or situations in which it would be helpful. Any API designs, mockups, or diagrams are also helpful. -->

closed time in 13 days

shafreeck

issue commenttikv/tikv

Add SECURITY.md

Closing this issue as resolved in https://github.com/tikv/tikv/pull/7820

shafreeck

comment created time in 13 days

push eventtikv/tikv

Lei Zhao

commit sha 3a1002b5ee9c943bad0ed70ad9620b3d354bd742

storage: add tests for pipelined pessimistic lock (#7706) Signed-off-by: youjiali1995 <zlwgx1023@gmail.com>

view details

Calvin Weng

commit sha df3ae6a87ef932cb98ff3dfe898d4b603dbcfd7f

Merge branch 'master' into WT-Liu-add-security

view details

push time in 13 days

pull request commenttikv/tikv

Update- security

/merge

WT-Liu

comment created time in 13 days

push eventtikv/tikv

TXXT

commit sha 18675bf7f8c6d06ee55dcafdb11c89bb596f2152

update grpcio version (#7819) Signed-off-by: TXXT <hunterlxt@live.com> Co-authored-by: qupeng <qupeng@pingcap.com>

view details

Calvin Weng

commit sha 42e7ad1e80b0680285d82f9015412ecb3cf91710

Merge branch 'master' into WT-Liu-add-security

view details

push time in 13 days

Pull request review commenttikv/tikv

Update- security

+# TiKV Security Policy++As a widely adopted distributed storage service, TiKV attaches great importance to code security. We are very grateful to users, security vulnerability researchers, etc. for reporting security vulnerabilities to us. All reported security vulnerabilities will be carefully assessed, addressed, and answered by us.++This document describes the security process and policy followed by the TiKV project.++## TiKV Security Team++Security vulnerabilities should be handled quickly and sometimes privately. The primary goal of this process is to reduce the total time users are vulnerable to publicly known exploits.++The TiKV Security Team is responsible for organizing the entire response including internal communication and external disclosure but will need help from relevant developers to successfully run this process.++The TiKV Security Team will consist of TiKV contributors assigned by the TiKV Maintainer team. ++## Supported versions++The following are the versions that we support for security updates++| Version | Supported          |+| ------- | ------------------ |+| 4.x   | :white_check_mark: |+| 3.x   | :white_check_mark: |+| 2.x   | :white_check_mark: |+| < 2.0   | :x:                |++## Reporting a vulnerability++For all TiKV security-related defects, please send an email to tikv-security@lists.cncf.io. This mailing list is specially maintained by the TiKV security team. You will receive an acknowledgement mail within 24 hours. After that, we will give a detailed response about the subsequent process within 48 hours. Please do not submit security vulnerabilities directly as Github Issues.++If you want to, you can choose to use the PGP public key provided by us to encrypt the content of the mail. The public key is provided at the end of this document.++## Disclosure policy++For known public security vulnerabilities, we will disclose the disclosure as soon as possible after receiving the report. Vulnerabilities discovered for the first time will be disclosed in accordance with the following process:+1. The received security vulnerability report shall be handed over to the security team for follow-up coordination and repair work.+2. After the vulnerability is confirmed, we will create a draft Security Advisory on Github that lists the details of the vulnerability.+3. Invite related personnel to discuss about the fix+4. Fork the temporary private repository on Github, and collaborate to fix the vulnerability+5. After the fix code is merged into all supported versions, the vulnerability will be publicly posted in the GitHub Advisory Database+	+## PGP Public Key++-----BEGIN PGP PUBLIC KEY BLOCK-----
···
-----BEGIN PGP PUBLIC KEY BLOCK-----
WT-Liu

comment created time in 13 days

Pull request review commenttikv/tikv

Update- security

+# TiKV Security Policy++As a widely adopted distributed storage service, TiKV attaches great importance to code security. We are very grateful to users, security vulnerability researchers, etc. for reporting security vulnerabilities to us. All reported security vulnerabilities will be carefully assessed, addressed, and answered by us.++This document describes the security process and policy followed by the TiKV project.++## TiKV Security Team++Security vulnerabilities should be handled quickly and sometimes privately. The primary goal of this process is to reduce the total time users are vulnerable to publicly known exploits.++The TiKV Security Team is responsible for organizing the entire response including internal communication and external disclosure but will need help from relevant developers to successfully run this process.++The TiKV Security Team will consist of TiKV contributors assigned by the TiKV Maintainer team. ++## Supported versions++The following are the versions that we support for security updates++| Version | Supported          |+| ------- | ------------------ |+| 4.x   | :white_check_mark: |+| 3.x   | :white_check_mark: |+| 2.x   | :white_check_mark: |+| < 2.0   | :x:                |++## Reporting a vulnerability++For all TiKV security-related defects, please send an email to tikv-security@lists.cncf.io. This mailing list is specially maintained by the TiKV security team. You will receive an acknowledgement mail within 24 hours. After that, we will give a detailed response about the subsequent process within 48 hours. Please do not submit security vulnerabilities directly as Github Issues.++If you want to, you can choose to use the PGP public key provided by us to encrypt the content of the mail. The public key is provided at the end of this document.++## Disclosure policy++For known public security vulnerabilities, we will disclose the disclosure as soon as possible after receiving the report. Vulnerabilities discovered for the first time will be disclosed in accordance with the following process:+1. The received security vulnerability report shall be handed over to the security team for follow-up coordination and repair work.+2. After the vulnerability is confirmed, we will create a draft Security Advisory on Github that lists the details of the vulnerability.+3. Invite related personnel to discuss about the fix+4. Fork the temporary private repository on Github, and collaborate to fix the vulnerability+5. After the fix code is merged into all supported versions, the vulnerability will be publicly posted in the GitHub Advisory Database+	+## PGP Public Key++-----BEGIN PGP PUBLIC KEY BLOCK-----++mQINBF65AgsBEADGYwoBKPUhCZgz24AGnJtOB/LgCRuqZupJHY/RmYdchKWIGHIv+buIP6890L2OlzyxItNWbZmGM6fgcqFpPKWX1budsDI01hafoPyIM/fpuWUCip5Pm+rXEaGXXmouVVeAS2fSkHXT2ZLCN4bzPvIwoc28a99QPRG+ldNYzsle7oNus12s+C+l7ZhNXsmyILc9c6cxkUN+hKx4jDeLBh1FbK5pbYWLWxfwmfz7wsogRRuDovtJmtX+JgHR/LZwU7RpHEPsU/IHeLhoC406sCTvAcUSH0M7LF2O4x9Crf/niGETjRAxH3nW+bYjJYcziL1IrvWsHhA11AGLkwpmCMilY1gHHnbbkslv5Gzx6nLQ/rA1Q2/R5KfKV+PwsrDavGtAgE3SAXw9WiBOpZK+zkKVdGHlit/G7qX1Y54Ez/UyYbqVsTH97cberU+chhu6eeI7ewV4Jp7yxaKK0QWEZufxioN5uoGCdyEGSvA3hkSNIpmPvKZN2/6ZqHb+87rT6zluTlMWuP7yVkhxF7BSanjNDvsiX+ZNjJiB/j4d3W8DXa8HH0EF5036QrDb+ofEELY9MDBlWzBTEtdJ+d5G6Ol3xOe0dUpWJagzyVH4gmHh9ybYiNhvaliF48gnt+pCDWZXn3HKUgSF09OjxuuUMzM5f1GA6QoplpSPTvM3C7sFV67sfRW4lXbwARAQAB+tDBUaUtWIFNlY3VyaXR5IFRlYW0gPHRpa3Ytc2VjdXJpdHlAbGlzdHMuY25jZi5p+bz6JAlQEEwEIAD4WIQTgOW4PEUEI8cZyOUfKixh14wzMzAUCXrkCCwIbAwUJA8Jn+AAULCQgHAgYVCgkICwIEFgIDAQIeAQIXgAAKCRDKixh14wzMzCfSD/91m/zL/dVm+NK2hQ8XUKHYECGWSCIwX2V7CLuqrj5oUlP3BWZvFoKdW0gcr0youywDPSwNLbx9++Mk56hWpYLaMyM1+bFS80eP+Ro0VWZ68FujPYzdkbVDxlF+GVGm7znwPcFRNBfuNe+Ey8f6cOFOMb/FgWxOV2UzLuO5xywI18Lbzk/s9cA32KIu5aLd8Pi0nLQss+XE4PT+9vPiZ1+4LHW5wzUIsX0mtxQRO0wcvdM2Tl/rsVSKIGFjU+riv5/sdWCiZ1ymdamp+++abu26S8XCFcwdcElchhPPGef0YnNmd+O5UQ3gVnpxtlmrKvCzeEw8SCvRRaaLa+ulH0aDH6BLYYXOy5hc3OAySL5xZk77k4oOREXwGtgu8kbzBpJYEvls+cuezDEohG+f1oAmGdj0ntJZqrOXuOOtVFnOMTn8NxnFZ0Zz4f2MJpGQX8mx3wS26FbPnPlC8MA+fqSQ5eo6sz/51fiEkwrvjwTvA98LhhqMkNq5+jatfko7Pe8QfXOERcfTXxlJSK3u+Mrr48ZCzvf4o1Cwnyv1TvCIZQBY0DrM0GHh7J5tXuLjD38O9m+UjxhHh7tyQZcyh+tXsiIOZwmme2EDuJ3kvB08Qr4vRrIKfOa1N4n2+qR1imN0l9YcrYY5ib1nyYAZRX+TcMEt1CESrcNBlcaL+nkFXwOaC4hqB3Ha7kCDQReuQILARAAwgzslCYn3kL01EBH+V6CQKc21nhSM0Qv+ehRJnZL9t5Ke074aevG3/4a5P07ze5cqKs/jSa/0wV+PP/yG+19TZrg6VtJ949ly3Hh+CHpVGBzhhX10cJs58b3/Q95LX4jBNJQcYbgSPDRw5KFkq+oIPJzD4wvBadrK7N7ZW19cLIoA8v6H8fvKiJCFfuD1ijh5W4F5pMyWxgcIEroppg+7uLaz1GX0GDDFKXxNk5jd8iFgRpCUZYuvryGO8wWxGpLIB3BWb/dNEQeCKYno4Ng+NdTA/tWBR5sQEYitkNQhAl4K1BRj52nwNVXdZWDxMtKhpxwUtzpUnb57fRm+wMWH+FvEEgtyfNVWkrt4/U6pyTmn1Ic4IHh3H3HhA5rhnqLQLW+9Brmv+TsOUdxRueQIw+KLcdjKPYfpU4BKhzbSnYs3JgFEJapXByZEsA5aFfpfANBJj8NoKiHM91R0g86Iv++I+nyAgOHE+6+sdHT7f5XKkt3gTPmIjpP3Li3NUTPDrzMcdfMxxbe937Ej9v1cSNY+3++VWWTKFqAa/MRPbcWaPx7sZQhERkyzuUBle1+7bdswXNApbczjnnxV2gvRMQq1+VJC9TGjTOQwF/ex+lkZiffjaVSeGdjsDBOUKyx7oQvSoSi6OuIJGswoN68wk0PO3+lw/vAtSomcLVIl4bhpd1gUUoZ3sAEQEAAYkCPAQYAQgAJhYhBOA5bg8RQQjxxnI5+R8qLGHXjDMzMBQJeuQILAhsMBQkDwmcAAAoJEMqLGHXjDMzMsgAQAInDBThgzaEl+zBJ8jLxVECw3V8LLKEaOp4Yl8G6caIzLJQ+8pFgWBmtua8IM3MsvfM6u5ET0cXqa+HXQcX91kCKS+GWIrTeC8zliOTeksrpz0orzMzAhxx5qK4WtgbcpU8FuvSF+v7JCm+U/YX8aGZJufrxeTgR4OmOoZUNtXO1YljVpLpxi0U0a2BMztSRATd9JQchEp5pGT/+Cvsf/45LtqEYY/NOHCZVqmZmF8RqTdwrcH5f1EP31J+F9IoVgonw+4VAUCqBiQQk+2MGR4XBASTYbJ8v8b8gzf2R0HZgvrDXxz1nwEaikmU7W+0r2RDGQy+etfJsarwkS+qwmc1AiznSTiuu1x9iV44tnCcmdFo3YFcd8kRHr1aIy1kdaXCL+Lns5HLmKKfOjQ+j9bAH01FuSSlPLoaTWoqf+Sm3Fu/KeW0mQHulDXujV1lYX0jUxy7lmj2P/yR8ZdD+12o9srqrh4Rja72g5utmA7ZTuSq4YwsXvQ13c3agZKO+WuiQkRfsgkh/NIWTyCXn+IvCICV7zG1cyuM/Z2Y7/TJ+upvahP46nM3s3G15b8FYuTSmRN1Kp9+mBt2BHqOy1+5MKKdj+J5co/zuRpgsuIIgTDrkS0UjN57BsHbIXhTQmQeablbIaMUtIxCH8t0V3K+ulx+VF4Lf9n3ydf593Nha9bMJ/rnSp01+=XbYK+-----END PGP PUBLIC KEY BLOCK-----
-----END PGP PUBLIC KEY BLOCK-----
···
WT-Liu

comment created time in 13 days

Pull request review commenttikv/tikv

add security

 Quick links:  ## Security - ### Security Audit  A third-party security auditing was performed by Cure53. See the full report [here](./docs/Security-Audit.pdf). +### Reporting Security Vulnerabilities++To report a security vulnerability, please send an email to tikv-security@lists.cncf.io.
To report a security vulnerability, please send an email to the [tikv-security](tikv-security@lists.cncf.io) group.
WT-Liu

comment created time in 13 days

pull request commenttikv/tikv

update community meeting with video links

/merge

WT-Liu

comment created time in 13 days

push eventWT-Liu/tikv

Lei Zhao

commit sha 9eb70c42397ad04d88b705d10f4d576bc1b401f9

storage: add tests for lock manager (#7663) Signed-off-by: youjiali1995 <zlwgx1023@gmail.com>

view details

Yilin Chen

commit sha cc9ac0d176e66bdcd86c7a123eac60c3e647d9c4

*: use given task id or random number as task id (#7521) Signed-off-by: Yilin Chen <sticnarf@gmail.com> Signed-off-by: Jay Lee <BusyJayLee@gmail.com>

view details

yiwu-arbug

commit sha 3adc3dab0b445efddeea4dd678eae1d2733215e5

encryption: Fix errors related to file ingestion (#7806) Signed-off-by: Yi Wu <yiwu@pingcap.com>

view details

NingLin-P

commit sha 0649dc17e0edfea8619ffac958cf6f4b0c45f72a

config: fix write config change to config file (#7795) Signed-off-by: linning <linningde25@gmail.com>

view details

Shuyang Wu

commit sha 87cada4de668ddf6f5330ea188d80ab703554908

Fix broken URL for "how-to/deploy" (#7809) Signed-off-by: Yiyiyimu <wosoyoung@gmail.com>

view details

Calvin Weng

commit sha 9809b9588ca1a4fb878beb6d79beaf9073d5c94f

Merge branch 'master' into update-meeting-videos

view details

push time in 13 days

pull request commenttikv/tikv

update VNG

LGTM

WT-Liu

comment created time in 14 days

push eventWT-Liu/tikv

Connor

commit sha 39b243217f5fe2c3f37f9283350b89ccb11f6238

engine: Add titan customized statistics (#6328) Signed-off-by: Connor1996 <zbk602423539@gmail.com> Signed-off-by: Connor <zbk602423539@gmail.com>

view details

yiwu-arbug

commit sha e26bc916c330fec127ca250fc065c6ffb56f766c

encryption: move encryption config to under security config (#7800) Signed-off-by: Yi Wu <yiwu@pingcap.com>

view details

Nick Cameron

commit sha ffea7ec19bfd8495c2d7fff4371aa49d51e0a3d0

storage,config: check size of lock cf when considering large CFs (#7676) Signed-off-by: Nick Cameron <nrc@ncameron.org> Signed-off-by: youjiali1995 <zlwgx1023@gmail.com>

view details

Calvin Weng

commit sha 153b16bb42f3657816f39a5f7139206e4d79914b

Merge branch 'master' into update-vng

view details

push time in 14 days

pull request commentcncf/artwork

update TiKV logos

@KimMcMahon FYI

WT-Liu

comment created time in 15 days

push eventtikv/website

Yu

commit sha acb42de17977d1b9258c005ab456de367bad46f2

Change the upstream URL to the correct one (#151) Signed-off-by: Youwithouto <youwithouto.z@gmail.com>

view details

push time in 15 days

PR merged tikv/website

Change the upstream URL to the correct one

Signed-off-by: Youwithouto youwithouto.z@gmail.com

<!--Thanks for your contribution to TiKV documentation. -->

What is changed?

The upstream URL in the CONTRIBUTING.md file is incorrect.

This fix changes the upstream URL from git@github.com:tikv/tikv.git to git@github.com:tikv/website.git.

Any related PRs or issues?

<!--Provide a reference link that is related to your change. -->

Which version does your change affect?

+1 -1

0 comment

1 changed file

youwithouto

pr closed time in 15 days

push eventtikv/website

Calvin Weng

commit sha e5480015b482bf8f6e9d2cb3e0eea27e95b87d61

fix error in aliases (#157) Signed-off-by: Calvin Weng <wenghao@pingcap.com>

view details

push time in 15 days

PR merged tikv/website

fix error in aliases

Signed-off-by: Calvin Weng wenghao@pingcap.com

<!--Thanks for your contribution to TiKV documentation. -->

What is changed?

Added "/" that's missing at the beginning of the aliases. <!--Tell us what you did and why.-->

Any related PRs or issues?

<!--Provide a reference link that is related to your change. -->

Which version does your change affect?

+32 -32

0 comment

32 changed files

dcalvin

pr closed time in 15 days

PR opened tikv/website

fix error in aliases

Signed-off-by: Calvin Weng wenghao@pingcap.com

<!--Thanks for your contribution to TiKV documentation. -->

What is changed?

Added "/" that's missing at the beginning of the aliases. <!--Tell us what you did and why.-->

Any related PRs or issues?

<!--Provide a reference link that is related to your change. -->

Which version does your change affect?

+32 -32

0 comment

32 changed files

pr created time in 15 days

create barnchdcalvin/website

branch : deep-dive-alias

created branch time in 15 days

pull request commenttikv/website

add alias

@zhouqiang-cl please fix your DCO.

zhouqiang-cl

comment created time in 15 days

fork dcalvin/scrapy

Scrapy, a fast high-level web crawling & scraping framework for Python.

https://scrapy.org

fork in 16 days

push eventdcalvin/website

WT

commit sha d546f74088b58ba31864c62e4cb6a063138b67dc

Fix links in RocksDB in TiKV (#135) * update the website Signed-off-by: Wenting Liu <liuwenting@pingcap.com>

view details

WT

commit sha e35bc1ac2f5eaae1314860813c989e7b80b9c61d

update the website (#140) Signed-off-by: Wenting Liu <liuwenting@pingcap.com>

view details

Ana Hobden

commit sha 35fc8d6c6a396cd4499bb76116a09b7bc15afc58

Add docker make task and more docs (#115) Signed-off-by: Ana Hobden <operator@hoverbear.org>

view details

TXXT

commit sha 30a5425022c434276f3514f945782862ff7c0bc0

add doc Signed-off-by: TXXT <hunterlxt@live.com>

view details

TXXT

commit sha 309837c718b7922f3a2f6aa5b52798e991f4198c

show some examples Signed-off-by: TXXT <hunterlxt@live.com>

view details

TXXT

commit sha 2353bff49aeebf1c8d57a9cad721cf483c69b1e3

Merge pull request #144 from hunterlxt/XT/add-doc-for-check-cn security doc: update allow cert config

view details

Calvin Weng

commit sha d63d4d90bb43c6bc16c35bc411edbea553207916

update roadmap (#142) * update 3.0 roadmap Signed-off-by: Calvin Weng <wenghao@pingcap.com>

view details

WT

commit sha 373400fe8da209b90dff24fceb6d814dc5973f39

add time in distributed systems (#143) * add time in distributed systems Signed-off-by: Wenting Liu <liuwenting@pingcap.com>

view details

anotherrachel

commit sha e6ead296752e5d3e5afe99d6dbe513888d9cd5a4

add release notes (#145) Signed-off-by: anotherrachel <wangyajing@pingcap.com>

view details

WT

commit sha 4e422eefbd81a49884f5267893cb1f2e52d24fa7

add Quickly Find Rust Program Bottlenecks Online Using a Go Tool (#141) * add-pprof Signed-off-by: Wenting Liu <liuwenting@pingcap.com>

view details

Wenting Liu

commit sha 7609593ca9b094cca7ef9849250350f8f94f60d6

add-monthly-april-2020 Signed-off-by: Wenting Liu <liuwenting@pingcap.com>

view details

TXXT

commit sha 1c9c1904ac26cf9d74c176637b700c31961d2f1a

Update tikv key metric (#147) * update tikv key metric Signed-off-by: TXXT <hunterlxt@live.com>

view details

Wenting Liu

commit sha 3f0a5d8d2de3d53cc650d6e977559777bc56c1c8

update content Signed-off-by: Wenting Liu <liuwenting@pingcap.com>

view details

WT

commit sha b252caae118e36389d452860da524faa139a64e7

Merge pull request #149 from WT-Liu/add-monthly-April-2020 add-monthly-april-2020

view details

hhb

commit sha a93a877c85973244fd7681799ac9a0670b5a5a0e

Update Percolator paper URL (#136) The old url is expired. Signed-off-by: Haibo Huang <hhng2046@gmail.com>

view details

Yu

commit sha 5ad91566e96dc50581b1abb9b77db43e839fc42e

Update first paragraph of "Consensus Algorithm" (#152) Signed-off-by: Youwithouto <youwithouto.z@gmail.com>

view details

WT

commit sha f7da730d47aa58467e2cbea8e72aafbce71d0321

update logos (#154) Signed-off-by: Wenting Liu <liuwenting@pingcap.com>

view details

Calvin Weng

commit sha 72536b48d049afec25151d10914ed2da9bf3d5bf

Merge branch 'master' of github.com:dcalvin/website

view details

push time in 17 days

pull request commentcncf/artwork

update TiKV logos

Updated the latest proposed TiKV logos, with "Ti" added before KV.

WT-Liu

comment created time in 18 days

push eventtikv/website

WT

commit sha f7da730d47aa58467e2cbea8e72aafbce71d0321

update logos (#154) Signed-off-by: Wenting Liu <liuwenting@pingcap.com>

view details

push time in 18 days

PR merged tikv/website

update TiKV logos

Signed-off-by: Wenting Liu liuwenting@pingcap.com

<!--Thanks for your contribution to TiKV documentation. -->

What is changed?

<!--Tell us what you did and why.-->

Any related PRs or issues?

<!--Provide a reference link that is related to your change. -->

Which version does your change affect?

+9 -2167

0 comment

27 changed files

WT-Liu

pr closed time in 18 days

PR opened pingcap/chaos-mesh

Update format for monthly meeting

What problem does this PR solve? <!--add and issue link with summary if exists-->

Updated formating for community meeting

What is changed and how does it work?

Check List <!--REMOVE the items that are not applicable-->

Tests <!-- At least one of them must be included. -->

  • Unit test
  • E2E test
  • Manual test (add detailed scripts or steps below)
  • No code

Code changes

  • Has Go code change
  • Has CI related scripts change
  • Has Terraform scripts change

Side effects

  • Breaking backward compatibility

Related changes

  • Need to update the documentation

Does this PR introduce a user-facing change?:

<!-- If no, just leave the release note block below as is. If yes, a release note is required: Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, include the string "action required". -->

NONE
+3 -3

0 comment

1 changed file

pr created time in 18 days

create barnchpingcap/chaos-mesh

branch : dcalvin-patch-1

created branch time in 18 days

push eventtikv/website

Yu

commit sha 5ad91566e96dc50581b1abb9b77db43e839fc42e

Update first paragraph of "Consensus Algorithm" (#152) Signed-off-by: Youwithouto <youwithouto.z@gmail.com>

view details

push time in 20 days

PR merged tikv/website

Update first paragraph of "Consensus Algorithm"

Signed-off-by: Youwithouto youwithouto.z@gmail.com

<!--Thanks for your contribution to TiKV documentation. -->

What is changed?

The first paragraph in the Consensus algorithm Section is a bit unclear to me. And I think it tries to paraphrase the first paragraph of the Hold on—what is consensus? Section of the Raft doc.

Please reject this PR if my understanding is incorrect.

Any related PRs or issues?

<!--Provide a reference link that is related to your change. -->

Which version does your change affect?

+1 -1

1 comment

1 changed file

youwithouto

pr closed time in 20 days

startedcncf/artwork

started time in 20 days

pull request commenttikv/website

Update first paragraph of "Consensus Algorithm"

PTAL @BusyJay. It looks good to me.

youwithouto

comment created time in 20 days

push eventtikv/website

hhb

commit sha a93a877c85973244fd7681799ac9a0670b5a5a0e

Update Percolator paper URL (#136) The old url is expired. Signed-off-by: Haibo Huang <hhng2046@gmail.com>

view details

push time in 20 days

PR merged tikv/website

Update Percolator paper URL

The old url is expired.

+1 -1

3 comments

1 changed file

hhb

pr closed time in 20 days

pull request commenttikv/website

Update Percolator paper URL

@hhb Sorry for the late response. Could you please sign off your commit? (using git commit --amend --signoff

Done

Thanks very much for your contribution!

hhb

comment created time in 20 days

pull request commentpingcap/blog

update code example in raft-in-rust

Need to fix the md lint error. kost-stack.md:24:1007 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]

hicqu

comment created time in 24 days

push eventtikv/website

TXXT

commit sha 1c9c1904ac26cf9d74c176637b700c31961d2f1a

Update tikv key metric (#147) * update tikv key metric Signed-off-by: TXXT <hunterlxt@live.com>

view details

push time in a month

PR merged tikv/website

Update tikv key metric

Signed-off-by: TXXT hunterlxt@live.com

<!--Thanks for your contribution to TiKV documentation. -->

What is changed?

Update tikv key metric

Any related PRs or issues?

close https://github.com/pingcap/docs-cn/issues/2801

Which version does your change affect?

4.0 master

+99 -41

6 comments

1 changed file

hunterlxt

pr closed time in a month

issue closedpingcap/docs-cn

更新 TiKV 重要监控指标文档

Change Request

https://pingcap.com/docs-cn/stable/reference/key-monitoring-metrics/tikv-dashboard/ 这里的指标很多已经过时,我们需要重新梳理并更新一下这个文档,特别是 TiKV 4.0 的部分需要更新。

closed time in a month

hunterlxt

pull request commenttikv/website

Update tikv key metric

LGTM. @dcalvin Shall we involve a tech review?

I think it's good in this case

hunterlxt

comment created time in a month

pull request commenttikv/website

add configuration file

@anotherrachel PTAL.

toutdesuite

comment created time in a month

Pull request review commenttikv/website

Update tikv key metric

 menu:         weight: 2 --- -If your TiKV cluster is deployed using Ansible or Docker Compose, the monitoring system is deployed at the same time. For more details, see [Overview of the TiKV Monitoring Framework](../../how-to/monitor/introduction/).+If your TiKV cluster is deployed using Ansible or Docker Compose, the monitoring system is deployed at the same time. For more details, see [Overview of the TiKV Monitoring Framework](https://pingcap.com/docs/stable/reference/key-monitoring-metrics/overview-dashboard/).  The Grafana dashboard is divided into a series of sub-dashboards which include Overview, PD, TiKV, and so on. You can use various metrics to help you diagnose the cluster. -For routine operations, you can get an overview of the component (PD, TiKV) status and the entire cluster from the Overview dashboard, where the key metrics are displayed. This document provides a detailed description of these key metrics.+But you can also deploy your own Grafana server to monitor the TiKV cluster, especially when you are going to use TiKV without TiDB. This document provides a detailed description of key metrics so that you can monitor the Prometheus metrics you are interested in.  ## Key metrics description -To understand the key metrics displayed on the Overview dashboard, check the following table:+To understand the key metrics, check the following table: -Service | Panel Name | Description | Normal Range+Service | Metric Name | Description | Normal Range ---- | ---------------- | ---------------------------------- | ---------------Services Port Status | Services Online | the online nodes number of each service |-Services Port Status | Services Offline | the offline nodes number of each service |-PD | Storage Capacity | the total storage capacity of the TiKV cluster |-PD | Current Storage Size | the occupied storage capacity of the TiKV cluster |-PD | Number of Regions | the total number of Regions of the current cluster |-PD | Leader Balance Ratio | the leader ratio difference of the nodes with the biggest leader ratio and the smallest leader ratio | It is less than 5% for a balanced situation and becomes bigger when you restart a node.-PD | Region Balance Ratio | the region ratio difference of the nodes with the biggest Region ratio and the smallest Region ratio | It is less than 5% for a balanced situation and becomes bigger when you add or remove a node.-PD | Store Status -- Up Stores | the number of TiKV nodes that are up |-PD | Store Status -- Disconnect Stores | the number of TiKV nodes that encounter abnormal communication within a short time |-PD | Store Status -- LowSpace Stores | the number of TiKV nodes with an available space of less than 80% |-PD | Store Status -- Down Stores | the number of TiKV nodes that are down | The normal value is `0`. If the number is bigger than `0`, it means some node(s) are abnormal.-PD | Store Status -- Offline Stores | the number of TiKV nodes (still providing service) that are being made offline |-PD | Store Status -- Tombstone Stores | the number of TiKV nodes that are successfully offline |-PD | 99% completed_cmds_duration_seconds | the 99th percentile duration to complete a pd-server request | less than 5ms-PD | handle_requests_duration_seconds | the request duration of a PD request |-TiKV | leader | the number of leaders on each TiKV node |-TiKV | region | the number of Regions on each TiKV node |-TiKV | CPU | the CPU usage ratio on each TiKV node |-TiKV | Memory | the memory usage on each TiKV node |-TiKV | store size | the data amount on each TiKV node |-TiKV | cf size | the data amount on different CFs in the cluster |-TiKV | channel full | `No data points` is displayed in normal conditions. If a monitoring value displays, it means the corresponding TiKV node fails to handle the messages |-TiKV | server report failures | `No data points` is displayed in normal conditions. If `Unreachable` is displayed, it means TiKV encounters a communication issue. |-TiKV | scheduler pending commands | the number of commits on queue | Occasional value peaks are normal.-TiKV | coprocessor pending requests | the number of requests on queue | `0` or very small-TiKV | coprocessor executor count | the number of various query operations |-TiKV | coprocessor request duration | the time consumed by TiKV queries |-TiKV | raft store CPU | the CPU usage ratio of the raftstore thread | Currently, it is a single thread. A value of over 80% indicates that the CPU usage ratio is very high.-TiKV | Coprocessor CPU | the CPU usage ratio of the TiKV query thread, related to the application; complex queries consume a great deal of CPU |-System Info | Vcores | the number of CPU cores |-System Info | Memory | the total memory |-System Info | CPU Usage | the CPU usage ratio, 100% at a maximum |-System Info | Load [1m] | the overload within 1 minute |-System Info | Memory Available | the size of the available memory |-System Info | Network Traffic | the statistics of the network traffic |-System Info | TCP Retrans | the statistics about network monitoring and TCP |-System Info | IO Util | the disk usage ratio, 100% at a maximum; generally you need to consider adding a new node when the usage ratio is up to 80% ~ 90% |\ No newline at end of file+Cluster | tikv_store_size_bytes | The size of storage. The metric has a `type` label (eg: "capacity", "available"). |+gRPC | tikv_grpc_msg_duration_seconds | Bucketed histogram of gRPC server messages. The metric has a `type` label which represents the type of the server message. You can count the metric and calculate the QPS. |+gRPC | tikv_grpc_msg_fail_total | The total number of gRPC message handling failure. The metric has a `type` label which represents gRPC message type. |+GRPC | grpc batch size of gRPC requests | grpc batch size of gRPC requests. |+Scheduler | tikv_scheduler_too_busy_total | The total count of too busy schedulers. The metric has a `type` label which represents the scheduler type. |

both are correct.

hunterlxt

comment created time in a month

Pull request review commenttikv/website

Update tikv key metric

 menu:         weight: 2 --- -If your TiKV cluster is deployed using Ansible or Docker Compose, the monitoring system is deployed at the same time. For more details, see [Overview of the TiKV Monitoring Framework](../../how-to/monitor/introduction/).+If your TiKV cluster is deployed using Ansible or Docker Compose, the monitoring system is deployed at the same time. For more details, see [Overview of the TiKV Monitoring Framework](https://pingcap.com/docs/stable/reference/key-monitoring-metrics/overview-dashboard/).  The Grafana dashboard is divided into a series of sub-dashboards which include Overview, PD, TiKV, and so on. You can use various metrics to help you diagnose the cluster. -For routine operations, you can get an overview of the component (PD, TiKV) status and the entire cluster from the Overview dashboard, where the key metrics are displayed. This document provides a detailed description of these key metrics.+But you can also deploy your own Grafana server to monitor the TiKV cluster, especially when you are going to use TiKV without TiDB. This document provides a detailed description of key metrics so that you can monitor the Prometheus metrics you are interested in.  ## Key metrics description -To understand the key metrics displayed on the Overview dashboard, check the following table:+To understand the key metrics, check the following table: -Service | Panel Name | Description | Normal Range+Service | Metric Name | Description | Normal Range ---- | ---------------- | ---------------------------------- | ---------------Services Port Status | Services Online | the online nodes number of each service |-Services Port Status | Services Offline | the offline nodes number of each service |-PD | Storage Capacity | the total storage capacity of the TiKV cluster |-PD | Current Storage Size | the occupied storage capacity of the TiKV cluster |-PD | Number of Regions | the total number of Regions of the current cluster |-PD | Leader Balance Ratio | the leader ratio difference of the nodes with the biggest leader ratio and the smallest leader ratio | It is less than 5% for a balanced situation and becomes bigger when you restart a node.-PD | Region Balance Ratio | the region ratio difference of the nodes with the biggest Region ratio and the smallest Region ratio | It is less than 5% for a balanced situation and becomes bigger when you add or remove a node.-PD | Store Status -- Up Stores | the number of TiKV nodes that are up |-PD | Store Status -- Disconnect Stores | the number of TiKV nodes that encounter abnormal communication within a short time |-PD | Store Status -- LowSpace Stores | the number of TiKV nodes with an available space of less than 80% |-PD | Store Status -- Down Stores | the number of TiKV nodes that are down | The normal value is `0`. If the number is bigger than `0`, it means some node(s) are abnormal.-PD | Store Status -- Offline Stores | the number of TiKV nodes (still providing service) that are being made offline |-PD | Store Status -- Tombstone Stores | the number of TiKV nodes that are successfully offline |-PD | 99% completed_cmds_duration_seconds | the 99th percentile duration to complete a pd-server request | less than 5ms-PD | handle_requests_duration_seconds | the request duration of a PD request |-TiKV | leader | the number of leaders on each TiKV node |-TiKV | region | the number of Regions on each TiKV node |-TiKV | CPU | the CPU usage ratio on each TiKV node |-TiKV | Memory | the memory usage on each TiKV node |-TiKV | store size | the data amount on each TiKV node |-TiKV | cf size | the data amount on different CFs in the cluster |-TiKV | channel full | `No data points` is displayed in normal conditions. If a monitoring value displays, it means the corresponding TiKV node fails to handle the messages |-TiKV | server report failures | `No data points` is displayed in normal conditions. If `Unreachable` is displayed, it means TiKV encounters a communication issue. |-TiKV | scheduler pending commands | the number of commits on queue | Occasional value peaks are normal.-TiKV | coprocessor pending requests | the number of requests on queue | `0` or very small-TiKV | coprocessor executor count | the number of various query operations |-TiKV | coprocessor request duration | the time consumed by TiKV queries |-TiKV | raft store CPU | the CPU usage ratio of the raftstore thread | Currently, it is a single thread. A value of over 80% indicates that the CPU usage ratio is very high.-TiKV | Coprocessor CPU | the CPU usage ratio of the TiKV query thread, related to the application; complex queries consume a great deal of CPU |-System Info | Vcores | the number of CPU cores |-System Info | Memory | the total memory |-System Info | CPU Usage | the CPU usage ratio, 100% at a maximum |-System Info | Load [1m] | the overload within 1 minute |-System Info | Memory Available | the size of the available memory |-System Info | Network Traffic | the statistics of the network traffic |-System Info | TCP Retrans | the statistics about network monitoring and TCP |-System Info | IO Util | the disk usage ratio, 100% at a maximum; generally you need to consider adding a new node when the usage ratio is up to 80% ~ 90% |\ No newline at end of file+Cluster | tikv_store_size_bytes | The size of storage. The metric has a `type` label (eg: "capacity", "available"). |+gRPC | tikv_grpc_msg_duration_seconds | Bucketed histogram of gRPC server messages. The metric has a `type` label which represents the type of the server message. You can count the metric and calculate the QPS. |+gRPC | tikv_grpc_msg_fail_total | The total number of gRPC message handling failure. The metric has a `type` label which represents gRPC message type. |+GRPC | grpc batch size of gRPC requests | grpc batch size of gRPC requests. |+Scheduler | tikv_scheduler_too_busy_total | The total count of too busy schedulers. The metric has a `type` label which represents the scheduler type. |+Scheduler | tikv_scheduler_contex_total | The total number of pending commands. The scheduler receives commands from clients, executes them against the MVCC layer storage engine. |+Scheduler | tikv_scheduler_stage_total | Total number of commands on each stage. The metric has two labels: `type` and `stage`. `stage` represents the stage of executed commands like "read_finish", "async_snapshot_err", "snapshot", etc. |+Scheduler | tikv_scheduler_commands_pri_total | Total count of different priority commands. The metric has a `priority` label. |+Server | tikv_server_grpc_resp_batch_size | grpc batch size of gRPC responses. |+Server | tikv_server_report_failure_msg_total | Total number of reporting failure messages. The metric has two labels: `type` and `store_id`. `type` represents the failure type, and `store_id` represents the destination peer store id. |+Server | tikv_server_raft_message_flush_total | Total number of raft messages flushed immediately. |+Server | tikv_server_raft_message_recv_total | Total number of raft messages received. |+Server | tikv_region_written_keys | Histogram of written keys for regions. |+Server | tikv_server_send_snapshot_duration_seconds | Bucketed histogram of duration in which the server sends snapshots. |+Server | tikv_region_written_bytes | Histogram of bytes written for regions. |+Raft | tikv_raftstore_leader_missing | Total number of leader missed regions. |+Raft | tikv_raftstore_region_count | The number of regions collected in each TiKV node. The label `type` has `region` and `leader`. `region` represents regions collected, and `leader` represents the number of leaders in each TiKV node. |+Raft | tikv_raftstore_region_size | Bucketed histogram of approximate region size. |+Raft | tikv_raftstore_apply_log_duration_seconds | Bucketed histogram of the duration in which each peer applies log. |+Raft | tikv_raftstore_commit_log_duration_seconds | Bucketed histogram of the duration in which each peer commits logs. |+Raft | tikv_raftstore_raft_ready_handled_total | Total number of Raft ready handled. The metric has label `type`. |+Raft | tikv_raftstore_raft_process_duration_secs | Bucketed histogram of duration in which each peer processes Raft. The metric has label `type`. |+Raft | tikv_raftstore_event_duration | Duration of raft store events. The metric has label `type`. |+Raft | tikv_raftstore_raft_sent_message_total | Total number of messages sent by Raft ready. The metric has label `type`. |+Raft | tikv_raftstore_raft_dropped_message_total | Total number of messages dropped by Raft. The metric has label `type`. |+Raft | tikv_raftstore_apply_proposal | The count of proposals sent by a region at once. |+Raft | tikv_raftstore_proposal_total | Total number of proposals made. The metric has label `type`. |+Raft | tikv_raftstore_request_wait_time_duration_secs | Bucketed histogram of request wait time duration. |+Raft | tikv_raftstore_propose_log_size | Bucketed histogram of peer proposing log size. |+Raft | tikv_raftstore_apply_wait_time_duration_secs | Bucketed histogram of apply task wait time duration. |+Raft | tikv_raftstore_admin_cmd_total | Total number of admin command processed. The metric has 2 labels `type` and `status`. |+Raft | tikv_raftstore_check_split_total | Total number of raftstore split check. The metric has label `type`. |

Suggested use: has a type label

hunterlxt

comment created time in a month

push eventBusyJay/tikv

ShuNing

commit sha 6df271418de89781b71d33498d3adbc6dc4d8296

raftstore: use batch split for auto-split (#7654) Signed-off-by: nolouch <nolouch@gmail.com>

view details

Nick Cameron

commit sha 8e97d1ca6f9e3ccbed3eb54f91faafc3f4ad26bd

tikv_util: Fix logging test (#7633) Signed-off-by: Nick Cameron <nrc@ncameron.org>

view details

Brian Anderson

commit sha 85fe1ad4989ccfa3c01613ed2d8454b7e294aefd

Two minor fixes to unsafe code (#7509) Signed-off-by: Brian Anderson <andersrb@gmail.com>

view details

gengliqi

commit sha f00746dcd9cfddf611388c03750b41d72ccc1c24

raftstore: change the condition of proposing rollback merge (#6584) Signed-off-by: Liqi Geng <gengliqiii@gmail.com>

view details

Rohan Jain

commit sha e794391c2d5f4b9b2aaa15630ceb318202ecb20f

CONTRIBUTING: update help wanted issues label (#7515) Signed-off-by: Rohan Jain <crodjer@gmail.com>

view details

Zhongyang Wu

commit sha 782bb0203c3e39b2517bbb5ac0ceeef3dd76e60d

remove empty log at startup (#7341) Signed-off-by: zhongyang.wu <zhongyang.wu@outlook.com>

view details

qupeng

commit sha f2401ff48d4f4217f1222603af4b1ca8681ca366

raftstore: encrypt lock cf in snapshots (#7616) Signed-off-by: qupeng <qupeng@pingcap.com>

view details

Calvin Weng

commit sha ffa54b3670f7786c52665346131fd989147a201d

Merge branch 'master' into fix-typos

view details

push time in a month

pull request commenttikv/website

Update tikv key metric

@hunterlxt Please fix the DCO.

hunterlxt

comment created time in a month

push eventtikv/website

WT

commit sha 4e422eefbd81a49884f5267893cb1f2e52d24fa7

add Quickly Find Rust Program Bottlenecks Online Using a Go Tool (#141) * add-pprof Signed-off-by: Wenting Liu <liuwenting@pingcap.com>

view details

push time in a month

PR merged tikv/website

add Quickly Find Rust Program Bottlenecks Online Using a Go Tool

Signed-off-by: Wenting Liu liuwenting@pingcap.com

<!--Thanks for your contribution to TiKV documentation. -->

What is changed?

add blog Quickly Find Rust Program Bottlenecks Online Using a Go Tool

Any related PRs or issues?

N/A

Which version does your change affect?

N/A

+80 -0

0 comment

4 changed files

WT-Liu

pr closed time in a month

startedlayer5io/meshery

started time in a month

pull request commenttikv/website

Update tikv key metric

@ran-huang PTAL.

hunterlxt

comment created time in a month

push eventtikv/website

anotherrachel

commit sha e6ead296752e5d3e5afe99d6dbe513888d9cd5a4

add release notes (#145) Signed-off-by: anotherrachel <wangyajing@pingcap.com>

view details

push time in a month

PR merged tikv/website

add release notes

Signed-off-by: anotherrachel wangyajing@pingcap.com

<!--Thanks for your contribution to TiKV documentation. -->

What is changed?

This PR adds release notes too v3.0 and dev. <!--Tell us what you did and why.-->

Any related PRs or issues?

N/A <!--Provide a reference link that is related to your change. -->

Which version does your change affect?

v3.0 and dev

+235 -2

1 comment

7 changed files

anotherrachel

pr closed time in a month

push eventWT-Liu/tikv

gengliqi

commit sha eacae77b9712812c1f62202d8cf4db44b2385b6a

raftstore: consider wake-up msg when checking stale msg (#7416) Signed-off-by: Liqi Geng <gengliqiii@gmail.com>

view details

Liu Cong

commit sha 22bdc46e8307ba90736412fae2b8af0693684667

cop: Fixed issue #6690 Coprocessor Cache is unsound (#7095) Signed-off-by: Liu Cong <innerr@gmail.com>

view details

Jay

commit sha fb7e39dc1388cb8954c787d78a9be9990a7795eb

tests: add restart test case for #6648 (#7458) Signed-off-by: Jay Lee <BusyJayLee@gmail.com>

view details

crazycs

commit sha 00812bdf682aa2b73e432abed184f554e90bfd51

diagnose: fix disk used percent information (#7487) Signed-off-by: crazycs520 <crazycs520@gmail.com>

view details

TXXT

commit sha 6411ffeb1c564949e685712a5780a8c904c37e7a

cmd: add uid flag for TIKV_LOCK_FILES (#7470) Signed-off-by: TXXT <hunterlxt@live.com>

view details

Wenxuan

commit sha 7d13ca02374582bd7714d3298efb74909d69ca64

*: reduce sys_getdents syscall (#7306) Signed-off-by: Breezewish <breezewish@pingcap.com>

view details

Brian Anderson

commit sha e76005b808e865996fe51dab3b133f5a03ead8ab

raftstore: Convert RocksEngine to type parameters (#7371) Signed-off-by: Brian Anderson <andersrb@gmail.com>

view details

Yilin Chen

commit sha 2a817a08363ccd2c86ae7ed8e0a424ee5ae22c79

conf: check storage or coprocessor readpool config when partially unified (#7387) Signed-off-by: Yilin Chen <sticnarf@gmail.com>

view details

Neil Shen

commit sha f5ee17b3101a24aafb897a76fbf3524fb19ccc58

Makefile: fix make docker (#7498) Signed-off-by: Neil Shen <overvenus@gmail.com>

view details

Jay

commit sha bd21a5b5c4a62e2bc57fa3f762227f2fc7aa2d1f

kv_service: fix batch empty request deadlock (#7535)

view details

qupeng

commit sha 7887c24822e2f049f97fa6b2b1b4044bae551ee6

raft_client: calculate batch size more approximately (#7522) Signed-off-by: qupeng <qupeng@pingcap.com>

view details

zhongzc

commit sha 4175d681d9e002af8f8326392ed27418b73363e0

tidb_query: fix converting bytes to bool (#7486) Signed-off-by: zhongzc <zhongzc_arch@outlook.com>

view details

Lei Zhao

commit sha b4dd42f649519f7d3b7e3061ad08f26b99ce5818

txn: only wake up waiters when locks are indeed released (#7379) Signed-off-by: youjiali1995 <zlwgx1023@gmail.com>

view details

yiwu-arbug

commit sha 635b02db82445fa92676ad41e3ce63c0d7385730

encryption: Fix panic when restore backup when encryption is enabled (#7519) Signed-off-by: Yi Wu <yiwu@pingcap.com>

view details

Wenxuan

commit sha 24625c43f90bf23618d8acf2fd5b3fb2c5cd082a

diagnose server: Fix cpu usage and support MacOS (#7524) Signed-off-by: Breezewish <breezewish@pingcap.com>

view details

Maxwell

commit sha 700f23b322142269b6e3f8cc08c7e2c05d8c08a7

tikv_util: fix compatibility issue in tikv rotating log file naming (#7437) Signed-off-by: Deardrops <passagesfall@gmail.com>

view details

Renkai

commit sha 3ffea91761a2212581c146cd8b547bc117d74b8b

use more thread local static metrics in `src/storage/metrics.rs` (#7461) Signed-off-by: Renkai <gaelookair@gmail.com>

view details

yiwu-arbug

commit sha cef1015232bd6a6b3fb477a9d37fc90c21902f24

external_storage: add GCS support (#6283) Signed-off-by: Yi Wu <yiwu@pingcap.com>

view details

zhongzc

commit sha b2a27d2175dc90ff876655aa64b0d3740957a444

tidb_query: add is true/false keep null ScalarFuncSig (#7532) Signed-off-by: zhongzc <zhongzc_arch@outlook.com>

view details

Calvin Weng

commit sha 5d38994815f33fb3189b5ab1e9a2bafc58edaeae

Merge branch 'master' into update-adopters-list

view details

push time in a month

pull request commenttikv/tikv

update adopters

/merge

WT-Liu

comment created time in a month

Pull request review commentpingcap/community

Contributors: how to sign cla.

 welcome!  ### Sign the CLA -TBD+Click the button "Sign in with Github to agree" to sign the CLA. For example: [here](https://cla-assistant.io/pingcap/tidb?pullRequest=16303).
Click the **Sign in with Github to agree** button to sign the CLA. See an example [here](https://cla-assistant.io/pingcap/tidb?pullRequest=16303).
winkyao

comment created time in a month

push eventtikv/website

WT

commit sha 373400fe8da209b90dff24fceb6d814dc5973f39

add time in distributed systems (#143) * add time in distributed systems Signed-off-by: Wenting Liu <liuwenting@pingcap.com>

view details

push time in a month

PR merged tikv/website

add time in distributed systems

Signed-off-by: Wenting Liu liuwenting@pingcap.com

<!--Thanks for your contribution to TiKV documentation. -->

What is changed?

add a blog <!--Tell us what you did and why.-->

Any related PRs or issues?

<!--Provide a reference link that is related to your change. -->

Which version does your change affect?

+174 -0

1 comment

5 changed files

WT-Liu

pr closed time in a month

PR merged tikv/website

update roadmap

<!--Thanks for your contribution to TiKV documentation. -->

What is changed?

<!--Tell us what you did and why.-->

Updated 3.0 Roadmap

Any related PRs or issues?

<!--Provide a reference link that is related to your change. -->

Which version does your change affect?

+8 -8

0 comment

1 changed file

dcalvin

pr closed time in a month

push eventtikv/website

Calvin Weng

commit sha d63d4d90bb43c6bc16c35bc411edbea553207916

update roadmap (#142) * update 3.0 roadmap Signed-off-by: Calvin Weng <wenghao@pingcap.com>

view details

push time in a month

pull request commenttikv/website

security doc: update allow cert config

LGTM. Do we need to update the 3.0 version?

@dcalvin Yes, just 3.1

As confirmed with @zhangjinpeng1987, we will not expose 3.1 on the website. Just dev (master). And when 4.0 GA is out, we will add 4.0 version.

hunterlxt

comment created time in a month

pull request commentcncf/toc

TiKV graduation proposal

TiKV Due Diligence Doc Hope this DD draft from our end could serve as a more comprehensive reference for your review. TiKV Due Diligence Doc

dcalvin

comment created time in a month

pull request commenttikv/tikv

update the tikv community meeting

/merge

WT-Liu

comment created time in a month

push eventWT-Liu/tikv

Renkai

commit sha 09c914a7be978e25cdf3ed8f6578de431884bcff

Make metrics of raftstore worker static & thread localize (#7274) Signed-off-by: Renkai <gaelookair@gmail.com>

view details

Renkai

commit sha 493654fe19077345210a3223263250996de8b4da

Improve TiKV metrics performance for tidb_query&engine_rocks (#7267) Signed-off-by: Renkai <gaelookair@gmail.com>

view details

Yilin Chen

commit sha 16658acc4e64ebe17b11c0d321061e10e6316ba8

util: use yatp for the future_pool (#7348) Signed-off-by: Yilin Chen <sticnarf@gmail.com>

view details

Wenxuan

commit sha a006e5b5ae6a39c1f8a5cc10581ce2a0b774a65a

copr: Add back missing signatures (#7399) Signed-off-by: Breezewish <breezewish@pingcap.com>

view details

Neil Shen

commit sha f16e1d11442799dc042ac7eed9a4d1327a68aa7b

*: make ChangeCmd as a significant message (#7377) Signed-off-by: Neil Shen <overvenus@gmail.com>

view details

gengliqi

commit sha 6037928eff2a3a42b64f449caf983eec7427bbe1

raftstore: set term in read index response (#7372) Signed-off-by: Liqi Geng <gengliqiii@gmail.com>

view details

Yilin Chen

commit sha 37dccf4ee0268ab205fe066ebe0c8ef964adc3fe

util: stablize test tikv_util::future_pool::test_tick (#7409) Signed-off-by: Yilin Chen <sticnarf@gmail.com>

view details

TXXT

commit sha a00b00877db7ecf9ac60a1a99d1bcc7a6b84cc24

Protect correct lifetime for lock file (#7407) Signed-off-by: TXXT <hunterlxt@live.com>

view details

5kbpers

commit sha ac398e271533d3243623a7bd3468852cfeb3b8b4

cdc: remove scan cache & add observe id (#7278) Signed-off-by: 5kbpers <tangminghua@pingcap.com>

view details

3pointer

commit sha c018ce7f9427189bbc57226b926f4b6a9d26f475

sst_importer: skip validation in ingest temporary until we can handle sst file size correctly (#7415) Signed-off-by: luancheng <luancheng@pingcap.com>

view details

5kbpers

commit sha faa42d24a5cba23a301fc1630bb33b48fe7d9aef

cdc: check leadership before advancing resolved ts (#7390) Signed-off-by: 5kbpers <tangminghua@pingcap.com>

view details

Qiannan

commit sha ce111fbecc978c1a553d623814ab9ea5626b6a62

copr: Migrate scalar function `Lpad` from TiDB (#7300) Signed-off-by: Qiannan Lyu <lvqiannan@gmail.com>

view details

Jay

commit sha 66cecaa09c4324f669b1a11c73f920324df31f99

*: remove quorum algorithm (#7376) Signed-off-by: Jay Lee <BusyJayLee@gmail.com>

view details

Lei Zhao

commit sha 3a547b9aba1df43d72f59703baad15a8ca610ee1

raftkv: enhance failpoint raftkv_early_error_report (#7260) Signed-off-by: youjiali1995 <zlwgx1023@gmail.com>

view details

Wallace

commit sha d2c269b823913a6ae9f12ea5c4c90db1ad000add

Remove `get_db` of `engine_traits::Snapshot` (#7411) Signed-off-by: Little-Wallace <bupt2013211450@gmail.com>

view details

gengliqi

commit sha bd16634c4c5fc90de73b9d5676fd4903bf8d016d

txn: ignore lock when ts is less than min_commit_ts (#7423) Signed-off-by: Liqi Geng <gengliqiii@gmail.com>

view details

Neil Shen

commit sha 7b938f3d669c6c0daafe6dd1ae50c9473a525104

cdc: fix deregister ABA problem and support cancel incremental scan (#7433) Signed-off-by: Neil Shen <overvenus@gmail.com>

view details

lhy1024

commit sha 16f229b4a33573b73b859b437cc9bf08985c5e2c

Update README (#7421) Signed-off-by: lhy1024 <admin@liudos.us> Co-authored-by: pingcap-github-bot <sre-bot@pingcap.com>

view details

TXXT

commit sha 2c5dad365bc80e9add8e23ea5cb907791d2dcc92

cmd: add file lock to work around port conflict (#7355) Signed-off-by: TXXT <hunterlxt@live.com>

view details

lhy1024

commit sha 877c75b165a172447267cbd6cfb2aa7702fe608e

add load base split config and controller (#7401) Signed-off-by: lhy1024 <admin@liudos.us>

view details

push time in a month

Pull request review commenttikv/tikv

update the tikv community meeting

 Quick links:  *   [Meeting notes](https://docs.google.com/document/d/1CWUAkBrcm9KPclAu8fWHZzByZ0yhsQdRggnEdqtRMQ8/edit) *   [Zoom meeting link](https://zoom.us/my/cncftikvproject)+*   [Add to my calendar](https://calendar.google.com/calendar/r/month/2020/4/23?eid=MXZiaDg4YmEwYW1rbDlwajRtdjIyb2w3ZTlfMjAyMDA0MjNUMDEwMDAwWiBsaW51eGZvdW5kYXRpb24ub3JnX281YXZqbHZ0MmNhZTlicTdhOTVlbWM0NzQwQGc&ctz=America/New_York&sf=true)

This is generated from the CNCF. And also it makes more sense to add to calendar only for the current week because we can't make the decision on behalf of other people.

WT-Liu

comment created time in a month

pull request commentpingcap/community

update rules

@WT-Liu FYI

dcalvin

comment created time in a month

push eventdcalvin/community-1

notginger

commit sha 8e8314cf333a97b4c8394ba7b086d5654a48c483

update rules (#205) Co-authored-by: Calvin Weng <wenghao@pingcap.com>

view details

Calvin Weng

commit sha 4fe03c771d1a99f66710f2e00cf9942b605227f9

Merge branch 'master' into update-bug-hunting-rules

view details

push time in a month

PR opened pingcap/community

update rules

Updated baed on https://github.com/pingcap/community/pull/205

+25 -44

0 comment

1 changed file

pr created time in a month

create barnchdcalvin/community-1

branch : update-bug-hunting-rules

created branch time in a month

push eventpingcap/community

Yue Yang

commit sha 0d4ffda0af957c4dcd8d1d982cd400fa6d723e11

rfc: add discourse theme asktug into incubator programs (#202)

view details

Soline

commit sha 392ce16e677fae2649a3ab30167c227db840d66a

governance: add SIG governance and charter template (#150)

view details

Calvin Weng

commit sha d1cd94121501bdfabd27cc3cb45875e118d9e7c5

Merge branch 'master' into gingerkidney-update-rule

view details

push time in a month

Pull request review commenttikv/tikv

update adopters

 category: adopters  # TiKV Adopters -This is a list of TiKV adopters in various industries.+The following adopters deploy TiKV independently without TiDB.   | Company | Industry | Success Story | | :--- | :--- | :--- |-|[Zhihu](https://en.wikipedia.org/wiki/Zhihu)|Knowledge Sharing|[English](https://pingcap.com/success-stories/lesson-learned-from-queries-over-1.3-trillion-rows-of-data-within-milliseconds-of-response-time-at-zhihu/); [Chinese](https://pingcap.com/cases-cn/user-case-zhihu/)| |[JD Cloud](https://www.crunchbase.com/organization/jd-cloud)|Cloud Computing|[English](https://pingcap.com/success-stories/lesson-learned-from-40-k-qps-and-20-billion-rows-of-data-in-a-single-scale-out-cluster/); [Chinese](https://pingcap.com/cases-cn/user-case-jingdongyun/)|+|[Shopee](https://en.wikipedia.org/wiki/Shopee)|E-commerce|[English](https://www.pingcap.com/success-stories/tidb-in-shopee/); [Chinese](https://www.pingcap.com/cases-cn/user-case-shopee/)|+|[LY.com](https://www.crunchbase.com/organization/ly-com)|Travel|[Chinese](https://www.pingcap.com/cases-cn/user-case-tongcheng/)|+|[Zhuan Zhuan](https://www.crunchbase.com/organization/zhuan-zhuan)|Online Marketplace|[English](https://www.pingcap.com/success-stories/tidb-in-zhuanzhuan/); [Chinese](https://pingcap.com/cases-cn/user-case-zhuanzhuan/)|+|[Meituan-Dianping](https://en.wikipedia.org/wiki/Meituan-Dianping)|Food Delivery|[English](https://www.pingcap.com/success-stories/tidb-in-meituan-dianping/); [Chinese](https://pingcap.com/cases-cn/user-case-meituan/)|+|[Ele.me](https://en.wikipedia.org/wiki/Ele.me)|Food Delivery|+|[Yidian Zixun](https://www.crunchbase.com/organization/yidian-zixun#section-overview)|Media and Entertainment|+|[KuGou](https://en.wikipedia.org/wiki/KuGou)|Entertainment and Music Streaming|+|[Meitu](https://en.wikipedia.org/wiki/Meitu)|Photo-editing|++This is a list of TiKV adopters deploying TiKV with TiDB.
The following are a list of TiKV adopters deploying TiKV with TiDB.
WT-Liu

comment created time in a month

pull request commenttikv/tikv

doc: update allow cert config

This should be updated in https://github.com/tikv/website/tree/master/content/docs

hunterlxt

comment created time in a month

push eventtikv/website

Ana Hobden

commit sha 35fc8d6c6a396cd4499bb76116a09b7bc15afc58

Add docker make task and more docs (#115) Signed-off-by: Ana Hobden <operator@hoverbear.org>

view details

push time in a month

PR merged tikv/website

Add docker make task and more docs

Addresses #109 in a slightly different way, making it easier to use docker based workflows without needing docker-compose since it's not as commonly installed.

+17 -4

0 comment

2 changed files

Hoverbear

pr closed time in a month

more