JobGateway Common Parameters
Configuration Page
To go to the JobGateway configuration page, refer to Modifying Cluster Service Configuration Parameters.
Parameters
Parameter |
Description |
Default Value |
---|---|---|
HTTP_INSTANCE_PORT |
HTTP port of the JobServer service. |
Default value: 29973 Value range: 29970 to 29979 |
HTTPS_INSTANCE_PORT |
HTTPS port of the JobServer service. |
Default value: 29972 Value range: 29970 to 29979 |
JAVA_OPTS |
JVM parameter used for garbage collection (GC). Ensure that GC_OPT is correctly set. Otherwise, the process will fail to start. |
See the default configuration on the page. |
job.record.batch.delete.count |
25 |
Number of aged data records in each batch on JobServers |
job.record.expire.count |
500000 |
Number of aged JobServer data records |
job.record.expire.day |
7 |
Number of days after which a JobServer job expires |
logging.level.org.apache.tomcat |
Log level of Tomcat logs on the JobServer server. |
Default value: INFO Value range: DEBUG, INFO, WARN, ERROR, or FATAL |
root.level |
Level of logs on the JobServer server. |
Default value: INFO Value range: DEBUG, INFO, WARN, ERROR, or FATAL |
NGINX_PORT |
Communication port of the JobBalancer service. |
Default value: 29970 for HTTPS and 29971 for HTTP Value range: 29970 to 29979 |
client_body_buffer_size |
Buffer size for reading client request body data. If the request body is larger than the buffer, the entire body or only part of it is written to the temporary file. |
Default value: 10240 Value range: greater than 0 |
client_body_timeout |
Timeout interval for reading the client request body, in seconds. The timeout is set only for a period of time between two consecutive read operations, not for the transmission of the entire request body. If the client does not transmit any content within this period, the request is terminated and a 408 (request timeout) error occurs. |
Default value: 60 Value range: 1 to 86400 |
client_header_buffer_size |
Buffer size for reading client request headers. For most requests, a buffer of 1 KB is sufficient. However, if a request includes long cookies or comes from a WAP client, 1 KB may not be appropriate. If the request line or request header field is not suitable for this buffer, a larger buffer configured by the large_client_header_buffers directive is allocated. |
Default value: 1024 Value range: greater than 0 |
client_header_timeout |
Timeout interval for reading the client request header. If the client does not transmit the entire header during this period, the request is terminated and a 408 (request timeout) error occurs. |
Default value: 60 Value range: 1 to 86400 |
client_max_body_size |
Maximum size of an HTTP request body, in MB. |
Default value: 80 Value range: 1 to 10240 |
keepalive_requests |
Maximum number of requests that can be served through a keepalive connection. After the maximum number of requests is sent, the connection is closed. Closing connections periodically is necessary to free up the memory allocation for each connection. Using a high maximum number of requests may cause excessive memory usage. Therefore, this method is not recommended. |
Default value: 1000 Value range: 1 to 100000 |
keepalive_time |
Maximum time during which requests can be processed through one keepalive connection, in seconds. After the time specified by this parameter is reached, the connection is closed after subsequent requests are processed. |
Default value: 3600 Value range: 1 to 86400 |
keepalive_timeout |
Timeout during which an idle keepalive connection to an upstream server will stay open. The value 0 disables keepalive client connections. |
Default value: 75 Value range: 0 to 86400 |
large_client_header_buffers.size |
Maximum number (large_client_header_buffers.number) and size of buffers used to read large client request headers. A request line cannot exceed the size of one buffer. Otherwise, error 414 (Request-URI Too Large) is returned to the client. A request header field cannot exceed the size of one buffer as well. Otherwise, error 400 (Bad Request) is returned to the client. Buffers are allocated only on demand. These buffers are released if a connection is transitioned into the keepalive state after the request processing is complete. |
Default value: 4096 Value range: greater than 0 |
lb_limit_req_burst |
When a large number of requests are sent, the requests that exceed the access frequency limit are stored in the buffer, and error 503 is returned if the requests exceed the buffer size. |
Default value: 50 Value range: 1 to 1000 |
lb_limit_zone_rate |
Rate limit on HTTP requests of clients with the same ID, in r/s or r/m. For example, 30r/s indicates that 30 access requests are allowed per second. |
Default value: 30r/s Value range: 1 to 100 r/s or 1 to 6000 r/min |
lb_limit_zone_size |
Size of the HTTP memory buffer, in MB |
Default value: 20 Value range: 1 to 10240 |
lb_req_timeout |
Timeout interval for Nginx read/write. |
Default value: 60s Value range: 1 to 3600s |
proxy_connect_timeout |
Timeout interval for setting up a TCP connection with the proxy server. The value is a combination of numbers and units. m indicates minutes and s indicates seconds. |
Default value: 3m Value range: 1 to 60 min or 1 to 3600s |
proxy_timeout |
Timeout between two consecutive read or write operations on a TCP connection to the proxy server. If no data is transmitted within this period, the connection is closed. The value is a combination of numbers and units. m indicates minutes and s indicates seconds. |
Default value: 3m Value range: 1 to 60 min or 1 to 3600s |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot