Jim Garlick
Jim Garlick
In #4267 > I'm not sure about making this is the default, since there is unexplained job throughput degradation in this mode. However it is not currently possible to even...
One other thought is would it make sense to split the broker checkpoint stuff off to another source file? content-cache.c is already long and complex and this seems to be...
Suggest not using the `json_` prefix because then it's hard to tell what's part of jansson and what's not when perusing the code. Since this is the zeromq destructor footprint...
I was going to say it doesn't seem too important to me. Sort of a nice to have I guess.
> But it does help that ping outputs a "header": @grondo commented: > I like that idea, flux ping could always output rank and hostname (when available) in a header....
> though it wouldn't work when pinging a service on "any" rank One idea would be to have the ping handler tack on the rank to the response, then we...
Good point about journal permission! I edited my description to include the `job-list` idea concurrently with your comment. Sorry about that. > Would it be so bad to just query...
Possibly we can just wrap [ev_is_active()](https://metacpan.org/dist/EV/view/libev/ev.pod#bool-ev_is_active-(ev_TYPE-*watcher))?
Maybe it would be useful to add a whatsup(1) compatible subcommand to [flux-overlay(1)](https://flux-framework.readthedocs.io/projects/flux-core/en/latest/man1/flux-overlay.html)? An idset and/or hostlist representing up and down ranks can be easily generated from groups info tracked...