: Because our user send very long and complex queries with asterisk and near : operator. : Sometimes near operator exceeds 1,000 and keywords almost include asterisk. : If such query is sent to server, jvm memory is full. (our jvm memory
"near" operator isn't something I know of as a built in feature of SOlr (definitely not Solr 1.4) ... which query parser are you using? what is the value of your <maxBooleanClauses> setting in solrconfig.xml? that's the method that should help to limit the risk of query explosion if users try to overwelm the server with really large queries, but for wildcard and prefix queries (ie: using "*") even Solr 1.4 implemented those using "ConstantScoreQuery" instead of using query expansion, so i'm no sure how/why a single query could eat up so much ram. In general, there have been a lot of improvements in memory usage in recent versions of Solr, so i suggest you upgrade to Solr 3.5 -- but beyond that basic advice any other suggestions will require a *lot* more specifics about exactly waht your configs look like, the full requests (all params) of queries that are causing you problems, detials on your JVM configuration, etc... -Hoss
