hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12089) StorageException complaining " no lease ID" when updating FolderLastModifiedTime in WASB
Date Tue, 30 Jun 2015 15:20:11 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-12089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14608471#comment-14608471
] 

Hudson commented on HADOOP-12089:
---------------------------------

SUCCESS: Integrated in Hadoop-Mapreduce-trunk-Java8 #242 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/242/])
HADOOP-12089. StorageException complaining " no lease ID" when updating FolderLastModifiedTime
in WASB. Contributed by Duo Xu. (cnauroth: rev 460e98f7b3ec84f3c5afcb2aad4f4e7031d16e3a)
* hadoop-common-project/hadoop-common/CHANGES.txt
* hadoop-tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azure/NativeAzureFileSystem.java


> StorageException complaining " no lease ID" when updating FolderLastModifiedTime in WASB
> ----------------------------------------------------------------------------------------
>
>                 Key: HADOOP-12089
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12089
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: tools
>    Affects Versions: 2.7.0
>            Reporter: Duo Xu
>            Assignee: Duo Xu
>             Fix For: 2.8.0
>
>         Attachments: HADOOP-12089.01.patch, HADOOP-12089.02.patch
>
>
> This is a similar issue to HADOOP-11523. HADOOP-11523 happens when HBase is doing distributed
log splitting. This JIRA happens when HBase is deleting old WALs and trying to update /hbase/oldWALs
folder.
> The fix is the same as HADOOP-11523.
> {code}
> 2015-06-10 08:11:40,636 WARN org.apache.hadoop.hbase.master.cleaner.CleanerChore: Error
while deleting: wasb://basecus1-1@basestoragecus1.blob.core.windows.net/hbase/oldWALs/workernode10.dthbasecus1.g1.internal.cloudapp.net%2C60020%2C1433908062461.1433921692855
> org.apache.hadoop.fs.azure.AzureException: com.microsoft.azure.storage.StorageException:
There is currently a lease on the blob and no lease ID was specified in the request.
> 	at org.apache.hadoop.fs.azure.AzureNativeFileSystemStore.updateFolderLastModifiedTime(AzureNativeFileSystemStore.java:2602)
> 	at org.apache.hadoop.fs.azure.AzureNativeFileSystemStore.updateFolderLastModifiedTime(AzureNativeFileSystemStore.java:2613)
> 	at org.apache.hadoop.fs.azure.NativeAzureFileSystem.delete(NativeAzureFileSystem.java:1505)
> 	at org.apache.hadoop.fs.azure.NativeAzureFileSystem.delete(NativeAzureFileSystem.java:1437)
> 	at org.apache.hadoop.hbase.master.cleaner.CleanerChore.checkAndDeleteFiles(CleanerChore.java:256)
> 	at org.apache.hadoop.hbase.master.cleaner.CleanerChore.checkAndDeleteEntries(CleanerChore.java:157)
> 	at org.apache.hadoop.hbase.master.cleaner.CleanerChore.chore(CleanerChore.java:124)
> 	at org.apache.hadoop.hbase.Chore.run(Chore.java:80)
> 	at java.lang.Thread.run(Thread.java:745)
> Caused by: com.microsoft.azure.storage.StorageException: There is currently a lease on
the blob and no lease ID was specified in the request.
> 	at com.microsoft.azure.storage.StorageException.translateException(StorageException.java:162)
> 	at com.microsoft.azure.storage.core.StorageRequest.materializeException(StorageRequest.java:307)
> 	at com.microsoft.azure.storage.core.ExecutionEngine.executeWithRetry(ExecutionEngine.java:177)
> 	at com.microsoft.azure.storage.blob.CloudBlob.uploadProperties(CloudBlob.java:2991)
> 	at org.apache.hadoop.fs.azure.StorageInterfaceImpl$CloudBlobWrapperImpl.uploadProperties(StorageInterfaceImpl.java:372)
> 	at org.apache.hadoop.fs.azure.AzureNativeFileSystemStore.updateFolderLastModifiedTime(AzureNativeFileSystemStore.java:2597)
> 	... 8 more
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message