It just seems like the auto scaling ThreadPoolExecutor will do a pretty
good job of scaling up and down the threads as they are needed (we're
already doing that right now the only difference would be the core pool
threads would be shared). If things are way off then the user can pass in
their own. This seems like a case of making the beginner user pay the cost
of an advanced feature.
On Tue, Apr 2, 2013 at 6:16 PM, lars hofhansl <[EMAIL PROTECTED]> wrote:
> I think it'd make it hard to size the pool correctly.
> There is a proposed patch here:
> https://issues.apache.org/jira/browse/HBASE-6580 where we'd tie the
> threadpool to an HConnection, I think that would be the correct going
> -- Lars
> From: Elliott Clark <[EMAIL PROTECTED]>
> To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Sent: Tuesday, April 2, 2013 3:44 PM
> Subject: Shared ThreadPoolExecutor in HTable by default.
> Is there any reason that the ThreadPoolExecutor used in HTable couldn't
> be a singleton. That would mean that by default htables share threads (as I
> would argue is correct), but still give advanced users the ability to
> override this using the more explicit constructor.