Logging failures to refresh metadata

[cbb330]

Summary

problem - when an exception throws under super.refreshFromMetadataLocation , there is no failure log which shows how long it took to fail. Adding logging here for the total duration Helps us measure how long a request takes when it fails to retrieve metadata from hdfs. This is a common cause for 504 gateway timeouts. Without this, we can only guess the total duration by correlating it with metrics. The metrics don’t have a failure/success dimension, and also cannot be isolated to a single request/table metadata file.

solution - try/catch and log before throwing the existing error. There is another PR which aims to reduce the total duration via better configured timeouts+retries at hdfs layer #386

At the same time, adding a missing log message for catalog update, for future operations

Changes

• Client-facing API Changes
• Internal API Changes
• Bug Fixes
• New Features
• Performance Improvements
• Code Style
• Refactoring
• Documentation
• Tests

Testing Done

existing tests should cover this

• Manually Tested on local docker setup. Please include commands ran, and their output.
• Added new tests for the changes made.
• Updated existing tests to reflect the changes made.
• No tests added or updated. Please explain why. If unsure, please feel free to ask for help.
• Some other form of testing like staging or soak time in production. Please explain.

Additional Information

• Breaking Changes
• Deprecations
• Large PR broken into smaller PRs, and PR plan linked in the description.

[abhisheknath2011]

Thanks @cbb330 for adding logs.