Technology

37727 readers

590 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

alyaza@beehaw.org

TheRtRevKaiser@beehaw.org

gyrfalcon@beehaw.org

rs5th@beehaw.org

Los@beehaw.org

coldredlight@beehaw.org

SemioticStandard@beehaw.org

TheRtRevKaiser@kbin.social

remington@beehaw.org

FYI: lemmy.ml - central hub for many communities - has been down 2 hours so far after 0.18 upgrade EDIT: back up! (beehaw.org)

submitted 1 year ago* (last edited 1 year ago) by BitOneZero@beehaw.org to c/technology@beehaw.org

5 comments fedilink hide all child comments

I do not believe 0.18 itself is the cause of the problem. I highly suspect the problem is with federation logic of how peer servers retry and connect to each other. Multiple servers going down in a short period to upgrade to 0.18 could be causing lemmy.ml to internally swarm within the outbound code or some other resource problem.

Lemmy.ml has hundreds of peer instances to distribute comments to.

Other instances could be having cascading problems if they have a lot of outbound messages to distribute.

you are viewing a single comment's thread
view the rest of the comments