Skip to content
This repository was archived by the owner on Jan 24, 2025. It is now read-only.

Commit

Permalink
Fixed SW QoS doc to use getClusterNodes (#578)
Browse files Browse the repository at this point in the history 
The QUIC tpu port number was incorrectly listed in
the docs. This change tells the user to get the
QUIC tpu port from the getClusterNodes RPC call.
  • Loading branch information
@tigarcia
tigarcia authored Oct 21, 2024
1 parent c050fd3 commit 91dbe8d
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions content/guides/advanced/stake-weighted-qos.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -140,9 +140,8 @@ On the RPC you will have to use `--rpc-send-transaction-tpu-peer` to forward
transactions to a specific leader. The exact usage would be
`--rpc-send-transaction-tpu-peer HOST:PORT`. The Host is the ip address of the
leader you have the `staked-nodes-overrides` enabled on and the Port is the QUIC
TPU port of that host. The QUIC TPU port number is the lowest value of your
`--dynamic-port-range` plus 9. For example, if the flag is
`--dynamic-port-range 8000-8100`, the QUIC TPU port is `8009`.
TPU port of that host. The QUIC TPU port for a leader can be identified by
making an RPC call to [getClusterNodes](/docs/rpc/http/getClusterNodes.mdx).

The peering would looking like the following:

Expand Down

0 comments on commit 91dbe8d

Please sign in to comment.