Stopping application takes longer now

[Dmitry@Rivermine]

Hi, I noticed that it's taking a while for 3t shell to give prompt back after it prints the message "Application tgltest stopped successfully". On some applications could be several minutes.

What is AppLogic doing after it prints this message and before gives the prompt back?

[PeterNic]

Dmitry,

What happens after AppLogic prints the "stopped successfully" message is essentially release the resources reserved for the application, including dissolving volume connections.

One possible reason for this taking longer time is if there was a lot of data being written during application's stop -- data is sill being flushed. Let me know if this may be the case.

Another scenario would be to have a bad disk on one of the servers -- you would start getting reports of degraded volumes if that was the case.

I think it may also make sense to make the "resource release" a separate phase in stopping, so that we won't print that the app stopped successfully until everything is really done. The result will be something like this:

Stopping appliance main.web... Done.
Stopping appliance main.db... Done.
Releasing resources... Done.

Application xyz stopped successfully.



Also note that, in the web shell, sometimes you need to hit enter to get the prompt after initial login or a long operation (seems to be a peculiarity with some browsers).


Best regards,
-- Peter