You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The text was updated successfully, but these errors were encountered:
dothebart
changed the title
--starter.port and direved ports not persistet across restarts--starter.port and derived ports not persistet across restarts
Oct 5, 2020
dothebart
changed the title
--starter.port and derived ports not persistet across restarts
--starter.port and derived ports not persistet across restarts
Oct 5, 2020
dothebart
changed the title
--starter.port and derived ports not persistet across restarts
--starter.port of "leader" starter not persisted across restarts
Oct 5, 2020
launch a cluster with these
--starter.port
's :and stop all instances.
go into the respective directories, and re-launch the starter without any parameters again. The cluster will now bind:
So, starter instance 1 will not bind port
9528
but port8528
instead.Starter instance 2 & 3 will continue to groan about not being able to connect the first starter:
The processes will re-launch and work as expected.
This happenes, though the
setup.json
contains the proper port to bind:The text was updated successfully, but these errors were encountered: