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
