Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Fri, 9 Mar 2012 02:45:57 +0000 (UTC)
From: "Greg Bowyer (Updated) (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <2131654877.42076.1331261157672.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1461309911.41922.1331256238488.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (SOLR-3221) Make Shard handler threadpool
 configurable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/SOLR-3221?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:all-tabpanel ]

Greg Bowyer updated SOLR-3221:
------------------------------

    Attachment: SOLR-3221-3x_branch.patch
                SOLR-3221-trunk.patch

Whoops ! I didnt spot a silly potential NPE in this patch, found locally by=
 the randomised testing and corrected
               =20
> Make Shard handler threadpool configurable
> ------------------------------------------
>
>                 Key: SOLR-3221
>                 URL: https://issues.apache.org/jira/browse/SOLR-3221
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 3.6, 4.0
>            Reporter: Greg Bowyer
>            Assignee: Erick Erickson
>              Labels: distributed, http, shard
>         Attachments: SOLR-3221-3x_branch.patch, SOLR-3221-3x_branch.patch=
, SOLR-3221-trunk.patch, SOLR-3221-trunk.patch
>
>
> From profiling of monitor contention, as well as observations of the
> 95th and 99th response times for nodes that perform distributed search
> (or =E2=80=9Faggregator=E2=80=9F nodes) it would appear that the HttpShar=
dHandler code
> currently does a suboptimal job of managing outgoing shard level
> requests.
> Presently the code contained within lucene 3.5's SearchHandler and
> Lucene trunk / 3x's ShardHandlerFactory create arbitrary threads in
> order to service distributed search requests. This is done presently to
> limit the size of the threadpool such that it does not consume resources
> in deployment configurations that do not use distributed search.
> This unfortunately has two impacts on the response time if the node
> coordinating the distribution is under high load.
> The usage of the MaxConnectionsPerHost configuration option results in
> aggressive activity on semaphores within HttpCommons, it has been
> observed that the aggregator can have a response time far greater than
> that of the searchers. The above monitor contention would appear to
> suggest that in some cases its possible for liveness issues to occur and
> for simple queries to be starved of resources simply due to a lack of
> attention from the viewpoint of context switching.
> With, as mentioned above the http commons connection being hotly
> contended
> The fair, queue based configuration eliminates this, at the cost of
> throughput.
> This patch aims to make the threadpool largely configurable allowing for
> those using solr to choose the throughput vs latency balance they
> desire.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org