RadiatorDB collection creation failed

Logged when RadiatorDB setup could not create newly configured collections on every configured node. The collections field names the collections, which stay unavailable, and the attached error names the failed step and its node and gives the cause, for example a node that stopped answering, a lock that was not granted within health_check_timeout because another transaction held the document tables on that node, or a step that did not finish within setup_timeout. When a commit failed on one node, nodes that committed earlier keep the new collections empty, and the next attempt adopts them. Setup retries the creation periodically and whenever a node is set up again.

Check the attached error and the RadiatorDB maintenance view of Radiator UI for unreachable or unhealthy nodes, and resolve the reported connection or lock problem. If the creation keeps running out of time on a slow cluster, increase setup_timeout.