You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
A replicated restart_service on Harper core alone ends ERROR instead of restarting this node #3508
On Harper core alone, a restart_service with replicated: true runs as a job, and the job's first step (restartService in bin/restart.ts) calls server.replication.monitorNodeCAs() to load the cluster's nodes. Core's replication stand-in (server/Server.ts) throws Replication not implemented. there. So the job ends ERROR before it restarts even this node's workers. harper deploy restart=rolling reaches this path when a deploy is not certified (certification: "unavailable"), and the CLI reference documents the ERROR.
The activation path for a certified rolling deploy already treats the stand-in's error as "no peers" (harper#3502): the stand-ins now throw with code: 'REPLICATION_NOT_IMPLEMENTED'.
Done when
A replicated restart_service on core alone restarts this node and completes, treating REPLICATION_NOT_IMPLEMENTED as a cluster with no other nodes, and the CLI reference no longer says such a job ends ERROR.
Activity