[jira] [Created] (HDFS-2883) trash behavior needs to be improved to be consistent so that only server side configs are enforced
trash behavior needs to be improved to be consistent so that only server side configs are enforced -- Key: HDFS-2883 URL: https://issues.apache.org/jira/browse/HDFS-2883 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.24.0, 1.1.0 Reporter: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2854) SecurityUtil.buildTokenService returns java.net.UnknownHostException when using paths like viewfs://default/some/path
SecurityUtil.buildTokenService returns java.net.UnknownHostException when using paths like viewfs://default/some/path - Key: HDFS-2854 URL: https://issues.apache.org/jira/browse/HDFS-2854 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.24.0, 0.23.1 Reporter: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2790) FSNamesystem.setTimes throws exception with wrong configuration name in the message
FSNamesystem.setTimes throws exception with wrong configuration name in the message --- Key: HDFS-2790 URL: https://issues.apache.org/jira/browse/HDFS-2790 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 1.0.0, 0.24.0, 1.1.0 Reporter: Arpit Gupta Priority: Minor the api throws this message when hdfs is not configured for accessTime Access time for hdfs is not configured. Please set dfs.support.accessTime configuration parameter. The property name should be dfs.access.time.precision -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2528) webhdfs rest call to a secure dn fails when a token is sent
webhdfs rest call to a secure dn fails when a token is sent
---
Key: HDFS-2528
URL: https://issues.apache.org/jira/browse/HDFS-2528
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 0.20.205.0
Reporter: Arpit Gupta
Assignee: Tsz Wo (Nicholas), SZE
curl -L -u : --negotiate -i
http://NN:50070/webhdfs/v1/tmp/webhdfs_data/file_small_data.txt?op=OPEN;
the following exception is thrown by the datanode when the redirect happens.
{RemoteException:{exception:IOException,javaClassName:java.io.IOException,message:Call
to hrt12n23.cc1.ygridcore.net/98.137.234.231:8020 failed on local exception:
java.io.IOException: javax.security.sasl.SaslException: GSS initiate failed
[Caused by GSSException: No valid credentials provided (Mechanism level: Failed
to find any Kerberos tgt)]}}
Interestingly when using ./bin/hadoop with a webhdfs path we are able to cat or
tail a file successfully.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2508) webhdfs getfileblocklocations is not returning the correct block information when multiple blocks are present
webhdfs getfileblocklocations is not returning the correct block information when multiple blocks are present - Key: HDFS-2508 URL: https://issues.apache.org/jira/browse/HDFS-2508 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta Assignee: Tsz Wo (Nicholas), SZE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2475) webhdfs rest api's should send the content-length header consistently on all calls
webhdfs rest api's should send the content-length header consistently on all calls --- Key: HDFS-2475 URL: https://issues.apache.org/jira/browse/HDFS-2475 Project: Hadoop HDFS Issue Type: Improvement Affects Versions: 0.20.205.0 Reporter: Arpit Gupta webhdfs rest api's on some calls return the content-length header in some calls but not on all. I think if possible we should return content-length header whenever possible -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2468) webhdfs create a file and send permission does not set the permission to the expected value
webhdfs create a file and send permission does not set the permission to the expected value --- Key: HDFS-2468 URL: https://issues.apache.org/jira/browse/HDFS-2468 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta Assignee: Tsz Wo (Nicholas), SZE Issue a create call and send permission(666). The file that is created gets the permission rw-r--r-- instead of expected rw-rw-rw- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2469) webhdfs create a file and send buffersize=0 hangs the request
webhdfs create a file and send buffersize=0 hangs the request - Key: HDFS-2469 URL: https://issues.apache.org/jira/browse/HDFS-2469 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta Assignee: Tsz Wo (Nicholas), SZE Issue a create call and send buffersize=0 the user gets the redirect and upon sending the request to the new location the request does not return with the content. Should we set a min and max value for buffersize? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2453) tail using a webhdfs uri throws an error
tail using a webhdfs uri throws an error Key: HDFS-2453 URL: https://issues.apache.org/jira/browse/HDFS-2453 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta Assignee: Tsz Wo (Nicholas), SZE /usr//bin/hadoop --config /etc/hadoop dfs -tail webhdfs://NN:50070/file tail: HTTP_PARTIAL expected, received 200 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2456) webhdfs default to a replication factor of 1 instead of using the dfs.replication property
webhdfs default to a replication factor of 1 instead of using the dfs.replication property -- Key: HDFS-2456 URL: https://issues.apache.org/jira/browse/HDFS-2456 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta Assignee: Tsz Wo (Nicholas), SZE create a file using webhdfs rest api's and the replication factor it gets is 1 instead of 3 which is being set by the property dfs.replication -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2458) webhdfs create call throws an error after the redirect if the file exists, we should throw a 403 before
webhdfs create call throws an error after the redirect if the file exists, we should throw a 403 before --- Key: HDFS-2458 URL: https://issues.apache.org/jira/browse/HDFS-2458 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta Assignee: Tsz Wo (Nicholas), SZE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2460) webhdfs returns content type text/html when an error is thrown, we should return application/json
webhdfs returns content type text/html when an error is thrown, we should return application/json -- Key: HDFS-2460 URL: https://issues.apache.org/jira/browse/HDFS-2460 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta Assignee: Tsz Wo (Nicholas), SZE make a create call using rest api's and send an invalid value for parameter overwrite Actual Content type returned: type text/html; charset=utf-8 We should return application/json. This seems similar to the earlier bug where we had 2 content types being returned. We patched it for success but not for errors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2462) webhdfs create a file that exists and overwrite it also changes the permission of the file
webhdfs create a file that exists and overwrite it also changes the permission of the file -- Key: HDFS-2462 URL: https://issues.apache.org/jira/browse/HDFS-2462 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2463) webhdfs able to write data to a file that was readonly
webhdfs able to write data to a file that was readonly -- Key: HDFS-2463 URL: https://issues.apache.org/jira/browse/HDFS-2463 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta Assignee: Tsz Wo (Nicholas), SZE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2435) webhdfs able to set access and mod times of paths to a value in future
webhdfs able to set access and mod times of paths to a value in future -- Key: HDFS-2435 URL: https://issues.apache.org/jira/browse/HDFS-2435 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta I am able to use the settimes api and set the access and modification time of paths to a value in future. Should that be allowed? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2436) webhdfs settimes api returns a 404 when called on a dir
webhdfs settimes api returns a 404 when called on a dir --- Key: HDFS-2436 URL: https://issues.apache.org/jira/browse/HDFS-2436 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta settimes api is working when called on a file, but when called on a dir it returns a 404. I should be able to set time on both a file and a directory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2437) webhdfs setowner does not set the group to new value
webhdfs setowner does not set the group to new value Key: HDFS-2437 URL: https://issues.apache.org/jira/browse/HDFS-2437 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2438) webhdfs setowner and send an empty value for owner returns a 200
webhdfs setowner and send an empty value for owner returns a 200 Key: HDFS-2438 URL: https://issues.apache.org/jira/browse/HDFS-2438 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2439) webhdfs open an invalid path leads to a 500 which states a npe, we should return a 404 with appropriate error message
webhdfs open an invalid path leads to a 500 which states a npe, we should return a 404 with appropriate error message - Key: HDFS-2439 URL: https://issues.apache.org/jira/browse/HDFS-2439 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2440) webhdfs open a file and send 0 or invalid bufferSize throws a 500 with xml content
webhdfs open a file and send 0 or invalid bufferSize throws a 500 with xml content -- Key: HDFS-2440 URL: https://issues.apache.org/jira/browse/HDFS-2440 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2423) webhdfs returns two content-type headers
webhdfs returns two content-type headers Key: HDFS-2423 URL: https://issues.apache.org/jira/browse/HDFS-2423 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta $ curl -i http://localhost:50070/webhdfs/path?op=GETFILESTATUS; HTTP/1.1 200 OK Content-Type: text/html; charset=utf-8 Expires: Thu, 01-Jan-1970 00:00:00 GMT Content-Type: application/json Transfer-Encoding: chunked Server: Jetty(6.1.26) It should only return one content type header = application/json -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2424) webhdfs liststatus json does not convert to a valid xml document
webhdfs liststatus json does not convert to a valid xml document Key: HDFS-2424 URL: https://issues.apache.org/jira/browse/HDFS-2424 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2425) webhdfs GETFILESTATUS calls shows the localName as empty where as the localName for the same path in LISTSTATUS call has the correct value
webhdfs GETFILESTATUS calls shows the localName as empty where as the localName for the same path in LISTSTATUS call has the correct value -- Key: HDFS-2425 URL: https://issues.apache.org/jira/browse/HDFS-2425 Project: Hadoop HDFS Issue Type: Bug Reporter: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2426) webhdfs GETFILESTATUAS for a path that does not exist returns a 200 instead of a 404
webhdfs GETFILESTATUAS for a path that does not exist returns a 200 instead of a 404 Key: HDFS-2426 URL: https://issues.apache.org/jira/browse/HDFS-2426 Project: Hadoop HDFS Issue Type: Bug Reporter: Arpit Gupta http://NN:50070/webhdfs/some_invalid_path?op=GETFILESTATUS Returns a 200 with no content. We should return a 404 in this case -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2427) webhdfs mkdirs api call creates path with 777 permission, we should default it to 755
webhdfs mkdirs api call creates path with 777 permission, we should default it to 755 - Key: HDFS-2427 URL: https://issues.apache.org/jira/browse/HDFS-2427 Project: Hadoop HDFS Issue Type: Bug Reporter: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2428) webhdfs mkdir call fails with a 500 when an invalid permission is sent, we should return a 400
webhdfs mkdir call fails with a 500 when an invalid permission is sent, we
should return a 400
--
Key: HDFS-2428
URL: https://issues.apache.org/jira/browse/HDFS-2428
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Arpit Gupta
PUT Request: http://localhost:50070/webhdfs/some_path?op=MKDIRSpermission=955
Exception returned
HTTP/1.1 500 Internal Server Error
{RemoteException:{className:com.sun.jersey.api.ParamException$QueryParamException,message:java.lang.NumberFormatException:
For input string: \955\}}
We should return a 400 with appropriate error message
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2429) webhdfs delete a path that does not exists returns a 200, we should return a 404
webhdfs delete a path that does not exists returns a 200, we should return a 404
Key: HDFS-2429
URL: https://issues.apache.org/jira/browse/HDFS-2429
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Arpit Gupta
Priority: Minor
Request URI http://NN:50070/webhdfs/some_path_that_does_not_exists?op=DELETE
Request Method: DELETE
Status Line: HTTP/1.1 200 OK
Request Content: {boolean:false}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2431) webhdfs setpermission api does not return any content upon success
webhdfs setpermission api does not return any content upon success -- Key: HDFS-2431 URL: https://issues.apache.org/jira/browse/HDFS-2431 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta Request URI http://NN:50070/webhdfs/tmp/webhdfs_data/file_change_perm.txt?op=SETPERMISSIONpermission=500 Request Method: PUT Status Line: HTTP/1.1 200 OK Response Content: none We should return some success content. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2432) webhdfs setreplication api should return a 400 when called on a directory
webhdfs setreplication api should return a 400 when called on a directory
-
Key: HDFS-2432
URL: https://issues.apache.org/jira/browse/HDFS-2432
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Arpit Gupta
Currently the set replication api on a directory leads to a 200.
Request URI
http://NN:50070/webhdfs/tmp/webhdfs_data/dir_replication_tests?op=SETREPLICATIONreplication=5
Request Method: PUT
Status Line: HTTP/1.1 200 OK
Response Content: {boolean:false}
Since we can determine that this call did not succeed (boolean=false) we should
rather just return a 400 (Bad Request)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2416) hadoop calls cat, tail, copyToLocal, distcp on a secure cluster with an webhdfs uri fail with a 401
hadoop calls cat, tail, copyToLocal, distcp on a secure cluster with an webhdfs uri fail with a 401 --- Key: HDFS-2416 URL: https://issues.apache.org/jira/browse/HDFS-2416 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2419) hadoop calls cat, tail, get, copyToLocal, on a secure cluster with an webhdfs uri fail with a 401
hadoop calls cat, tail, get, copyToLocal, on a secure cluster with an webhdfs uri fail with a 401 - Key: HDFS-2419 URL: https://issues.apache.org/jira/browse/HDFS-2419 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta Assignee: Jitendra Nath Pandey a dfs -cat returns the following... cat: Unauthorized (error code=401) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2411) with webhdfs enabled in secure mode the auth to local mappings are not being respected.
with webhdfs enabled in secure mode the auth to local mappings are not being respected. --- Key: HDFS-2411 URL: https://issues.apache.org/jira/browse/HDFS-2411 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2404) webhdfs liststatus json response is not correct
webhdfs liststatus json response is not correct --- Key: HDFS-2404 URL: https://issues.apache.org/jira/browse/HDFS-2404 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta Assignee: Suresh Srinivas -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2405) hadoop dfs command with webhdfs fails
hadoop dfs command with webhdfs fails - Key: HDFS-2405 URL: https://issues.apache.org/jira/browse/HDFS-2405 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta Assignee: Jitendra Nath Pandey Priority: Critical -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2406) webhdfs shows wrong message when content is deleted
webhdfs shows wrong message when content is deleted --- Key: HDFS-2406 URL: https://issues.apache.org/jira/browse/HDFS-2406 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2402) namenode does not start with can not access a member of class exception
namenode does not start with can not access a member of class exception --- Key: HDFS-2402 URL: https://issues.apache.org/jira/browse/HDFS-2402 Project: Hadoop HDFS Issue Type: Bug Reporter: Arpit Gupta Assignee: Jitendra Nath Pandey Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2396) dfs -tail command with an hftp source fails with a cant seek error
dfs -tail command with an hftp source fails with a cant seek error -- Key: HDFS-2396 URL: https://issues.apache.org/jira/browse/HDFS-2396 Project: Hadoop HDFS Issue Type: Bug Reporter: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2395) webhdfs api's should return a root element in the json response
webhdfs api's should return a root element in the json response --- Key: HDFS-2395 URL: https://issues.apache.org/jira/browse/HDFS-2395 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.206.0 Reporter: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2386) fsck calls lead to handshake_failure
fsck calls lead to handshake_failure Key: HDFS-2386 URL: https://issues.apache.org/jira/browse/HDFS-2386 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2387) hftp fails as it is not able to get delegation token over https
hftp fails as it is not able to get delegation token over https --- Key: HDFS-2387 URL: https://issues.apache.org/jira/browse/HDFS-2387 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta Run a dfs command with the path specified as hftp leads to the following issue bash-3.2$ /bin/hadoop --config HADOOP_CONF_DIR dfs -ls hftp://NN_HOST:50070/path 11/09/29 16:07:23 INFO fs.FileSystem: Couldn't get a delegation token from https://NN_HOST:50470 using https. ls: Security enabled but user not authenticated by filter -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2389) restart dns and namenode when hbase master and region servers are running and the namenode does not come out of safemode
restart dns and namenode when hbase master and region servers are running and the namenode does not come out of safemode Key: HDFS-2389 URL: https://issues.apache.org/jira/browse/HDFS-2389 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2376) fsck reports the fs as healthy even when all replicas of a block are corrupted by overwriting them with smaller content
fsck reports the fs as healthy even when all replicas of a block are corrupted by overwriting them with smaller content --- Key: HDFS-2376 URL: https://issues.apache.org/jira/browse/HDFS-2376 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta Here is the issue 1. Find all 3 replicas for a block 2. Corrupt the 3 blocks by overwriting them with smaller content 3. cat the file which had the above block (cat fails as content is not correct) 4. run fsck and fsck still reports the fs as healthy -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2365) namenode ui does not show we are running secure hadoop when security is on
namenode ui does not show we are running secure hadoop when security is on -- Key: HDFS-2365 URL: https://issues.apache.org/jira/browse/HDFS-2365 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta Priority: Minor namenode ui used to have a line saying Security is ON when one was using a secure cluster. Up unit 204 we used to see that but in 205 it is no longer there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2366) webhds throws a npe when ugi is null from getDelegationToken
webhds throws a npe when ugi is null from getDelegationToken Key: HDFS-2366 URL: https://issues.apache.org/jira/browse/HDFS-2366 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta Assignee: Tsz Wo (Nicholas), SZE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2368) defaults created for web keytab and principal, these properties should not have defaults
defaults created for web keytab and principal, these properties should not have
defaults
Key: HDFS-2368
URL: https://issues.apache.org/jira/browse/HDFS-2368
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 0.20.205.0
Reporter: Arpit Gupta
Assignee: Tsz Wo (Nicholas), SZE
the following defaults are set in hdfs-defaults.xml
property
namedfs.web.authentication.kerberos.principal/name
valueHTTP/${dfs.web.hostname}@${kerberos.realm}/value
description
The HTTP Kerberos principal used by Hadoop-Auth in the HTTP endpoint.
The HTTP Kerberos principal MUST start with 'HTTP/' per Kerberos
HTTP SPENGO specification.
/description
/property
property
namedfs.web.authentication.kerberos.keytab/name
value${user.home}/dfs.web.keytab/value
description
The Kerberos keytab file with the credentials for the
HTTP Kerberos principal used by Hadoop-Auth in the HTTP endpoint.
/description
/property
These properties should not have defaults
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2373) webhdfs and hftp print extra info to the console
webhdfs and hftp print extra info to the console Key: HDFS-2373 URL: https://issues.apache.org/jira/browse/HDFS-2373 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta run an hdfs command using either hftp or webhdfs and it prints the following line to the console (system out) Retrieving token from: https://NN_HOST:50470/getDelegationToken Probably in the code where we get the delegation token. This should be removed as people using the dfs commands to get a handle to the content such as dfs -cat will now get an extra line that is not part of the actual content. This should either be only in the log or not logged at all. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HDFS-2374) hftp: not able to delete content using hftp url
hftp: not able to delete content using hftp url --- Key: HDFS-2374 URL: https://issues.apache.org/jira/browse/HDFS-2374 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.20.205.0 Reporter: Arpit Gupta issue command bin/hadoop dfs -rmr hftp://nn:port/path Command fails with the following exception 11/09/27 03:53:43 WARN fs.Trash: Can't create trash directory: hftp://nn:port/user/some_user/.Trash/Current/path Problem with Trash.Not supported. Consider using -skipTrash option -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
