I’m trying to use a copy of our production database in a test environment. The production MapD instance’s data directory is on an EBS volume mounted on the EC2 instance running MapD (file system is ext4 on Ubuntu). I took a snapshot of the production EBS volume, and on a new test MapD EC2 instance I mounted a new EBS volume using this snapshot from production, with the intent of having this test MapD instance have a copy of production data.
Before starting up the test MapD instance, I clean out all of the logs files in data/mapd_log, and remove the lock file in data/mapd_server_pid.lck. I then start the test MapD instance. It starts up fine, and it writes it’s log files to the mapd_log/ directory and creates a new .data/mapd_server_pid.lck file. However, when I try to run anything in mapdql it just hangs. Simply doing a \t to list tables just hangs indefinitely. Queries hang as well.
I’m trying to figure out where it’s running into a problem. Is there some sort of debugging knob I can turn to see what the MapD server is doing and why it’s hanging? All I see in the log after all of the start up info is this when it’s hanging:
I1020 12:59:22.741915 759 MapDHandler.cpp:349] User XXXXX connected to database XXXXXX I1020 12:59:24.183737 759 FileMgr.cpp:116] Read table metadata, Epoch is 5787 for table data at '/mapd-storage/data/mapd_data/table_2_1/'
Or is there something special I need to do to MapD before taking the EBS snapshot so that it is in a "clean’ state when taking the snapshot?
Thanks in advance.