[
https://issues.apache.org/jira/browse/HAWQ-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14955676#comment-14955676
]
Caleb Welton commented on HAWQ-52:
----------------------------------
What is the proposed fix for this?
1. We can perform some validation on CREATE FILESPACE to validate that we are
pointing to a valid hdfs port.
2. However the fact that there is a valid HDFS port at the time of filespace
creation does not mean that it will always be there and available, so error
handling if that HDFS service has been stopped is still needed at time of table
space creation.
3. It would be desirable if we could have a better error message for the CREATE
TABLESPACE command.
I would expect:
{noformat}
CREATE FILESPACE fsinvalid on hdfs ('localhost:10086/fsinvalid');
ERROR: could not connect to HDFS NameNode at 'localhost:10086'
DETAIL: Connection to remote host on the specified port failed to connect to
the HDFS NameNode. Check the hostname and port are correct and that the HDFS
service is running.
CREATE FILESPACE fsvalid on HDFS ('localhost:50070/fsvalid');
CREATE FILESPACE
bash$ service hadoop-hdfs-namenode stop
CREATE TABLESPACE ts_hdfs_stopped FILESPACE fsvalid;
ERROR: could not create tablespace directory
'hdfs://localhost:50070/fsvalid/17464'
DETAIL: Connection from HDFS NameNode refused, check that the HDFS service is
running and that the FILESPACE points to the correct access point.
{noformat}
> filespace can be created in invalid hdfs port
> ---------------------------------------------
>
> Key: HAWQ-52
> URL: https://issues.apache.org/jira/browse/HAWQ-52
> Project: Apache HAWQ
> Issue Type: Bug
> Components: Storage
> Reporter: Dong Li
> Assignee: Roman Shaposhnik
>
> you can create filespace in invalid hdfs port , it didn't check the hdfs port
> and not check if it was created successfully. Actually it was not created in
> hdfs and can not be used.
> create filespace fsinvalid on hdfs ('localhost:10086/fsinvalid');
> CREATE FILESPACE
> create TABLESPACE tsinvalid FILESPACE fsinvalid;
> WARNING: could not remove tablespace directory 17464: Input/output error
> CONTEXT: Dropping file-system object -- Tablespace Directory: '17464'
> ERROR: could not create tablespace directory 17464: Input/output error
> select * from gp_persistent_filespace_node;
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
