{"shas":[["8025d6c91a50ae7eee201c0655b925e8910fe602","5900d56196fe29dba8e3ae556d57eae28e9f0195@hpccsystems.com","gh-450 Add support for roxie listening on a queue\n\nTo make Roxie-on-demand more efficient, and to make Roxie more like other\ncomponents and thus simplify the middleware, Roxie now has the ability to\nlisten for workunits on a job queue in the same way that hthor and thor do.\n\nIf a port value of 0 is specified for a roxie server to listen on, it will\ncreate a threadpool that listens on a job queue rather than on a socket.\nWhen workunits are added to the queue a temporary query factory is created,\nexecuted, and destroyed.\n\nSlaves will do a lazy create of the required IQueryFactory if a request is\nreceived for a workunit that is not loaded. This is added to a cache so that\nsubsequent slave requests on the same channel are efficient. A broadcast\nmessage at the end of the job allows the IQueryFactory to be removed from\nthe cache and released.\n\nSigned-off-by: Richard Chapman <rchapman@hpccsystems.com>","Richard Chapman"]],"ref":"refs/heads/roxie-queue","size":1,"head":"8025d6c91a50ae7eee201c0655b925e8910fe602","push_id":43349638}