Skip to content

Commit

Permalink
clean up markdown on 2.28.0 release notes
Browse files Browse the repository at this point in the history
  • Loading branch information
sreuland committed Jan 26, 2024
1 parent fcfa5a1 commit 24a7e9f
Showing 1 changed file with 6 additions and 4 deletions.
10 changes: 6 additions & 4 deletions services/horizon/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,14 +26,16 @@ file. This project adheres to [Semantic Versioning](http://semver.org/).
### Breaking Changes
- Deprecation of legacy, non-captive core ingestion([5158](https://github.com/stellar/go/pull/5158)):
* removed configuration flags `--stellar-core-url-db`, `--cursor-name` `--skip-cursor-update`, they are no longer usable.
* removed automatic updating of core cursor from ingestion background processing.
* Note for upgrading on existing horizon deployments - Since horizon will no longer maintain advancement of this cursor on core, it may require manual removal of the cursor from the core process that your horizon was using for captive core, otherwise that core process may un-necessarily retain older data in buckets on disk up to the last cursor ledger sequence set by prior horizon release.
* removed automatic updating of core cursor from ingestion background processing.<br/>
**Note** for upgrading on existing horizon deployments - Since horizon will no longer maintain advancement of this cursor on core, it may require manual removal of the cursor from the core process that your horizon was using for captive core, otherwise that core process may un-necessarily retain older data in buckets on disk up to the last cursor ledger sequence set by prior horizon release.

The captive core process to check and verify presence of cursor usage is determined by the horizon deployment, if `NETWORK` is present, or `STELLAR_CORE_URL` is present or `CAPTIVE-CORE-HTTP-PORT` is present and set to non-zero value, or `CAPTIVE-CORE_CONFIG_PATH` is used and the toml has `HTTP_PORT` set to non-zero and `PUBLIC_HTTP_PORT` is not set to false, then it is recommended to perform the following preventative measure on the machine hosting horizon after upgraded to 2.28.0 and process restarted:
```
$ curl http://<captive_core_process_url:captive_core_process_port>/getcursor
2. # If there are no cursors reported, done, no need for any action
3. # If any horizon cursors exist they need to be dropped by id. By default horizon sets cursor id to "HORIZON" but if it was customised using the --cursor-name flag the id might be different
# If there are no cursors reported, done, no need for any action
# If any horizon cursors exist they need to be dropped by id.
# By default horizon sets cursor id to "HORIZON" but if it was customized
# using the --cursor-name flag the id might be different
$ curl http://<captive_core_process_url:captive_core_process_port>/dropcursor?id=<reported_id_from_getcursor>
```
Expand Down

0 comments on commit 24a7e9f

Please sign in to comment.