imbajin opened a new pull request, #3303:
URL: https://github.com/apache/hugegraph/pull/3303

   Store can close its databases while scans, RPC callbacks or TTL workers 
still own native resources. This change closes admission, cancels active work 
and drains its owners before storage shutdown. Request half-close remains 
distinct from transport cancellation, final batches are retained, cleanup 
failures stay visible, and interrupted Raft joins finish before teardown 
continues.
   
   Client response parsing now runs outside the short state lock. Early 
iterator close cancels the transport without waiting for a blocked request 
send; normal half-close remains serialized. Client and server changes stay 
together so their cancellation/feedback behavior agrees. Tests, 
plain/executable Node artifact packaging and lifecycle CI registration 
accompany the functionality.
   
   Split from hugegraph/hugegraph#261 and ASF #3294. Org review: 
https://github.com/hugegraph/hugegraph/pull/280. Based directly on current 
master, independent of the Server transaction split. Scan cancellation and 
shutdown share the same owner registry and drain barrier; separating them would 
leave an unsafe intermediate shutdown path and duplicate lifecycle wiring. 
Required packaging/test changes therefore stay here rather than forming a 
separate build PR.
   
   Validation: independent diff review, formatting and `git diff --check` pass. 
Java 17 PD/Store packaging passes. Focused client, Scan/partition/barrier, 
aggregate-query, shutdown/TTL/Raft and native-iterator regressions pass using 
the reactor classpath; shutdown coverage includes an isolated JNI subprocess. 
JaCoCo and stop-script contracts pass. Full reactor CI, real Store process 
stop/restart checks and master-versus-candidate benchmarks are still being 
completed. No throughput improvement or full CI pass is claimed.
   
   Doc - Done: `docs/store-lifecycle.md` and Store README shutdown instructions.
   


-- 
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]

Reply via email to