Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.3.1
Description
Seen when running HBase 2.2 on top of ABFS with Hadoop 3.1ish:
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)
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).
Attachments
Issue Links
- causes
-
-
- Resolved
-
- is related to
-
HADOOP-18012 ABFS: Enable config controlled ETag check for Rename idempotency
-
- Resolved
-
-
-
- Resolved
-
- links to
