Hi I am in process of upgrading Kong docker instances to 0.12.2 from 0.10.3. Have completed upgrading in my test environment, noticed some changes, for ex in 0.10.3 if Cassandra would not be running , proxy port 8000 would still function from cache but this doesnt seem to be the case in 0.12.2. I have two Kong instances in test lets say A & B using same common cassandra db on A , if db goes down i have seen both Kong A & B proxy ports error out or sometimes proxy port on B will work for some time before it errors out. I am assuming this has something to do with removed SERF dependency since version 0.11, and constant polling of DB( Architecture step forward or backward?). what would be ways to avoid proxy port stop functioning? running multiple cassandra instances in their own cluster and pointing Kong instances to these cassandra instances? do these variables db_update_propogation etc help?
Related Topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| High x-kong-proxy-latency | 1 | 834 | February 4, 2019 | |
| Kong timeouts at start up | 2 | 725 | December 15, 2017 | |
| Kong + nginx proxy manager | 0 | 431 | November 20, 2022 | |
| Route Caching and Latency | 4 | 1191 | April 23, 2018 | |
| Kong Container limiting number of connections | 0 | 376 | October 4, 2021 |