You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Zheng Shao (JIRA)" <ji...@apache.org> on 2008/11/02 23:56:44 UTC

[jira] Created: (HADOOP-4574) Support of change the metadata of a hive table

Support of change the metadata of a hive table
----------------------------------------------

                 Key: HADOOP-4574
                 URL: https://issues.apache.org/jira/browse/HADOOP-4574
             Project: Hadoop Core
          Issue Type: Bug
          Components: contrib/hive
            Reporter: Zheng Shao


>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


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HADOOP-4574) Support of change the metadata of a hive table

Posted by "Joey Pan (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joey Pan updated HADOOP-4574:
-----------------------------


Verified the cause of  the issue, after drop tables and recreate them , the issue was gone. 

the issue can be fixed if  in : hive-default.xml 

  "hive.metastore.warehouse.dir"  can be indpendent of the hdfs url and uses the default hdfs url on the node running hadoop. 

> Support of change the metadata of a hive table
> ----------------------------------------------
>
>                 Key: HADOOP-4574
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4574
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/hive
>            Reporter: Zheng Shao
>
> 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

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.