On 4/23/2018 11:56 PM, Papa Pappu wrote:
> I've written down my query over stack-overflow. Here is the link for that :
> https://stackoverflow.com/questions/49993681/preventing-solr-cache-flush-when-commiting
>
> In short, I am facing troubles maintaining my solr caches when commits
> happen and th
On 4/24/2018 10:26 AM, Lee Carroll wrote:
> Does the solr cell contrib give access to the files raw content along with
> the extracted metadata?\
That's not usually the kind of information you want to have in a Solr
index. Most of the time, there will be an entry in the Solr index that
tells the
On 4/24/2018 1:53 PM, Markus Jelsma wrote:
> I don't see stack traces for most WARNs, for example the checksum
> warning on recovery (other thread), or the Trie* deprecations.
I just tried it on 7.3.0. Added a line to CoreContainer.java to log an
exception at warn when Solr is starting:
log
I didn't know you can add boosts like that (&boost=2 ). Are you boosting on
a field or document by using that syntax?
On Sun, Apr 22, 2018 at 10:51 PM, Ryan Yacyshyn
wrote:
> Hi all,
>
> When viewing the explain under debug=true in Solr 7.3.0 using
> the edismax query parser with a boost, I only
Inline.
-Original message-
> From:Shawn Heisey
> Sent: Tuesday 24th April 2018 21:18
> To: solr-user@lucene.apache.org
> Subject: Re: IndexFetcher cannot download index file
>
> On 4/24/2018 12:36 PM, Markus Jelsma wrote:
> > I should be more precise, i said the stack traces of WARN are
On 4/24/2018 12:36 PM, Markus Jelsma wrote:
> I should be more precise, i said the stack traces of WARN are not shown, only
> the messages are visible. The 'low disk space' line was hidden in the stack
> trace of the WARN, as you can see in the pasted example, thus invisible in
> the GUI with de
Does Solr have regex search support for "\s"? as in: q=FIELD:/starts
with[\s0-9]*/
Both \s and \\s do not seem to have an effect. thanks
using solr 5.5.4
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
To be even more precise, it seems some WARN logs do show a stack trace in the
GUI, but others don't. For example:
org.apache.solr.common.SolrException: URLDecoder: Invalid character encoding
detected after position 23 of query string / form data (while parsing as UTF-8)
at
org.apache.so
Hello Shawn,
I should be more precise, i said the stack traces of WARN are not shown, only
the messages are visible. The 'low disk space' line was hidden in the stack
trace of the WARN, as you can see in the pasted example, thus invisible in the
GUI with default settings.
If the log level of t
>From memory try the following:
Don't manually commit from client after batch indexing
set soft commit to be a a long time interval. As long as acceptable to run
stale, say 5 mins or longer if you can.
set hard commit to be short (seconds ) to keep everything neat and tidy
regards updates and avo
On 4/24/2018 9:46 AM, Markus Jelsma wrote:
> Disk space was WARN level. It seems only stack traces of ERROR level messages
> are visible via the GUI, and that is where the 'No space left' was hiding.
> Without logging in and inspecting the logs manually, you will never notice
> that message.
Th
Hi,
I've written down my query over stack-overflow. Here is the link for that :
https://stackoverflow.com/questions/49993681/preventing-solr-cache-flush-when-commiting
In short, I am facing troubles maintaining my solr caches when commits
happen and the question provides detailed description of th
: I also noticed that there's the concept of "latest" (similar to "current"
: in postgres documentation) in solr. This is pretty cool. I am afraid
: though, that this currently is somewhat confusing. E.g., if I search for
: managed schema in google I get this as 1st url:
:
:
https://lucene.apach
Hello,
I am wondering under what different conditions does that CDCR bootstrap
process gets triggered. I did notice it getting triggered after I stopped
CDCR and then started again later and now I am trying to reproduce the same
behavior.
In case target cluster is left behind and buffer was disa
Does the solr cell contrib give access to the files raw content along with
the extracted metadata?
cheers Lee C
On 24/04/2018 16:44, Walter Underwood wrote:
In Ultraseek, we checked free disk space before starting a merge or
replication. If there wasn’t enough space, it emailed an error to the admin and
disabled merging or replication, respectively.
Checking free disk space on Windows was a pain.
On a
Hello,
Disk space was WARN level. It seems only stack traces of ERROR level messages
are visible via the GUI, and that is where the 'No space left' was hiding.
Without logging in and inspecting the logs manually, you will never notice that
message.
Regards,
Markus
2018-04-24 12:23:44.215 WARN
In Ultraseek, we checked free disk space before starting a merge or
replication. If there wasn’t enough space, it emailed an error to the admin and
disabled merging or replication, respectively.
Checking free disk space on Windows was a pain.
wunder
Walter Underwood
wun...@wunderwood.org
http:/
On 4/24/2018 6:52 AM, Markus Jelsma wrote:
Forget about it, recovery got a java.io.IOException: No space left on device
but it wasn't clear until i inspected the real logs.
The logs in de web admin didn't show the disk space exception, even when i
expand the log line. Maybe that could be chang
On 4/24/2018 2:03 AM, msaunier wrote:
If I access to the interface, I have a null pointer exception:
null:java.lang.NullPointerException
at
org.apache.solr.handler.RequestHandlerBase.getVersion(RequestHandlerBase.java:233)
The line of code where this exception occurred uses fundamenta
On 4/24/2018 6:30 AM, Chris Ulicny wrote:
I haven't worked with AWS, but recently we tried to move some of our solr
instances to a cloud in Google's Cloud offering, and it did not go well.
All of our problems ended up stemming from the fact that the I/O is
throttled. Any complicated enough query
On 4/24/2018 8:50 AM, Steven White wrote:
We currently support both Oracle and IBM Java to run Solr and I'm task to
switch over to OpenJDK.
Oracle Java is the preferred choice. OpenJDK should be work very well,
as long as it's at least version 7. Recent Solr versions require Java
8, so that
Denis,
Can you enable infoSteam
https://lucene.apache.org/solr/guide/6_6/indexconfig-in-solrconfig.html#IndexConfiginSolrConfig-OtherIndexingSettings
and examine logs about throttling?
And what if you try without auto-commit?
On Tue, Apr 24, 2018 at 12:37 AM, Denis Demichev wrote:
> I conducted
Hi everyone,
We currently support both Oracle and IBM Java to run Solr and I'm task to
switch over to OpenJDK.
Does anyone use Solr, any version, with OpenJDK? If so, what has been your
experience? Also, what platforms have you used it on?
I run Solr on Windows, Linux, AIX and Solaris and on e
Forget about it, recovery got a java.io.IOException: No space left on device
but it wasn't clear until i inspected the real logs.
The logs in de web admin didn't show the disk space exception, even when i
expand the log line. Maybe that could be changed.
Thanks,
Markus
-Original messag
Hello,
Slightly different questions/problem, what is going on here on 7.2.1? During
the recovery, none of this node's fellow replicas indexes were changed but we
still got this error.
When we got that error, the recovery was restarted, but shortly after the
replicas indexes got updated and re
I haven't worked with AWS, but recently we tried to move some of our solr
instances to a cloud in Google's Cloud offering, and it did not go well.
All of our problems ended up stemming from the fact that the I/O is
throttled. Any complicated enough query would require too many disk reads
to return
Hello,
After a failed log replay (it got a ClassCastException) with 7.2.1 it seems
Solr tries to haul over a 50 GB index from another replica. While doing so, it
throws a good number of checksum warnings.
Why don't the checksums match? Can i safely ignore them? Do i need to do
something about
Hello,
We have a DocumentTransformer that gets a Field from the SolrDocument and casts
it to StoredField (although aparently we don't need to cast). This works well
in tests and fine in production, except for some curious, unknown and
unreproducible, cases, throwing the ClassCastException.
I c
Are you using SolrCloud or any distributed search ?
If you are using just a single Solr instance, LTR should have no problem
with pagination.
The re-rank involves the top K and then you paginate.
So if a document from the original score page 1 ends up in page 3, you will
see it at page three.
have
I have modify DIH definition to simplify but sames errors:
## indexation_events.xml
##
Maxence,
-Message d'origine-
De : msaunier [mailto:msaun...@citya.com]
Envoyé : mardi 24
If I access to the interface, I have a null pointer exception:
null:java.lang.NullPointerException
at
org.apache.solr.handler.RequestHandlerBase.getVersion(RequestHandlerBase.java:233)
at
org.apache.solr.handler.admin.SolrInfoMBeanHandler.addMBean(SolrInfoMBeanHandler.java:187)
Hello Shawn,
Thanks for your answers.
#
So, indexation_events.xml file is:
Hi Hoss et al,
Thanks for the prompt answer and the links. I see there's quite some
interesting discussions around the issue already. Let me take some time to
get into details.
I also noticed that there's the concept of "latest" (similar to "current"
in postgres documentation) in solr. This is pr
34 matches
Mail list logo
