RadiatorDB collection creation refused

Logged when RadiatorDB setup does not create a newly configured collection because the configured nodes disagree about it. The collection field names the collection, and requests to it fail until it is created. The attached error names the nodes. Most often some nodes still store documents in the collection while other nodes do not store it, for example after a forced destroy that skipped an unreachable node or a destroy whose commit failed on some nodes. Creating the collection empty on the other nodes would leave the nodes with different documents permanently, because replication never sends those documents again. Otherwise some nodes store or set up the collection with a storage that differs from configuration. Setup retries the creation periodically and immediately after a successful destroy.

Open the collection list in the RadiatorDB maintenance view of Radiator UI and destroy the collection, which is shown as leftover or as a storage conflict. Setup then creates it empty on every node, as described in Add a Collection. To keep the leftover documents, back them up before the destroy and import them after the creation, in the order described in Keep leftover documents.