{"action":"opened","issue":{"url":"https://api.github.com/repos/flux-framework/flux-core/issues/1456","repository_url":"https://api.github.com/repos/flux-framework/flux-core","labels_url":"https://api.github.com/repos/flux-framework/flux-core/issues/1456/labels{/name}","comments_url":"https://api.github.com/repos/flux-framework/flux-core/issues/1456/comments","events_url":"https://api.github.com/repos/flux-framework/flux-core/issues/1456/events","html_url":"https://github.com/flux-framework/flux-core/issues/1456","id":313886401,"number":1456,"title":"wreck: need a way to list running,pending jobs","user":{"login":"grondo","id":741970,"avatar_url":"https://avatars3.githubusercontent.com/u/741970?v=4","gravatar_id":"","url":"https://api.github.com/users/grondo","html_url":"https://github.com/grondo","followers_url":"https://api.github.com/users/grondo/followers","following_url":"https://api.github.com/users/grondo/following{/other_user}","gists_url":"https://api.github.com/users/grondo/gists{/gist_id}","starred_url":"https://api.github.com/users/grondo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/grondo/subscriptions","organizations_url":"https://api.github.com/users/grondo/orgs","repos_url":"https://api.github.com/users/grondo/repos","events_url":"https://api.github.com/users/grondo/events{/privacy}","received_events_url":"https://api.github.com/users/grondo/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-04-12T21:03:07Z","updated_at":"2018-04-12T21:03:07Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"The wreck prototype is not well suited for real-world use. It doesn't have a concept of queue (so pending jobs can't be sorted in priority order), doesn't track which jobs are running besides the `lwj.state` kvs entry, and doesn't offer any kind of search functionality (like show all single node jobs, or jobs by name, etc)\r\n\r\nThis means that the job listing tool `flux-wreck ls` is very awkward, since it orders output based on job id, which is pretty arbitrary in real-world use.\r\n\r\nLike job listing utilities in other schedulers, we may need a way to list pending and running jobs, in priority order (with running jobs having de facto infinite priority, so they are always listed first), to get much more mileage with real-world use of the wreck system.\r\n\r\nThere's probably multiple ways to accomplish this, but reading all job states from the kvs is probably contraindicated, so we may want to set up some new soft link dirs like lwj-complete (because everything is solved with another layer of indirection).\r\n\r\nWe could also just keep a list of not-complete jobs in the `job` module. This might help that module ensure that `runrequest` jobs make it to `running` within some timeout. The wreck tools could query for this list.\r\n\r\nIf we wanted to sort pending jobs in priority order, then we'd probably have to query the scheduler.\r\n\r\nIn the wreck-replacement, we'll have to have a good story for how to do this in a distributed manner. I think we already had the beginning of a design in the KVS schema doc, but I haven't looked back at that yet. The purpose of this issue would be to satisfy the minimum requirement for splash.\r\n"}}
{"actor":{"display_login":"grondo"}}