Closed anonymouskitler closed 5 years ago
Hello @chandureddivari Thanks for your report. I've tried your procedure and can not reproduce the issue.
Could you give more insight on how you stop the container at step 1 ?
@jbfavre Thanks for the prompt reply. Attaching the set of steps to recreate the issue:
@chandureddivari thanks for the details.
Could you please test, from an empty data directory, and add --timeout 20
or 30
option to docker stop ?
My guess is that default timeout is too short for Vertica to properly shutdown.
I'll try to improve that in the future, but using the option could be a suitable workaround for now.
Please let me know
@jbfavre thanks for the help. Yes it worked, but with -t 60
though! Also it'd be nice if you can pass db password as env variable. Thanks again for the awesome image :)
@jbfavre I'm testing the Vertica docker container in Azure, and to stop the container I have two options, on the GUI or with a command. In either case I cannot specify a timeout for properly shutdown. How can this scenario be handled?
Thanks
@pgschr Thanks for your report. Unfortunatly, I've no idea of any possible workaround since I don't use Azure.
Steps:
docker run -p 5433:5433 -d -v ~/vertica:/home/dbadmin/docker jbfavre/vertica:9.2.0-7_ubuntu-16.04
. Everything good. Stop the container. Exitdocker run -p 5433:5433 -d -v ~/vertica:/home/dbadmin/docker jbfavre/vertica:9.2.0-7_ubuntu-16.04
. The container exits witherror_message=Catalog parent directory already exists:
. This is because the directory was already created and rerunning is trying to create the same directory again.Full log:
I think we can do something like this to check if the database already exists