Thanks Parth. As I stated in, there are no other jobs running in the cluster when this happens. I do have queueing enabled, however, with no other jobs running, why would any single job sit in the ENQUEUED state for 30 seconds? This seems to be an issue or am I missing something?
I would really like to use queueing as this is a multi-tenant cluster, so I don't want to remove it all together. John On Wed, Jun 29, 2016 at 10:57 PM, qiang li <tiredqi...@gmail.com> wrote: > I have the same doult. > > I set the queue.threshold to 50000000, queue.large to 20 and the > queue.small to 200. But when I query with about 100 small querys > concurrently, most of them are ENQUEUED. > > If I turn off the queue, it will query fast. If turn on the queue , our > querys will speed about 7 seconds, while only take 2 to 3 seconds if I turn > off queue. > > Currently , we turn off the queue and limit the querys at client side. > > 2016-06-30 6:19 GMT+08:00 Parth Chandra <pchan...@maprtech.com>: > > > I would guess you have queueing enabled. With queueing enabled, only a > max > > number of queries will be actually running and the rest will wait in an > > ENQUEUED state. > > > > There are two queues: one for large queries and one for small queries. > You > > can change their size with the following parameters - > > exec.queue.large > > exec.queue.small > > > > > > > > > > > > > > On Wed, Jun 29, 2016 at 1:51 PM, John Omernik <j...@omernik.com> wrote: > > > > > I have some jobs that will stay in an ENQUEUED state for what I think > to > > be > > > an excessive amount of time. (No other jobs running on the cluster, > the > > > ENQUEUED state lasted for 30 seconds) . What causes this? Is it > planning > > > when it's in this state? Any information about this would be helpful. > > > > > > John > > > > > >
