[jira] [Created] (HADOOP-17934) NullPointerException when no HTTP response set on AbfsRestOperation
Josh Elser created HADOOP-17934:
---
Summary: NullPointerException when no HTTP response set on
AbfsRestOperation
Key: HADOOP-17934
URL: https://issues.apache.org/jira/browse/HADOOP-17934
Project: Hadoop Common
Issue Type: Bug
Components: fs/azure
Reporter: Josh Elser
Assignee: Josh Elser
Seen when running HBase 2.2 on top of ABFS with Hadoop 3.1ish:
{noformat}
Caused by: java.lang.NullPointerException
at
org.apache.hadoop.fs.azurebfs.services.AbfsClient.renameIdempotencyCheckOp(AbfsClient.java:382)
at
org.apache.hadoop.fs.azurebfs.services.AbfsClient.renamePath(AbfsClient.java:348)
at
org.apache.hadoop.fs.azurebfs.AzureBlobFileSystemStore.rename(AzureBlobFileSystemStore.java:722)
at
org.apache.hadoop.fs.azurebfs.AzureBlobFileSystem.rename(AzureBlobFileSystem.java:327)
at
org.apache.hadoop.fs.FilterFileSystem.rename(FilterFileSystem.java:249)
at
org.apache.hadoop.hbase.regionserver.HRegionFileSystem.rename(HRegionFileSystem.java:1115)
{noformat}
Digging in, it looks like the {{AbfsHttpOperation}} inside of
{{AbfsRestOperation}} may sometimes be null, but {{AbfsClient}} will try to
unwrap it (and read the status code from the HTTP call). I'm not sure why we
sometimes _get_ the null HttpOperation but it seems pretty straightforward to
not get the NPE.
HBase got wedged after this, but I'm not sure if it's because of this NPE or
(perhaps) we weren't getting any responses from ABFS itself (i.e. there was
some ABFS outage/unavailability or the node itself couldn't talk to ABFS).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-14911) Upgrade netty-all jar to 4.0.37.Final
Josh Elser created HADOOP-14911: --- Summary: Upgrade netty-all jar to 4.0.37.Final Key: HADOOP-14911 URL: https://issues.apache.org/jira/browse/HADOOP-14911 Project: Hadoop Common Issue Type: Bug Reporter: Josh Elser Assignee: Vinayakumar B Priority: Critical Upgrade netty-all jar to 4.0.37.Final version to fix latest vulnerabilities reported. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-10928) Incorrect usage on `hadoop credential list`
Josh Elser created HADOOP-10928:
---
Summary: Incorrect usage on `hadoop credential list`
Key: HADOOP-10928
URL: https://issues.apache.org/jira/browse/HADOOP-10928
Project: Hadoop Common
Issue Type: Bug
Components: security
Reporter: Josh Elser
Priority: Trivial
Attachments: HADOOP-10928.diff
{{hadoop credential list}}'s usage message states a mandatory {{alias}}
argument. The code does not actually accept an alias.
Fix the message.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (HADOOP-10927) Ran `hadoop credential` expecting usage, got NPE instead
Josh Elser created HADOOP-10927:
---
Summary: Ran `hadoop credential` expecting usage, got NPE instead
Key: HADOOP-10927
URL: https://issues.apache.org/jira/browse/HADOOP-10927
Project: Hadoop Common
Issue Type: Bug
Components: security
Reporter: Josh Elser
Priority: Minor
{noformat}
$ hadoop credential
java.lang.NullPointerException
at
org.apache.hadoop.security.alias.CredentialShell.run(CredentialShell.java:67)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at
org.apache.hadoop.security.alias.CredentialShell.main(CredentialShell.java:420)
{noformat}
Ran a no-arg version of {{hadoop credential}} expecting to get the usage/help
message (like other commands act), and got the above exception instead.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
