I came up with a bit of a solution for this single global port 0 as well. Instead of creating your cluster in your main process, spawn a child process to create your cluster. Listening on port 0 within that child process seems to only affect that child and its children. You can then spawn another child from your main process to create a second cluster that can be bound to a different port 0.
Achievements
9
Karma
0
Total ProTip Views
Charity
Fork and commit to someone's open source project in need
I came up with a bit of a solution for this single global port 0 as well. Instead of creating your cluster in your main process, spawn a child process to create your cluster. Listening on port 0 within that child process seems to only affect that child and its children. You can then spawn another child from your main process to create a second cluster that can be bound to a different port 0.