Documentation #15245
closedDocumenting Civetweb options for Rados Gateway
0%
Description
- Documenting Civetweb options for Rados Gateway
We have many Civetweb options given in this link : https://github.com/civetweb/civetweb/blob/master/docs/UserManual.md
Some times these options are very useful for tuning Civetweb with Rados Gateway .
For example :
- request_timeout_ms :
Timeout for network read and network write operations, in milliseconds. If a client intends to keep long-running connection, either increase this value or (better) use keep-alive messages.
- num_threads 50
Number of worker threads. Civetweb handles each incoming connection in a separate thread. Therefore, the value of this option is effectively the number of concurrent HTTP connections Civetweb can handle.
- access_log_file
Path to a file for access logs. Either full path, or relative to the current working directory. If absent (default), then accesses are not logged.
- error_log_file
Path to a file for error logs. Either full path, or relative to the current working directory. If absent (default), then errors are not logged.
Updated by Vikhyat Umrao about 8 years ago
ceph-users discussion : http://lists.ceph.com/pipermail/ceph-users-ceph.com/2015-September/004407.html
Updated by Vikhyat Umrao about 8 years ago
Now question is how to set them in ceph.conf in [radosgw] section ?
You can do it as given below :
[radosgw] rgw frontends = civetweb request_timeout_ms=<new timeout value in milliseconds> error_log_file=/var/log/radosgw/civetweb.error.log access_log_file=/var/log/radosgw/civetweb.access.log
Updated by Aron Gunn almost 8 years ago
- Status changed from New to In Progress
- Assignee set to Aron Gunn
Updated by Zac Dover over 4 years ago
- Status changed from In Progress to Closed
This bug has been judged too old to fix. This is because either it is either 1) raised against a version of Ceph prior to Luminous, or 2) just really old, and untouched for so long that it is unlikely nowadays to represent a live documentation concern.
If you think that the closing of this bug is an error, raise another bug of a similar kind. If you think that the matter requires urgent attention, please let Zac Dover know at zac.dover@gmail.com.