From: Yuval Lifshitz Date: Wed, 10 Apr 2019 16:32:02 +0000 (+0300) Subject: rgw/pubsub: fix comments from PR #27493 X-Git-Tag: v15.1.0~2931^2~1 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=cb256dd92ac39baddce252acb634b587653da4f3;p=ceph.git rgw/pubsub: fix comments from PR #27493 Signed-off-by: Yuval Lifshitz --- diff --git a/doc/radosgw/pubsub-module.rst b/doc/radosgw/pubsub-module.rst index b61752d5893b..116541ffd147 100644 --- a/doc/radosgw/pubsub-module.rst +++ b/doc/radosgw/pubsub-module.rst @@ -41,7 +41,7 @@ PubSub Zone Configuration The pubsub sync module requires the creation of a new zone in a `Multisite`_ environment. First, a master zone must exist (see: :ref:`master-zone-label`), then a secondary zone should be created (see :ref:`secondary-zone-label`). -None that, When doing the actual creation of the secondary zone zone, its tier type must be set to ``pubsub``: +In the creation of the secondary zone, its tier type must be set to ``pubsub``: :: @@ -84,8 +84,8 @@ The oid prefix for the stored events. How many days to keep events that weren't acked. -How to Configure? -~~~~~~~~~~~~~~~~~ +Configuring Parameters via CLI +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The tier configuration could be set using the following command: @@ -95,8 +95,8 @@ The tier configuration could be set using the following command: --rgw-zone={zone-name} \ --tier-config={key}={val}[,{key}={val}] -Where the ``key`` in the configuration specifies the configuration variable that needs to be updated, and -the ``val`` specifies its new value. Nested values can be accessed using period. For example: +Where the ``key`` in the configuration specifies the configuration variable that needs to be updated (from the list above), and +the ``val`` specifies its new value. For example, setting the pubsub control user ``uid`` to ``user_ps``: :: @@ -119,11 +119,13 @@ PubSub Performance Stats .. note:: ``pubsub_event_triggered`` and ``pubsub_event_lost`` are incremented per event, while: - ``pubsub_store_ok``, ``pubsub_store_fail``, ``pubsub_push_ok``, ``pubsub_push_fail``, are incremented per store/push action on each subscription + ``pubsub_store_ok``, ``pubsub_store_fail``, ``pubsub_push_ok``, ``pubsub_push_fail``, are incremented per store/push action on each subscriptions. PubSub REST API --------------- +.. tip:: PubSub REST calls, and only them, should be sent to an RGW which belong to a PubSub zone + Topics ~~~~~~