When restarting the pseudo-distributed sandbox the clients do not find the combiner

[ahellander]

If you start the example sandbox as such:

docker-compose -f ../../docker-compose.yaml -f docker-compose.override.yaml up

Then stop, and restart, the clients do not manage to attach to the combiner (now set in the db).

Workaround: Flushing the db before restart.

How if should work: The default combiner name is "combiner" and the clients should manage to get assigned to this upon restart.

Severity

• Critical/Blocker (select if the issue makes the application unusable or causes serious data loss)
• High (select if the issue affects a major feature and there is no workaround or the available workaround is very complex)
• Medium (select if the issue affects a minor feature or affects a major feature but has an easy enough workaround to not cause any major inconvenience)
• Low (select if the issue doesn't significantly affect the user experience, like minor visual bugs)

[ahellander]

This has been solved via a more robust check usign grpc health checking.