You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shawn Heisey (JIRA)" <ji...@apache.org> on 2012/12/18 03:16:13 UTC
[jira] [Comment Edited] (SOLR-4143) setRequestHandler - option to
not set qt parameter
[ https://issues.apache.org/jira/browse/SOLR-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534542#comment-13534542 ]
Shawn Heisey edited comment on SOLR-4143 at 12/18/12 2:15 AM:
--------------------------------------------------------------
Going back to the OverseerTest that I noted was failing before -- I have been having a lot of nearly identical failures in a lot of programs lately, OOMs when trying to create a thread. One of the programs that is having this failure is a very small servlet (SolrJ-based) that cycles between 15 and 25MB of heap usage, then suddenly it crashes with an OOM, with no changes in access. The JVM has a 1GB max heap, and jconsole shows no growth pattern in memory usage, then at the crash point it goes down to zero.
I am suspecting that the OOM problem might actually be in the jdk 1.7.0_09 (linux x64) that I was using. I have upgraded that to 1.7.0_10 to see if it gets better.
was (Author: elyograg):
Going back to the OverseerTest that I noted was failing before -- I have been having a lot of nearly identical failures in a lot of programs lately, OOMs when trying to create a thread. One of the programs that is having this failure is a very small servlet (SolrJ-based) that cycles between 15 and 25MB of heap usage, then suddenly it crashes with an OOM, with no changes in access.
I am suspecting that the OOM problem might actually be in the jdk 1.7.0_09 (linux x64) that I was using. I have upgraded that to 1.7.0_10 to see if it gets better.
> setRequestHandler - option to not set qt parameter
> --------------------------------------------------
>
> Key: SOLR-4143
> URL: https://issues.apache.org/jira/browse/SOLR-4143
> Project: Solr
> Issue Type: Improvement
> Components: clients - java
> Affects Versions: 4.0
> Environment: solr-impl 4.1-SNAPSHOT 1416639M - ncindex - 2012-12-03 12:54:38
> Reporter: Shawn Heisey
> Fix For: 4.1, 5.0
>
> Attachments: SOLR-4143-alternate.patch, SOLR-4143-alternate-testsfailing.patch, SOLR-4143.patch, SOLR-4143.patch, SOLR-4143.patch, SOLR-4143.patch, SOLR-4143.patch
>
>
> The setRequestHandler method does what I expect in one way - it changes the URL path from /select to the String argument. It is however doing something that I did not expect, which is setting the qt parameter on the query as well. Here is the code:
> private static final String PING_HANDLER = "/admin/ping";
> query.setRequestHandler(PING_HANDLER);
> This is resulting in the following exception being logged in my Solr 3.5.0 servers. I am not including the whole exception, because this issue is for SolrJ 4, not Solr 3.5, and the 3.5 version is working as it was designed.
> {code}
> Dec 3, 2012 4:04:01 PM org.apache.solr.common.SolrException log
> SEVERE: org.apache.solr.common.SolrException: Cannot execute the PingRequestHandler recursively
> at org.apache.solr.handler.PingRequestHandler.handleRequestBody(PingRequestHandler.java:60)
> at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:208)
> {code}
> I believe it would be useful to include an alternate setRequestHandler method that includes a boolean option deciding whether or not to also set the qt parameter.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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