Details
-
Improvement
-
Status: Patch Available
-
Trivial
-
Resolution: Unresolved
-
2.9.0
-
None
-
None
Description
The new azure parallel deleter shares too much information in the logs about what is going on
2016-08-26 18:56:16,461 WARN azure.AzureFileSystemThreadPoolExecutor (AzureFileSystemThreadPoolExecutor.java:executeParallel(150)) - Disabling threads for Delete operation as thread count 0 is <= 1 2016-08-26 18:56:21,424 INFO azure.AzureFileSystemThreadPoolExecutor (AzureFileSystemThreadPoolExecutor.java:executeParallel(235)) - Time taken for Delete operation is: 4963 ms with threads: 0
- given that thread count of 0 is the default, warn is overkill and misleading
- I (and presumably many other users) don't care about how long something took.
These should both be downgraded to debug
Attachments
Attachments
Issue Links
- is broken by
-
HADOOP-13403 AzureNativeFileSystem rename/delete performance improvements
- Resolved