[Enhancement] InterruptedExceptions should never be ignored in the code.[EtcdMetaService]

[Alonexc]

Search before asking

• I had searched in the issues and found no similar issues.

Enhancement Request

located at:
eventmesh-registry-plugin/eventmesh-registry-etcd/src/main/java/org/apache/eventmesh/registry/etcd/service/EtcdRegistryService.java line 173,290
analysis and explanation:
InterruptedExceptions should never be ignored in the code, and simply logging the exception counts in this case as "ignoring". The throwing of the InterruptedException clears the interrupted state of the Thread, so if the exception is not handled properly the information that the thread was interrupted will be lost. Instead, InterruptedExceptions should either be rethrown - immediately or after cleaning up the method’s state - or the thread should be re-interrupted by calling Thread.interrupt() even if this is supposed to be a single-threaded application. Any other course of action risks delaying thread shutdown and loses the information that the thread was interrupted - probably without finishing its task.

Describe the solution you'd like

restore interrupted state

Are you willing to submit PR?

• Yes I am willing to submit a PR!

[HarshSawarkar]

Hi all, I have raised a PR for this issue.Can anyone please review it? Here's the link #4636

[HarshSawarkar]

Also can someone please add me to ASF slack.Here's my email id: [email protected]