Support retry mechanism when get available tablet server nodes failed #480

Search before asking

• I searched in the issues and found nothing similar.

Motivation

Currently, fluss will directly throw an exception when get available tablet server node fails, no matter what the reason once tablet server list is empty at the first attampet get, it will throw an exception, this is too unfriendly, so we can add retry logic to become strong.

Solution

Add retry times to avoid throwing an exception directly in getOneAvailableTabletServerNode(), and we need send metadata request to update cluster then try to get one available tablet server node again when available tablet server node list is empty in cluster.

Anything else?

No response

Willingness to contribute

• I'm willing to submit a PR!