Best way to handle large number of frequently updated redirects
al-nginx at none.at
Tue Aug 2 10:43:59 UTC 2022
On 02.08.22 00:29, justin_achievable wrote:
> Hi, I'm looking for advice on the best way to handle a fairly large and
> frequently updated list of redirects.
> Basically, I have a CSV file with source, target, and redirect type. There
> are several hundred entries, with updates made about weekly. We expect this
> list to grow quickly into the thousands once we have a process in place.
> From my research, it feels like a redirect map using
> (http://nginx.org/en/docs/http/ngx_http_map_module.html) might be the best
> option. So would the preferred approach be to write a script to process the
> CSV file into an include that works with map, sync the map file to the
> server and reload periodically to pick up on the updated config?
> Any advice would be appreciated.
Well we have done exactly that.
What we have recognized is that a to often reload does not give nginx
the time to kill old childs.
Our solution was to lookup via ps to old process and only run the next
reload when the old process are gone.
> Thank you,
> Justin Pincar
> Posted at Nginx Forum: https://forum.nginx.org/read.php?2,294889,294889#msg-294889
> nginx mailing list -- nginx at nginx.org
> To unsubscribe send an email to nginx-leave at nginx.org
More information about the nginx