GitHub user zwoop opened a pull request:

    https://github.com/apache/trafficserver/pull/521

    TS-4207 Adds better checks to avoid HostDB crashes in 6.x

    As much as I dislike this bandaid fix, it does prevent the crashes that 
we've
    been experiencing since upgrading to 6.1.x. It's also in line with other
    checks for the validity of the rr done in other places. Since the crash is
    rather infrequent (once or twice a day on ~30 machines), it's difficult to
    track down the exact commit that broke this.
    
    But I did run a build that reverted all HostDB changes since 5.3.x and that
    also fixes the crasher. So it's definitely either a fix triggering an old 
bug,
    or a regression.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/zwoop/trafficserver TS-4207

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/trafficserver/pull/521.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #521
    
----
commit 19b233306b89e5e9ad32dc69a957f90f4312b306
Author: Leif Hedstrom <zw...@apache.org>
Date:   2016-03-07T22:34:56Z

    TS-4207 Adds better checks to avoid HostDB crashes in 6.x
    
    As much as I dislike this bandaid fix, it does prevent the crashes that 
we've
    been experiencing since upgrading to 6.1.x. It's also in line with other
    checks for the validity of the rr done in other places. Since the crash is
    rather infrequent (once or twice a day on ~30 machines), it's difficult to
    track down the exact commit that broke this.
    
    But I did run a build that reverted all HostDB changes since 5.3.x and that
    also fixes the crasher. So it's definitely either a fix triggering an old 
bug,
    or a regression.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to