mirrors/nomulus
1
0
Fork 0
mirror of https://github.com/google/nomulus synced 2026-01-04 04:04:22 +00:00
Code Issues Releases Wiki Activity

Update documentation about manually creating RDE commands

Browse Source 
-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=144451211
This commit is contained in:
cgoldfeder
2017-01-13 09:34:02 -08:00
committed by Ben McIlwain
parent f30b87d40e
commit 4e34fd53f4
1 changed files with 8 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/operational-procedures/rde-deposits.md
View File

@@ -119,7 +119,7 @@ manually by visiting the following URL:
https://backend-dot-{PROJECT-ID}.appspot.com/_dr/task/rdeStaging
That will spawn a staging task for each TLD under the backend module in that App
Engine project.
Engine project. You can also run the task from the cron tab of the GAE console.
## Notification of upload problems
@@ -185,8 +185,12 @@ ICANN.
## Generating RDE files
You can use the `nomulus` command to generate the RDE files on a per-TLD basis.
Here's an example:
In general RDE files should be regenerated by updating the cursors to before the
desired date and then re-running the mapreduce (either by waiting until the next
scheduled cron execution, or by manually invoking the RDE staging action).
In very rare cases (and only for small TLDs) you can use `nomulus` to generate
the RDE files on a per-TLD basis. Here's an example:
```shell
# Define the tld/date combination.
@@ -245,7 +249,7 @@ $ gsutil cp ${tld}_${date}_full_S1_R0{,-report}.xml.ghostryde gs://{PROJECT-ID}-
If the rdeStaging or rdeUpload tasks are failing and you find yourself needing
to perform this process manually, you must make sure to update the appropriate
cursors. Again, you can use the `nomulus` to perform this operation.
cursors. Again, you can use `nomulus` to perform this operation.
```shell
$ nomulus -e production update_cursors --timestamp=2015-05-21T00:00:00Z --type=RDE_STAGING $tld