mirror of
https://github.com/google/nomulus.git
synced 2025-04-30 12:07:51 +02:00
Readability nits
Minor readability nits ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=135726729
This commit is contained in:
parent
049c636966
commit
27ec47051e
1 changed files with 9 additions and 9 deletions
|
@ -79,11 +79,11 @@ https://tools-dot-project-id.appspot.com, like `/_dr/task/refreshAllDomains`.
|
||||||
Engine provide an asynchronous way to enqueue tasks and then execute them on
|
Engine provide an asynchronous way to enqueue tasks and then execute them on
|
||||||
some kind of schedule. There are two types of queues, push queues and pull
|
some kind of schedule. There are two types of queues, push queues and pull
|
||||||
queues. Tasks in push queues are always executing up to some throttlable limit.
|
queues. Tasks in push queues are always executing up to some throttlable limit.
|
||||||
Tasks in pull queues remain there indefinitely until the queue is polled by code
|
Tasks in pull queues remain there until the queue is polled by code that is
|
||||||
that is running for some other reason. Essentially, push queues run their own
|
running for some other reason. Essentially, push queues run their own tasks
|
||||||
tasks while pull queues just enqueue data that is used by something else. Many
|
while pull queues just enqueue data that is used by something else.
|
||||||
other parts of App Engine are implemented using task queues. For example, [App
|
Many other parts of App Engine are implemented using task queues. For example,
|
||||||
Engine cron](https://cloud.google.com/appengine/docs/java/config/cron) adds
|
[App Engine cron](https://cloud.google.com/appengine/docs/java/config/cron) adds
|
||||||
tasks to push queues at regularly scheduled intervals, and the [MapReduce
|
tasks to push queues at regularly scheduled intervals, and the [MapReduce
|
||||||
framework](https://cloud.google.com/appengine/docs/java/dataprocessing/) adds
|
framework](https://cloud.google.com/appengine/docs/java/dataprocessing/) adds
|
||||||
tasks for each phase of the MapReduce algorithm.
|
tasks for each phase of the MapReduce algorithm.
|
||||||
|
@ -159,10 +159,10 @@ explicitly marked as otherwise.
|
||||||
`SyncGroupMembersAction`.
|
`SyncGroupMembersAction`.
|
||||||
* `load[0-9]` -- Queues used to load-test the system by `LoadTestAction`.
|
* `load[0-9]` -- Queues used to load-test the system by `LoadTestAction`.
|
||||||
These queues don't need to exist except when actively running load tests
|
These queues don't need to exist except when actively running load tests
|
||||||
(which is not recommended on production environments). There are ten of
|
(running load tests on production environments is not recommended). There
|
||||||
these queues to provide simple sharding, because Nomulus is capable of
|
are ten of these queues to provide simple sharding, because Nomulus is
|
||||||
handling significantly more Queries Per Second than the highest throttle
|
capable of handling significantly more Queries Per Second than the highest
|
||||||
limit available on task queues (which is 500 qps).
|
throttle limit available on task queues (which is 500 qps).
|
||||||
* `lordn-claims` and `lordn-sunrise` -- Pull queues for handling LORDN
|
* `lordn-claims` and `lordn-sunrise` -- Pull queues for handling LORDN
|
||||||
exports. Tasks are enqueued synchronously during EPP commands depending on
|
exports. Tasks are enqueued synchronously during EPP commands depending on
|
||||||
whether the domain name in question has a claims notice ID.
|
whether the domain name in question has a claims notice ID.
|
||||||
|
|
Loading…
Add table
Reference in a new issue