flux-core
flux-core copied to clipboard
core services for the Flux resource management framework
So I'm admittedly not sure if the pros outweigh the cons on this. This was initially going to be just comments to point readers to the tests in `t2900-job-limits`, but...
Problem: flux job list is too easy to confuse with flux-jobs(1), but the former is a test tool that emits JSON. Omit the list, list-inactive, and list-ids subcommands from help...
Problem: if a job is stuck completing for whatever reason (such as the painfully slow epilog on LC systems, but another one would be a hung node), `flux jobs` shows...
Problem: it's easy to confuse `flux job` with `flux jobs`. Perhaps `flux job list`, which outputs JSON, should just be a test program that is not installed (or a hidden...
This issue tracks reliability/administration issues that would prevent Flux from being deployed as the native resource manager on production systems. - [x] #4311 - [x] #4446 - [x] #4301 -...
Per discussion in #4267, always loading the backing module content-sqlite can lead to performance issues, especially for shorter lived single user instances. Default to not loading a backing module. -...
Problem: the job-ingest `feasibility` plugin sends jobspec to the scheduler for an early determination of request feasibility, but the `jobspec-defaults` jobtap plugin has not yet assigned default values for jobspec...
This issue tracks the implementation of queues for partitioned resources, needed for rollout of Flux as the native resource manager on production systems. - [x] #4386 (default queue, and queue-specific...
While working on #4267, I noticed that sometimes the `acct_dirty` field can be greater than the length of the `flush` list, even when a backing module is not loaded. a...
As noted in #3744, it would be useful to have some way for a process to determine the context in which it is running as it relates to Flux jobs,...