Mark Grondona

This issue came up again in a meeting recently. The time to shutdown Flux on busy system instances is a pain point for sysadmins.

Well that list is just hardcoded in the `flux job info` command. I wonder, though, if instead the command with no args could list available keys that the current user...

> Will "added" keys have descriptions with them? (like where "R" says "allocated resources" next to it) No. I was thinking they'd just be listed under "Other available keys:". However,...

> Thoughts? If palatable we can hot-potato this issue back to flux-coral2 :-) :joy: Actually not a bad idea at all! Better separation of concerns.

The two use cases I was thinking of for this feature would still require getting all history first, so ignoring some portion of events already in the eventlog wouldn't work....

To get the correct time for a status/list response, you should check the low-level RPC call. Probably half the time is spent in Python assembling the results, though we vastly...

Though the `rlist_mrlist->zlistx_find` seems like _very_ low hanging fruit.

I think I looked at this before and decided it wasn't worth it at the time because other issues were 2-10x the cost. However, definitely take another look.

Your argument does make sense, I don't recall the exact arguments for the journald approach. I had just agreed to open an issue describing the idea. If the worry is...

Note that we don't currently have a way to expand a field to make room for a larger list of queues, so at this point the output would be more...