-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-25292 [branch-2.4] Improve InetSocketAddress usage discipline #5515
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
💔 -1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
Thank you. This is looking good to me but since I was involved in creating this patch I'll give @apurtell (or others) a chance to take a look as well. Thank you @sbernauer! |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
Co-authored-by: Andrew Purtell <[email protected]> (cherry picked from commit f813479)
ddc046f to
c4dc0eb
Compare
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
@sbernauer Thanks for opening this PR. So you guys needs this on branch-2.4? The patch here removes a configuration, so typically we do not want to include it in a patch release. And looking at the discussion on #2669 , there are also some other follow on tasks need to be done before making a release. Thanks. |
|
Yep, we find that without it, running 2.4.x on Kubernetes is very unstable across restarts because of DNS issues. We're also happy to just maintain the patch on our end for the rest of the lifecycle of 2.4 but thought others might benefit from this. Indeed, it removes a config and at least I didn't think about that when we put this PR up. Which other follow on tasks are you referring to? But as I mentioned: We can also close this PR if you're opposed to the change, we don't have very strong feelings about it. And thanks for taking a look! |
|
See HBASE-25335. I think at least we should also backport HBASE-25336? |
|
Ah! Yes, sorry. We have a patch for that as well and can put up a PR as well. Only makes sense if we agree that this one should go in though I believe. They might even depend on each other, I haven't checked now. |
|
I'm OK with backporting all these issues to 2.4. |
|
Thank you! I'll merge it then and we'll get the second PR up as well. |
|
Thanks a lot for the quick review! |
|
Created #5537 as a follow-up |
…pache#5515) Co-authored-by: Andrew Purtell <[email protected]> (cherry picked from commit f813479) (cherry picked from commit 8707793) Change-Id: Idef951d038f8bda6e74d57d2894323322cae3e86
Back-port of #2669 to the 2.4 release line.
(cherry picked from commit f813479)
Co-authored-by: Andrew Purtell [email protected]