I have a customer cluster who had a long term outage requiring them to activate a standby node for several weeks. Now they have fixed the dead node and would like that to be the new standby node while converting the standby / standing_in_for node to active status. What is the sequence of commands needed to reset the status - in this case here is the node table showing node0041 as the old standby node, want to make it permanent ACTIVE while node0003 should be active standby:
select node_name, node_state, node_address, node_type, standing_in_for from nodes order by node_name;;
node_name | node_state | node_address | node_type | standing_in_for
-----------------+------------+---------------+-----------+-----------------
v_vbit_node0001 | UP | 172.31.242.10 | PERMANENT |
v_vbit_node0002 | UP | 172.31.242.11 | PERMANENT |
v_vbit_node0003 | STANDBY | 172.31.242.12 | STANDBY |
v_vbit_node0004 | UP | 172.31.242.51 | PERMANENT |
v_vbit_node0005 | UP | 172.31.242.14 | PERMANENT |
v_vbit_node0006 | UP | 172.31.242.15 | PERMANENT |
v_vbit_node0007 | UP | 172.31.242.16 | PERMANENT |
v_vbit_node0008 | UP | 172.31.242.24 | PERMANENT |
v_vbit_node0009 | UP | 172.31.242.25 | PERMANENT |
v_vbit_node0010 | UP | 172.31.242.26 | PERMANENT |
v_vbit_node0011 | UP | 172.31.242.27 | PERMANENT |
v_vbit_node0012 | UP | 172.31.242.28 | PERMANENT |
v_vbit_node0013 | UP | 172.31.242.29 | PERMANENT |
v_vbit_node0014 | UP | 172.31.242.30 | PERMANENT |
v_vbit_node0015 | UP | 172.31.242.38 | PERMANENT |
v_vbit_node0016 | UP | 172.31.242.39 | PERMANENT |
v_vbit_node0017 | UP | 172.31.242.40 | PERMANENT |
v_vbit_node0018 | UP | 172.31.242.41 | PERMANENT |
v_vbit_node0019 | UP | 172.31.242.42 | PERMANENT |
v_vbit_node0020 | UP | 172.31.242.43 | PERMANENT |
v_vbit_node0021 | UP | 172.31.242.49 | PERMANENT |
v_vbit_node0022 | UP | 172.31.242.48 | PERMANENT |
v_vbit_node0023 | UP | 172.31.242.17 | PERMANENT |
v_vbit_node0024 | UP | 172.31.242.34 | PERMANENT |
v_vbit_node0025 | UP | 172.31.242.50 | PERMANENT |
v_vbit_node0026 | UP | 172.31.242.36 | PERMANENT |
v_vbit_node0027 | UP | 172.31.242.37 | PERMANENT |
v_vbit_node0028 | UP | 172.31.242.45 | PERMANENT |
v_vbit_node0029 | UP | 172.31.242.44 | PERMANENT |
v_vbit_node0030 | UP | 172.31.242.47 | PERMANENT |
v_vbit_node0031 | UP | 172.31.242.46 | PERMANENT |
v_vbit_node0032 | UP | 172.31.242.23 | PERMANENT |
v_vbit_node0033 | UP | 172.31.242.22 | PERMANENT |
v_vbit_node0034 | UP | 172.31.242.21 | PERMANENT |
v_vbit_node0035 | UP | 172.31.242.20 | PERMANENT |
v_vbit_node0036 | UP | 172.31.242.32 | PERMANENT |
v_vbit_node0037 | UP | 172.31.242.31 | PERMANENT |
v_vbit_node0038 | UP | 172.31.242.33 | PERMANENT |
v_vbit_node0039 | UP | 172.31.242.18 | PERMANENT |
v_vbit_node0040 | UP | 172.31.242.19 | PERMANENT |
v_vbit_node0041 | UP | 172.31.242.13 | PERMANENT | v_vbit_node0003
v_vbit_node0042 | STANDBY | 172.31.242.35 | STANDBY |
(42 rows)
Question
Replace a standby node permanently (reset standing_in_for)
Sign up
Already have an account? Login
Welcome to the Rocket Forum!
Please log in or register:
Employee Login | Registration Member Login | RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.