Non-standard procedures for deploying checklistbank-nub-ws

[MattBlissett]

Because of the Lucene index, this service seems to require stopping the running service before we deploy a new version.

This isn't part of the deployment process for any other webservice. We could introduce workarounds into the c-deploy deployment scripts, but this might make it more difficult to do non-standard deployments, e.g. a new backbone.

Could clb-nub-ws notice there's already an index when it starts up, and if so, open it in a read-only mode? I think that would be the most reliable fix.

If that's not possible, adding a comment in deploy-plugin to change the name "checklistbank-nub-ws" to "checklistbank-nub-ws (NB stop existing service manually)" or similar would be useful.

[mdoering]

Yes, this is indeed needed and not nice. I am not sure if it is possible to open the same lucene index with multiple readers in the old Lucene 5 version, but worth figuring out.

In COL ChecklistBank I have avoided this problem by allowing a service to shutdown components like the lucene index while still running. The deploy then first shutsdown the component and spins it up again in the newly deployed service. This still leaves a few seconds of downtime, but at least the error during that time tell you the component was down.