4.13. Transport LBT-RU Operation Options
For most LBT-RU operation options, there is a corresponding LBT-RM operation option. For more information on how LBT-RU operation options interact and for illustrations, please see the introduction to the transport LBT-RM operation options section.
Two options unique to LBT-RU are transport_lbtru_client_map_size and transport_lbtru_connect_interval.
The illustration below shows the interaction of two more options unique to LBT-RU:
transport_lbtru_acknowledgement_interval and transport_lbtru_client_activity_timeout.
4.13.1. transport_lbtru_acknowledgement_interval (receiver)
For LBT-RU session only. The interval between sending acknowledgements. Each client continually sends acknowledgements to let the source know that the client is still alive. This option affects the transport session underlying the receiver rather than the receiver itself. The transport session uses the value from the first receiver created on the session and ignores subsequent receivers. Refer to Receiver Configuration and Transport Sessions for additional information.
4.13.2. transport_lbtru_activity_timeout (receiver)
For LBT-RU sessions only. The maximum time that an LBT-RU session may be quiescent before it is deleted and an EOS event is delivered for all topics using this transport session. This option affects the transport session underlying the receiver rather than the receiver itself. The transport session uses the value from the first receiver created on the session and ignores subsequent receivers. Refer to Receiver Configuration and Transport Sessions for additional information.
4.13.3. transport_lbtru_client_activity_timeout (source)
The maximum time that an LBT-RU client may be quiescent, i.e. not sending ACKs, before the sender assumes that it is dead and stops sending to it. This option affects the transport session underlying the source rather than the source itself. The transport session uses the value from the first source created on the session and ignores subsequent sources. Refer to Source Configuration and Transport Sessions for additional information.
4.13.4. transport_lbtru_client_map_size (source)
The size of the hash table used to store client information and state. This option affects the transport session underlying the source rather than the source itself. The transport session uses the value from the first source created on the session and ignores subsequent sources. Refer to Source Configuration and Transport Sessions for additional information.
4.13.5. transport_lbtru_coalesce_threshold (source)
The threshold of the maximum number of individual messages that are copied into a single buffer before being sent to the LBT-RU source internals. When used with small messages, this allows LBT-RU to use less memory at the expense of an additional copy operation of the data before being sent. The default value is also the maximum allowable value for Solaris and AIX. For Linux and Microsoft® Windows®, the maximum allowable value is 1023. This option affects the transport session underlying the source rather than the source itself. The transport session uses the value from the first source created on the session and ignores subsequent sources. Refer to Source Configuration and Transport Sessions for additional information.
4.13.6. transport_lbtru_connect_interval (receiver)
For LBT-RU session only. The interval between sending connection requests. This option affects the transport session underlying the receiver rather than the receiver itself. The transport session uses the value from the first receiver created on the session and ignores subsequent receivers. Refer to Receiver Configuration and Transport Sessions for additional information.
4.13.7. transport_lbtru_data_rate_limit (context)
Maximum aggregate transmission rate of all LBT-RU sessions original data for this particular context.
4.13.8. transport_lbtru_datagram_max_size (context)
The maximum datagram size that can be generated for a LBT-RU transport session. The default value is 8192, the minimum is 500 bytes, and the maximum is 65535.
4.13.9. transport_lbtru_maximum_connect_attempts (receiver)
The maximum number of connect attempts to make before this transport session is deleted and an EOS event is delivered for all topics using this transport session. This option affects the transport session underlying the receiver rather than the receiver itself. The transport session uses the value from the first receiver created on the session and ignores subsequent receivers. Refer to Receiver Configuration and Transport Sessions for additional information.
4.13.10. transport_lbtru_rate_interval (context)
Period that LBT-RU rate limiter runs. Reducing period reduces burst intensity, but also increases CPU load.
| Scope: | context |
| Type: | lbm_ulong_t |
| Units: | milliseconds |
| Default value: | 100 |
| When to Set: | Can only be set during object initialization. |
| String value | Integer value | Description |
|---|---|---|
"10" (Integer value as a string.) |
10 |
LBT-RU rate limiter runs every 10 milliseconds. |
"20" (Integer value as a string.) |
20 |
LBT-RU rate limiter runs every 20 milliseconds. |
"50" (Integer value as a string.) |
50 |
LBT-RU rate limiter runs every 50 milliseconds. |
"100" (Integer value as a string.) |
100 |
LBT-RU rate limiter runs every 100 milliseconds. Default for all. |
4.13.11. transport_lbtru_retransmit_rate_limit (context)
Maximum aggregate transmission rate of all LBT-RU sessions retransmissions for this particular context. This should always be less than the value used for original data.
4.13.12. transport_lbtru_sm_maximum_interval (source)
The maximum interval between LBT-RU session messages. In lieu of data being sent, LBT-RU sends session messages to each client to inform them of sequence numbers and to let receivers know that the sender is still transmitting. This option affects the transport session underlying the source rather than the source itself. The transport session uses the value from the first source created on the session and ignores subsequent sources. Refer to Source Configuration and Transport Sessions for additional information.
4.13.13. transport_lbtru_sm_minimum_interval (source)
The minimum interval between LBT-RU session messages. In lieu of data being sent, LBT-RU sends session messages to each client to inform them of sequence numbers and to let receivers know that the sender is still transmitting. This option affects the transport session underlying the source rather than the source itself. The transport session uses the value from the first source created on the session and ignores subsequent sources. Refer to Source Configuration and Transport Sessions for additional information.
4.13.14. transport_lbtru_use_session_id (source)
Flag to indicate whether the application desires LBT-RU to use a session ID or not. Older versions of UM may not understand session IDs with LBT-RU and may not be able to receive LBT-RU transport sessions that include session IDs.