Re: FilterQueries with NRT

2018-05-12 Thread Mikhail Khludnev
You can experiment with the backdoor NRT filters:
- replace COLOR:Red to {!parent which='COLOR:Red' v=''}
- add *NoOpRegenerator **into perSegFilter*
*- **monitor cache stats. *

On Fri, May 11, 2018 at 10:46 PM, root23  wrote:

> Hi all,
> We have a requirement for NRT search. Our autosoft commit time is set to
> 500
> ms(i know its low.But that's another story). We use filter queries
> extensively for most of our queries.
>
> But i am trying to understand how filter query caching works with NRT.
> Now as i understand we use fq for queries which are commonly used across
> most of our searches, so that they get cached and will be reused across
> multiple queries. However the cache is only good for the life time of a
> indexSearcher.
> And as we do a new soft commit a new searcher will open and it will creates
> its own cache and if we have autowarmcount set to 0, its essentially will
> start with an empty filter cache.
> Now since the autosoft commit time is 500 ms, in theory we are openeing a
> searcher every 0.5 second.
>
> So in this case does it make even sense to cache anything, if we are gona
> throw it away 0.5 second later and start again.
> Does adding stuff to fq gives us anything in this particular scenario.
>
>
>
> --
> Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
>



-- 
Sincerely yours
Mikhail Khludnev


Apache SOLR Design Query

2018-05-12 Thread NetUser MSUser
Hi team,


We have a business case like the below one.


There are nearly 150 GB of docs(pdf/ppt/word/xl/msg) files which are in
stored in a N/w Path as of now. To implement text search on these , we are
planning to use solr search in these. Listed below is the plan.

1)Using a high configuration Windows server(16 GB RAM , 1 TB Disk etc)
2)Keep all the files in this server.
3)Index all the above docs to solr server(Solr installed in the same
windows server). Will use solr post command to post documents to this
server.
4)Using a Web application user can further add or remove files to/from
shared path in this server.
5)Web UI to search the text from these docs. and display the file Names.
User can click and download the files

Listed are the queries what we have.

1)Since we cannot index fields here, (as search is across all text in the
docs of various types. User can search for any text and it might be in XL
or in DOC or in PPT or in .MSG files), whether querying(Rest API from the
Web ) the search data will have any performance hit?

2)Is it a right decision to keep the physical files in the Shared folder of
Server itself(as a shared drive) instead of storing it in a DB or any other
storage?


Regards,
MS


Solr 6.6.3 won't start - unrecognized vm option "UseParNewGC" - Java 10.0.1

2018-05-12 Thread turpentyne
Running into an issue beyond my experience level.


In Installed and started Solr 7.3. But, then I realized I need to use an
older 6.x version (for Drupal)

So, I installed Solr 6.6.3. But, it will not start.

The message I get is:

**Still not seeing Solr listening on 8983 after 180 seconds!*

*tail: /Applications/solr-6.6.3/server/logs/solr.log: No such file or
directory**

I get the same same result, whether I use *bin/solr start* or *sudo*.

The solr.log is definitely missing. But there is a Solr-8983-console.log.
This shows the message below:

**Java HotSpot(TM) 64-Bit Server VM warning: Option UseConcMarkSweepGC was
deprecated in version 9.0 and will likely be removed in a future release.*

*Unrecognized VM option 'UseParNewGC'*

*Error: Could not create the Java Virtual Machine.*

*Error: A fatal exception has occurred. Program will exit.**

Java -version displays as 10.0.1. This is a work computer with security
needs, and I believe I need to keep it as updated as possible:

**java version "10.0.1" 2018-04-17*

*Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10)*

*Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode)**

Also tried with Solr 6.6.3, 6.6.0 and 5.0.0 with same failure and log
message.

If relevant, I'm on a 2015 macbook pro, using high sierra 10.13.3


Re: Solr 6.6.3 won't start - unrecognized vm option "UseParNewGC" - Java 10.0.1

2018-05-12 Thread Erick Erickson
Just what it says, you are using (or rather the start scripts that
Solr 6.6.3 uses) are using options not supported in Java 10.

Java 10 is in process of being verified to work with Solr, see this
JIRA in the 7.3.1 release notes: SOLR-12141: Fix "bin/solr" shell
scripts (Windows/Linux/Mac) to correctly detect major Java version
and use numerical version comparison to enforce minimum requirements.
Also remove obsolete "UseParNewGC" option.  This allows to start Solr
with Java 10 or later. (Uwe Schindler)

I'd pretty strongly recommend moving back to the version of Java
specified with 6.6.3, probably Java 9. Java 8 has the most mileage
with that Solr code base.

Best,
Erick

On Sat, May 12, 2018 at 5:02 PM, turpentyne  wrote:
> Running into an issue beyond my experience level.
>
>
> In Installed and started Solr 7.3. But, then I realized I need to use an
> older 6.x version (for Drupal)
>
> So, I installed Solr 6.6.3. But, it will not start.
>
> The message I get is:
>
> **Still not seeing Solr listening on 8983 after 180 seconds!*
>
> *tail: /Applications/solr-6.6.3/server/logs/solr.log: No such file or
> directory**
>
> I get the same same result, whether I use *bin/solr start* or *sudo*.
>
> The solr.log is definitely missing. But there is a Solr-8983-console.log.
> This shows the message below:
>
> **Java HotSpot(TM) 64-Bit Server VM warning: Option UseConcMarkSweepGC was
> deprecated in version 9.0 and will likely be removed in a future release.*
>
> *Unrecognized VM option 'UseParNewGC'*
>
> *Error: Could not create the Java Virtual Machine.*
>
> *Error: A fatal exception has occurred. Program will exit.**
>
> Java -version displays as 10.0.1. This is a work computer with security
> needs, and I believe I need to keep it as updated as possible:
>
> **java version "10.0.1" 2018-04-17*
>
> *Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10)*
>
> *Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode)**
>
> Also tried with Solr 6.6.3, 6.6.0 and 5.0.0 with same failure and log
> message.
>
> If relevant, I'm on a 2015 macbook pro, using high sierra 10.13.3


Re: Solr 6.6.3 won't start - unrecognized vm option "UseParNewGC" - Java 10.0.1

2018-05-12 Thread turpentyne
Erick,

Thank you, and sorry for 'beginner' questions!

So, I've installed a second version of Java. I believe 8? (Titled:
oracle65-1.8.0.172), and I turned it on for the local Solr-6.6.3 folder.
Double checked it's using that version (using homebrew, cask and jenv)

But... I'm getting exactly the same error still. no such file, and the
console.log

Java HotSpot(TM) 64-Bit Server VM warning: Option UseConcMarkSweepGC was
deprecated in version 9.0 and will likely be removed in a future release.
Unrecognized VM option 'UseParNewGC'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

thoughts?

On Sat, May 12, 2018 at 2:38 PM, Erick Erickson 
wrote:

> Just what it says, you are using (or rather the start scripts that
> Solr 6.6.3 uses) are using options not supported in Java 10.
>
> Java 10 is in process of being verified to work with Solr, see this
> JIRA in the 7.3.1 release notes: SOLR-12141: Fix "bin/solr" shell
> scripts (Windows/Linux/Mac) to correctly detect major Java version
> and use numerical version comparison to enforce minimum requirements.
> Also remove obsolete "UseParNewGC" option.  This allows to start Solr
> with Java 10 or later. (Uwe Schindler)
>
> I'd pretty strongly recommend moving back to the version of Java
> specified with 6.6.3, probably Java 9. Java 8 has the most mileage
> with that Solr code base.
>
> Best,
> Erick
>
> On Sat, May 12, 2018 at 5:02 PM, turpentyne  wrote:
> > Running into an issue beyond my experience level.
> >
> >
> > In Installed and started Solr 7.3. But, then I realized I need to use an
> > older 6.x version (for Drupal)
> >
> > So, I installed Solr 6.6.3. But, it will not start.
> >
> > The message I get is:
> >
> > **Still not seeing Solr listening on 8983 after 180 seconds!*
> >
> > *tail: /Applications/solr-6.6.3/server/logs/solr.log: No such file or
> > directory**
> >
> > I get the same same result, whether I use *bin/solr start* or *sudo*.
> >
> > The solr.log is definitely missing. But there is a Solr-8983-console.log.
> > This shows the message below:
> >
> > **Java HotSpot(TM) 64-Bit Server VM warning: Option UseConcMarkSweepGC
> was
> > deprecated in version 9.0 and will likely be removed in a future
> release.*
> >
> > *Unrecognized VM option 'UseParNewGC'*
> >
> > *Error: Could not create the Java Virtual Machine.*
> >
> > *Error: A fatal exception has occurred. Program will exit.**
> >
> > Java -version displays as 10.0.1. This is a work computer with security
> > needs, and I believe I need to keep it as updated as possible:
> >
> > **java version "10.0.1" 2018-04-17*
> >
> > *Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10)*
> >
> > *Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode)**
> >
> > Also tried with Solr 6.6.3, 6.6.0 and 5.0.0 with same failure and log
> > message.
> >
> > If relevant, I'm on a 2015 macbook pro, using high sierra 10.13.3
>


Re: Solr 6.6.3 won't start - unrecognized vm option "UseParNewGC" - Java 10.0.1

2018-05-12 Thread Alexandre Rafalovitch
You may need to set JAVA_HOME or PATH variables to point to your java 8 .
Possibly both.

Regards,
 Alex

On Sat, May 12, 2018, 6:28 PM turpentyne,  wrote:

> Erick,
>
> Thank you, and sorry for 'beginner' questions!
>
> So, I've installed a second version of Java. I believe 8? (Titled:
> oracle65-1.8.0.172), and I turned it on for the local Solr-6.6.3 folder.
> Double checked it's using that version (using homebrew, cask and jenv)
>
> But... I'm getting exactly the same error still. no such file, and the
> console.log
>
> Java HotSpot(TM) 64-Bit Server VM warning: Option UseConcMarkSweepGC was
> deprecated in version 9.0 and will likely be removed in a future release.
> Unrecognized VM option 'UseParNewGC'
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
>
> thoughts?
>
> On Sat, May 12, 2018 at 2:38 PM, Erick Erickson 
> wrote:
>
> > Just what it says, you are using (or rather the start scripts that
> > Solr 6.6.3 uses) are using options not supported in Java 10.
> >
> > Java 10 is in process of being verified to work with Solr, see this
> > JIRA in the 7.3.1 release notes: SOLR-12141: Fix "bin/solr" shell
> > scripts (Windows/Linux/Mac) to correctly detect major Java version
> > and use numerical version comparison to enforce minimum requirements.
> > Also remove obsolete "UseParNewGC" option.  This allows to start Solr
> > with Java 10 or later. (Uwe Schindler)
> >
> > I'd pretty strongly recommend moving back to the version of Java
> > specified with 6.6.3, probably Java 9. Java 8 has the most mileage
> > with that Solr code base.
> >
> > Best,
> > Erick
> >
> > On Sat, May 12, 2018 at 5:02 PM, turpentyne 
> wrote:
> > > Running into an issue beyond my experience level.
> > >
> > >
> > > In Installed and started Solr 7.3. But, then I realized I need to use
> an
> > > older 6.x version (for Drupal)
> > >
> > > So, I installed Solr 6.6.3. But, it will not start.
> > >
> > > The message I get is:
> > >
> > > **Still not seeing Solr listening on 8983 after 180 seconds!*
> > >
> > > *tail: /Applications/solr-6.6.3/server/logs/solr.log: No such file or
> > > directory**
> > >
> > > I get the same same result, whether I use *bin/solr start* or *sudo*.
> > >
> > > The solr.log is definitely missing. But there is a
> Solr-8983-console.log.
> > > This shows the message below:
> > >
> > > **Java HotSpot(TM) 64-Bit Server VM warning: Option UseConcMarkSweepGC
> > was
> > > deprecated in version 9.0 and will likely be removed in a future
> > release.*
> > >
> > > *Unrecognized VM option 'UseParNewGC'*
> > >
> > > *Error: Could not create the Java Virtual Machine.*
> > >
> > > *Error: A fatal exception has occurred. Program will exit.**
> > >
> > > Java -version displays as 10.0.1. This is a work computer with security
> > > needs, and I believe I need to keep it as updated as possible:
> > >
> > > **java version "10.0.1" 2018-04-17*
> > >
> > > *Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10)*
> > >
> > > *Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode)**
> > >
> > > Also tried with Solr 6.6.3, 6.6.0 and 5.0.0 with same failure and log
> > > message.
> > >
> > > If relevant, I'm on a 2015 macbook pro, using high sierra 10.13.3
> >
>