cui2022 commented on issue #3142: URL: https://github.com/apache/hugegraph/issues/3142#issuecomment-5238542865
Thank you very much for your reply. I will handle this issue within this week. In addition, I have another question. Currently, I am conducting tests by simulating potential problems that may occur in a production environment. My current test scenario is as follows: I have 5 Store nodes, and each partition has 3 replicas. The service processes are running on the system disks, while the data is stored on separate data disks. I simulated a situation where the data disk of one Store node was suddenly disconnected, causing data loss, while the system disk remained intact. As a result, data queries may fail, but the node status still appears to be normal. After I stopped the damaged node, its status changed from UP to OFFLINE. However, I understand that there is a maximum waiting period (48 hours by default) before the system considers this node unavailable and triggers replica migration. My question is: Is there any way to manually trigger replica migration? Or is it possible to manually change the node status from OFFLINE to an invalid/unavailable state, or any other state that can trigger replica migration? My goal is to allow the replica migration to complete first, and then restart the damaged node afterward. I could not find any available APIs related to this operation. Alternatively, could you please advise whether there is a standard recovery procedure for handling a data disk failure scenario? For example, what is the recommended process to recover the cluster after a Store node loses its data disk? Thank you very much for your help. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
