forked from lei.chen/myxce
d3a92f1033
Phase 3 (B1 dual-state + B2): a job never lingers as RUN when its worker is lost. Dual-state B1 (user-approved): RDHUP (worker TCP dropped = confirmed dead) marks its RUN jobs EXIT immediately (mark_worker_jobs_exit). Heartbeat timeout (unknown) keeps them UNKWN+TRANSIENT awaiting reconnect reconciliation; the TRANSIENT TTL GC is the backstop. handle_worker_leave now calls mark_worker_jobs_exit (was mark_worker_jobs_unknown in Phase 2). B2 (worker side): resend_job_status now checks the recovered process is alive (kill(pid,0)) before re-reporting RUN — a dead process is reported finished so the controller converges to EXIT instead of a stale RUN. And resend_job_status runs on EVERY rejoin (checking_connection), not just startup, so a reconnecting worker's jobs are reconciled (clears UNKWN via the existing notify_jobstart claim path). Design: docs/Job-Finish-Robustness-设计文档.md §4.4 (dual-state decision). Unit test: worker RDHUP marks jobs EXIT (not UNKWN). |
||
|---|---|---|
| .. | ||
| conf | ||
| include | ||
| scripts | ||
| src | ||
| CLAUDE.md | ||
| meson.build | ||
| README.md | ||
Cross-Platform Xcecd Process
This is a cross-platform process manager implementation in C that supports both Linux and Windows platforms. The xcecd provides the following features:
- Sending status to the remote controller module at port 6789 and receive job requests
- Maintains a configurable thread pool for request processing
- Periodically collects and updates system resource status
- Manages child processes spawned from received commands
- Caches job status information
- Uses Unix Domain Sockets for communication between the main process and worker processes
Building
Prerequisites
- C compiler with C11 support
- Windows: Visual Studio
- Linux: GCC and development tools
Build Instructions
On Linux
make
On Windows
nmake
Configuration
The xcecd can be configured through the following parameters in main.c:
thread_pool_size: Number of threads in the thread pool (default: 4)resource_update_interval: Interval for updating system resource status in seconds (default: 1)job_status_update_interval: Interval for updating job status in seconds (default: 1)port: Port number to listen on (default: 7869)acct_file_path: Path to the accounting file (default:/tmp/xcecd.acct)log_file_path: Path to the log file (default:/tmp/xcecd.log)domain_sock_path: Path to the Unix Domain Socket file (default:/tmp/xcecd.sock)remote_host: Remote server address (default:lchen02)remote_port: Remote server port (default: 6789)update_interval: Interval for sending status updates to the remote server (default: 1 second)
Usage
Starting the Xcecd
On Windows:
xcecd.exe
On Linux:
./xcecd
Features
-
Cross-Platform Support
- Works on both Windows and Linux
- Abstracts platform-specific implementations
-
Thread Pool
- Configurable number of worker threads
- Efficient request handling
-
System Monitoring
- CPU usage monitoring
- Memory usage monitoring
- Disk space monitoring
-
Process Management
- Spawns child processes for received commands
- Tracks process status
- Manages process lifecycle
-
Network Communication
- TCP socket-based communication
- Simple text-based protocol
-
Unix Domain Socket Communication
- Uses Unix Domain Sockets for communication between the main process and worker processes
Architecture
The xcecd is composed of several key components:
- Main Process: Coordinates all components and manages the lifecycle
- Thread Pool: Handles concurrent request processing
- System Monitor: Collects and updates system resource information
- Process Manager: Manages child processes and their status
- Network Handler: Handles network communication and request receiving
- Resource Sync: Synchronizes and aggregates resource collection thread, system monitor, and job information
Contributing
Feel free to submit issues and enhancement requests!