runtime-rs: Adjust VSOCK timeouts for IBM SEL

The default `reconnect_timeout` (3 seconds) was found to be insufficient for
IBM SEL when using VSOCK. This commit updates the timeouts as follows:

- `dial_timeout_ms`: Set to 90ms to match the value used in go-runtime for IBM SEL
- `reconnect_timeout_ms`: Increased to 5000ms based on empirical testing

Signed-off-by: Hyounggyu Choi <Hyounggyu.Choi@ibm.com>
This commit is contained in:
Hyounggyu Choi 2025-05-28 12:45:22 +02:00
parent b7d2973ce5
commit faf5aed965

View File

@ -541,7 +541,7 @@ kernel_modules=[]
# Agent dial timeout in millisecond.
# (default: 10)
dial_timeout_ms = 30
dial_timeout_ms = 90
# Agent reconnect timeout in millisecond.
# Retry times = reconnect_timeout_ms / dial_timeout_ms (default: 300)
@ -550,7 +550,7 @@ dial_timeout_ms = 30
# You'd better not change the value of dial_timeout_ms, unless you have an
# idea of what you are doing.
# (default: 3000)
#reconnect_timeout_ms = 3000
reconnect_timeout_ms = 5000
# Create Container Request Timeout
# This timeout value is used to set the maximum duration for the agent to process a CreateContainerRequest.