Re: [PR] HBASE-28608 More sensible client meta operation timeout default [hbase]
Apache9 merged PR #6481: URL: https://github.com/apache/hbase/pull/6481 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] HBASE-28608 More sensible client meta operation timeout default [hbase]
Apache9 merged PR #6000: URL: https://github.com/apache/hbase/pull/6000 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] HBASE-28608 More sensible client meta operation timeout default [hbase]
droudnitsky commented on PR #6000: URL: https://github.com/apache/hbase/pull/6000#issuecomment-2400162303 Hi @Apache9 , from dev list thread started one week ago the proposal has received two +1s (so three +1s in total including your approval). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] HBASE-28608 More sensible client meta operation timeout default [hbase]
droudnitsky commented on PR #6000: URL: https://github.com/apache/hbase/pull/6000#issuecomment-2227060072 Thank you for the explanation @Apache9 . I have opened HBASE-28358 to propose decoupling the meta operation timeout from the branch-2 userRegionLock/locate region codepath. If my proposal there sounds reasonable, I can work to get that implemented, and once that big branch-2 userRegionLock dependence on the property is gone, it should be simpler to reason about the implications of a new default for meta operation timeout and I can bring this PR up on the devlist for discussion. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] HBASE-28608 More sensible client meta operation timeout default [hbase]
Apache9 commented on PR #6000: URL: https://github.com/apache/hbase/pull/6000#issuecomment-2210913557 On branch-3+, we have removed all the sync client code and reimplement sync client on top of async client. In async client,the locate region timeout is controlled by meta operation timeout, but since we are asynchronous, the upper layer could get a timeout even if the locating region operation has not completed yet, so there is no problem. On branch-2, it is a problem since we run all the operations in one thread. Thanks. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
