Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
From Joey Pan [jpan@rocketfuelinc.com]
The issue occurs when try to query table when restarting ec2 cluster (will get diff server ip), currently the warehouse dir is hardcoded as some internal ip.
It failed after retrying the old location:
08/11/02 14:41:51 INFO ipc.Client: Retrying connect to server: ip-10-250-75-160.ec2.internal/10.250.75.160:50001. Already tried 0 time(s).
08/11/02 14:41:52 INFO ipc.Client: Retrying connect to server: ip-10-250-75-160.ec2.internal/10.250.75.160:50001. Already tried 1 time(s).
08/11/02 14:41:53 INFO ipc.Client: Retrying connect to server: ip-10-250-75-160.ec2.internal/10.250.75.160:50001. Already tried 2 time(s).
08/11/02 14:41:54 INFO ipc.Client: Retrying connect to server: ip-10-250-75-160.ec2.internal/10.250.75.160:50001. Already tried 3 time(s).
08/11/02 14:41:55 INFO ipc.Client: Retrying connect to server: ip-10-250-75-160.ec2.internal/10.250.75.160:50001. Already tried 4 time(s).
08/11/02 14:41:56 INFO ipc.Client: Retrying connect to server: ip-10-250-75-160.ec2.internal/10.250.75.160:50001. Already tried 5 time(s).
08/11/02 14:41:57 INFO ipc.Client: Retrying connect to server: ip-10-250-75-160.ec2.internal/10.250.75.160:50001. Already tried 6 time(s).
08/11/02 14:41:58 INFO ipc.Client: Retrying connect to server: ip-10-250-75-160.ec2.internal/10.250.75.160:50001. Already tried 7 time(s).
08/11/02 14:41:59 INFO ipc.Client: Retrying connect to server: ip-10-250-75-160.ec2.internal/10.250.75.160:50001. Already tried 8 time(s).
08/11/02 14:42:00 INFO ipc.Client: Retrying connect to server: ip-10-250-75-160.ec2.internal/10.250.75.160:50001. Already tried 9 time(s).
Is there a way to set the warehouse.dir manually for the already existent db? Otherwise all tables have to be created again...
Thanks,
joey