Content
@
0 reply
0 recast
0 reaction
Sanjay
@sanjay
We've released 1.11.1. @wazzymandias.eth made it so that hubs will now automatically use snapshot sync to catch up if they are too many messages behind. Note that this will reset the db, if you're running a replicator you can disable this to be safe, by setting `CATCHUP_SYNC_WITH_SNAPSHOT=false` in your .env file
6 replies
3 recasts
11 reactions
Manan
@manan
That’s a great idea. - How often does a hub do the “am I behind?” check? - How many is too many behind?
1 reply
0 recast
0 reaction
patxol 🟪 Building F4R
@patxol.eth
I am now regretting the upgrade. Getting the following error
1 reply
0 recast
1 reaction
johnjjung.eth 🛟
@jj
Folks really love the pace of the team - it just wondering if you’re thinking of doing like an LTS type of hub versioning
1 reply
0 recast
0 reaction
johnjjung.eth 🛟
@jj
Hi folks, the snapshot is really awesome and fast but for me it downloaded the snapshot and then restarts the downloading of snapshots again. Looking closely at the logs I see an error message but it’s all \n so thinking there’s a typo or bug
2 replies
0 recast
0 reaction
bruce
@brucexc.eth
Incredible upgrade! Syncing 80M messages only took 3 hours. Amazing!👍
0 reply
0 recast
2 reactions
Fookinnowan 🎩🔵
@fookinnowan
The snapshot is really life saver, was having hard time to have my hub fully synced previous but from version 1.11.1 onwards the sync is a breeze 👍 222 $DEGEN
0 reply
0 recast
2 reactions