Daniel Hilst
5ac62ebb51
The install monitor holds the later connections for a node whose handler is still running, and forks the next one when it reaps that handler. SIGCHLD is what brings the parent back to look: it interrupts the accept. A handler can exit after the parent checks its queue and before the accept begins. The signal is then handled where there is no accept to interrupt, and the parent blocks in accept with a connection already queued and ready to run. That connection waits until some other node calls in. A single node retrying on its own waits until it times out. do_installm_service now waits through wait_for_installm_connection, which selects on the listening socket. The wait is bounded by $installm_wakeup_seconds while connections are queued, so the parent looks at its queue again instead of waiting for another client. An idle monitor with an empty queue still waits without a bound, because a handler that exits then leaves nothing to do. The new case asserts the wait ends on its own bound with nothing to accept, and ends at once when a connection is already there. It fails when the bound is ignored. Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
xCAT
xCAT is a toolkit for deployment and administration of clusters of all sizes.
The xCAT sunset was only a quick eclipse
Dear xCAT Community,
The xCAT sunset has changed course. VersatusHPC has been invited to join the xCAT Consortium, and future development will move toward direct upstream contributions coordinated with the Consortium and its existing member companies.
That matters most for Enterprise Linux 10 (EL10). EL10 support is coming to xCAT, restoring a future operating-system path for sites that still rely on xCAT. This is an important change from the previous sunset guidance, where the lack of an EL10 path was one of the strongest reasons to move away from xCAT.
The xCAT Consortium continues to recommend Confluent as the long-term successor to xCAT, and that remains the Consortium position. Users planning new cluster-management deployments should evaluate Confluent and its xCAT comparison documentation.
At the same time, xCAT is no longer sunsetted. The Consortium and participating companies will continue updating xCAT while there is community and user demand for it.
In summary:
- xCAT development is continuing upstream through the Consortium and participating companies.
- Enterprise Linux 10 support is coming.
- Confluent remains the Consortium-recommended successor and migration path.
- xCAT updates will continue while there is community and user demand.
We want to thank the xCAT Consortium and community for keeping this project moving. The sun went behind the moon for a moment, but xCAT is still here.
For more information on Confluent and how to get started, please visit the Confluent: Project Page, Documentation or Confluent vs xCAT comparison.
With thanks,
The xCAT Consortium
Documentation
xCAT Documentation is hosted on Read The Docs: https://xcat-docs.readthedocs.io
Status
| xCAT Version | Build Status |
|---|---|
| Latest (master branch) | |
| Stable (latest release) |
Looking for older versions?
Open Source License
xCAT is made available under the EPL license: https://opensource.org/licenses/eclipse-1.0.php
Developers
Want to help? Check out the developers guide!