Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/issues/1335
@jacksontj @vmamidi is working on this, and has a fix (hopefully).
---
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 proj
Github user jacksontj commented on the issue:
https://github.com/apache/trafficserver/issues/1335
@zwoop Where you able to come up with a reproducible case for this? I'm
going to try and take a look this week-- it'd be easier if I had a repro method
:)
---
If your project is set up
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/issues/1335
@randall reports that this happens with sync off as well :-/
---
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 do
GitHub user zwoop opened an issue:
https://github.com/apache/trafficserver/issues/1335
Deadlock in HostDB
We have some 7.0.0 boxes, which ends up completely wedged, where all ET_NET
threads get stuck on the same lock (so, a deadlock):
```
#6 HostDBProcessor::getbyname_