spacewander commented on issue #4941:
URL: https://github.com/apache/apisix/issues/4941#issuecomment-908967424


   I try to reproduce it but fail. Here is my route configuration:
   
   ```
   routes:
     -
       uri: /hello*
       upstream:
           nodes:
               ttl.1s.test.local:1980: 1
           type: roundrobin
   #END
   
   ```
   
   I used coredns and a python script to change DNS configuration each second, 
and the IP rotates from 127.0.0.1 to 127.0.0.8:
   
   ```
   #!/usr/bin/env python3
   # coding: utf-8
   import time
   ip = 0
   serial = 2017042745
   while True:
       ip = (ip % 8) + 1
       tpl = """$ORIGIN test.local.
   @    3600 IN SOA sns.dns.icann.org. noc.dns.icann.org. (
                   %d ; serial
                   7200       ; refresh (2 hours)
                   3600       ; retry (1 hour)
                   1209600    ; expire (2 weeks)
                   3600       ; minimum (1 hour)
                   )
   
       3600 IN NS a.iana-servers.net.
       3600 IN NS b.iana-servers.net.
   
   ttl.1s 1  IN A     127.0.0.%d
       """ % (serial, ip)
       serial += 1
       ip += 1
       with open("./db.test.local", "w") as f:
           f.write(tpl)
       time.sleep(1)
   
   ```
   
   ```
   test.local {
       file db.test.local {
           reload 1s
       }
       log
   }
   ```
   
   Then I loaded test the `/hello` for minutes but nothing found.
   
   I am curious about why the input can bypass the loop check:
   
https://github.com/apache/apisix/blob/a062a9c83bad20672babd0b0b64484220dcac16c/apisix/core/table.lua#L102-L103
   
   Maybe it only happens with special route configuration? What's your route 
configuration?
   And you may need to add more log inside `_deepcopy`.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to