Can TiKV be forcibly started in read-only mode if only a few nodes are alive?

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: TiKV如果只存活少数节点，可以强制启动到只读状态吗？

| username: alfred

【TiDB Usage Environment】Production\Test Environment\POC
【TiDB Version】
【Encountered Issues】
【Reproduction Path】What operations were performed that caused the issue
【Issue Phenomenon and Impact】
【TiDB Operator Version】：
【K8s Version】：
【Attachments】：

2
| username: ddhe9527 | Original post link

No. If only a few nodes survive and read-only mode is enabled, the data read will be inconsistent. Some regions may have lost all replicas, resulting in complete data loss.

3
| username: alfred | Original post link

For example, if two out of three replicas with good labels fail, the remaining one cannot be started no matter what, right?

4
| username: ddhe9527 | Original post link

After removing all peers located on the faulty TiKV, and adding enough TiKV nodes, the regions that lost the majority can re-elect a leader and become available again.

5
| username: alfred | Original post link

That means new nodes need to be added.

6
| username: system | Original post link

This topic will be automatically closed 60 days after the last reply. No new replies are allowed.