Allocating a port by IPC Broker
IPC Broker allocates the port for itself using a value in the [port] setting. If you want IPC Broker to always allocate a specific port to a sidecar, configure the following setting in the [ipc_broker] stanza in the server.conf file:
<splunkd_helper_process_name>:<service_name>:address = <value>
where:
-
splunkd_helper_process_nameis the process name of the sidecar. For process names of sidecars, see the Process name column in the No Content found for /db/organizations/splunk/repositories/splunk-10_4/content/documents/Platform/Shared/Splunk_Sidecars/Sidecarconfigurationsettings/Sidecarconfigurationsettings.dita table. -
service_nameis the name of a service exposed by a sidecar. Each sidecar can have any number of services. Each service has to have a unique name. IPC broker allocates a specific port to each service. -
valueis the IPC address, in this case a TCP/IP network port, that the sidecar service uses to serve incoming requests. The valid port range is from 1024 to 65535.
If this setting is not configured, then IPC Broker assigns a random available port to the sidecar.
In this example:
-
IPC Broker is allocated the port 8194 using the
portsetting. -
Storage is allocated the ports 5432, 5433, 5434, 8008, 6432, 5435, 2380, and 2379 using the
<splunkd_helper_process_name>:<service_name>:addresssettings.
//server.conf
[ipc_broker]
port = 8194
postgres:postgres:address = 5432
postgres:postgres-primary:address = 5433
postgres:postgres-replica:address = 5434
postgres:patroni:address = 8008
postgres:pgbouncer:address = 6432
postgres:postgres_nanny:address = 5435
nascent:etcd_peer:address = 2380
nascent:etcd_client:address = 2379