Hi, I was trying to debug an issue where a low QPS service's host keeps getting traffic even after it goes out of rotation. While debugging I observed that hostdb record for any given origin doesn't get updated unless trafficserver gets a call corresponding to that origin. This happen even when `ttl` field of that origin's hostdb record is negative (`timedout` field having value `yes`).
So, let's say that 1 host of an origin went out of rotation (OOR) at time T seconds, and the first call that the trafficserver got for that origin (after the host going OOR) was at time T + 100 seconds. Since the hostdb records have not been updated up until T + 100, there is a chance that the first call can go to the OOR host. As soon as the first call comes hostdb record for that origin gets updated (by making a call to DNS) and everything works fine next call onwards. As I said earlier this only becomes a problem with services which are having very less QPS. I just wanted to ask if there is a way to overcome this problem so that the hostdb record can be updated every time ttl expires? I tried to work with proxy.config.hostdb.verify_after (by setting it to a low value) - but that didn't solve it for me. Regards, Nishant
