Problem using user.timezone in DIH

2017-09-22 Thread Jamie Jackson
Solr 6.6.0 I'm getting a weird issue and a misleading error when I try to use the user.timezone property in a data import handler configuration which has child entities: Caused by: java.sql.SQLInvalidAuthorizationSpecException: Could not connect: Access denied for user '{}'@'111.222.111.222'

Re: Replicates not recovering after rolling restart

2017-09-22 Thread Erick Erickson
Gah! Don't you hate it when you spend days on something like this? Slight clarification. _version_ is used for optimistic locking, not replication. Let's say you have two clients updating the same document and sending it to Solr at the same time. The _version_ field is filled out automagically

Re: Replicates not recovering after rolling restart

2017-09-22 Thread Bill Oconnor
Thanks everyone for the responses. I believe I have found the problem. The type of __version__ is incorrect in our schema. This is a required field that is primarily used by Solr. Our schema has typed it as type=int instead of type=long I believe that this number is used by the

RE: AEM SOLR integaration

2017-09-22 Thread Davis, Daniel (NIH/NLM) [C]
Gunalan, I think this depends on your system environment. It is a general "service discovery" issue. On-premise, my organization uses f5 BigIP as a load balancer, and so we merely have f5 LTM direct traffic from one name to any of a number of Solr instances. If they are all SolrCloud, it

Re: How to build solr

2017-09-22 Thread Erick Erickson
1> do you have ant installed? My guess is yes but thought I'd check 2> what target are you executing? "ant server"? "ant dist"? ??? 3> the first time you execute an ant task you should see a message about a target to install "ivy", did you see it and did you follow it? That should install

Re: Error Opening new IndexSearcher - LockObtainFailedException

2017-09-22 Thread Erick Erickson
Hmmm, 6.4 was considerably before the refactoring that this patch addresses so it's not a surprise that it doesn't apply. On Thu, Sep 21, 2017 at 10:28 PM, Shashank Pedamallu wrote: > Hi Luiz, > > Unfortunately, I’m on version Solr-6.4.2 and the patch does not apply >

Re: Solr nodes crashing (OOM) after 6.6 upgrade

2017-09-22 Thread shamik
Susheel, my inference was based on the Qtime value from Solr log and not based on application log. Before the CPU spike, the query time didn’t give any indication that they are slow in the process of slowing down. As the GC suddenly triggers a high CPU usage, query execution slows down or chocks,

Re: mm is not working if you have same term multiple times in query

2017-09-22 Thread Aman Deep Singh
We can't use shingles as user can query lock and lock ,or any other combination although and and some other words can be passed in stop word processing but can't rely on that completely. On 22-Sep-2017 7:00 PM, "Emir Arnautović" wrote: It seems to me that all OOTB

Re: Strange Behavior When Extracting Features

2017-09-22 Thread alessandro.benedetti
I think this has nothing to do with the LTR plugin. The problem here should be just the way you use the local params, to properly pass multi term local params in Solr you need to use *'* : efi.case_description='added couple of fiber channel' This should work. If not only the first term will be

Re: mm is not working if you have same term multiple times in query

2017-09-22 Thread Emir Arnautović
It seems to me that all OOTB solution would include some query parsing on client side. If those are adjacent values, you could try play with shingles to get it to work. Brainstorming: custom token filter that would assign token occurrence number to each token: e.g. “foo lock bar lock” would

Re: Indexing CSV files with filenames

2017-09-22 Thread sophia250
how did you find the file name? When i do posting, i use wildcard *.csv. Your way seems work only when you are posting by each -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: mm is not working if you have same term multiple times in query

2017-09-22 Thread Aman Deep Singh
Hi Emir, Thanks for the reply, I understand how the dismax/edismax works ,my problem is I don't want to show the results with one token only , I cannot use phrase query here because the phrase query doesn't work with single word query so to do so we need to change the search request (qf or pf

Re: Solr nodes crashing (OOM) after 6.6 upgrade

2017-09-22 Thread Susheel Kumar
It may happen that you may never find the queries/query time being logged for the queries which caused OOM and your app never got chance to log how much time it took... So if you had proper exception handled in your client code, you may see exception being logged but not see the query time for

Re: mm is not working if you have same term multiple times in query

2017-09-22 Thread Emir Arnautović
Hi Aman, You have wrong expectations: Edismax does respect mm, it’s just that it is met. If you take a look at parsed query, it’ll be something like: +(((name:lock) (name:lock))~2) And from dismax perspective it found both terms. It will not start searching for the next term after first is found

Re: AEM SOLR integaration

2017-09-22 Thread Gunalan V
Thank You! I was looking for some suggestions in building the SOLR infrastructure. Like how each AEM instance should point to ? Might be one AEM instance to one SOLR cloud (With internal zookeeper) in all environments or any specific architecture we need to follow while going with AEM.

mm is not working if you have same term multiple times in query

2017-09-22 Thread Aman Deep Singh
Hi, I'm using Solr 6.6.0 i have set mm as 100% but when i have the repeated search term then mm param is not honoured I have 2 docs in index Doc1- name=lock Doc 2- name=lock lock Now when i'm quering the solr with query

Re: Solr nodes crashing (OOM) after 6.6 upgrade

2017-09-22 Thread shamik
I usually log queries that took more than 1sec. Based on the logs, I haven't seen anything alarming or surge in terms of slow queries, especially around the time when the CPU spike happened. I don't necessarily have the data for deep paging, but the usage of sort parameter (date in our case) has

Re: Solr nodes crashing (OOM) after 6.6 upgrade

2017-09-22 Thread Michael Kuhlmann
Hi Shamik, funny enough, we had a similar issue with our old legacy application that still used plain Lucene code in a JBoss container. Same, there were no specific queries or updates causing this, the performance just broke completely without unusual usage. GC was raising up to 99% or so.

RE: How to build solr

2017-09-22 Thread Sidana, Mohit
Here's a very nice article on " How to Debug Solr With Eclipse" which I have used previously to debug solr with eclipse. http://opensourceconnections.com/blog/2013/04/13/how-to-debug-solr-with-eclipse/ -Original Message- From: Atita Arora [mailto:atitaar...@gmail.com] Sent: Friday,

Re: Solr nodes crashing (OOM) after 6.6 upgrade

2017-09-22 Thread Emir Arnautović
It does not have to be query load - it can be one heavy query that cause memory consumption (heavy faceting, deep paging,…) and after that GC jumps in. Maybe you could start with log and see if there are queries that have large QTime, Emir > On 22 Sep 2017, at 12:00, shamik

Re: Solr nodes crashing (OOM) after 6.6 upgrade

2017-09-22 Thread shamik
All the tuning and scaling down of memory seemed to be stable for a couple of days but then came down due to a huge spike in CPU usage, contributed by G1 Old Generation GC. I'm really puzzled why the instances are suddenly behaving like this. It's not that a sudden surge of load contributed to

Re: Sorting by distance resources with WKT polygon data

2017-09-22 Thread Ere Maijala
Hi, our strategy is to have a separate center coordinate field that we use for sorting. This has the additional benefit that it's possible to have the indexed center point differ from the polygon's centroid, which can be useful e.g. with cities, where the city center can be quite a bit

Re: How to build solr

2017-09-22 Thread Atita Arora
http://www.gingercart.com/Home/search-and-crawl/build-and-run-solr-from-source and follow thread http://lucene.472066.n3.nabble.com/running-solr-in-debug-through-eclipse-td4159777.html to run solr server in debug mode through eclipse. Should give you some hint. Let me go through your error

Re: AEM SOLR integaration

2017-09-22 Thread Atita Arora
https://www.slideshare.net/DEEPAKKHETAWAT/basics-of-solr-and-solr-integration-with-aem6-61150010 This could probably help too along with the link Nicole shared. On Fri, Sep 22, 2017 at 12:28 PM, Nicole Bilić wrote: > Hi, > > Maybe this could help you out

Re: Replicates not recovering after rolling restart

2017-09-22 Thread Rick Leir
Wunder, Erick $ dc 16o 1578578283947098112p 15E83C95E8D0 That is an interesting number. Is it, as a guess, machine instructions or an address pointer? It does not look like UTF-8 or ASCII. Machine code looks promising: Disassembly: 0: 15 e8 3c 95 e8 adceax,0xe8953ce8 5:

Re: AEM SOLR integaration

2017-09-22 Thread Nicole Bilić
Hi, Maybe this could help you out http://www.aemsolrsearch.com/ Regards, Nicole On Sep 22, 2017 05:41, "Gunalan V" wrote: > Hello, > > I'm looking for suggestion in building the SOLR infrastructure so Kindly > let me know if anyone has integerated AEM (Adobe Experience

Re: CloudSolrServer set http request timeout

2017-09-22 Thread Vincenzo D'Amore
Thanks for the suggestion, it's working like a charm. Ciao, Vincenzo > On 21 Sep 2017, at 19:51, Jason Gerlowski wrote: > > Hi Vincenzo, > > Have you tried setting the read/socket timeout on your client? > CloudSolrServer uses a LBHttpSolrServer under the hood, which

Re: How to build solr

2017-09-22 Thread srini sampath
PS: I have Installed both Ant and Ivy in my system. But there is no ${user.home}\.ant\lib folder On Fri, Sep 22, 2017 at 11:41 AM, srini sampath wrote: > Thanks Aman, > Erick, I followed the link and I am getting the following error, > > Buildfile:

Re: How to build solr

2017-09-22 Thread srini sampath
Thanks Aman, Erick, I followed the link and I am getting the following error, Buildfile: ${user.home}\git\lucene-solr\build.xml compile: -check-git-state: -git-cleanroot: -copy-git-state: git-autoclean: resolve: ivy-availability-check: BUILD FAILED