hugegraph-sync/.github
KAI de62d97f34
fix(server): configure finite DNS cache TTL (#3126)
1. A Store pod is replaced in Kubernetes and comes back on a new IP behind the
   same stable DNS name.
2. HugeGraph Server runs with `HugeSecurityManager` installed by default.
3. With a `SecurityManager` present and no explicit policy, Java 11 falls back to
   `networkaddress.cache.ttl = -1`, so `InetAddressCachePolicy` is `FOREVER`.
4. The Server therefore keeps resolving the Store name to the old pod IP, and
   HStore writes keep going to an address that no longer exists.
5. Nothing recovers this until the Server process is restarted.

The setting is only honoured as a **security** property. The ordinary
`-Dnetworkaddress.cache.ttl` system property has no effect here, which is why
that form is deliberately not used.

---------

Co-authored-by: imbajin <jin@apache.org>
2026-08-04 21:24:18 +08:00
..
ISSUE_TEMPLATE doc: update issue template & README file (#2131) 2023-02-28 00:16:32 +08:00
configs fix(server): unify the license headers (#2438) 2024-02-07 12:53:57 +08:00
outdated BREAKING CHANGE(server): disable legacy backends include `MySQL/PG/c*`(.etc) (#2746) 2025-04-28 15:20:37 +08:00
workflows fix(server): configure finite DNS cache TTL (#3126) 2026-08-04 21:24:18 +08:00
PULL_REQUEST_TEMPLATE.md docs: update repo artifacts references (#2695) 2024-11-19 00:09:25 +08:00