openstack/swift
Code Issues Proposed changes

Small clarification to swift-recon section of admin guide.

Browse Source 
Apparently the use of port 6030 was causing some confusion.

Fixes bug 1095474.

Change-Id: I0cc71f4733ad91694e015a9b75c3eda080aca6fb
This commit is contained in:
Samuel Merritt 2013-03-17 15:58:06 -07:00
parent c2f8f00a3e
commit d88d12b120
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/source/admin_guide.rst
View File

@ -328,8 +328,9 @@ periodically on your object servers::
*/5 * * * * swift /usr/bin/swift-recon-cron /etc/swift/object-server.conf */5 * * * * swift /usr/bin/swift-recon-cron /etc/swift/object-server.conf
Once the recon middleware is enabled a GET request for "/recon/<metric>" to Once the recon middleware is enabled, a GET request for
the server will return a json formatted response:: "/recon/<metric>" to the backend object server will return a
JSON-formatted response::
fhines@ubuntu:~$ curl -i http://localhost:6030/recon/async fhines@ubuntu:~$ curl -i http://localhost:6030/recon/async
HTTP/1.1 200 OK HTTP/1.1 200 OK
@ -339,6 +340,10 @@ the server will return a json formatted response::
{"async_pending": 0} {"async_pending": 0}
Note that the default port for the object server is 6000, except on a
Swift All-In-One installation, which uses 6010, 6020, 6030, and 6040.
The following metrics and telemetry are currently exposed: The following metrics and telemetry are currently exposed:
========================= ======================================================================================== ========================= ========================================================================================