[
https://issues.apache.org/jira/browse/RATIS-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747224#comment-17747224
]
Baolong Mao edited comment on RATIS-1860 at 7/26/23 1:32 AM:
-------------------------------------------------------------
[~szetszwo] Thanks for your reply! I can be a possible way to change hostname
and let new node use the hostname as same as the old one in majority test
purpose scenarios, but we have no permission to change the hostname in most of
production environments.
So, is there a way to do some effects like what hdfs provide?
* Record the node info into a human editable config file, something like
raft-meta.
* Remove the node info segment from ratis log file, instead, it can be read
from raft-meta
After that, we can write a document to show how to move a ratis server from one
node to another node offline.
Although Alluxio provide a way to backup alluxio master statemachine, but it
can only work while alluxio primary master process live and serve rpc normally.
In some situation, we can only copy the alluxio journal folder(based on ratis)
to another test node to reproduce the production issue, so I think this feature
requirement is necessary.
[https://docs.alluxio.io/os/user/stable/en/operation/Journal.html#backing-up-the-journal]
Maybe there are some tools can upgrade the ratis meta and log to a specific new
node name?
was (Author: maobaolong):
[~szetszwo] Thanks for your reply! I can be a possible way to change hostname
and let new node use the hostname as same as the old one in majority test
purpose scenarios, but we have no permission to change the hostname in most of
production environments.
So, is there a way to do some effects like what hdfs provide?
* Record the node info into a human editable config file, something like
raft-meta.
* Remove the node info segment from ratis log file, instead, it can be read
from raft-meta
After that, we can write a document to show how to move a ratis server from one
node to another node offline.
> Support copy alluxio journal(ratis-based) to another node and start it
> ----------------------------------------------------------------------
>
> Key: RATIS-1860
> URL: https://issues.apache.org/jira/browse/RATIS-1860
> Project: Ratis
> Issue Type: New Feature
> Reporter: Baolong Mao
> Priority: Major
>
> There are ip in the ratis conf and ratis log files, so it can not be moved to
> another node and start a new state machine from it.
>
> cat journal/raft/02511d47-d67c-49a3-9011-abb3109a44c1/current/raft-meta.conf
> ".
> ,
> 192.168.1.100_1920011.151.252.98:192008#
>
> cat journal/raft/02511d47-d67c-49a3-9011-abb3109a44c1/current/raft-meta
> #
> #Wed Jul 19 18:58:15 CST 2023
> votedFor=192.168.1.100_19200
> term=3
>
> head journal/raft/02511d47-d67c-49a3-9011-abb3109a44c1/current/log_0-10
> RaftLog1".
> ,
> 192.168.1.100_19200192.168.1.100:192008=�m!
> ���ݤ틻�r�4�}[@Ùj���(x-�'
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
