rgw:If the endpoint of the event notification does not respond, the process will be stuck.

[ybwang0211]

rgw:If the endpoint of the event notification does not respond, the process will be stuck.

We use the function of uploading objects and set an event notification for the bucket. However, due to the wrong endpoint setting, the file cannot be uploaded and is stuck all the time without reporting an error.
So we added the CURLOPT_CONNECTTIMEOUT parameter to control the connection timeout.

fix: https://tracker.ceph.com/issues/51855

Signed-off-by: wangyingbin ybwang0211@163.com

Checklist

• References tracker ticket
• Updates documentation if necessary
• Includes tests for new functionality or reproducer for bug

---

Show available Jenkins commands

• jenkins retest this please
• jenkins test classic perf
• jenkins test crimson perf
• jenkins test signed
• jenkins test make check
• jenkins test make check arm64
• jenkins test submodules
• jenkins test dashboard
• jenkins test api
• jenkins test docs
• jenkins render docs
• jenkins test ceph-volume all
• jenkins test ceph-volume tox

[cbodley]

from https://curl.se/libcurl/c/CURLOPT_CONNECTTIMEOUT.html, it sounds like there already is a default connection timeout of 300 seconds

[yuvalif]

from https://curl.se/libcurl/c/CURLOPT_CONNECTTIMEOUT.html, it sounds like there already is a default connection timeout of 300 seconds

300 seconds is probably too high, at least for the case of notifications.
make sense to change that to lower value, but should be don't for the case of notifications, and not in the general case.
see: https://github.com/ceph/ceph/blob/master/src/rgw/rgw_pubsub_push.cc#L138

we should probably also change the HTTP request timeout not the be the default (0 - infinite), to some lower values (5 sec?)
note that notifications are usually small (~1KB), and keeping a small timeout would make sense.

[cbodley]

ping @ybwang0211

[github-actions]

This pull request has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs for another 30 days.
If you are a maintainer or core committer, please follow-up on this pull request to identify what steps should be taken by the author to move this proposed change forward.
If you are the author of this pull request, thank you for your proposed contribution. If you believe this change is still appropriate, please ensure that any feedback has been addressed and ask for a code review.

[github-actions]

This pull request has been automatically closed because there has been no activity for 90 days. Please feel free to reopen this pull request (or open a new one) if the proposed change is still appropriate. Thank you for your contribution!