Aller au contenu principal

Get-ZrClientRouting

Reports that client routing state cannot be collected through the Management Service. Client routing is process-local to a connected client, so this cmdlet is a diagnostic placeholder that always fails with an explanatory error rather than returning a snapshot.

Syntax​

Get-ZrClientRouting
[-StoreName <string>]
[-Managers <string[]>] [-Port <int>] [-Token <string>] [-TimeoutSec <int>]

Description​

A Zaris client's routing table — which node currently owns each partition — lives inside the client process that built it from the live partition map. It is not exposed through the Management Service, so there is no remote snapshot for this cmdlet to gather. Get-ZrClientRouting therefore always throws, with the message:

Get-ZrClientRouting remains process-local and is not exposed through ManagementService.

To inspect routing, look at it from within the client process instead (for example, from the application or Clustron.Zaris.ClientShell session that holds the connection). For server-side ownership, use Get-ZrPartitionMap and Get-ZrPartitionRuntime.

Parameters​

ParameterTypeRequiredDescription
-StoreNamestringNoStore whose client routing was requested. Accepted for symmetry with other diagnostics cmdlets, but the command does not collect a snapshot.
-Managersstring[]NoManagement Service endpoints (host, host:port, or URL) to target. When omitted, the active workspace's managers are used.
-PortintNoManagement Service port for bare-host managers. Default 7801.
-TokenstringNoAdmin bearer token for authenticated control-plane calls.
-TimeoutSecintNoPer-request timeout in seconds. Default 30.

Examples​

Attempt to collect client routing for the orders store; the command reports that routing is process-local and not exposed through the Management Service.

Get-ZrClientRouting -StoreName orders