• F04118F@feddit.nl
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 day ago

    Good question!

    In the Home Operations Discord there’s some very smart people who solved this problem inside kubernetes by checking if their NAS is online (through a Prometheus exporter named node exporter) and then scaling down their workloads that use it, automatically, using KEDA (an autoscaler for kubernetes)

    Depending on how your processes are orchestrated, you might be able to do something similar?

    Source: https://github.com/onedr0p/home-ops/pull/9334/files

    • WhyJiffie@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      22 hours ago

      well that’s also interesting, but I mainly experience this problem on my desktop. there was a plasma version when even the taskbar panel got frozen, and the kde file manager, double commander too for like a minute, every time they try to do anything with an unreachable network drive. and its even worse on my laptop so there I just don’t mount my shares anymore.

      I have been wondering how does windows do it, and programs made for windows, because this is a nonissue there (though windows has its fair share of problems with network shares though…). maybe they just learned to do all IO ops on a different thread…