anton-vinogradov opened a new pull request, #13785: URL: https://github.com/apache/ignite/pull/13785
[IGNITE-29210](https://issues.apache.org/jira/browse/IGNITE-29210) builds on #13751. The target is `master`, so the PR includes the API changes. [Review the manual reload changes on their own](https://github.com/anton-vinogradov/ignite/compare/ignite-29209...ignite-29210). `control.sh --ssl reload` lets administrators rotate certificates and trust stores without restarting nodes. Discovery, communication, the client connector and binary REST use the replacement for new connections. Existing connections stay open. Transports that share a factory switch together. If a factory rejects a replacement, it keeps its working context. Both `reload` and `status` require `ADMIN_OPS` and report results for each server and client node. Reload checks TLS settings and the dates of reported certificates. A plain `Factory<SSLContext>` can participate by returning a fresh context on reload, but supplies no certificates for date checks or status. Verify peer trust with a new connection. Changing factory settings still requires a restart. Custom `TcpDiscoverySpi` subclasses that used the protected `sslSockFactory` or `sslSrvSockFactory` fields need to adapt and recompile. Local validation passed 23 provider, reload and reconnect cases at `4a7ce7c9`. The CLI case and Checkstyle passed at `756e613f` with one existing JMX skip. This head has no full CI result yet. -- 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]
