Redis extension not subscribing to changes after document is closed and reopened. about hocuspocus HOT 5 CLOSED

Hi @solirpa,

@hanspagel is still patiently waiting for my rewrite of y-redis. I'm aware that a ready-to-use solution for horizontal scaling is a highly requested feature. Another requested feature is the ability to sync all documents that a user has access to with a backend. I spent the last weeks finding a new scalable approach that allows syncing thousands of documents efficiently over a single connection for offline usage. I took some inspiration from the exchanges that I had with the author of Legendkeeper. The y-redis approach that I'm working on will be scalable and will enable syncing subdocuments. This significantly increases complexity, but I'd rather work on a complete solution than an incomplete solution that only works for some.

I updated the current y-redis implementation which should be usable and allow horizontal scaling. I will release some information about the rewrite of y-redis that allows syncing of subdocuments soon.

from hocuspocus.

Thanks for the report! I refactored the Redis extension. Unfortunately there’s still a major issue I can’t really grasp. Sometimes changes aren’t correctly sent to the server.

I’m still waiting for a rewrite of y-redis, not sure if it’s worth the time to look into issues related to Redis now - or if it’ll be better to wait for the rewrite.

from hocuspocus.

@hanspagel thanks for that refactor, will see if I can run into that issue you posted above. By not correctly sent to the server you mean @hocuspocus/server receives the update and @hocuspocus/extension-redis doesn't or @hocuspocus/server doesn't receive it at all?

I saw that mentioned a couple of times that the redis adapter is due a rewrite, would be interested in reading what is due to be changed with it. I noticed it in another thread about horizontal scalability which is something we're super interested in too. But was also interested if there were plans to allow reduction of the data size in it by doing set of the whole document instead of append of individual updates (as appending updates for our data at least ends up growing a lot larger than encoding state at any given time as an update as we have a lot of garbage collected data from update to update).

from hocuspocus.

I has same bug. QAQ
Is there has a available server horizontal-scaling way now?

from hocuspocus.

Thanks for reporting! I don’t think this issue applies to the upcoming rewrite of the Redis extension #285.

from hocuspocus.