DataPlane API service not propagating port changes from config on reload

[robschn]

Hello!

I was changing around some ports and went to do a reload via kill -s SIGUSR1 so the dataplaneapi service can read the new config but the old port numbers remained until I did a restart. Is this expected behavior and is there any documentation on what config parameters require a restart?

bash-5.0# netstat -anp | grep datapla | grep LISTEN
tcp        0      0 127.0.0.1:557          0.0.0.0:*               LISTEN      115515/dataplaneap
tcp        0      0 127.0.0.1:110           0.0.0.0:*               LISTEN      104114/dataplaneap
bash-5.0# systemctl reload dataplaneapi
bash-5.0# netstat -anp | grep datapla | grep LISTEN
tcp        0      0 127.0.0.1:557          0.0.0.0:*               LISTEN      115515/dataplaneap
tcp        0      0 127.0.0.1:110           0.0.0.0:*               LISTEN      104114/dataplaneap
bash-5.0# systemctl restart dataplaneapi
bash-5.0# netstat -anp | grep datapla | grep LISTEN
tcp        0      0 127.0.0.1:559          0.0.0.0:*               LISTEN      115515/dataplaneap
tcp        0      0 127.0.0.1:210           0.0.0.0:*               LISTEN      107918/dataplaneap

Thank you!

[smeroth]

Hello

Please describe step by step what you're doing from the start to the end.

this to let us understand

• the status before the modifications
• what you modify , the actions you do ...
• the status after your modifications and actions
• what you expect

Thank you

[robschn]

Hey @smeroth !

So in this case, I was updating the dataplaneapi.yml config to go from port 110 to 210. I ran systemctl reload dataplaneapi and then saw the port did not change. Only running systemctl restart dataplaneapi propagated the port change.

I expected that updating the yaml config and issuing a reload was enough for the dataplaneapi service to see and act on the port changes. Is that the expected behavior or do port and socket connections always require a restart?