• 26 Posts
  • 1.85K Comments
Joined 3 years ago
cake
Cake day: July 7th, 2023

help-circle






  • Red Hat is the largest funder of the Fedora Projects because it serves as a base for other things they make and support aside from their enterprise distros. Being the largest single funder gets you the most pull on the direction of said projects. They also have Red Hat employees directly running or contributing to various projects and upstream commits.

    The actual community boards and such are independent of Red Hat otherwise. Similar to how Valve suddenly has a bunch of pull in the direction of the projects they’ve been directly funding and contributing to the past few years, Red Hat informs the independent community board with commits and contributions.

    This is how the FOSS community works in general though. ‘Project A’ could be widely used in the community, but generally have fairly slow development. ‘Company A’ comes in and offers to fund feature development or big hunts, or maybe directly contribute fixes because they rely on this project. That project then either has the choice to turn down that extra help that could greatly benefit the project, or take that help, and as part of that deal, accept that ‘Company A’ now has some pull in the direction of the project.

    Kind of a majority rule via resource commitment.













    1. Get some sort of resource monitor running on the machine to collect timeseries data about your procs, preferably sent to another machine. Prometheus is simple enough, but SigNoz and Outrace are like DataDog alternatives if you want to go there.
    2. Identify what’s running out of control. Check CPU and Memory (most likely a memory leak)
    3. Check logs to see if something is obviously wrong
    4. Look and see if there is an update for whatever the proc is that addresses this issue
    5. If it’s a systems process, set proper limits

    In general, it’s not an out of control CPU that’s going to halt your machine, it’s memory loss. If you have an out of control process taking too much memory, it should get OOMkilled by the kernel, but if you don’t have proper swap configured, and not enough memory, it may not have time to successfully prevent the machine from running out of memory and halting.