Hi James, 4.1 right now. We are currently using defaults. I can try and jacking that up if it makes sense.
Right now, this version of DBVis doesn't have our stock hbase-site.xml in its classpath. Do we have to add that or can we get away with setting that somewhere in the query tool. What is the best way to do that? Thanks! Abe On Mon, Dec 15, 2014 at 2:15 PM, James Taylor <[email protected]> wrote: > > What version are you using, Abe? The important parameter to bump up if > you get a rejected exception is the queue depth > (phoenix.query.queueSize). When you upgrade to 4.2.x, the default for > this went up to 5000, the reason being that we chunk up work into > smaller pieces. If you're already overriding this, make sure you > remove that override (or increase it substantially). > > Thanks, > James > > On Mon, Dec 15, 2014 at 10:08 AM, Abe Weinograd <[email protected]> wrote: > > Hi, > > > > We resized (reduced) our cluster size. Running any queries that > aggregate > > on our datasets, I am getting the following errors. After the first > query, > > that error returns immediately AND even for an EXPLAIN. I saw a couple > of > > other posts about this and the recommendation is to jack up the > threadPool > > and queue configs. Is that right? > > > > Abe > > > > Task org.apache.phoenix.job.JobManager$JobFutureTask@513c74aa rejected > from > > org.apache.phoenix.job.JobManager$1@6312e0f8[Running, pool size = 128, > > active threads = 128, queued tasks = 500, completed tasks = 2183] >
