Mirror from bluesky-social/pds
Fix cursor readme (#319)
* add desync fix to readme
* reorder steps
authored by
Alex Garnett
and committed by
GitHub
660b2354
0b5cd117
+35
+35
README.md
+35
README.md
···
34
34
- [Updating your PDS](#updating-your-pds)
35
35
- [Environment Variables](#environment-variables)
36
36
- [Migrating your PDS](#migrating-your-pds)
37
+
- [Fixing a Relay desync](#fixing-a-relay-desync)
37
38
- [License](#license)
38
39
39
40
<!-- tocstop -->
···
356
357
This means that if you wipe and reinstall your PDS on the same hostname, or move it to a new hostname without performing the appropriate cutover steps, the PDS and Relay can go out of sync.
357
358
358
359
To avoid this, you should always [migrate accounts individually](https://atproto.com/guides/account-migration) from one PDS to another when updating your PDS host configuration.
360
+
361
+
### Fixing a Relay desync
362
+
363
+
If you become desynced from the Relay due to migration issues — i.e., new records created on your PDS aren't being picked up by other applications — you can fix it with these steps:
364
+
365
+
1. Look up the last known sequence number for your PDS host. You can use `goat` to retrieve the last observed cursor from the `bsky.network` relay:
366
+
367
+
```bash
368
+
docker exec pds sh -c 'goat relay host status "$PDS_HOSTNAME" --json'
369
+
```
370
+
371
+
```
372
+
{"hostname":"justdothings.net","seq":12,"status":"active"}
373
+
```
374
+
375
+
2. Stop the `pds` service:
376
+
377
+
```bash
378
+
systemctl stop pds
379
+
```
380
+
381
+
3. Set the cursor sequence on your PDS to the value of `seq` from step 1, incremented by 1:
382
+
383
+
```bash
384
+
sqlite3 /pds/sequencer.sqlite "UPDATE sqlite_sequence SET seq = {new_sequence_number} WHERE name = 'repo_seq';"
385
+
```
386
+
387
+
4. Restart your `pds` service:
388
+
389
+
```bash
390
+
systemctl start pds
391
+
```
392
+
393
+
New records should now be indexed as normal.
359
394
360
395
## License
361
396