The Vertica Forum recently got a makeover! Let us know what you think by filling out this short, anonymous survey.
Cannot shutdown database due to a session that cannot be closed
As part of ongoing maintenance of our 3 node 6.1.0 Vertica database we had to shutdown the database. During this process we attempted to forcefully close all the sessions using the select close_all_sessions(); Unfortunately this did not close all the sessions. One remained and could not be closed directly with the close_session() command. We confirmed that this session was no longer running on the client host and therefore no session should have been present. We then tried the shutdown(‘true’) command to forcefully shutdown the database. This could not complete and we saw that the database log file was waiting continually for the session to close. Finally we had to forcefully kill the vertica process on the node which the session was connected to. Is there a bug fix or improved workaround for when sessions become detached in this way, as it is impossible to shutdown the database in a 'safe' fashion.