[Bug]: After the double data partition is decommissioned and the damaged disk becomes a single data partition, how to repair it?

[zcola]

Contact Details

No response

Is there an existing issue for this?

• [X] I have searched all the existing issues

Priority

low (Default)

Environment

- CubeFS version:  v3.3.0 Commit  : 3d9f15e4cf21e1b7599fed5239d67f4e092f5d4f
- Deployment mode(docker or standalone or cluster): cluster
- Dependent components:
- OS kernel version(Ubuntu or CentOS): debian 10/8
- CPU/Memory: 40 core/ 128gb

Current Behavior

The disk failed to be decommissioned, leaving several data partitions. After resetting the partition status and forcibly decommissioning it, it becomes a single data partition. An attempt to add a data partition failed

 docker exec -it master-01 /cfs/bin/cfs-cli datapartition add-replica 10.90.140.181:17310 309836
Error: result code[243],msg[ActionAddDataPartitionRaftMember_no raft leader]

View the metadata on the only remaining single data partition disk

Expected Behavior

How to fix it?

Steps To Reproduce

No response

CubeFS Log

No response

Anything else? (Additional Context)

No response

[leonrayang]

@zcola The suitable way is update the metadata of datanode partition then restart. This a desgin issue known as automic incomplete, the release-3.4.0 will be available in the next few weeks , please be patient. Thank you very much.

[zcola]

@zcola The suitable way is update the metadata of datanode partition then restart. This a desgin issue known as automic incomplete, the release-3.4.0 will be available in the next few weeks , please be patient. Thank you very much.

This method can solve the problem, but it is too cumbersome. Looking forward to 3.4