As a user I want a shortest possible downtime for WCQS in case of data reload, so that I can continue using that.
- Feed the second blazegraph instance, switch journals afterwards
- The same but with two namespaces (single instance of Blazegraph)
Category reload happens this way already.
Switch can also happen via nginx.
- data reload doesn't trigger maintenance page
- data is available after reload.