incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Williams <william...@gmail.com>
Subject Re: controllers and evil queries
Date Fri, 15 Feb 2013 01:09:05 GMT
Thanks I think that helps.. i assume there's a relationship between
these and blur.shard.server.thrift.thread.count? Maybe in practice
blur.shard.server.thread.count should at least be equivalent to the
controller incoming thrift thread limit?

Thanks,
--tim

On Thu, Feb 14, 2013 at 9:26 AM, Aaron McCurry <amccurry@gmail.com> wrote:
> My guess is that it's thread starvation in the controllers.  See file:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-blur.git;a=blob;f=src/blur-util/src/main/resources/blur-default.properties;h=50900056a7507528f1f71d645ce84d5246f6892b;hb=b89d456411e0a184dee1a63709ba7c175ec4dcef
>
> blur.controller.server.thrift.thread.count=32
>
> The number of thrift requests that the controller can handle, meaning a
> single query will use just one of these.  We run 128 in production on this
> setting.
>
> blur.controller.server.remote.thread.count=64
>
> The number of remote calls to shard servers, meaning if you have 32 shard
> servers a single query will use 32 of these threads.  We run 2000 in
> production on this setting.
>
> Aaron
>
>
> On Thu, Feb 14, 2013 at 9:17 AM, Tim Williams <williamstw@gmail.com> wrote:
>
>> When an evil query (e.g. leading wildcard) are received, the
>> controllers become unresponsive until the query is either killed or
>> finished.  Killing it is actually very difficult without responsive
>> controllers:(  The odd things is, the controller server itself doesn't
>> seem to be under much load during that time.  Anyone seen this before?
>>
>> Thanks,
>> --tim
>>

Mime
View raw message