Suppress stacktrace of InterruptedException in CommonCacheNotifier

[kfaraz]

Addresses #10709

Description

When CommonCachedNotifier is being stopped while the thread is waiting on updateQueue.take(),
an InterruptedException is thrown. The stack trace from this exception gives the wrong idea that something went wrong with the shutdown.

---

This PR has:

• been self-reviewed.
  • using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)
• added documentation for new or modified features or behaviors.
• added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
• added or updated version, license, or notice information in licenses.yaml
• added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
• added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
• added integration tests.
• been tested in a test Druid cluster.

[abhishekagarwal87]

how does the InterruptedException affect graceful shutdown?

[abhishekagarwal87]

should this be emitted as an alert?

[kfaraz]

I guess we could just log an INFO here instead.

[abhishekagarwal87]

makes sense to me.

[kfaraz]

The stack trace from the InterruptedException might give the wrong notion that something went wrong with the shutdown.

By graceful shutdown, I meant avoiding the above confusion. Let me fix this description 🙂

[abhishekagarwal87]

The stack trace from the InterruptedException might give the wrong notion that something went wrong with the shutdown.

By graceful shutdown, I meant avoiding the above confusion. Let me fix this description 🙂

Thanks 🙂

[abhishekagarwal87]

Ignoring code coverage check and merging since it is just a logging change.