From d88d12b12032009087b30b5eade332f1b2ea9ee8 Mon Sep 17 00:00:00 2001 From: Samuel Merritt Date: Sun, 17 Mar 2013 15:58:06 -0700 Subject: [PATCH] Small clarification to swift-recon section of admin guide. Apparently the use of port 6030 was causing some confusion. Fixes bug 1095474. Change-Id: I0cc71f4733ad91694e015a9b75c3eda080aca6fb --- doc/source/admin_guide.rst | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/doc/source/admin_guide.rst b/doc/source/admin_guide.rst index cdcd48b865..627c95f0ff 100644 --- a/doc/source/admin_guide.rst +++ b/doc/source/admin_guide.rst @@ -328,8 +328,9 @@ periodically on your object servers:: */5 * * * * swift /usr/bin/swift-recon-cron /etc/swift/object-server.conf -Once the recon middleware is enabled a GET request for "/recon/" to -the server will return a json formatted response:: +Once the recon middleware is enabled, a GET request for +"/recon/" to the backend object server will return a +JSON-formatted response:: fhines@ubuntu:~$ curl -i http://localhost:6030/recon/async HTTP/1.1 200 OK @@ -339,6 +340,10 @@ the server will return a json formatted response:: {"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: ========================= ========================================================================================