[HADOOP-13550] Azure threaded deleter logs too much at info

• Type: Improvement
• Status: Patch Available
• Priority: Trivial
• Resolution: Unresolved
• Affects Version/s: 2.9.0
• Component/s: fs/azure
• Assignee: Steve Loughran
• Reporter: Steve Loughran
• Created: 26/Aug/16 18:01
• Updated: 26/Apr/17 01:10

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

1. given that thread count of 0 is the default, warn is overkill and misleading
2. I (and presumably many other users) don't care about how long something took.

These should both be downgraded to debug

Issue Links

• is broken by: HADOOP-13403 AzureNativeFileSystem rename/delete performance improvements