[jira] [Commented] (HDFS-9283) DFS client retry trace should not be dispalyed in CLI
[
https://issues.apache.org/jira/browse/HDFS-9283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15804440#comment-15804440
]
Jagadesh Kiran N commented on HDFS-9283:
Thanks for your review [~templedf] ,the aim is to handle it for all the API not
only for the getFileInfo()
> DFS client retry trace should not be dispalyed in CLI
> --
>
> Key: HDFS-9283
> URL: https://issues.apache.org/jira/browse/HDFS-9283
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9283_00.patch
>
>
> In Secure HA Mode when we try to
> {code}
> ./hdfs fsck /
> {code}
> If more than 2 name nodes are present it will through the below exception and
> stack trace.
> {code}
> 15/10/22 18:39:06 INFO retry.RetryInvocationHandler: Exception while invoking
> getFileInfo of class ClientNamenodeProtocolTranslatorPB over
> /10.18.111.177:65110 after 1 fail over attempts. Trying to fail over after
> sleeping for 843ms.
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
> Operation category READ is not supported in state standby
> at
> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1875)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:1297)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getFileInfo(FSNamesystem.java:3745)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.getFileInfo(NameNodeRpcServer.java:1014)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.getFileInfo(ClientNamenodeProtocolServerSideTranslatorPB.java:853)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:973)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2088)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2084)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1672)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2082)
> at org.apache.hadoop.ipc.Client.call(Client.java:1511)
> at org.apache.hadoop.ipc.Client.call(Client.java:1442)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:229)
> at com.sun.proxy.$Proxy9.getFileInfo(Unknown Source)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.getFileInfo(ClientNamenodeProtocolTranslatorPB.java:771)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:187)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:102)
> at com.sun.proxy.$Proxy10.getFileInfo(Unknown Source)
> at org.apache.hadoop.hdfs.DFSClient.getFileInfo(DFSClient.java:1789)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$25.doCall(DistributedFileSystem.java:1387)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$25.doCall(DistributedFileSystem.java:1383)
> at
> org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1383)
> at org.apache.hadoop.fs.FileSystem.resolvePath(FileSystem.java:753)
> at org.apache.hadoop.hdfs.tools.DFSck.getResolvedPath(DFSck.java:232)
> at org.apache.hadoop.hdfs.tools.DFSck.doWork(DFSck.java:311)
> at org.apache.hadoop.hdfs.tools.DFSck.access$000(DFSck.java:73)
> at org.apache.hadoop.hdfs.tools.DFSck$1.run(DFSck.java:151)
> at org.apache.hadoop.hdfs.tools.DFSck$1.run(DFSck.java:148)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
>
[jira] [Updated] (HDFS-9283) DFS client retry trace should not be dispalyed in CLI
[
https://issues.apache.org/jira/browse/HDFS-9283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9283:
---
Status: Patch Available (was: Open)
> DFS client retry trace should not be dispalyed in CLI
> --
>
> Key: HDFS-9283
> URL: https://issues.apache.org/jira/browse/HDFS-9283
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9283_00.patch
>
>
> In Secure HA Mode when we try to
> {code}
> ./hdfs fsck /
> {code}
> If more than 2 name nodes are present it will through the below exception and
> stack trace.
> {code}
> 15/10/22 18:39:06 INFO retry.RetryInvocationHandler: Exception while invoking
> getFileInfo of class ClientNamenodeProtocolTranslatorPB over
> /10.18.111.177:65110 after 1 fail over attempts. Trying to fail over after
> sleeping for 843ms.
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
> Operation category READ is not supported in state standby
> at
> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1875)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:1297)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getFileInfo(FSNamesystem.java:3745)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.getFileInfo(NameNodeRpcServer.java:1014)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.getFileInfo(ClientNamenodeProtocolServerSideTranslatorPB.java:853)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:973)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2088)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2084)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1672)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2082)
> at org.apache.hadoop.ipc.Client.call(Client.java:1511)
> at org.apache.hadoop.ipc.Client.call(Client.java:1442)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:229)
> at com.sun.proxy.$Proxy9.getFileInfo(Unknown Source)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.getFileInfo(ClientNamenodeProtocolTranslatorPB.java:771)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:187)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:102)
> at com.sun.proxy.$Proxy10.getFileInfo(Unknown Source)
> at org.apache.hadoop.hdfs.DFSClient.getFileInfo(DFSClient.java:1789)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$25.doCall(DistributedFileSystem.java:1387)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$25.doCall(DistributedFileSystem.java:1383)
> at
> org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1383)
> at org.apache.hadoop.fs.FileSystem.resolvePath(FileSystem.java:753)
> at org.apache.hadoop.hdfs.tools.DFSck.getResolvedPath(DFSck.java:232)
> at org.apache.hadoop.hdfs.tools.DFSck.doWork(DFSck.java:311)
> at org.apache.hadoop.hdfs.tools.DFSck.access$000(DFSck.java:73)
> at org.apache.hadoop.hdfs.tools.DFSck$1.run(DFSck.java:151)
> at org.apache.hadoop.hdfs.tools.DFSck$1.run(DFSck.java:148)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1672)
> at
[jira] [Updated] (HDFS-9283) DFS client retry trace should not be dispalyed in CLI
[
https://issues.apache.org/jira/browse/HDFS-9283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9283:
---
Attachment: HDFS-9283_00.patch
Ataching the patch ,Please Review
> DFS client retry trace should not be dispalyed in CLI
> --
>
> Key: HDFS-9283
> URL: https://issues.apache.org/jira/browse/HDFS-9283
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9283_00.patch
>
>
> In Secure HA Mode when we try to
> {code}
> ./hdfs fsck /
> {code}
> If more than 2 name nodes are present it will through the below exception and
> stack trace.
> {code}
> 15/10/22 18:39:06 INFO retry.RetryInvocationHandler: Exception while invoking
> getFileInfo of class ClientNamenodeProtocolTranslatorPB over
> /10.18.111.177:65110 after 1 fail over attempts. Trying to fail over after
> sleeping for 843ms.
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
> Operation category READ is not supported in state standby
> at
> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1875)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:1297)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getFileInfo(FSNamesystem.java:3745)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.getFileInfo(NameNodeRpcServer.java:1014)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.getFileInfo(ClientNamenodeProtocolServerSideTranslatorPB.java:853)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:973)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2088)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2084)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1672)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2082)
> at org.apache.hadoop.ipc.Client.call(Client.java:1511)
> at org.apache.hadoop.ipc.Client.call(Client.java:1442)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:229)
> at com.sun.proxy.$Proxy9.getFileInfo(Unknown Source)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.getFileInfo(ClientNamenodeProtocolTranslatorPB.java:771)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:187)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:102)
> at com.sun.proxy.$Proxy10.getFileInfo(Unknown Source)
> at org.apache.hadoop.hdfs.DFSClient.getFileInfo(DFSClient.java:1789)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$25.doCall(DistributedFileSystem.java:1387)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$25.doCall(DistributedFileSystem.java:1383)
> at
> org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1383)
> at org.apache.hadoop.fs.FileSystem.resolvePath(FileSystem.java:753)
> at org.apache.hadoop.hdfs.tools.DFSck.getResolvedPath(DFSck.java:232)
> at org.apache.hadoop.hdfs.tools.DFSck.doWork(DFSck.java:311)
> at org.apache.hadoop.hdfs.tools.DFSck.access$000(DFSck.java:73)
> at org.apache.hadoop.hdfs.tools.DFSck$1.run(DFSck.java:151)
> at org.apache.hadoop.hdfs.tools.DFSck$1.run(DFSck.java:148)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1672)
> at
[jira] [Issue Comment Deleted] (HDFS-9675) BlockSender incorrectly output error logs with non-English locale
[
https://issues.apache.org/jira/browse/HDFS-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9675:
---
Comment: was deleted
(was: [~ajisakaa] ,{code} String ioem = e.getLocalizedMessage() {code} should
workout for ioem.startWith , Please review )
> BlockSender incorrectly output error logs with non-English locale
> -
>
> Key: HDFS-9675
> URL: https://issues.apache.org/jira/browse/HDFS-9675
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode
>Reporter: Akira Ajisaka
>Assignee: Jagadesh Kiran N
> Labels: i18n
>
> If the locale is non-English, the following code does not work.
> {code:title=BlockSender.java}
> String ioem = e.getMessage();
> if (!ioem.startsWith("Broken pipe") && !ioem.startsWith("Connection
> reset")) {
> LOG.error("BlockSender.sendChunks() exception: ", e);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-9675) BlockSender incorrectly output error logs with non-English locale
[
https://issues.apache.org/jira/browse/HDFS-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15774450#comment-15774450
]
Jagadesh Kiran N commented on HDFS-9675:
[~ajisakaa] ,{code} String ioem = e.getLocalizedMessage() {code} should workout
for ioem.startWith , Please review
> BlockSender incorrectly output error logs with non-English locale
> -
>
> Key: HDFS-9675
> URL: https://issues.apache.org/jira/browse/HDFS-9675
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode
>Reporter: Akira Ajisaka
>Assignee: Jagadesh Kiran N
> Labels: i18n
>
> If the locale is non-English, the following code does not work.
> {code:title=BlockSender.java}
> String ioem = e.getMessage();
> if (!ioem.startsWith("Broken pipe") && !ioem.startsWith("Connection
> reset")) {
> LOG.error("BlockSender.sendChunks() exception: ", e);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-11262) Remove unused variables in FSImage.java
[
https://issues.apache.org/jira/browse/HDFS-11262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15764379#comment-15764379
]
Jagadesh Kiran N commented on HDFS-11262:
-
Thanks [~ajisakaa] for committing the same
> Remove unused variables in FSImage.java
> ---
>
> Key: HDFS-11262
> URL: https://issues.apache.org/jira/browse/HDFS-11262
> Project: Hadoop HDFS
> Issue Type: Improvement
>Reporter: Akira Ajisaka
>Assignee: Jagadesh Kiran N
>Priority: Trivial
> Labels: newbie
> Fix For: 2.8.0, 3.0.0-alpha2
>
> Attachments: HDFS-11262_00.patch, HDFS-11262_01.patch,
> HDFS-11262_02.patch
>
>
> {code:title=FSImage.java}
> Exception le = null;
> FSImageFile imageFile = null;
> for (int i = 0; i < imageFiles.size(); i++) {
> try {
> imageFile = imageFiles.get(i);
> loadFSImageFile(target, recovery, imageFile, startOpt);
> break;
> } catch (IllegalReservedPathException ie) {
> throw new IOException("Failed to load image from " + imageFile,
> ie);
> } catch (Exception e) {
> le = e;
> LOG.error("Failed to load image from " + imageFile, e);
> target.clear();
> imageFile = null;
> }
> }
> {code}
> Exception {{le}} is not used. It can be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-11262) Remove unused variable in FSImage.java
[
https://issues.apache.org/jira/browse/HDFS-11262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-11262:
Attachment: HDFS-11262_02.patch
Updated the patch,please review
> Remove unused variable in FSImage.java
> --
>
> Key: HDFS-11262
> URL: https://issues.apache.org/jira/browse/HDFS-11262
> Project: Hadoop HDFS
> Issue Type: Improvement
>Reporter: Akira Ajisaka
>Assignee: Jagadesh Kiran N
>Priority: Trivial
> Labels: newbie
> Attachments: HDFS-11262_00.patch, HDFS-11262_01.patch,
> HDFS-11262_02.patch
>
>
> {code:title=FSImage.java}
> Exception le = null;
> FSImageFile imageFile = null;
> for (int i = 0; i < imageFiles.size(); i++) {
> try {
> imageFile = imageFiles.get(i);
> loadFSImageFile(target, recovery, imageFile, startOpt);
> break;
> } catch (IllegalReservedPathException ie) {
> throw new IOException("Failed to load image from " + imageFile,
> ie);
> } catch (Exception e) {
> le = e;
> LOG.error("Failed to load image from " + imageFile, e);
> target.clear();
> imageFile = null;
> }
> }
> {code}
> Exception {{le}} is not used. It can be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-11262) Remove unused variable in FSImage.java
[
https://issues.apache.org/jira/browse/HDFS-11262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15761982#comment-15761982
]
Jagadesh Kiran N commented on HDFS-11262:
-
private int quotaInitThreads; this variable also not used,please check
> Remove unused variable in FSImage.java
> --
>
> Key: HDFS-11262
> URL: https://issues.apache.org/jira/browse/HDFS-11262
> Project: Hadoop HDFS
> Issue Type: Improvement
>Reporter: Akira Ajisaka
>Assignee: Jagadesh Kiran N
>Priority: Trivial
> Labels: newbie
> Attachments: HDFS-11262_00.patch, HDFS-11262_01.patch
>
>
> {code:title=FSImage.java}
> Exception le = null;
> FSImageFile imageFile = null;
> for (int i = 0; i < imageFiles.size(); i++) {
> try {
> imageFile = imageFiles.get(i);
> loadFSImageFile(target, recovery, imageFile, startOpt);
> break;
> } catch (IllegalReservedPathException ie) {
> throw new IOException("Failed to load image from " + imageFile,
> ie);
> } catch (Exception e) {
> le = e;
> LOG.error("Failed to load image from " + imageFile, e);
> target.clear();
> imageFile = null;
> }
> }
> {code}
> Exception {{le}} is not used. It can be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-11262) Remove unused variable in FSImage.java
[
https://issues.apache.org/jira/browse/HDFS-11262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-11262:
Attachment: HDFS-11262_01.patch
Thanks [~ajisakaa] for review, updated the patch please review
> Remove unused variable in FSImage.java
> --
>
> Key: HDFS-11262
> URL: https://issues.apache.org/jira/browse/HDFS-11262
> Project: Hadoop HDFS
> Issue Type: Improvement
>Reporter: Akira Ajisaka
>Assignee: Jagadesh Kiran N
>Priority: Trivial
> Labels: newbie
> Attachments: HDFS-11262_00.patch, HDFS-11262_01.patch
>
>
> {code:title=FSImage.java}
> Exception le = null;
> FSImageFile imageFile = null;
> for (int i = 0; i < imageFiles.size(); i++) {
> try {
> imageFile = imageFiles.get(i);
> loadFSImageFile(target, recovery, imageFile, startOpt);
> break;
> } catch (IllegalReservedPathException ie) {
> throw new IOException("Failed to load image from " + imageFile,
> ie);
> } catch (Exception e) {
> le = e;
> LOG.error("Failed to load image from " + imageFile, e);
> target.clear();
> imageFile = null;
> }
> }
> {code}
> Exception {{le}} is not used. It can be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-11262) Remove unused variable in FSImage.java
[
https://issues.apache.org/jira/browse/HDFS-11262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-11262:
Status: Patch Available (was: Open)
> Remove unused variable in FSImage.java
> --
>
> Key: HDFS-11262
> URL: https://issues.apache.org/jira/browse/HDFS-11262
> Project: Hadoop HDFS
> Issue Type: Improvement
>Reporter: Akira Ajisaka
>Assignee: Jagadesh Kiran N
>Priority: Trivial
> Labels: newbie
> Attachments: HDFS-11262_00.patch
>
>
> {code:title=FSImage.java}
> Exception le = null;
> FSImageFile imageFile = null;
> for (int i = 0; i < imageFiles.size(); i++) {
> try {
> imageFile = imageFiles.get(i);
> loadFSImageFile(target, recovery, imageFile, startOpt);
> break;
> } catch (IllegalReservedPathException ie) {
> throw new IOException("Failed to load image from " + imageFile,
> ie);
> } catch (Exception e) {
> le = e;
> LOG.error("Failed to load image from " + imageFile, e);
> target.clear();
> imageFile = null;
> }
> }
> {code}
> Exception {{le}} is not used. It can be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-11262) Remove unused variable in FSImage.java
[
https://issues.apache.org/jira/browse/HDFS-11262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-11262:
Attachment: HDFS-11262_00.patch
Attaching the patch please review
> Remove unused variable in FSImage.java
> --
>
> Key: HDFS-11262
> URL: https://issues.apache.org/jira/browse/HDFS-11262
> Project: Hadoop HDFS
> Issue Type: Improvement
>Reporter: Akira Ajisaka
>Assignee: Jagadesh Kiran N
>Priority: Trivial
> Labels: newbie
> Attachments: HDFS-11262_00.patch
>
>
> {code:title=FSImage.java}
> Exception le = null;
> FSImageFile imageFile = null;
> for (int i = 0; i < imageFiles.size(); i++) {
> try {
> imageFile = imageFiles.get(i);
> loadFSImageFile(target, recovery, imageFile, startOpt);
> break;
> } catch (IllegalReservedPathException ie) {
> throw new IOException("Failed to load image from " + imageFile,
> ie);
> } catch (Exception e) {
> le = e;
> LOG.error("Failed to load image from " + imageFile, e);
> target.clear();
> imageFile = null;
> }
> }
> {code}
> Exception {{le}} is not used. It can be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Assigned] (HDFS-11262) Remove unused variable in FSImage.java
[
https://issues.apache.org/jira/browse/HDFS-11262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N reassigned HDFS-11262:
---
Assignee: Jagadesh Kiran N
> Remove unused variable in FSImage.java
> --
>
> Key: HDFS-11262
> URL: https://issues.apache.org/jira/browse/HDFS-11262
> Project: Hadoop HDFS
> Issue Type: Improvement
>Reporter: Akira Ajisaka
>Assignee: Jagadesh Kiran N
>Priority: Trivial
> Labels: newbie
>
> {code:title=FSImage.java}
> Exception le = null;
> FSImageFile imageFile = null;
> for (int i = 0; i < imageFiles.size(); i++) {
> try {
> imageFile = imageFiles.get(i);
> loadFSImageFile(target, recovery, imageFile, startOpt);
> break;
> } catch (IllegalReservedPathException ie) {
> throw new IOException("Failed to load image from " + imageFile,
> ie);
> } catch (Exception e) {
> le = e;
> LOG.error("Failed to load image from " + imageFile, e);
> target.clear();
> imageFile = null;
> }
> }
> {code}
> Exception {{le}} is not used. It can be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-11249) Redundant toString() in DFSConfigKeys.java
[
https://issues.apache.org/jira/browse/HDFS-11249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-11249:
Status: Patch Available (was: Open)
> Redundant toString() in DFSConfigKeys.java
> --
>
> Key: HDFS-11249
> URL: https://issues.apache.org/jira/browse/HDFS-11249
> Project: Hadoop HDFS
> Issue Type: Improvement
>Reporter: Akira Ajisaka
>Assignee: Jagadesh Kiran N
>Priority: Trivial
> Labels: newbie
> Attachments: HDFS-11249_00.patch
>
>
> {code:title=DFSConfigKeys.java}
> public static final String DFS_WEBHDFS_AUTHENTICATION_FILTER_DEFAULT =
> "org.apache.hadoop.hdfs.web.AuthFilter".toString();
> {code}
> {{.toString()}} is not necessary and can be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-11249) Redundant toString() in DFSConfigKeys.java
[
https://issues.apache.org/jira/browse/HDFS-11249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-11249:
Attachment: HDFS-11249_00.patch
Attaching the patch please review
> Redundant toString() in DFSConfigKeys.java
> --
>
> Key: HDFS-11249
> URL: https://issues.apache.org/jira/browse/HDFS-11249
> Project: Hadoop HDFS
> Issue Type: Improvement
>Reporter: Akira Ajisaka
>Assignee: Jagadesh Kiran N
>Priority: Trivial
> Labels: newbie
> Attachments: HDFS-11249_00.patch
>
>
> {code:title=DFSConfigKeys.java}
> public static final String DFS_WEBHDFS_AUTHENTICATION_FILTER_DEFAULT =
> "org.apache.hadoop.hdfs.web.AuthFilter".toString();
> {code}
> {{.toString()}} is not necessary and can be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Assigned] (HDFS-11249) Redundant toString() in DFSConfigKeys.java
[
https://issues.apache.org/jira/browse/HDFS-11249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N reassigned HDFS-11249:
---
Assignee: Jagadesh Kiran N
> Redundant toString() in DFSConfigKeys.java
> --
>
> Key: HDFS-11249
> URL: https://issues.apache.org/jira/browse/HDFS-11249
> Project: Hadoop HDFS
> Issue Type: Improvement
>Reporter: Akira Ajisaka
>Assignee: Jagadesh Kiran N
>Priority: Trivial
> Labels: newbie
>
> {code:title=DFSConfigKeys.java}
> public static final String DFS_WEBHDFS_AUTHENTICATION_FILTER_DEFAULT =
> "org.apache.hadoop.hdfs.web.AuthFilter".toString();
> {code}
> {{.toString()}} is not necessary and can be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-9335) Webhdfs hangs when folder is used for Append
[
https://issues.apache.org/jira/browse/HDFS-9335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15737261#comment-15737261
]
Jagadesh Kiran N commented on HDFS-9335:
Analyzed this issue, this is not related to Hadoop, issue related to Curl
,[~ajisakaa] & [~surendrasingh] please provide your inputs for the same, so
that i can invalidate it
> Webhdfs hangs when folder is used for Append
>
>
> Key: HDFS-9335
> URL: https://issues.apache.org/jira/browse/HDFS-9335
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
>Priority: Critical
>
> a. Submit HTTP POST request using the URL in the Location header with the
> file data to be appended
> {code}
> curl -i -X POST -T /opt/folder/file
> "http://host-10-19-92-117:50075/webhdfs/v1/folder1/file1?op=APPEND=hacluster=1;
> {code}
> b. The client receives a response with zero content length
> c. Now execute the same for a folder (/opt/folder) rather than Local file
> {code}
> curl -i -X POST -T /opt/folder
> "http://host-10-19-92-117:50075/webhdfs/v1/folder1/file1?op=APPEND=hacluster=1;
> {code}
> d. No response will be given to the user and it will hang
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-11217) Annotate NameNode and DataNode MXBean interfaces as Private/Stable
[
https://issues.apache.org/jira/browse/HDFS-11217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15737171#comment-15737171
]
Jagadesh Kiran N commented on HDFS-11217:
-
Thanks [~andrew.wang] for commiting the same ,and Akira & Anu for discussion
> Annotate NameNode and DataNode MXBean interfaces as Private/Stable
> --
>
> Key: HDFS-11217
> URL: https://issues.apache.org/jira/browse/HDFS-11217
> Project: Hadoop HDFS
> Issue Type: Improvement
>Reporter: Akira Ajisaka
>Assignee: Jagadesh Kiran N
> Fix For: 2.8.0, 3.0.0-alpha2
>
> Attachments: HDFS-11217_00.patch
>
>
> NameNodeMXBean, NameNodeStatusMXBean, DataNodeMXBean are annotated
> {{@Public}} and {{@Stable}}, but some methods are being added. For example,
> DataNodeMXBean.getBPServiceActorInfo was added between branch-2.7.3 and
> branch-2.8. Adding methods to interfaces breaks the user classes which
> implement them, so we should make them {{@Private}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-11217) Make some JMX interfaces private
[
https://issues.apache.org/jira/browse/HDFS-11217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-11217:
Status: Patch Available (was: Open)
> Make some JMX interfaces private
>
>
> Key: HDFS-11217
> URL: https://issues.apache.org/jira/browse/HDFS-11217
> Project: Hadoop HDFS
> Issue Type: Improvement
>Reporter: Akira Ajisaka
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-11217_00.patch
>
>
> NameNodeMXBean, NameNodeStatusMXBean, DataNodeMXBean are annotated
> {{@Public}} and {{@Stable}}, but some methods are being added. For example,
> DataNodeMXBean.getBPServiceActorInfo was added between branch-2.7.3 and
> branch-2.8. Adding methods to interfaces breaks the user classes which
> implement them, so we should make them {{@Private}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-11217) Make some JMX interfaces private
[
https://issues.apache.org/jira/browse/HDFS-11217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-11217:
Attachment: HDFS-11217_00.patch
Attached the patch, please review
> Make some JMX interfaces private
>
>
> Key: HDFS-11217
> URL: https://issues.apache.org/jira/browse/HDFS-11217
> Project: Hadoop HDFS
> Issue Type: Improvement
>Reporter: Akira Ajisaka
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-11217_00.patch
>
>
> NameNodeMXBean, NameNodeStatusMXBean, DataNodeMXBean are annotated
> {{@Public}} and {{@Stable}}, but some methods are being added. For example,
> DataNodeMXBean.getBPServiceActorInfo was added between branch-2.7.3 and
> branch-2.8. Adding methods to interfaces breaks the user classes which
> implement them, so we should make them {{@Private}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-11211) Add a time unit to the DataNode client trace format
[
https://issues.apache.org/jira/browse/HDFS-11211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15728242#comment-15728242
]
Jagadesh Kiran N commented on HDFS-11211:
-
Thanks [~liuml07] for commiting the same , thanks [~ajisakaa] for reporting the
same & thanks [~linyiqun] for reviewing the same
> Add a time unit to the DataNode client trace format
>
>
> Key: HDFS-11211
> URL: https://issues.apache.org/jira/browse/HDFS-11211
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode
>Reporter: Akira Ajisaka
>Assignee: Jagadesh Kiran N
>Priority: Minor
> Labels: newbie, supportability
> Fix For: 2.9.0, 3.0.0-alpha2
>
> Attachments: HDFS-11211_00.patch
>
>
> {code:title=DataNode.java}
> public static final String DN_CLIENTTRACE_FORMAT =
> "src: %s" + // src IP
> ", dest: %s" + // dst IP
> ", bytes: %s" + // byte count
> ", op: %s" + // operation
> ", cliID: %s" + // DFSClient id
> ", offset: %s" + // offset
> ", srvID: %s" + // DatanodeRegistration
> ", blockid: %s" + // block id
> ", duration: %s"; // duration time
> {code}
> The time unit of the duration is nanosecond, but it is not documented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Assigned] (HDFS-11217) Make some JMX interfaces private
[
https://issues.apache.org/jira/browse/HDFS-11217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N reassigned HDFS-11217:
---
Assignee: Jagadesh Kiran N
> Make some JMX interfaces private
>
>
> Key: HDFS-11217
> URL: https://issues.apache.org/jira/browse/HDFS-11217
> Project: Hadoop HDFS
> Issue Type: Improvement
>Reporter: Akira Ajisaka
>Assignee: Jagadesh Kiran N
>
> NameNodeMXBean, NameNodeStatusMXBean, DataNodeMXBean are annotated
> {{@Public}} and {{@Stable}}, but some methods are being added. For example,
> DataNodeMXBean.getBPServiceActorInfo was added between branch-2.7.3 and
> branch-2.8. Adding methods to interfaces breaks the user classes which
> implement them, so we should make them {{@Private}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-11211) Add a time unit to the DataNode client trace format
[
https://issues.apache.org/jira/browse/HDFS-11211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-11211:
Attachment: HDFS-11211_00.patch
Attaching the patch [~ajisakaa] ,please review
> Add a time unit to the DataNode client trace format
>
>
> Key: HDFS-11211
> URL: https://issues.apache.org/jira/browse/HDFS-11211
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode
>Reporter: Akira Ajisaka
>Assignee: Jagadesh Kiran N
>Priority: Minor
> Labels: newbie, supportability
> Attachments: HDFS-11211_00.patch
>
>
> {code:title=DataNode.java}
> public static final String DN_CLIENTTRACE_FORMAT =
> "src: %s" + // src IP
> ", dest: %s" + // dst IP
> ", bytes: %s" + // byte count
> ", op: %s" + // operation
> ", cliID: %s" + // DFSClient id
> ", offset: %s" + // offset
> ", srvID: %s" + // DatanodeRegistration
> ", blockid: %s" + // block id
> ", duration: %s"; // duration time
> {code}
> The time unit of the duration is nanosecond, but it is not documented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-11211) Add a time unit to the DataNode client trace format
[
https://issues.apache.org/jira/browse/HDFS-11211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-11211:
Status: Patch Available (was: Open)
> Add a time unit to the DataNode client trace format
>
>
> Key: HDFS-11211
> URL: https://issues.apache.org/jira/browse/HDFS-11211
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode
>Reporter: Akira Ajisaka
>Assignee: Jagadesh Kiran N
>Priority: Minor
> Labels: newbie, supportability
> Attachments: HDFS-11211_00.patch
>
>
> {code:title=DataNode.java}
> public static final String DN_CLIENTTRACE_FORMAT =
> "src: %s" + // src IP
> ", dest: %s" + // dst IP
> ", bytes: %s" + // byte count
> ", op: %s" + // operation
> ", cliID: %s" + // DFSClient id
> ", offset: %s" + // offset
> ", srvID: %s" + // DatanodeRegistration
> ", blockid: %s" + // block id
> ", duration: %s"; // duration time
> {code}
> The time unit of the duration is nanosecond, but it is not documented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Assigned] (HDFS-11211) Add a time unit to the DataNode client trace format
[
https://issues.apache.org/jira/browse/HDFS-11211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N reassigned HDFS-11211:
---
Assignee: Jagadesh Kiran N
> Add a time unit to the DataNode client trace format
>
>
> Key: HDFS-11211
> URL: https://issues.apache.org/jira/browse/HDFS-11211
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode
>Reporter: Akira Ajisaka
>Assignee: Jagadesh Kiran N
>Priority: Minor
> Labels: newbie, supportability
> Attachments: HDFS-11211_00.patch
>
>
> {code:title=DataNode.java}
> public static final String DN_CLIENTTRACE_FORMAT =
> "src: %s" + // src IP
> ", dest: %s" + // dst IP
> ", bytes: %s" + // byte count
> ", op: %s" + // operation
> ", cliID: %s" + // DFSClient id
> ", offset: %s" + // offset
> ", srvID: %s" + // DatanodeRegistration
> ", blockid: %s" + // block id
> ", duration: %s"; // duration time
> {code}
> The time unit of the duration is nanosecond, but it is not documented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-9337) Validate required params for WebHDFS requests
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15654055#comment-15654055
]
Jagadesh Kiran N commented on HDFS-9337:
Thanks [~vinayrpet] for commiting the patch
> Validate required params for WebHDFS requests
> -
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Fix For: 3.0.0-alpha2
>
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch,
> HDFS-9337_05.patch, HDFS-9337_06.patch, HDFS-9337_07.patch,
> HDFS-9337_08.patch, HDFS-9337_09.patch, HDFS-9337_10.patch,
> HDFS-9337_11.patch, HDFS-9337_12.patch, HDFS-9337_13.patch,
> HDFS-9337_14.patch, HDFS-9337_15.patch, HDFS-9337_16.patch,
> HDFS-9337_17.patch, HDFS-9337_18.patch, HDFS-9337_19.patch,
> HDFS-9337_20.patch, HDFS-9337_21.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15648302#comment-15648302
]
Jagadesh Kiran N commented on HDFS-9337:
The test failures and check style error is not related to patch, [~vinayrpet]
,Please review,
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch,
> HDFS-9337_05.patch, HDFS-9337_06.patch, HDFS-9337_07.patch,
> HDFS-9337_08.patch, HDFS-9337_09.patch, HDFS-9337_10.patch,
> HDFS-9337_11.patch, HDFS-9337_12.patch, HDFS-9337_13.patch,
> HDFS-9337_14.patch, HDFS-9337_15.patch, HDFS-9337_16.patch,
> HDFS-9337_17.patch, HDFS-9337_18.patch, HDFS-9337_19.patch,
> HDFS-9337_20.patch, HDFS-9337_21.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_21.patch
Removed all delegation token tests,please review
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch,
> HDFS-9337_05.patch, HDFS-9337_06.patch, HDFS-9337_07.patch,
> HDFS-9337_08.patch, HDFS-9337_09.patch, HDFS-9337_10.patch,
> HDFS-9337_11.patch, HDFS-9337_12.patch, HDFS-9337_13.patch,
> HDFS-9337_14.patch, HDFS-9337_15.patch, HDFS-9337_16.patch,
> HDFS-9337_17.patch, HDFS-9337_18.patch, HDFS-9337_19.patch,
> HDFS-9337_20.patch, HDFS-9337_21.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_20.patch
The check style and test failures are fixed, please review
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch,
> HDFS-9337_05.patch, HDFS-9337_06.patch, HDFS-9337_07.patch,
> HDFS-9337_08.patch, HDFS-9337_09.patch, HDFS-9337_10.patch,
> HDFS-9337_11.patch, HDFS-9337_12.patch, HDFS-9337_13.patch,
> HDFS-9337_14.patch, HDFS-9337_15.patch, HDFS-9337_16.patch,
> HDFS-9337_17.patch, HDFS-9337_18.patch, HDFS-9337_19.patch, HDFS-9337_20.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_19.patch
Thanks [~vinayrpet] for review,Updated the patch ,please review
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch,
> HDFS-9337_05.patch, HDFS-9337_06.patch, HDFS-9337_07.patch,
> HDFS-9337_08.patch, HDFS-9337_09.patch, HDFS-9337_10.patch,
> HDFS-9337_11.patch, HDFS-9337_12.patch, HDFS-9337_13.patch,
> HDFS-9337_14.patch, HDFS-9337_15.patch, HDFS-9337_16.patch,
> HDFS-9337_17.patch, HDFS-9337_18.patch, HDFS-9337_19.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_18.patch
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch,
> HDFS-9337_05.patch, HDFS-9337_06.patch, HDFS-9337_07.patch,
> HDFS-9337_08.patch, HDFS-9337_09.patch, HDFS-9337_10.patch,
> HDFS-9337_11.patch, HDFS-9337_12.patch, HDFS-9337_13.patch,
> HDFS-9337_14.patch, HDFS-9337_15.patch, HDFS-9337_16.patch,
> HDFS-9337_17.patch, HDFS-9337_18.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_17.patch
Attaching patch fixing whitespaces and cc ,pls review
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch,
> HDFS-9337_05.patch, HDFS-9337_06.patch, HDFS-9337_07.patch,
> HDFS-9337_08.patch, HDFS-9337_09.patch, HDFS-9337_10.patch,
> HDFS-9337_11.patch, HDFS-9337_12.patch, HDFS-9337_13.patch,
> HDFS-9337_14.patch, HDFS-9337_15.patch, HDFS-9337_16.patch, HDFS-9337_17.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_16.patch
Fixed CC and Whitespaces , Test failures are not related to patch, please review
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch,
> HDFS-9337_05.patch, HDFS-9337_06.patch, HDFS-9337_07.patch,
> HDFS-9337_08.patch, HDFS-9337_09.patch, HDFS-9337_10.patch,
> HDFS-9337_11.patch, HDFS-9337_12.patch, HDFS-9337_13.patch,
> HDFS-9337_14.patch, HDFS-9337_15.patch, HDFS-9337_16.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_15.patch
Fixed the test failures,please review
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch,
> HDFS-9337_05.patch, HDFS-9337_06.patch, HDFS-9337_07.patch,
> HDFS-9337_08.patch, HDFS-9337_09.patch, HDFS-9337_10.patch,
> HDFS-9337_11.patch, HDFS-9337_12.patch, HDFS-9337_13.patch,
> HDFS-9337_14.patch, HDFS-9337_15.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_14.patch
Thanks [~vinayrpet] for review, Had updated the patch with covering all mandory
params for different ops ,Please review
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch,
> HDFS-9337_05.patch, HDFS-9337_06.patch, HDFS-9337_07.patch,
> HDFS-9337_08.patch, HDFS-9337_09.patch, HDFS-9337_10.patch,
> HDFS-9337_11.patch, HDFS-9337_12.patch, HDFS-9337_13.patch, HDFS-9337_14.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15635245#comment-15635245
]
Jagadesh Kiran N commented on HDFS-9337:
Test Failures are not releated to Patch , [~vinayrpet] please review
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch,
> HDFS-9337_05.patch, HDFS-9337_06.patch, HDFS-9337_07.patch,
> HDFS-9337_08.patch, HDFS-9337_09.patch, HDFS-9337_10.patch,
> HDFS-9337_11.patch, HDFS-9337_12.patch, HDFS-9337_13.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: (was: HDFS-9337_13)
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch,
> HDFS-9337_05.patch, HDFS-9337_06.patch, HDFS-9337_07.patch,
> HDFS-9337_08.patch, HDFS-9337_09.patch, HDFS-9337_10.patch,
> HDFS-9337_11.patch, HDFS-9337_12.patch, HDFS-9337_13.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_13.patch
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch,
> HDFS-9337_05.patch, HDFS-9337_06.patch, HDFS-9337_07.patch,
> HDFS-9337_08.patch, HDFS-9337_09.patch, HDFS-9337_10.patch,
> HDFS-9337_11.patch, HDFS-9337_12.patch, HDFS-9337_13.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_13
Updated the patch,please review
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch,
> HDFS-9337_05.patch, HDFS-9337_06.patch, HDFS-9337_07.patch,
> HDFS-9337_08.patch, HDFS-9337_09.patch, HDFS-9337_10.patch,
> HDFS-9337_11.patch, HDFS-9337_12.patch, HDFS-9337_13
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_12.patch
Updated patch fixing UT Failures, Checkstyle is not related to patch uploaded
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch,
> HDFS-9337_05.patch, HDFS-9337_06.patch, HDFS-9337_07.patch,
> HDFS-9337_08.patch, HDFS-9337_09.patch, HDFS-9337_10.patch,
> HDFS-9337_11.patch, HDFS-9337_12.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_11.patch
Updating the patch pls review
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch,
> HDFS-9337_05.patch, HDFS-9337_06.patch, HDFS-9337_07.patch,
> HDFS-9337_08.patch, HDFS-9337_09.patch, HDFS-9337_10.patch, HDFS-9337_11.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_10.patch
Attaching patch fixing ut and check style errors
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch,
> HDFS-9337_05.patch, HDFS-9337_06.patch, HDFS-9337_07.patch,
> HDFS-9337_08.patch, HDFS-9337_09.patch, HDFS-9337_10.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_09.patch
Fixed test case failures , [~vinayrpet] please review
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch,
> HDFS-9337_05.patch, HDFS-9337_06.patch, HDFS-9337_07.patch,
> HDFS-9337_08.patch, HDFS-9337_09.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_08.patch
Attached patch for Checkstyle errors, analyzing the failures will update patch
tommarow once test errors are fixed
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch,
> HDFS-9337_05.patch, HDFS-9337_06.patch, HDFS-9337_07.patch, HDFS-9337_08.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_07.patch
Updated the patch with UT,Please review
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch,
> HDFS-9337_05.patch, HDFS-9337_06.patch, HDFS-9337_07.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-9061) hdfs groups should be exposed via WebHDFS
[ https://issues.apache.org/jira/browse/HDFS-9061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15585645#comment-15585645 ] Jagadesh Kiran N commented on HDFS-9061: As discussed [~brahma] offline ,assigning to me > hdfs groups should be exposed via WebHDFS > - > > Key: HDFS-9061 > URL: https://issues.apache.org/jira/browse/HDFS-9061 > Project: Hadoop HDFS > Issue Type: New Feature > Components: webhdfs >Affects Versions: 3.0.0-alpha1 >Reporter: Allen Wittenauer >Assignee: Brahma Reddy Battula > > It would be extremely useful from a REST perspective to expose which groups > the NN says the user belongs to. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Assigned] (HDFS-9061) hdfs groups should be exposed via WebHDFS
[ https://issues.apache.org/jira/browse/HDFS-9061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadesh Kiran N reassigned HDFS-9061: -- Assignee: Jagadesh Kiran N (was: Brahma Reddy Battula) > hdfs groups should be exposed via WebHDFS > - > > Key: HDFS-9061 > URL: https://issues.apache.org/jira/browse/HDFS-9061 > Project: Hadoop HDFS > Issue Type: New Feature > Components: webhdfs >Affects Versions: 3.0.0-alpha1 >Reporter: Allen Wittenauer >Assignee: Jagadesh Kiran N > > It would be extremely useful from a REST perspective to expose which groups > the NN says the user belongs to. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (HDFS-9059) Expose lssnapshottabledir via WebHDFS
[ https://issues.apache.org/jira/browse/HDFS-9059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15585639#comment-15585639 ] Jagadesh Kiran N edited comment on HDFS-9059 at 10/18/16 2:48 PM: -- As discussed [~brahma] offline ,assigning to me was (Author: jagadesh.kiran): As discussed [~brahma] ,internally assigning to me > Expose lssnapshottabledir via WebHDFS > - > > Key: HDFS-9059 > URL: https://issues.apache.org/jira/browse/HDFS-9059 > Project: Hadoop HDFS > Issue Type: New Feature > Components: webhdfs >Affects Versions: 3.0.0-alpha1 >Reporter: Allen Wittenauer >Assignee: Jagadesh Kiran N > > lssnapshottabledir should be exposed via WebHDFS. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-9059) Expose lssnapshottabledir via WebHDFS
[ https://issues.apache.org/jira/browse/HDFS-9059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15585639#comment-15585639 ] Jagadesh Kiran N commented on HDFS-9059: As discussed [~brahma] ,internally assigning to me > Expose lssnapshottabledir via WebHDFS > - > > Key: HDFS-9059 > URL: https://issues.apache.org/jira/browse/HDFS-9059 > Project: Hadoop HDFS > Issue Type: New Feature > Components: webhdfs >Affects Versions: 3.0.0-alpha1 >Reporter: Allen Wittenauer >Assignee: Jagadesh Kiran N > > lssnapshottabledir should be exposed via WebHDFS. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Assigned] (HDFS-9059) Expose lssnapshottabledir via WebHDFS
[ https://issues.apache.org/jira/browse/HDFS-9059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadesh Kiran N reassigned HDFS-9059: -- Assignee: Jagadesh Kiran N (was: Brahma Reddy Battula) > Expose lssnapshottabledir via WebHDFS > - > > Key: HDFS-9059 > URL: https://issues.apache.org/jira/browse/HDFS-9059 > Project: Hadoop HDFS > Issue Type: New Feature > Components: webhdfs >Affects Versions: 3.0.0-alpha1 >Reporter: Allen Wittenauer >Assignee: Jagadesh Kiran N > > lssnapshottabledir should be exposed via WebHDFS. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_06.patch
Updating with check style fix,pls review
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch,
> HDFS-9337_05.patch, HDFS-9337_06.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_05.patch
Attaching patch after updating check style and white spaces
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch, HDFS-9337_05.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-10936) allow & disallow snapshot command should not print exception trace when folder not found
[
https://issues.apache.org/jira/browse/HDFS-10936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551087#comment-15551087
]
Jagadesh Kiran N commented on HDFS-10936:
-
Thanks [~brahmareddy] for reviewing the same, i will add unit test for the
same.,
> allow & disallow snapshot command should not print exception trace when
> folder not found
>
>
> Key: HDFS-10936
> URL: https://issues.apache.org/jira/browse/HDFS-10936
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-10936_00.patch, HDFS-10936_01.patch,
> HDFS-10936_02.patch
>
>
> Allow snapshot for a folder which is not present
> {code}./hdfs dfsadmin -allowsnapshot /kiran1 {code}
> the following exception occurs
> {code}
> allowsnapshot: Directory does not exist: /kiran1
> at
> org.apache.hadoop.hdfs.server.namenode.INodeDirectory.valueOf(INodeDirectory.java:61)
> at
> org.apache.hadoop.hdfs.server.namenode.snapshot.SnapshotManager.setSnapshottable(SnapshotManager.java:113)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirSnapshotOp.allowSnapshot(FSDirSnapshotOp.java:60)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.allowSnapshot(FSNamesystem.java:7406)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.allowSnapshot(NameNodeRpcServer.java:1766)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.allowSnapshot(ClientNamenodeProtocolServerSideTranslatorPB.java:1131)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:973)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2143)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2139)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1726)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2137)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-10869) Remove the unused method InodeId#checkId()
[
https://issues.apache.org/jira/browse/HDFS-10869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551050#comment-15551050
]
Jagadesh Kiran N commented on HDFS-10869:
-
Thanks [~brahmareddy] for commiting the same .,
> Remove the unused method InodeId#checkId()
> ---
>
> Key: HDFS-10869
> URL: https://issues.apache.org/jira/browse/HDFS-10869
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Fix For: 2.8.0, 2.9.0, 3.0.0-alpha2
>
> Attachments: HDFS-10869.patch, HDFS-10869_01.patch
>
>
> The following method in InodeId.java is not used anywhere , We can remove the
> code
> {code}
> public static void checkId(long requestId, INode inode)
> throws FileNotFoundException {
> if (requestId != HdfsConstants.GRANDFATHER_INODE_ID && requestId !=
> inode.getId()) {
> throw new FileNotFoundException(
> "ID mismatch. Request id and saved id: " + requestId + " , "
> + inode.getId() + " for file " + inode.getFullPathName());
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-10944) Correct the javadoc of dfsadmin#disallowSnapshot
[
https://issues.apache.org/jira/browse/HDFS-10944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551049#comment-15551049
]
Jagadesh Kiran N commented on HDFS-10944:
-
Thanks [~brahmareddy] for commiting the same .,
> Correct the javadoc of dfsadmin#disallowSnapshot
>
>
> Key: HDFS-10944
> URL: https://issues.apache.org/jira/browse/HDFS-10944
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: documentation
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
>Priority: Minor
> Fix For: 2.8.0, 3.0.0-alpha2
>
> Attachments: HDFS-10944_00.patch
>
>
> in DFSadmin.java ,the javadoc for Disallow snapshot is not proper
> {code}
> /**
>* Allow snapshot on a directory.
>* Usage: hdfs dfsadmin -disallowSnapshot snapshotDir
>* @param argv List of of command line parameters.
>* @exception IOException
>*/
> {code}
> Change the Allow Snapshot to Disallow Snapshot
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-10936) allow & disallow snapshot command should not print exception trace when folder not found
[
https://issues.apache.org/jira/browse/HDFS-10936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-10936:
Attachment: HDFS-10936_02.patch
Updated the patch correcting checkstyle errors. Please review
> allow & disallow snapshot command should not print exception trace when
> folder not found
>
>
> Key: HDFS-10936
> URL: https://issues.apache.org/jira/browse/HDFS-10936
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-10936_00.patch, HDFS-10936_01.patch,
> HDFS-10936_02.patch
>
>
> Allow snapshot for a folder which is not present
> {code}./hdfs dfsadmin -allowsnapshot /kiran1 {code}
> the following exception occurs
> {code}
> allowsnapshot: Directory does not exist: /kiran1
> at
> org.apache.hadoop.hdfs.server.namenode.INodeDirectory.valueOf(INodeDirectory.java:61)
> at
> org.apache.hadoop.hdfs.server.namenode.snapshot.SnapshotManager.setSnapshottable(SnapshotManager.java:113)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirSnapshotOp.allowSnapshot(FSDirSnapshotOp.java:60)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.allowSnapshot(FSNamesystem.java:7406)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.allowSnapshot(NameNodeRpcServer.java:1766)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.allowSnapshot(ClientNamenodeProtocolServerSideTranslatorPB.java:1131)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:973)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2143)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2139)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1726)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2137)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-10936) allow & disallow snapshot command should not print exception trace when folder not found
[
https://issues.apache.org/jira/browse/HDFS-10936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-10936:
Summary: allow & disallow snapshot command should not print exception trace
when folder not found (was: allow snapshot command should not print exception
trace when folder not found)
> allow & disallow snapshot command should not print exception trace when
> folder not found
>
>
> Key: HDFS-10936
> URL: https://issues.apache.org/jira/browse/HDFS-10936
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-10936_00.patch, HDFS-10936_01.patch
>
>
> Allow snapshot for a folder which is not present
> {code}./hdfs dfsadmin -allowsnapshot /kiran1 {code}
> the following exception occurs
> {code}
> allowsnapshot: Directory does not exist: /kiran1
> at
> org.apache.hadoop.hdfs.server.namenode.INodeDirectory.valueOf(INodeDirectory.java:61)
> at
> org.apache.hadoop.hdfs.server.namenode.snapshot.SnapshotManager.setSnapshottable(SnapshotManager.java:113)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirSnapshotOp.allowSnapshot(FSDirSnapshotOp.java:60)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.allowSnapshot(FSNamesystem.java:7406)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.allowSnapshot(NameNodeRpcServer.java:1766)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.allowSnapshot(ClientNamenodeProtocolServerSideTranslatorPB.java:1131)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:973)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2143)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2139)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1726)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2137)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-10936) allow snapshot command should not print exception trace when folder not found
[
https://issues.apache.org/jira/browse/HDFS-10936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-10936:
Attachment: HDFS-10936_01.patch
Updated with Checkstyle error, fixed for Disallow snapshot also,please review
> allow snapshot command should not print exception trace when folder not found
> -
>
> Key: HDFS-10936
> URL: https://issues.apache.org/jira/browse/HDFS-10936
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-10936_00.patch, HDFS-10936_01.patch
>
>
> Allow snapshot for a folder which is not present
> {code}./hdfs dfsadmin -allowsnapshot /kiran1 {code}
> the following exception occurs
> {code}
> allowsnapshot: Directory does not exist: /kiran1
> at
> org.apache.hadoop.hdfs.server.namenode.INodeDirectory.valueOf(INodeDirectory.java:61)
> at
> org.apache.hadoop.hdfs.server.namenode.snapshot.SnapshotManager.setSnapshottable(SnapshotManager.java:113)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirSnapshotOp.allowSnapshot(FSDirSnapshotOp.java:60)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.allowSnapshot(FSNamesystem.java:7406)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.allowSnapshot(NameNodeRpcServer.java:1766)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.allowSnapshot(ClientNamenodeProtocolServerSideTranslatorPB.java:1131)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:973)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2143)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2139)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1726)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2137)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-8972) EINVAL Invalid argument when RAM_DISK usage 90%+
[
https://issues.apache.org/jira/browse/HDFS-8972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15548840#comment-15548840
]
Jagadesh Kiran N commented on HDFS-8972:
Not able to reproduce the same , please suggest how to reproduce
> EINVAL Invalid argument when RAM_DISK usage 90%+
>
>
> Key: HDFS-8972
> URL: https://issues.apache.org/jira/browse/HDFS-8972
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Xu Chen
>Assignee: Jagadesh Kiran N
>Priority: Critical
>
> the directory which uses LAZY_PERSIST policy , so use "df" command look up
> tmpfs is usage >=90% , run spark,hive or mapreduce application , Datanode
> come out following exception
> {code}
> 2015-08-26 17:37:34,123 WARN org.apache.hadoop.io.ReadaheadPool: Failed
> readahead on null
> EINVAL: Invalid argument
> at org.apache.hadoop.io.nativeio.NativeIO$POSIX.posix_fadvise(Native
> Method)
> at
> org.apache.hadoop.io.nativeio.NativeIO$POSIX.posixFadviseIfPossible(NativeIO.java:267)
> at
> org.apache.hadoop.io.nativeio.NativeIO$POSIX$CacheManipulator.posixFadviseIfPossible(NativeIO.java:146)
> at
> org.apache.hadoop.io.ReadaheadPool$ReadaheadRequestImpl.run(ReadaheadPool.java:206)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> And the application is slowly than without exception 25%
> Regards
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-10936) allow snapshot command should not print exception trace when folder not found
[
https://issues.apache.org/jira/browse/HDFS-10936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-10936:
Status: Patch Available (was: Open)
> allow snapshot command should not print exception trace when folder not found
> -
>
> Key: HDFS-10936
> URL: https://issues.apache.org/jira/browse/HDFS-10936
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-10936_00.patch
>
>
> Allow snapshot for a folder which is not present
> {code}./hdfs dfsadmin -allowsnapshot /kiran1 {code}
> the following exception occurs
> {code}
> allowsnapshot: Directory does not exist: /kiran1
> at
> org.apache.hadoop.hdfs.server.namenode.INodeDirectory.valueOf(INodeDirectory.java:61)
> at
> org.apache.hadoop.hdfs.server.namenode.snapshot.SnapshotManager.setSnapshottable(SnapshotManager.java:113)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirSnapshotOp.allowSnapshot(FSDirSnapshotOp.java:60)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.allowSnapshot(FSNamesystem.java:7406)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.allowSnapshot(NameNodeRpcServer.java:1766)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.allowSnapshot(ClientNamenodeProtocolServerSideTranslatorPB.java:1131)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:973)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2143)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2139)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1726)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2137)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-10936) allow snapshot command should not print exception trace when folder not found
[
https://issues.apache.org/jira/browse/HDFS-10936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-10936:
Attachment: HDFS-10936_00.patch
Uploading the patch please review
> allow snapshot command should not print exception trace when folder not found
> -
>
> Key: HDFS-10936
> URL: https://issues.apache.org/jira/browse/HDFS-10936
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-10936_00.patch
>
>
> Allow snapshot for a folder which is not present
> {code}./hdfs dfsadmin -allowsnapshot /kiran1 {code}
> the following exception occurs
> {code}
> allowsnapshot: Directory does not exist: /kiran1
> at
> org.apache.hadoop.hdfs.server.namenode.INodeDirectory.valueOf(INodeDirectory.java:61)
> at
> org.apache.hadoop.hdfs.server.namenode.snapshot.SnapshotManager.setSnapshottable(SnapshotManager.java:113)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirSnapshotOp.allowSnapshot(FSDirSnapshotOp.java:60)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.allowSnapshot(FSNamesystem.java:7406)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.allowSnapshot(NameNodeRpcServer.java:1766)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.allowSnapshot(ClientNamenodeProtocolServerSideTranslatorPB.java:1131)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:973)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2143)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2139)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1726)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2137)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-10944) Change javadoc "Allow Snapshot " to " DisAllow Snapshot" for disallowSnapshot function
[
https://issues.apache.org/jira/browse/HDFS-10944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15543182#comment-15543182
]
Jagadesh Kiran N commented on HDFS-10944:
-
Failures are not related to Patch, please review
> Change javadoc "Allow Snapshot " to " DisAllow Snapshot" for disallowSnapshot
> function
> ---
>
> Key: HDFS-10944
> URL: https://issues.apache.org/jira/browse/HDFS-10944
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
>Priority: Minor
> Attachments: HDFS-10944_00.patch
>
>
> in DFSadmin.java ,the javadoc for Disallow snapshot is not proper
> {code}
> /**
>* Allow snapshot on a directory.
>* Usage: hdfs dfsadmin -disallowSnapshot snapshotDir
>* @param argv List of of command line parameters.
>* @exception IOException
>*/
> {code}
> Change the Allow Snapshot to Disallow Snapshot
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (HDFS-10944) Change javadoc "Allow Snapshot " to " DisAllow Snapshot" for disallowSnapshot function
[
https://issues.apache.org/jira/browse/HDFS-10944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15543182#comment-15543182
]
Jagadesh Kiran N edited comment on HDFS-10944 at 10/3/16 7:25 PM:
--
Unit Test Failures are not related to Patch, please review
was (Author: jagadesh.kiran):
Failures are not related to Patch, please review
> Change javadoc "Allow Snapshot " to " DisAllow Snapshot" for disallowSnapshot
> function
> ---
>
> Key: HDFS-10944
> URL: https://issues.apache.org/jira/browse/HDFS-10944
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
>Priority: Minor
> Attachments: HDFS-10944_00.patch
>
>
> in DFSadmin.java ,the javadoc for Disallow snapshot is not proper
> {code}
> /**
>* Allow snapshot on a directory.
>* Usage: hdfs dfsadmin -disallowSnapshot snapshotDir
>* @param argv List of of command line parameters.
>* @exception IOException
>*/
> {code}
> Change the Allow Snapshot to Disallow Snapshot
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_04.patch
Attaching the patch please review,.
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch, HDFS-9337_04.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542444#comment-15542444
]
Jagadesh Kiran N commented on HDFS-9337:
Analyzed all the commands ,please find the areas where null point execptions
are present
{code}
a. RENAMESNAPSHOT
b. REMOVEXATTR
c. CANCELDELEGATIONTOKEN
d. RENEWDELEGATIONTOKEN
e. DELETESNAPSHOT
f. TRUNCATE
g. SETXATTR
h. GETXATTR
{code}
I will update the patch accordingly
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-10944) Change javadoc "Allow Snapshot " to " DisAllow Snapshot" for disallowSnapshot function
[
https://issues.apache.org/jira/browse/HDFS-10944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-10944:
Status: Patch Available (was: Open)
> Change javadoc "Allow Snapshot " to " DisAllow Snapshot" for disallowSnapshot
> function
> ---
>
> Key: HDFS-10944
> URL: https://issues.apache.org/jira/browse/HDFS-10944
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
>Priority: Minor
> Attachments: HDFS-10944_00.patch
>
>
> in DFSadmin.java ,the javadoc for Disallow snapshot is not proper
> {code}
> /**
>* Allow snapshot on a directory.
>* Usage: hdfs dfsadmin -disallowSnapshot snapshotDir
>* @param argv List of of command line parameters.
>* @exception IOException
>*/
> {code}
> Change the Allow Snapshot to Disallow Snapshot
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-10944) Change javadoc "Allow Snapshot " to " DisAllow Snapshot" for disallowSnapshot function
[
https://issues.apache.org/jira/browse/HDFS-10944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-10944:
Attachment: HDFS-10944_00.patch
Uploading the patch after modification
> Change javadoc "Allow Snapshot " to " DisAllow Snapshot" for disallowSnapshot
> function
> ---
>
> Key: HDFS-10944
> URL: https://issues.apache.org/jira/browse/HDFS-10944
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
>Priority: Minor
> Attachments: HDFS-10944_00.patch
>
>
> in DFSadmin.java ,the javadoc for Disallow snapshot is not proper
> {code}
> /**
>* Allow snapshot on a directory.
>* Usage: hdfs dfsadmin -disallowSnapshot snapshotDir
>* @param argv List of of command line parameters.
>* @exception IOException
>*/
> {code}
> Change the Allow Snapshot to Disallow Snapshot
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Created] (HDFS-10944) Change javadoc "Allow Snapshot " to " DisAllow Snapshot" for disallowSnapshot function
Jagadesh Kiran N created HDFS-10944:
---
Summary: Change javadoc "Allow Snapshot " to " DisAllow Snapshot"
for disallowSnapshot function
Key: HDFS-10944
URL: https://issues.apache.org/jira/browse/HDFS-10944
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Jagadesh Kiran N
Assignee: Jagadesh Kiran N
Priority: Minor
in DFSadmin.java ,the javadoc for Disallow snapshot is not proper
{code}
/**
* Allow snapshot on a directory.
* Usage: hdfs dfsadmin -disallowSnapshot snapshotDir
* @param argv List of of command line parameters.
* @exception IOException
*/
{code}
Change the Allow Snapshot to Disallow Snapshot
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-10936) allow snapshot command should not print exception trace when folder not found
[
https://issues.apache.org/jira/browse/HDFS-10936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-10936:
Description:
Allow snapshot for a folder which is not present
{code}./hdfs dfsadmin -allowsnapshot /kiran1 {code}
the following exception occurs
{code}
allowsnapshot: Directory does not exist: /kiran1
at
org.apache.hadoop.hdfs.server.namenode.INodeDirectory.valueOf(INodeDirectory.java:61)
at
org.apache.hadoop.hdfs.server.namenode.snapshot.SnapshotManager.setSnapshottable(SnapshotManager.java:113)
at
org.apache.hadoop.hdfs.server.namenode.FSDirSnapshotOp.allowSnapshot(FSDirSnapshotOp.java:60)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.allowSnapshot(FSNamesystem.java:7406)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.allowSnapshot(NameNodeRpcServer.java:1766)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.allowSnapshot(ClientNamenodeProtocolServerSideTranslatorPB.java:1131)
at
org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:973)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2143)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2139)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1726)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2137)
{code}
was:
Allow snapshot for a folder which is not present
{code }./hdfs dfsadmin -allowsnapshot /kiran1 {code }
the following exception occurs
{code }
allowsnapshot: Directory does not exist: /kiran1
at
org.apache.hadoop.hdfs.server.namenode.INodeDirectory.valueOf(INodeDirectory.java:61)
at
org.apache.hadoop.hdfs.server.namenode.snapshot.SnapshotManager.setSnapshottable(SnapshotManager.java:113)
at
org.apache.hadoop.hdfs.server.namenode.FSDirSnapshotOp.allowSnapshot(FSDirSnapshotOp.java:60)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.allowSnapshot(FSNamesystem.java:7406)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.allowSnapshot(NameNodeRpcServer.java:1766)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.allowSnapshot(ClientNamenodeProtocolServerSideTranslatorPB.java:1131)
at
org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:973)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2143)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2139)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1726)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2137)
{code }
> allow snapshot command should not print exception trace when folder not found
> -
>
> Key: HDFS-10936
> URL: https://issues.apache.org/jira/browse/HDFS-10936
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
>
> Allow snapshot for a folder which is not present
> {code}./hdfs dfsadmin -allowsnapshot /kiran1 {code}
> the following exception occurs
> {code}
> allowsnapshot: Directory does not exist: /kiran1
> at
> org.apache.hadoop.hdfs.server.namenode.INodeDirectory.valueOf(INodeDirectory.java:61)
> at
> org.apache.hadoop.hdfs.server.namenode.snapshot.SnapshotManager.setSnapshottable(SnapshotManager.java:113)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirSnapshotOp.allowSnapshot(FSDirSnapshotOp.java:60)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.allowSnapshot(FSNamesystem.java:7406)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.allowSnapshot(NameNodeRpcServer.java:1766)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.allowSnapshot(ClientNamenodeProtocolServerSideTranslatorPB.java:1131)
> at
>
[jira] [Created] (HDFS-10936) allow snapshot command should not print exception trace when folder not found
Jagadesh Kiran N created HDFS-10936:
---
Summary: allow snapshot command should not print exception trace
when folder not found
Key: HDFS-10936
URL: https://issues.apache.org/jira/browse/HDFS-10936
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Jagadesh Kiran N
Assignee: Jagadesh Kiran N
Allow snapshot for a folder which is not present
{code }./hdfs dfsadmin -allowsnapshot /kiran1 {code }
the following exception occurs
{code }
allowsnapshot: Directory does not exist: /kiran1
at
org.apache.hadoop.hdfs.server.namenode.INodeDirectory.valueOf(INodeDirectory.java:61)
at
org.apache.hadoop.hdfs.server.namenode.snapshot.SnapshotManager.setSnapshottable(SnapshotManager.java:113)
at
org.apache.hadoop.hdfs.server.namenode.FSDirSnapshotOp.allowSnapshot(FSDirSnapshotOp.java:60)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.allowSnapshot(FSNamesystem.java:7406)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.allowSnapshot(NameNodeRpcServer.java:1766)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.allowSnapshot(ClientNamenodeProtocolServerSideTranslatorPB.java:1131)
at
org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:973)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2143)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2139)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1726)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2137)
{code }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Assigned] (HDFS-9675) BlockSender incorrectly output error logs with non-English locale
[
https://issues.apache.org/jira/browse/HDFS-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N reassigned HDFS-9675:
--
Assignee: Jagadesh Kiran N
> BlockSender incorrectly output error logs with non-English locale
> -
>
> Key: HDFS-9675
> URL: https://issues.apache.org/jira/browse/HDFS-9675
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode
>Reporter: Akira Ajisaka
>Assignee: Jagadesh Kiran N
> Labels: i18n
>
> If the locale is non-English, the following code does not work.
> {code:title=BlockSender.java}
> String ioem = e.getMessage();
> if (!ioem.startsWith("Broken pipe") && !ioem.startsWith("Connection
> reset")) {
> LOG.error("BlockSender.sendChunks() exception: ", e);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-9509) Add new metrics for measuring datanode storage statistics
[
https://issues.apache.org/jira/browse/HDFS-9509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529840#comment-15529840
]
Jagadesh Kiran N commented on HDFS-9509:
[~szetszwo] ,Currently along with
{code} sendDataPacketBlockedOnNetworkNanosQuantiles {code}&
{code}sendDataPacketTransferNanosQuantiles {code},
already some more metrics are there in trunk for example
{code}
ramDiskBlocksEvictionWindowMsQuantiles
ramDiskBlocksLazyPersistWindowMsQuantiles,
packetAckRoundTripTimeNanosQuantiles,
flushNanosQuantiles,
fsyncNanosQuantiles
{code}
are there, Can you please suggest if any other metrics is required ?
> Add new metrics for measuring datanode storage statistics
> -
>
> Key: HDFS-9509
> URL: https://issues.apache.org/jira/browse/HDFS-9509
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode
>Reporter: Tsz Wo Nicholas Sze
>
> We already have sendDataPacketBlockedOnNetworkNanos and
> sendDataPacketTransferNanos for the transferTo case. We should add more
> metrics for the other cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-9060) expose snapshotdiff via WebHDFS
[ https://issues.apache.org/jira/browse/HDFS-9060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15523247#comment-15523247 ] Jagadesh Kiran N commented on HDFS-9060: As discussed offline assigning myself, Thanks [~kanaka] > expose snapshotdiff via WebHDFS > --- > > Key: HDFS-9060 > URL: https://issues.apache.org/jira/browse/HDFS-9060 > Project: Hadoop HDFS > Issue Type: New Feature >Reporter: Allen Wittenauer >Assignee: Jagadesh Kiran N > > snapshotDiff should be exposed via webhdfs. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Assigned] (HDFS-9060) expose snapshotdiff via WebHDFS
[ https://issues.apache.org/jira/browse/HDFS-9060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadesh Kiran N reassigned HDFS-9060: -- Assignee: Jagadesh Kiran N (was: Kanaka Kumar Avvaru) > expose snapshotdiff via WebHDFS > --- > > Key: HDFS-9060 > URL: https://issues.apache.org/jira/browse/HDFS-9060 > Project: Hadoop HDFS > Issue Type: New Feature >Reporter: Allen Wittenauer >Assignee: Jagadesh Kiran N > > snapshotDiff should be exposed via webhdfs. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-10869) Unused method checkId() in InodeId.java file
[
https://issues.apache.org/jira/browse/HDFS-10869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-10869:
Attachment: HDFS-10869_01.patch
Attaching the patch ,Please review
> Unused method checkId() in InodeId.java file
> -
>
> Key: HDFS-10869
> URL: https://issues.apache.org/jira/browse/HDFS-10869
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-10869.patch, HDFS-10869_01.patch
>
>
> The following method in InodeId.java is not used anywhere , We can remove the
> code
> {code}
> public static void checkId(long requestId, INode inode)
> throws FileNotFoundException {
> if (requestId != HdfsConstants.GRANDFATHER_INODE_ID && requestId !=
> inode.getId()) {
> throw new FileNotFoundException(
> "ID mismatch. Request id and saved id: " + requestId + " , "
> + inode.getId() + " for file " + inode.getFullPathName());
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-10869) Unused method checkId() in InodeId.java file
[
https://issues.apache.org/jira/browse/HDFS-10869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15516504#comment-15516504
]
Jagadesh Kiran N commented on HDFS-10869:
-
Updated the patch after removing unused imports as part of checkstyle errors
> Unused method checkId() in InodeId.java file
> -
>
> Key: HDFS-10869
> URL: https://issues.apache.org/jira/browse/HDFS-10869
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-10869.patch, HDFS-10869_01.patch
>
>
> The following method in InodeId.java is not used anywhere , We can remove the
> code
> {code}
> public static void checkId(long requestId, INode inode)
> throws FileNotFoundException {
> if (requestId != HdfsConstants.GRANDFATHER_INODE_ID && requestId !=
> inode.getId()) {
> throw new FileNotFoundException(
> "ID mismatch. Request id and saved id: " + requestId + " , "
> + inode.getId() + " for file " + inode.getFullPathName());
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-10869) Unused method checkId() in InodeId.java file
[
https://issues.apache.org/jira/browse/HDFS-10869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-10869:
Status: Patch Available (was: Open)
> Unused method checkId() in InodeId.java file
> -
>
> Key: HDFS-10869
> URL: https://issues.apache.org/jira/browse/HDFS-10869
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-10869.patch
>
>
> The following method in InodeId.java is not used anywhere , We can remove the
> code
> {code}
> public static void checkId(long requestId, INode inode)
> throws FileNotFoundException {
> if (requestId != HdfsConstants.GRANDFATHER_INODE_ID && requestId !=
> inode.getId()) {
> throw new FileNotFoundException(
> "ID mismatch. Request id and saved id: " + requestId + " , "
> + inode.getId() + " for file " + inode.getFullPathName());
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-10869) Unused method checkId() in InodeId.java file
[
https://issues.apache.org/jira/browse/HDFS-10869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-10869:
Attachment: HDFS-10869.patch
Attaching the patch Please review
> Unused method checkId() in InodeId.java file
> -
>
> Key: HDFS-10869
> URL: https://issues.apache.org/jira/browse/HDFS-10869
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-10869.patch
>
>
> The following method in InodeId.java is not used anywhere , We can remove the
> code
> {code}
> public static void checkId(long requestId, INode inode)
> throws FileNotFoundException {
> if (requestId != HdfsConstants.GRANDFATHER_INODE_ID && requestId !=
> inode.getId()) {
> throw new FileNotFoundException(
> "ID mismatch. Request id and saved id: " + requestId + " , "
> + inode.getId() + " for file " + inode.getFullPathName());
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-10869) Unused method checkId() in InodeId.java file
[
https://issues.apache.org/jira/browse/HDFS-10869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-10869:
Issue Type: Improvement (was: Bug)
> Unused method checkId() in InodeId.java file
> -
>
> Key: HDFS-10869
> URL: https://issues.apache.org/jira/browse/HDFS-10869
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
>
> The following method in InodeId.java is not used anywhere , We can remove the
> code
> {code}
> public static void checkId(long requestId, INode inode)
> throws FileNotFoundException {
> if (requestId != HdfsConstants.GRANDFATHER_INODE_ID && requestId !=
> inode.getId()) {
> throw new FileNotFoundException(
> "ID mismatch. Request id and saved id: " + requestId + " , "
> + inode.getId() + " for file " + inode.getFullPathName());
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-10869) Unused method checkId() in InodeId.java file
[
https://issues.apache.org/jira/browse/HDFS-10869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503607#comment-15503607
]
Jagadesh Kiran N commented on HDFS-10869:
-
Pls assign to me
> Unused method checkId() in InodeId.java file
> -
>
> Key: HDFS-10869
> URL: https://issues.apache.org/jira/browse/HDFS-10869
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
>Reporter: Jagadesh Kiran N
>
> The following method in InodeId.java is not used anywhere , We can remove the
> code
> {code}
> public static void checkId(long requestId, INode inode)
> throws FileNotFoundException {
> if (requestId != HdfsConstants.GRANDFATHER_INODE_ID && requestId !=
> inode.getId()) {
> throw new FileNotFoundException(
> "ID mismatch. Request id and saved id: " + requestId + " , "
> + inode.getId() + " for file " + inode.getFullPathName());
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Created] (HDFS-10869) Unused method checkId() in InodeId.java file
Jagadesh Kiran N created HDFS-10869:
---
Summary: Unused method checkId() in InodeId.java file
Key: HDFS-10869
URL: https://issues.apache.org/jira/browse/HDFS-10869
Project: Hadoop HDFS
Issue Type: Bug
Components: namenode
Reporter: Jagadesh Kiran N
The following method in InodeId.java is not used anywhere , We can remove the
code
{code}
public static void checkId(long requestId, INode inode)
throws FileNotFoundException {
if (requestId != HdfsConstants.GRANDFATHER_INODE_ID && requestId !=
inode.getId()) {
throw new FileNotFoundException(
"ID mismatch. Request id and saved id: " + requestId + " , "
+ inode.getId() + " for file " + inode.getFullPathName());
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434558#comment-15434558
]
Jagadesh Kiran N commented on HDFS-9337:
[~walter.k.su] & [~vinayrpet] Sorry for the delay was busy with other work, I
will update the patch soon
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-8986) Add option to -du to calculate directory space usage excluding snapshots
[
https://issues.apache.org/jira/browse/HDFS-8986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035970#comment-15035970
]
Jagadesh Kiran N commented on HDFS-8986:
no issues [~ggop] ,you can assign
> Add option to -du to calculate directory space usage excluding snapshots
>
>
> Key: HDFS-8986
> URL: https://issues.apache.org/jira/browse/HDFS-8986
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: snapshots
>Reporter: Gautam Gopalakrishnan
>Assignee: Jagadesh Kiran N
>
> When running {{hadoop fs -du}} on a snapshotted directory (or one of its
> children), the report includes space consumed by blocks that are only present
> in the snapshots. This is confusing for end users.
> {noformat}
> $ hadoop fs -du -h -s /tmp/parent /tmp/parent/*
> 799.7 M 2.3 G /tmp/parent
> 799.7 M 2.3 G /tmp/parent/sub1
> $ hdfs dfs -createSnapshot /tmp/parent snap1
> Created snapshot /tmp/parent/.snapshot/snap1
> $ hadoop fs -rm -skipTrash /tmp/parent/sub1/*
> ...
> $ hadoop fs -du -h -s /tmp/parent /tmp/parent/*
> 799.7 M 2.3 G /tmp/parent
> 799.7 M 2.3 G /tmp/parent/sub1
> $ hdfs dfs -deleteSnapshot /tmp/parent snap1
> $ hadoop fs -du -h -s /tmp/parent /tmp/parent/*
> 0 0 /tmp/parent
> 0 0 /tmp/parent/sub1
> {noformat}
> It would be helpful if we had a flag, say -X, to exclude any snapshot related
> disk usage in the output
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15006414#comment-15006414
]
Jagadesh Kiran N commented on HDFS-9337:
[~walter.k.su] nice idea i will first go through all the commands once ,will
try to identify as many as NPE's then we will apply patch on the same.,
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HDFS-8986) Add option to -du to calculate directory space usage excluding snapshots
[
https://issues.apache.org/jira/browse/HDFS-8986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15004051#comment-15004051
]
Jagadesh Kiran N commented on HDFS-8986:
Thanks [~qwertymaniac] , i am working on this will try to provide patch next
week, busy with other work as of now
> Add option to -du to calculate directory space usage excluding snapshots
>
>
> Key: HDFS-8986
> URL: https://issues.apache.org/jira/browse/HDFS-8986
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: snapshots
>Reporter: Gautam Gopalakrishnan
>Assignee: Jagadesh Kiran N
>
> When running {{hadoop fs -du}} on a snapshotted directory (or one of its
> children), the report includes space consumed by blocks that are only present
> in the snapshots. This is confusing for end users.
> {noformat}
> $ hadoop fs -du -h -s /tmp/parent /tmp/parent/*
> 799.7 M 2.3 G /tmp/parent
> 799.7 M 2.3 G /tmp/parent/sub1
> $ hdfs dfs -createSnapshot /tmp/parent snap1
> Created snapshot /tmp/parent/.snapshot/snap1
> $ hadoop fs -rm -skipTrash /tmp/parent/sub1/*
> ...
> $ hadoop fs -du -h -s /tmp/parent /tmp/parent/*
> 799.7 M 2.3 G /tmp/parent
> 799.7 M 2.3 G /tmp/parent/sub1
> $ hdfs dfs -deleteSnapshot /tmp/parent snap1
> $ hadoop fs -du -h -s /tmp/parent /tmp/parent/*
> 0 0 /tmp/parent
> 0 0 /tmp/parent/sub1
> {noformat}
> It would be helpful if we had a flag, say -X, to exclude any snapshot related
> disk usage in the output
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-9337) Should check required params in WebHDFS to avoid NPE
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_03.patch
Thanks [~vinayrpet] & [~walter.k.su] for your review ,updated the patch as per
your review comments and suggestions ,please review
> Should check required params in WebHDFS to avoid NPE
>
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch, HDFS-9337_03.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HDFS-9337) In webhdfs Nullpoint exception will be thrown in renamesnapshot when oldsnapshotname is not given
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1453#comment-1453
]
Jagadesh Kiran N commented on HDFS-9337:
THanks [~vinayrpet] for your review, Agree there should be common function as
many areas this issue might repeat when validated., I will update the patch
accordingly
> In webhdfs Nullpoint exception will be thrown in renamesnapshot when
> oldsnapshotname is not given
> -
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-9337) In webhdfs Nullpoint exception will be thrown in renamesnapshot when oldsnapshotname is not given
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_02.patch
Updated with fix of whitespace
> In webhdfs Nullpoint exception will be thrown in renamesnapshot when
> oldsnapshotname is not given
> -
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch,
> HDFS-9337_02.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-9337) In webhdfs Nullpoint exception will be thrown in renamesnapshot when oldsnapshotname is not given
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_01.patch
Thanks [~surendrasingh] , I have updated the patch with your comments ,please
review
> In webhdfs Nullpoint exception will be thrown in renamesnapshot when
> oldsnapshotname is not given
> -
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch, HDFS-9337_01.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HDFS-8986) Add option to -du to calculate directory space usage excluding snapshots
[
https://issues.apache.org/jira/browse/HDFS-8986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14984749#comment-14984749
]
Jagadesh Kiran N commented on HDFS-8986:
[~qwertymaniac] i am not opposing the same , i was collecting the opinions
before i start implementing the same.
> Add option to -du to calculate directory space usage excluding snapshots
>
>
> Key: HDFS-8986
> URL: https://issues.apache.org/jira/browse/HDFS-8986
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: snapshots
>Reporter: Gautam Gopalakrishnan
>Assignee: Jagadesh Kiran N
>
> When running {{hadoop fs -du}} on a snapshotted directory (or one of its
> children), the report includes space consumed by blocks that are only present
> in the snapshots. This is confusing for end users.
> {noformat}
> $ hadoop fs -du -h -s /tmp/parent /tmp/parent/*
> 799.7 M 2.3 G /tmp/parent
> 799.7 M 2.3 G /tmp/parent/sub1
> $ hdfs dfs -createSnapshot /tmp/parent snap1
> Created snapshot /tmp/parent/.snapshot/snap1
> $ hadoop fs -rm -skipTrash /tmp/parent/sub1/*
> ...
> $ hadoop fs -du -h -s /tmp/parent /tmp/parent/*
> 799.7 M 2.3 G /tmp/parent
> 799.7 M 2.3 G /tmp/parent/sub1
> $ hdfs dfs -deleteSnapshot /tmp/parent snap1
> $ hadoop fs -du -h -s /tmp/parent /tmp/parent/*
> 0 0 /tmp/parent
> 0 0 /tmp/parent/sub1
> {noformat}
> It would be helpful if we had a flag, say -X, to exclude any snapshot related
> disk usage in the output
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-9338) in webhdfs Null pointer exception will be thrown when xattrname is not given
[
https://issues.apache.org/jira/browse/HDFS-9338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9338:
---
Status: Patch Available (was: Open)
> in webhdfs Null pointer exception will be thrown when xattrname is not given
>
>
> Key: HDFS-9338
> URL: https://issues.apache.org/jira/browse/HDFS-9338
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9338-00.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/?op=REMOVEXATTR=;
> or
> curl -i -X PUT "http://10.19.92.127:50070/webhdfs/v1/kiran/?op=REMOVEXATTR;
> {code}
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":"XAttr
> name cannot be null."}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-9338) in webhdfs Null pointer exception will be thrown when xattrname is not given
[
https://issues.apache.org/jira/browse/HDFS-9338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9338:
---
Attachment: HDFS-9338-00.patch
Attached the patch please review
> in webhdfs Null pointer exception will be thrown when xattrname is not given
>
>
> Key: HDFS-9338
> URL: https://issues.apache.org/jira/browse/HDFS-9338
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9338-00.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/?op=REMOVEXATTR=;
> or
> curl -i -X PUT "http://10.19.92.127:50070/webhdfs/v1/kiran/?op=REMOVEXATTR;
> {code}
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":"XAttr
> name cannot be null."}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HDFS-9344) QUEUE_WITH_CORRUPT_BLOCKS is no longer needed
[
https://issues.apache.org/jira/browse/HDFS-9344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14983902#comment-14983902
]
Jagadesh Kiran N commented on HDFS-9344:
No issues [~xiaochen] , Good Analysis
> QUEUE_WITH_CORRUPT_BLOCKS is no longer needed
> -
>
> Key: HDFS-9344
> URL: https://issues.apache.org/jira/browse/HDFS-9344
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
>Affects Versions: 2.7.1
>Reporter: Zhe Zhang
>Assignee: Xiao Chen
>Priority: Minor
>
> After the change of HDFS-9205, the {{QUEUE_WITH_CORRUPT_BLOCKS}} queue in
> {{UnderReplicatedBlocks}} is no longer needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-9337) In webhdfs Nullpoint exception will be thrown in renamesnapshot when oldsnapshotname is not given
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Attachment: HDFS-9337_00.patch
Attached the patch please review
> In webhdfs Nullpoint exception will be thrown in renamesnapshot when
> oldsnapshotname is not given
> -
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-9337) In webhdfs Nullpoint exception will be thrown in renamesnapshot when oldsnapshotname is not given
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N updated HDFS-9337:
---
Status: Patch Available (was: Open)
> In webhdfs Nullpoint exception will be thrown in renamesnapshot when
> oldsnapshotname is not given
> -
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HDFS-9337) In webhdfs Nullpoint exception will be thrown in renamesnapshot when oldsnapshotname is not given
[
https://issues.apache.org/jira/browse/HDFS-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14984005#comment-14984005
]
Jagadesh Kiran N commented on HDFS-9337:
Thanks [~surendrasingh] for your comments,i will update the patch soon as per
your comment
> In webhdfs Nullpoint exception will be thrown in renamesnapshot when
> oldsnapshotname is not given
> -
>
> Key: HDFS-9337
> URL: https://issues.apache.org/jira/browse/HDFS-9337
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Jagadesh Kiran N
>Assignee: Jagadesh Kiran N
> Attachments: HDFS-9337_00.patch
>
>
> {code}
> curl -i -X PUT
> "http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
> {code}
> Null point exception will be thrown
> {code}
> {"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (HDFS-9344) QUEUE_WITH_CORRUPT_BLOCKS is no longer needed
[
https://issues.apache.org/jira/browse/HDFS-9344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jagadesh Kiran N reassigned HDFS-9344:
--
Assignee: Jagadesh Kiran N
> QUEUE_WITH_CORRUPT_BLOCKS is no longer needed
> -
>
> Key: HDFS-9344
> URL: https://issues.apache.org/jira/browse/HDFS-9344
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
>Affects Versions: 2.7.1
>Reporter: Zhe Zhang
>Assignee: Jagadesh Kiran N
>Priority: Minor
>
> After the change of HDFS-9205, the {{QUEUE_WITH_CORRUPT_BLOCKS}} queue in
> {{UnderReplicatedBlocks}} is no longer needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HDFS-9338) in webhdfs Null pointer exception will be thrown when xattrname is not given
Jagadesh Kiran N created HDFS-9338:
--
Summary: in webhdfs Null pointer exception will be thrown when
xattrname is not given
Key: HDFS-9338
URL: https://issues.apache.org/jira/browse/HDFS-9338
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Jagadesh Kiran N
Assignee: Jagadesh Kiran N
{code}
curl -i -X PUT
"http://10.19.92.127:50070/webhdfs/v1/kiran/?op=REMOVEXATTR=;
or
curl -i -X PUT "http://10.19.92.127:50070/webhdfs/v1/kiran/?op=REMOVEXATTR;
{code}
{code}
{"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":"XAttr
name cannot be null."}}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HDFS-9337) In webhdfs Nullpoint exception will be thrown in renamesnapshot when oldsnapshotname is not given
Jagadesh Kiran N created HDFS-9337:
--
Summary: In webhdfs Nullpoint exception will be thrown in
renamesnapshot when oldsnapshotname is not given
Key: HDFS-9337
URL: https://issues.apache.org/jira/browse/HDFS-9337
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Jagadesh Kiran N
Assignee: Jagadesh Kiran N
{code}
curl -i -X PUT
"http://10.19.92.127:50070/webhdfs/v1/kiran/sreenu?op=RENAMESNAPSHOT=SNAPSHOTNAME;
{code}
Null point exception will be thrown
{code}
{"RemoteException":{"exception":"NullPointerException","javaClassName":"java.lang.NullPointerException","message":null}}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HDFS-9327) WebHDFS throws html trace if Source is not provided
Jagadesh Kiran N created HDFS-9327:
--
Summary: WebHDFS throws html trace if Source is not provided
Key: HDFS-9327
URL: https://issues.apache.org/jira/browse/HDFS-9327
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Jagadesh Kiran N
Assignee: Jagadesh Kiran N
Execute the following command in webhdfs with out entering Sources
{code}
curl -i -X POST "http://10.19.92.127:50070/webhdfs/v1/kiran/1?op=CONCAT;
{code}
the html trace will be disclosed with jetty version
{code}
HTTP/1.1 500 Absolute path required
Cache-Control: must-revalidate,no-cache,no-store
Date: Wed, 28 Oct 2015 16:10:44 GMT
Pragma: no-cache
Date: Wed, 28 Oct 2015 16:10:44 GMT
Pragma: no-cache
Content-Type: text/html; charset=iso-8859-1
Content-Length: 7082
Server: Jetty(6.1.26)
Error 500 Absolute path required
HTTP ERROR 500
Problem accessing /webhdfs/v1/kiran/1. Reason:
Absolute path requiredCaused
by:java.lang.AssertionError: Absolute path required
at
org.apache.hadoop.hdfs.server.namenode.INode.getPathNames(INode.java:745)
at
org.apache.hadoop.hdfs.server.namenode.INode.getPathComponents(INode.java:724)
at
org.apache.hadoop.hdfs.server.namenode.FSDirectory.getINodesInPath4Write(FSDirectory.java:1456)
at
org.apache.hadoop.hdfs.server.namenode.FSDirectory.getINodesInPath4Write(FSDirectory.java:1417)
at
org.apache.hadoop.hdfs.server.namenode.FSDirConcatOp.verifySrcFiles(FSDirConcatOp.java:112)
at
org.apache.hadoop.hdfs.server.namenode.FSDirConcatOp.concat(FSDirConcatOp.java:71)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.concat(FSNamesystem.java:1790)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.concat(NameNodeRpcServer.java:880)
at
org.apache.hadoop.hdfs.server.namenode.web.resources.NamenodeWebHdfsMethods.post(NamenodeWebHdfsMethods.java:705)
at
org.apache.hadoop.hdfs.server.namenode.web.resources.NamenodeWebHdfsMethods.access$200(NamenodeWebHdfsMethods.java:101)
at
org.apache.hadoop.hdfs.server.namenode.web.resources.NamenodeWebHdfsMethods$2.run(NamenodeWebHdfsMethods.java:670)
at
org.apache.hadoop.hdfs.server.namenode.web.resources.NamenodeWebHdfsMethods$2.run(NamenodeWebHdfsMethods.java:666)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1667)
at
org.apache.hadoop.hdfs.server.namenode.web.resources.NamenodeWebHdfsMethods.post(NamenodeWebHdfsMethods.java:666)
at sun.reflect.GeneratedMethodAccessor138.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
at
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:699)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1221)
at
[jira] [Created] (HDFS-9335) Webhdfs hangs when folder is used for Append
Jagadesh Kiran N created HDFS-9335:
--
Summary: Webhdfs hangs when folder is used for Append
Key: HDFS-9335
URL: https://issues.apache.org/jira/browse/HDFS-9335
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Jagadesh Kiran N
Assignee: Jagadesh Kiran N
Priority: Critical
a. Submit HTTP POST request using the URL in the Location header with the file
data to be appended
{code}
curl -i -X POST -T /opt/folder/file
"http://host-10-19-92-117:50075/webhdfs/v1/folder1/file1?op=APPEND=hacluster=1;
{code}
b. The client receives a response with zero content length
c. Now execute the same for a folder (/opt/folder) rather than Local file
{code}
curl -i -X POST -T /opt/folder
"http://host-10-19-92-117:50075/webhdfs/v1/folder1/file1?op=APPEND=hacluster=1;
{code}
d. No response will be given to the user and it will hang
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
