Skip to content

Conversation

@JackShi148
Copy link
Contributor

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

@JackShi148 JackShi148 force-pushed the fix_multicf_tablegroup branch from c84cfb3 to e87f3ff Compare February 27, 2025 01:57
@JackShi148 JackShi148 force-pushed the fix_multicf_tablegroup branch from 74eaecd to 9c2b15c Compare March 12, 2025 06:17
@JackShi148 JackShi148 force-pushed the fix_multicf_tablegroup branch from 2f4f23e to 34b752b Compare March 25, 2025 02:45
@JackShi148 JackShi148 force-pushed the fix_multicf_tablegroup branch from 34b752b to e6a2428 Compare March 25, 2025 02:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants