feat(worker,gateway): report record-info pin outcome in WorkerReady; drain-thread completion tests
The worker logged its MXSTATUS_PROXY record-info pin outcome only to its own stderr, which the gateway's launcher does not capture, so operators never saw whether the pin took. - Contract (additive, internal IPC): WorkerReady.record_info_pin_status = 5. No protocol version bump; an older peer ignores it or sends it empty. Regenerated Contracts/Generated, the client protoset, the Rust vendored proto, and the Go/Python/Java worker bindings (real delta only). - Worker: the handshake copies MxStatusProxyRecordInfoPin.Status into WorkerReady unless the runtime already set it. - Gateway: WorkerClient records it (IWorkerClient.RecordInfoPinStatus, default null) and logs it at Information when pinned, Warning otherwise; empty is not logged. Shown as "Record-info pin" in the dashboard session details Worker table via DashboardSessionSummary.WorkerRecordInfoPinStatus. - Tests: drain-thread cancellation (task ends Canceled; RunAsync cancels, runtime disposed, thread exits, no EventDrain stop-failure log) and fault (exception on the thread faults RunAsync with the same instance) paths; WorkerReady carries the pin status; gateway logging/recording and the dashboard projection. - Docs: gateway.md STA thread model (drain thread, pin step in COM lifetime), MxAccessWorkerInstanceDesign, GatewayProcessDesign, GatewayDashboardDesign, WorkerFrameProtocol.
This commit is contained in:
@@ -500,10 +500,12 @@ microsecond. Measured at ~240 events/s on the dev box, worker CPU fell from 67%
|
||||
with the pin alone.
|
||||
|
||||
The pin only warms a cache. It changes no MXAccess behaviour, and a failure is never fatal. The
|
||||
outcome is in `MxStatusProxyRecordInfoPin.Status`, and the worker logs it as `WorkerRecordInfoPin`
|
||||
just before `WorkerReady`. Worker logs go to stderr, which the gateway does not redirect, so the
|
||||
line lands wherever the host captures the gateway's stderr (the NSSM stderr log on deployed
|
||||
boxes).
|
||||
outcome is in `MxStatusProxyRecordInfoPin.Status`. During the handshake `WorkerPipeSession` logs it
|
||||
as `WorkerRecordInfoPin` and copies it into `WorkerReady.record_info_pin_status`, unless the runtime
|
||||
already filled that field. The copy is the one operators see: the worker's own log goes to stderr,
|
||||
which the gateway's launcher does not redirect. The gateway logs the reported status (Warning when
|
||||
it is not a successful pin) and shows it on the dashboard's session details page; see
|
||||
`GatewayProcessDesign.md`.
|
||||
|
||||
If COM creation fails, the worker should send a structured fault with:
|
||||
|
||||
@@ -602,7 +604,9 @@ CLR thread pool:
|
||||
- It blocks on the frame writer's batch write.
|
||||
- `RunEventDrainLoopAsync` starts the thread and returns a task that completes,
|
||||
faults or cancels exactly as the loop does, so the message loop's `Task.WhenAny`
|
||||
supervision is unchanged.
|
||||
supervision is unchanged. Cancelling the session ends the task Canceled, which
|
||||
teardown treats as a clean stop; an exception thrown on the thread faults the task
|
||||
with that same exception, which ends `RunAsync` with it as the async loop did.
|
||||
|
||||
The reason is .NET Framework's thread pool. As an async loop, every enqueue's
|
||||
semaphore release queued a continuation to the pool, and each pool worker that ran
|
||||
|
||||
Reference in New Issue
Block a user