this post was submitted on 03 Apr 2024
27 points (100.0% liked)

sh.itjust.works Main Community

7733 readers
1 users here now

Home of the sh.itjust.works instance.

Matrix

founded 2 years ago
MODERATORS
TheDude
manifex
biela
imaqtpie
27
Anyone else notice a long delay for comments/posts from lemmy.world? (self.main)
submitted 7 months ago* (last edited 7 months ago) by jballs to c/main
18 comments fedilink hide all child comments
 

It might not just be lemmy.world, but several times recently I've made posts (usually to !helldivers2.lemmy.ca) that I check throughout the day. Then like 8 hours after I've made the post, I'll see comments appear from people on lemmy.world that are several hours old.

It seems like there can be a queue that gets build up and then is suddenly flushed.

I see it happening the other way as well. This morning I made a post from my sh.itjust.works account and then switched over to a lemmy.world account and can't see it. So the delay is going both ways.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] InEnduringGrowStrong 13 points 7 months ago (1 children)

We are currently seeing a backlog in outbound federation towards lemmy.world.
Really, this graph says it all... ๐Ÿ“ˆ

I've restarted the containers, hoping it starts catching up.

[โ€“] jballs 7 points 7 months ago (1 children)

Oh yeah, that looks pretty telling. Also, just wanted to say thanks for how awesome you guys are on the admin team. The work you guys do and how responsive you are is freaking impressive. Thanks!

[โ€“] InEnduringGrowStrong 5 points 7 months ago (2 children)

Sadly that line keeps going up.
I don't have much of an update but it's really specific to outbound federation and just with lemmy.world.
ie: inbound works fine, outbound with other instances works fine.

[โ€“] jballs 2 points 7 months ago (1 children)

Hmm sounds like it's a problem on the lemmy.world side then.

[โ€“] InEnduringGrowStrong 3 points 7 months ago

Not necessarily.
Thing is, after a few consecutive failures, the next retry is now in a while (later tonight).
This retry spacing at least explains why it hasn't gone down after the restart