ore the system crash? I've read some articles and they recommend that I
> can include this phase during the startup of the server
> '-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/heapDumps'. I've
> included this but this will only output the dump when the error o
Steven,
What does being your hero entails, beside a salute? :-)
Approach 1: Tinker with your-app - Solr relationship.
Approach 2: Gauge what's really used and limit the customization.
Approach 3: Offer what's wanted (might be different than what you're trying
to achieve).
In your write-up I'm un
Joseph,
You are doing a memory intensive operation and perhaps an IO intensive
operation at once. That makes your C-heap run out of memory or hit a thread
limit (thus first problem, java.lang.OutOfMemoryError: unable to create new
native thread) and later you're also hitting the problem of Java he
The error happens either when you have too large codebase or when you are
String-intensive in your application (Solr including) or when your previous
process did not terminate well.
Can't say for certain what Solr usage scenarios are string intensive
without deep look at it's code. Usually enlargi
There's also Perl-backed ACK. http://beyondgrep.com/
Which does the job of searching code really well.
And I think at least once I came across something that stemmed from ACK and
claimed it was faster/better... googling... aah! The Silver Searcher it
was. :-)
http://betterthanack.com/
pozdrawiam
Best I found so far is:
+place:(+word1~ +word2~ +word3~)
pozdrawiam,
LAFK
2015-04-26 3:20 GMT+02:00 Tomasz Borek :
> Ave!
>
> How do I make fuzzy search on lengthy names? As in "La Riviera Montana de
> los Diablos" or "Unified Mega Corp Super Dwelling"? Across
Short answer: wget skips body on 400 assuming you didn't want error page
stored.
Long answer: get your error page with additional wget params, like so:
✗ wget -Sd http://10.0.3.113:8080/solr/collection1/vitas\?q\=coreD%3A25
DEBUG output created by Wget 1.15 on linux-gnu.
URI encoding = `UTF-8'
--
FWIW you may also want to drop the boolean ops in favour of + and - (OR
being default)
pozdrawiam,
LAFK
2015-05-08 18:59 GMT+02:00 Erick Erickson :
> Steven:
>
> They're listed on the ref guide I posted. Not a concise list, but
> you'll see && || and other "interesting" bits.
>
> On Fri, May 8,
Out of curiosity: why bytecode?
pozdrawiam,
LAFK
2015-05-08 21:31 GMT+02:00 Mark :
> I looking to use Solr search over the byte code in Classes and Jars.
>
> Does anyone know or have experience of Analyzers, Tokenizers, and Token
> Filters for such a task?
>
> Regards
>
> Mark
>
Take a look at query parameters and use debug and/or explain.
https://wiki.apache.org/solr/CommonQueryParameters
Also, perhaps change parser from default one to less stringent dismax.
Hard to say what fits your case as I don't know it, but those two are best
starting points I know of.
pozdrawia
Perhaps belated and IANA Solr expert, but take a look at mergeFactor and
ramBufferSizeMB. I've had a situation where after Solr upgrade old values
were kept. Those are used for buffering during indexing AFAIR. If buffer
size is exceeded, merge happens. If merge factor is exceeded, coalesced
segment
Ave!
How do I make fuzzy search on lengthy names? As in "La Riviera Montana de
los Diablos" or "Unified Mega Corp Super Dwelling"? Across all queries?
My query has 3 levels of results:
Best results are: +title:X +place:Y -> Q1
If none such are found, +title:x -> Q2
then +place:Y -> Q3
All in all
Java side:
- launch jvisualvm
- see how heap and CPU are occupied
What are your JVM settings (heap) and how much RAM do you have?
The CPU100% is used only by Solr? That is, are you 100% certain it's Solr
that drives CPU to it's limit?
pozdrawiam,
LAFK
2015-04-24 12:14 GMT+02:00 Norgorn :
> The
13 matches
Mail list logo