[jira] [Updated] (HDFS-16207) Remove NN logs stack trace for non-existent xattr query
[ https://issues.apache.org/jira/browse/HDFS-16207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-16207: - Fix Version/s: 3.2.4 3.3.2 2.10.2 3.4.0 Resolution: Fixed Status: Resolved (was: Patch Available) [~ahussein], thank you for the additional patch to backport to branch-2.10. I just committed it. > Remove NN logs stack trace for non-existent xattr query > --- > > Key: HDFS-16207 > URL: https://issues.apache.org/jira/browse/HDFS-16207 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode >Affects Versions: 3.4.0, 2.10.2, 3.3.2, 3.2.4 >Reporter: Ahmed Hussein >Assignee: Ahmed Hussein >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0, 2.10.2, 3.3.2, 3.2.4 > > Attachments: HDFS-16207-branch-2.10.001.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > The NN logs a full stack trace every time a getXAttrs is called for a > non-existent xattr. The logging has zero value add. The increased logging > load may harm performance. Something is now probing for xattrs resulting in > many lines of: > {code:bash} > 2021-09-02 13:48:03,340 [IPC Server handler 5 on default port 59951] INFO > ipc.Server (Server.java:logException(3149)) - IPC Server handler 5 on default > port 59951, call Call#17 Retry#0 > org.apache.hadoop.hdfs.protocol.ClientProtocol.getXAttrs from 127.0.0.1:59961 > java.io.IOException: At least one of the attributes provided was not found. > at > org.apache.hadoop.hdfs.server.namenode.FSDirXAttrOp.getXAttrs(FSDirXAttrOp.java:134) > at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getXAttrs(FSNamesystem.java:8472) > at > org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.getXAttrs(NameNodeRpcServer.java:2317) > at > org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.getXAttrs(ClientNamenodeProtocolServerSideTranslatorPB.java:1745) > at > org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java) > at > org.apache.hadoop.ipc.ProtobufRpcEngine2$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine2.java:604) > at > org.apache.hadoop.ipc.ProtobufRpcEngine2$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine2.java:572) > at > org.apache.hadoop.ipc.ProtobufRpcEngine2$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine2.java:556) > at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1093) > at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:1155) > at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:1083) > 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:1900) > at org.apache.hadoop.ipc.Server$Handler.run(Server.java:3088) > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-16207) Remove NN logs stack trace for non-existent xattr query
[ https://issues.apache.org/jira/browse/HDFS-16207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ahmed Hussein updated HDFS-16207: - Attachment: HDFS-16207-branch-2.10.001.patch Status: Patch Available (was: In Progress) Submitted HDFS-16207-branch-2.10.001.patch *test-patch* {code:bash} dev-support/bin/test-patch \ --plugins="maven,checkstyle,javac,javadoc" \ --test-parallel=true \ --branch=branch-2.10 HDFS-16207-branch-2.10.001.patch {code} *unit-tests* {code:bash} mvn test -Dtest=TestDFSShell,TestEncryptionZones,TestFileContextXAttr,TestNameNodeXAttr,TestWebHDFSXAttr {code} > Remove NN logs stack trace for non-existent xattr query > --- > > Key: HDFS-16207 > URL: https://issues.apache.org/jira/browse/HDFS-16207 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode >Affects Versions: 3.4.0, 2.10.2, 3.3.2, 3.2.4 >Reporter: Ahmed Hussein >Assignee: Ahmed Hussein >Priority: Major > Labels: pull-request-available > Attachments: HDFS-16207-branch-2.10.001.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > The NN logs a full stack trace every time a getXAttrs is called for a > non-existent xattr. The logging has zero value add. The increased logging > load may harm performance. Something is now probing for xattrs resulting in > many lines of: > {code:bash} > 2021-09-02 13:48:03,340 [IPC Server handler 5 on default port 59951] INFO > ipc.Server (Server.java:logException(3149)) - IPC Server handler 5 on default > port 59951, call Call#17 Retry#0 > org.apache.hadoop.hdfs.protocol.ClientProtocol.getXAttrs from 127.0.0.1:59961 > java.io.IOException: At least one of the attributes provided was not found. > at > org.apache.hadoop.hdfs.server.namenode.FSDirXAttrOp.getXAttrs(FSDirXAttrOp.java:134) > at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getXAttrs(FSNamesystem.java:8472) > at > org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.getXAttrs(NameNodeRpcServer.java:2317) > at > org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.getXAttrs(ClientNamenodeProtocolServerSideTranslatorPB.java:1745) > at > org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java) > at > org.apache.hadoop.ipc.ProtobufRpcEngine2$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine2.java:604) > at > org.apache.hadoop.ipc.ProtobufRpcEngine2$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine2.java:572) > at > org.apache.hadoop.ipc.ProtobufRpcEngine2$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine2.java:556) > at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1093) > at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:1155) > at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:1083) > 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:1900) > at org.apache.hadoop.ipc.Server$Handler.run(Server.java:3088) > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-16207) Remove NN logs stack trace for non-existent xattr query
[ https://issues.apache.org/jira/browse/HDFS-16207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HDFS-16207: -- Labels: pull-request-available (was: ) > Remove NN logs stack trace for non-existent xattr query > --- > > Key: HDFS-16207 > URL: https://issues.apache.org/jira/browse/HDFS-16207 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode >Affects Versions: 3.4.0, 2.10.2, 3.3.2, 3.2.4 >Reporter: Ahmed Hussein >Assignee: Ahmed Hussein >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > The NN logs a full stack trace every time a getXAttrs is called for a > non-existent xattr. The logging has zero value add. The increased logging > load may harm performance. Something is now probing for xattrs resulting in > many lines of: > {code:bash} > 2021-09-02 13:48:03,340 [IPC Server handler 5 on default port 59951] INFO > ipc.Server (Server.java:logException(3149)) - IPC Server handler 5 on default > port 59951, call Call#17 Retry#0 > org.apache.hadoop.hdfs.protocol.ClientProtocol.getXAttrs from 127.0.0.1:59961 > java.io.IOException: At least one of the attributes provided was not found. > at > org.apache.hadoop.hdfs.server.namenode.FSDirXAttrOp.getXAttrs(FSDirXAttrOp.java:134) > at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getXAttrs(FSNamesystem.java:8472) > at > org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.getXAttrs(NameNodeRpcServer.java:2317) > at > org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.getXAttrs(ClientNamenodeProtocolServerSideTranslatorPB.java:1745) > at > org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java) > at > org.apache.hadoop.ipc.ProtobufRpcEngine2$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine2.java:604) > at > org.apache.hadoop.ipc.ProtobufRpcEngine2$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine2.java:572) > at > org.apache.hadoop.ipc.ProtobufRpcEngine2$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine2.java:556) > at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1093) > at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:1155) > at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:1083) > 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:1900) > at org.apache.hadoop.ipc.Server$Handler.run(Server.java:3088) > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org