imbajin commented on PR #3130:
URL: https://github.com/apache/hugegraph/pull/3130#issuecomment-5289870090
## Final refactor and Kubernetes validation
The refactor is now on exact head
`18ca057856684ff09ab8ac46951d30de84c0aca7`.
The implementation removes the PR's custom DNS fingerprint/polling and
whole-pool refresh machinery. It keeps the stable Store FQDN, lets gRPC own
resolution/reconnect, and fixes the HugeGraph boundary that the earlier A/B
run
identified: an `UNAVAILABLE` retry now invalidates the exact failed
node/target
and replaces the cached session when the same Store ID belongs to a new node
instance.
Measured exact `master + PR` result:
```text
Store: same ID + same FQDN + same PVC
Pod UID changed, IP 192.168.194.19 -> 192.168.194.20
Server: same Pod UID + PID + process start time, restart=0
Write started while replacement Store was not Ready
-> old endpoint failed with UNAVAILABLE
-> same HTTP request returned 201 after ~31s
-> final scan observed 1 matching uniquely identified vertex
-> post-recovery write/delete passed
-> 10/10 subsequent scans returned 200
```
Verification:
- Java 11 Store client suite: 9/9 passed.
- Compile, EditorConfig, Checkstyle, Apache RAT, and `git diff --check`:
passed.
- Exact-merge Docker build: 38/38 modules passed.
- Six independent code-review lanes completed; the one reproducible
same-transaction session race was fixed with a local atomic cache
transition
and passed three affected re-reviews.
- The isolated namespace, PVC/PV, and test image were removed; the
pre-existing
3 PD + 3 Store cluster retained the same Pod UIDs, restart counts, and
PVCs.
This result intentionally does not claim new cross-process exactly-once
commit
semantics. It is scoped to bounded recovery after Store replacement.
The earlier `192.168.194.10 -> .12` / HTTP 500 result in the previous comment
was the pre-refactor failing run. The `192.168.194.19 -> .20` / HTTP 201
result
above is a separate run built from exact head `18ca057856`.
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
