I’m completing the process of porting our solution from NServiceBus 5 to 7.
We have an acceptation test machine running on a shared vSphere server, and once a week at midnight there’s a backup plan running. While the backup is running, all our NServiceBus services shut down:
Message: Critical error, shutting down: ‘DataLogger MessagePump’ connection to the broker has failed.
Now I find it strange that a simple backup (more latency on the disk IO?) is enough to cut the network between our services and RabbitMQ broker (both on the same host) for over 2minutes, but it is possible.
With the previous versions, we would see lots of ‘AMQP shared queue closed’, broker disarmed and then armed log messages, but it would never shut down the services, it would just reconnect at some point.
The production environment is more stable, but I would love to make sure our services does not shut down by themselves in the middle of the night.
Based on the documentation, I can set the TimeToWaitBeforeTrigerring option to an higher value to prevent this.
My question is, are there any disadvantages or consequences to set this to an higher value? What would be the limit of acceptable? Would it be okay to set it to 15 or even 30 minutes?
I’m aware I can configure the services to automatically restart on shutdown, but we would really prefer them not restarting at all for a few different reasons.