Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[fix]Remove config cache #4301

Merged
merged 1 commit into from
Aug 23, 2022
Merged

[fix]Remove config cache #4301

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 6 additions & 7 deletions src/gateway/kong-production/deployment-topologies/hybrid-mode/hybrid-mode-setup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -477,7 +477,7 @@ kong:{{page.kong_versions[page.version-index].ce-version}}-alpine
: The tag of the {{site.base_gateway}} image that you're using, and the Docker network it communicates on.

`KONG_CLUSTER_CONTROL_PLANE`
: Sets the address and port of the control plane (port `8005` by defaut).
: Sets the address and port of the control plane (port `8005` by default).

`KONG_DATABASE`
: Specifies whether this node connects directly to a database.
Expand Down Expand Up @@ -634,16 +634,15 @@ The output shows all of the connected data plane instances in the cluster:
When set as a DP node, {{site.base_gateway}} processes configuration in the
following order:

1. **Config cache**: If the file `config.json.gz` exists in the `kong_prefix`
path (`/usr/local/kong` by default), the DP node loads it as configuration.
2. **`declarative_config` exists**: If there is no config cache and the
1. **Config cache**: If the file `dbless.lmdb` exists in `/usr/local/kong`, the DP node loads it as configuration.
1. **`declarative_config` exists**: If there is no config cache and the
`declarative_config` parameter is set, the DP node loads the specified file.
3. **Empty config**: If there is no config cache or declarative
1.**Empty config**: If there is no config cache or declarative
configuration file available, the node starts with empty configuration. In this
state, it returns 404 to all requests.
4. **Contact CP Node**: In all cases, the DP node contacts the CP node to retrieve
1.**Contact CP Node**: In all cases, the DP node contacts the CP node to retrieve
the latest configuration. If successful, it gets stored in the local config
cache (`config.json.gz`).
cache (`dbless.lmdb`).

### Configuration reference

Expand Down