Revert it on the release branch and fix it on develop.
> On Sep 4, 2018, at 5:13 PM, Sean Goller <sgol...@pivotal.io> wrote: > > It affects us on any linux platform that doesn't use glibc. It's not worth > holding up the release for. It's been this way for 20 years, right? ;) > > Revert it. > >> On Tue, Sep 4, 2018 at 5:09 PM Udo Kohlmeyer <u...@apache.org> wrote: >> >> Imo (and I'm coming in cold)... We are NOT officially supporting Alpine >> linux (yet), which is the basis for this ticket, maybe push this to a >> later release? >> >> I prefer us getting out the fixes we have and release a more optimal >> version of GEODE-5591 later. >> >> IF this is a bug that will affect us on EVERY linux distro, then we >> should fix, otherwise, I vote to push it to 1.8 >> >> --Udo >> >> >>> On 9/4/18 16:38, Dan Smith wrote: >>> Spitting this into a separate thread. >>> >>> I see the issue. The two minute timeout is the constructor for >>> AcceptorImpl, where it retries to bind for 2 minutes. >>> >>> That behavior makes sense for CacheServer.start. >>> >>> But it doesn't make sense for the new logic in GatewayReceiver.start() >> from >>> GEODE-5591. That code is trying to use CacheServer.start to scan for an >>> available port, trying each port in a range. That free port finding logic >>> really doesn't want to have two minutes of retries for each port. It >> seems >>> like we need to rework the fix for GEODE-5591. >>> >>> Does it make sense to hold up the release to rework this fix, or should >> we >>> just revert it? Have we switched concourse over to using alpine linux, >>> which I think was the original motivation for this fix? >>> >>> -Dan >>> >>>> On Tue, Sep 4, 2018 at 4:25 PM, Dan Smith <dsm...@pivotal.io> wrote: >>>> >>>> Why is it waiting at all in this case? Where is this 2 minute timeout >>>> coming from? >>>> >>>> -Dan >>>> >>>> On Tue, Sep 4, 2018 at 4:12 PM, Sai Boorlagadda < >> sai.boorlaga...@gmail.com >>>>> wrote: >>>>> So the issue is that it takes longer to start than previous releases? >>>>> Also, is this wait time only when using Gfsh to create >> gateway-receiver? >>>>> >>>>>> On Tue, Sep 4, 2018 at 4:03 PM Nabarun Nag <n...@apache.org> wrote: >>>>>> >>>>>> Currently we have a minor issue in the release branch as pointed out >> by >>>>>> Barry O. >>>>>> We will wait till a resolution is figured out for this issue. >>>>>> >>>>>> Steps: >>>>>> 1. create locator >>>>>> 2. start server --name=server1 --server-port=40404 >>>>>> 3. start server --name=server2 --server-port=40405 >>>>>> 4. create gateway-receiver --member=server1 >>>>>> 5. create gateway-receiver --member=server2 `This gets stuck for 2 >>>>> minutes` >>>>>> Is the 2 minute wait time acceptable? Should we document it? When we >>>>> revert >>>>>> GEODE-5591, this issue does not happen. >>>>>> >>>>>> Regards >>>>>> Nabarun Nag >>>>>> >> >>
