> On 19 Aug 2016, at 18:09, Elliott Clark <ecl...@apache.org> wrote: > > Is it time to merge IPv6 branch? > > We have been running the patches in several production and test > clusters. We have tested it on ipv4 only clusters, on clusters where > DFS is ipv4 and HBase is using ipv6, and we've tested it on ipv6 only > clusters. We've seen no performance degredation, and have had no > issues with network name resolution. > > Thoughts? > > Thanks >
1. I think it's time to add Ipv6 2.The fact that the code is ready to merge now means we should try to merge it before it ages/dates and increases merge costs. Or worse, languishes unmerged for 18 months and then suddenly is panically pulled in and will need full retesting again. I think a good strategy here is to rebase the patches onto trunk, and anyone who can test, does test. In particular, I want to be confident that IPv4 doesn't suffer. Even if there are some corner cases of IPv6 to be found and dealt with (this is inevitable, simply due to the different network settings, Kerberos, etc) —it's critical that IPv4 doesn't suffer. The good news: testing IPv4 regression is straightforward. People running IPv4 just need to check out the branch and do the regression tests on any test infra they have.
