this post was submitted on 20 Jun 2023
6 points (100.0% liked)
Beehaw Support
2797 readers
2 users here now
Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.
A brief FAQ for lurkers and new users can be found here.
Our September 2024 financial update is here.
For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've never run a Lemmy or kbin instance, but have run a mastodon instance and am familiar with distributed systems in general.
Probably both the source instance and the destination instance have a queue of federated messages to process and the message needs to be sent to the destination and processed into the destination database respectively before it'll show up on the destination of the worker threads get overwhelmed.
I'd imagine that recently with the influx of users, activity, and the size of the federation, a number of instances probably sometimes have some pretty deep queues to work through at times.
Ten hours isn't ideal and hopefully isn't common, but doesn't seem out of the question in the case of connectivity issues or spikes im activity.
That makes sense, and is understandable. I think in some cases messages might be getting lost entirely though; like, I have one post from 6 days ago that didn't federate, for example.