LSF_PROXYD_BYPASS

The LSF_PROXYD_BYPASS parameter determines how the mbatchd daemon responds to requests without tokens for LSF rate limiter (lsfproxyd) requests.

The rate limiter is available as of Fix Pack 14.

Syntax

LSF_PROXYD_BYPASS=Y | y | N | n

Description

The rate limiter is managed by the lsfproxyd daemon, which monitors and controls the number of requests and connections that can reach the mbatchd daemon, protecting it from excess requests. For a request to contact mbatchd, it must first obtain a request token from lsfproxyd. After completing the request, the token returns to lsfproxyd. The lsfproxyd daemon distributes tokens in a round-robin fashion, ensuring that each user connection has an fair chance to be served and processed, even under heavy loads.

Requests from root or LSF cluster administrator users are always granted a token. For details on the rate limiter and tokens, see PROXYD_POLICIES in the lsb.params file.

If this parameter is set to LSF_PROXYD_BYPASS=N, the mbatchd daemon rejects requests without a token.

If this parameter is set to LSF_PROXYD_BYPASS=Y, the mbatchd daemon accepts requests without a token.

When the rate limiter is enabled, but LSF_PROXYD_BYPASS=Y, commands run, but with warning messages in the mbatchd daemon log to indicate that the commands ran without tokens. See the LSB_DEBUG_MBD parameter in the lsf.conf file.

For configuration to this parameter to take effect, restart the mbatchd daemon by running badmin mbdrestart.

Running the lsadmin showconf command displays the values for the LSF_PROXYD_HOSTS and LSF_PROXYD_PORT parameters, if set. Running the badmin showconf command displays the values for the LSF_PROXYD_HOSTS, LSF_PROXYD_PORT, LSF_PROXYD_HEARTBEAT_INTERVAL, and LSF_PROXYD_BYPASS values, if set.

Default

N|n

Example

LSF_PROXYD_BYPASS=Y