Skip to:
Command “pbm config --force-resync --wait” ends with timeout
Problem description:
In our environment the resync operation takes about 1.5 minute. This command ends with following error after 30 seconds:
Error: waiting for resync [opid "662f43475d9bcd2d16b97b24"]: timeout
On behind in logs I see that commands is still running without issues and it is finished properly after 1.5 minute without any errors.
I have checked code for this function and found out that this 30 seconds timeout is hardcoded for context:
Solution proposal:
This value should be configurable in same way as it is done for backup.timeouts.startingStatus in pbm agent config yaml file.
resync.timeout: 900 (in seconds)
Command “pbm cleanup --wait --older-than 30d --yes” ends with timeout
In our environment the delete operation takes about 2 minutes. This command ends with following error after 1 minute:
Error: read agents log: connection(<fqdn>:27017[-12]) incomplete read of message header: context deadline exceeded"
On behind in logs I see that commands is still running without issues and it is finished properly after 2 minute without any errors.
I have checked code for this function and found out that this 1 minute timeout is hardcoded for context:
delete.timeout: 900 (in seconds)
Hi
Thank you for the report and feedback. We are considering it as an improvement request.
Command “pbm config --force-resync --wait” ends with timeout
Problem description:
In our environment the resync operation takes about 1.5 minute. This command ends with following error after 30 seconds:
Error: waiting for resync [opid "662f43475d9bcd2d16b97b24"]: timeout
On behind in logs I see that commands is still running without issues and it is finished properly after 1.5 minute without any errors.
I have checked code for this function and found out that this 30 seconds timeout is hardcoded for context:
Solution proposal:
This value should be configurable in same way as it is done for backup.timeouts.startingStatus in pbm agent config yaml file.
resync.timeout: 900 (in seconds)
Command “pbm cleanup --wait --older-than 30d --yes” ends with timeout
Problem description:
In our environment the delete operation takes about 2 minutes. This command ends with following error after 1 minute:
Error: read agents log: connection(<fqdn>:27017[-12]) incomplete read of message header: context deadline exceeded"
On behind in logs I see that commands is still running without issues and it is finished properly after 2 minute without any errors.
I have checked code for this function and found out that this 1 minute timeout is hardcoded for context:
Solution proposal:
This value should be configurable in same way as it is done for backup.timeouts.startingStatus in pbm agent config yaml file.
delete.timeout: 900 (in seconds)