logos-messaging/docs.waku.org
1
0
Fork 0
mirror of https://github.com/logos-messaging/docs.waku.org.git synced 2026-01-02 12:53:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

new attempt

Browse Source
This commit is contained in:
Gabriel mermelstein 2024-08-29 15:00:02 -06:00
parent b38306c849
commit 4515b52310
No known key found for this signature in database
GPG Key ID: 82B8134785FEAE0D
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/guides/nwaku/upgrade-instructions.md
View File

@ -11,10 +11,12 @@ import { AccordionItem } from '@site/src/components/mdx'
<AccordionItem title="v0.31.0">
Named sharding was deprecated in this version. This means that pubsub topics will only be supported if they comply with the static sharding format:
/waku/2/rs/<CLUSTER_ID>/<SHARD_ID>
```
/waku/2/rs/<CLUSTER_ID>/<SHARD_ID>
```
In order to migrate your existing application, you need to:
1. Make sure that your clients are sending messages to pubsub topics in the required format
2. When running a node with the `--pubsub-topic` CLI flag, the values provided should compy with the static sharding format
3. If your application relies on nodes or clients that may not be updated immediately, keep your node on an older version while subscribing to both the currently pubsub topic and the new pubsub topic that will comply with the static sharding format. In that case, you can keep backward compatibility for a migration period.
In order to migrate your existing application, you need to:
1. Make sure that your clients are sending messages to pubsub topics in the required format
2. When running a node with the `--pubsub-topic` CLI flag, the values provided should compy with the static sharding format
3. If your application relies on nodes or clients that may not be updated immediately, keep your node on an older version while subscribing to both the currently pubsub topic and the new pubsub topic that will comply with the static sharding format. In that case, you can keep backward compatibility for a migration period.
</AccordionItem>