FYI: For weeks, lemmy deleting of comments by the user who created the comment has not been working properly. When users were on just a couple severs it worked, but now with over 1,000 servers...
FYI: For weeks, lemmy deleting of comments by the user who created the comment has not been working properly. When users were on just a couple severs it worked, but now with over 1,000 servers...
Cite: 1,3xx Lemmy servers federating https://join-lemmy.org/instances
The code in Lemmy does not seem to federate to all the subscribed servers when a end-user on a remote server deletes their own comment. So far, I can't determine if it has always been this way and nobody noticed, or if something broke at some point in Lemmy code changes. Has it been gong on for weeks, or did it always fail?
Please be kind to users, they may have intended to delete their own comment and Lemmy isn't properly removing it on over 1000 servers and only removes it on 2 servers.
This happens when a community is homed on a server different from the server the end-user is commenting (and deleting that comment) on.
Growing pains.
GitHub issue: https://github.com/LemmyNet/lemmy/issues/3625
Starting around June 1, there was a general strategy to upgrade hardware on the established Lemmy servers (that had been around for 6 months or longer, some going back several years).... but hardware upgrades didn't work. Lemmy had serious flaws with federation performance and the PostgreSQL database.
This landed us where we are in mid-July. over 1,300 servers with less than 66,000 active users!
A massive internal SQL usage performance problem was fixed in Lemmy 0.18.2, providing great relief to the most popular servers. It turned out that having an explosion of instances was making the performance far worse, as the code that distributed content to peer servers had extremely inefficient SQL queries.
the legacy is that we have a huge number of servers, but the problems with the logic in the code for federation not being complete/tested.