menghaoranss opened a new issue, #17945:
URL: https://github.com/apache/shardingsphere/issues/17945
## Background
In order to be compatible with the cloud native deployment scenario, the
instance nodes of the registry should be refactored statelessly to ensure
that when the proxy restarts, it does not retain any instance-related data
nodes in the registry center. The data nodes bound to the running instance in
the registry center cannot be persistent, so we now need to adjust all the data
nodes to ephemeral nodes.
This adjustment is for `/nodes/compute_nodes` node.
## Before
```
├──nodes
├ ├──compute_nodes
├ ├ ├──online
├ ├ ├ ├──proxy
├ ├ ├ ├ ├──${your_instance_ip_a}@${your_instance_port_x}
├ ├ ├ ├ ├──${your_instance_ip_b}@${your_instance_port_y}
├ ├ ├ ├ ├──....
├ ├ ├ ├──jdbc
├ ├ ├ ├ ├──${your_instance_ip_a}@${your_instance_pid_x}
├ ├ ├ ├ ├──${your_instance_ip_b}@${your_instance_pid_y}
├ ├ ├ ├ ├──....
├ ├ ├──attributies
├ ├ ├ ├──${your_instance_ip_a}@${your_instance_port_x}
├ ├ ├ ├ ├──status
├ ├ ├ ├ ├──label
├ ├ ├ ├ ├──xa_recovery_id
├ ├ ├ ├ ├──worker_id
├ ├ ├ ├──${your_instance_ip_b}@${your_instance_pid_y}
├ ├ ├ ├ ├──process_trigger
├ ├ ├ ├ ├ ├──process_id
├ ├ ├ ├──....
```
## After
```
├──nodes
├ ├──compute_nodes
├ ├ ├──online
├ ├ ├ ├──proxy
├ ├ ├ ├ ├──uuid-1(127.0.0.1@3306)
├ ├ ├ ├ ├──uuid-2(127.0.0.1@3307)
├ ├ ├ ├ ├──....
├ ├ ├ ├──jdbc
├ ├ ├ ├ ├──uuid-3(127.0.0.1@18306)
├ ├ ├ ├ ├──uuid-4(127.0.0.1@18307)
├ ├ ├ ├ ├──....
├ ├ ├──status
├ ├ ├ ├──uuid-1(circuit_break)
├ ├ ├ ├──uuid-3(circuit_break)
├ ├ ├──xa_recovery_id
├ ├ ├ ├──recovery_id_1
├ ├ ├ ├ ├──uuid-1
├ ├ ├ ├──recovery_id_2
├ ├ ├ ├ ├──uuid-2
├ ├ ├──worker_id
├ ├ ├ ├──uuid-1(0)
├ ├ ├ ├──uuid-2(1)
├ ├ ├──labels
├ ├ ├ ├──uuid-1(OLAP)
├ ├ ├ ├──uuid-2(OLTP)
├ ├ ├──process_trigger
├ ├ ├ ├──process_list_id_1:uuid-1
├ ├ ├ ├──process_list_id_2:uuid-1
```
--
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]
