federation between instances showing many comments not replicating (2023-06-13 example) · Issue #3101 · LemmyNet/lemmy
github.com
the normal bug report form does not serve this kind of issue. So far, the problem can be observed and reported, but not identified at the code or log levels. Even after lemmy.ml upgraded hardware y...

the normal bug report form does not serve this kind of issue. So far, the problem can be observed and reported, but not identified at the code or log levels.

Even after lemmy.ml upgraded hardware yesterday, this posting serves as an example of how comments are not making it to other instances of Lemmy. This is the same posting, different id on each instance:

https://lemmy.ml/post/1239920 has 19 comments (community home)
https://lemmy.pro/post/1354 has 1 comment
https://sh.itjust.works/post/74015 has 9 comments
https://lemmy.world/post/103943 has 9 comments
https://programming.dev/post/29631 has 13 comments
https://beehaw.org/post/536574 has 7 comments
https://lemmy.haigner.me/post/8 has 6 comments (posting originated with user there)
https://lemmy.wtf/post/1021 has 10 comments

Originally posted by RocketDerp in #3101

  • issue_tracking_bot@lemm.eeOPB
    1·
    1 year ago

    Fresh reports of missing comments and posts: https://lemmy.world/post/406956

    I am reaching a point where I feel like the major site operators are not publicly, on Lemmy or Github, acknowledging the scaling problems that Lemmy platform is having. Issue #3203 is happening again today from remote instances trying to reach lemmy.ml - and that is after the upgrade to 0.18

    Why am I seeing daily “nginx 500” errors that rapidly return from a browser refresh on Beehaw, Lemmy.ml, Lemmy.world - and none of these major operators have open issues with posting their application error logs and nginx logs for us to get our eyes on? The whole community is in scaling crisis.

    Making a fool of myself: https://lemmy.ml/post/1453121

    Originally posted by RocketDerp in #3101