Fix hbase tablegroup operations being hold for a long time #295
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
In getTableInternal, if there is a new tablet operations, client will refresh this tablet location from servers, and the main thread will be hold. In the specific situation that if a multi-cf hbase operation mapping to a new tablet comes, but the table cached by the client has been drop, the tablet location will never be returned from servers and the main thread will be hold to timeout.
Solution Description
Add waiting limit for the holding time, if fail to wait for the location returned, throw exception to refresh tablegroup caching.s