{"push_id":973901617,"size":2,"distinct_size":2,"ref":"refs/heads/kvs_persist","head":"5a7034910eb1350ae640dcbbdee9b87f89358b35","before":"32bef5af90dce379a9d52caf4a4f32574b960c7f","commits":[{"sha":"c44526ef2aebffcf72d955c0d70057fe17609373","author":{"email":"90eebc3ed9e472707552aa1f0850807e64b4e5e4@gmail.com","name":"Jim Garlick"},"message":"broker: report slow nodeset with LOG_INFO","distinct":true,"url":"https://api.github.com/repos/garlick/flux-core/commits/c44526ef2aebffcf72d955c0d70057fe17609373"},{"sha":"5a7034910eb1350ae640dcbbdee9b87f89358b35","author":{"email":"90eebc3ed9e472707552aa1f0850807e64b4e5e4@gmail.com","name":"Jim Garlick"},"message":"broker/content-cache: respect flush-batch-limit\n\nWhen a backing store is loaded on rank 0, avoid letting the number\nof outstanding requests to the backing store exceed the configured\n'content-flush-batch-limit'.\n\nThe limit was being checked when store requests to the backing store\nwere begun as a result of a flush request.  It was not being checked\nwhen they were started as a result of new content landing in the cache.\n\nChecking in this case avoids \"handle thrashing\" when each new message\nreceived by the broker has to be checked against a long list of\noutstanding request messages.","distinct":true,"url":"https://api.github.com/repos/garlick/flux-core/commits/5a7034910eb1350ae640dcbbdee9b87f89358b35"}]}