Hi Anchal,
the IBM JVM behaves differently in the TLS setup then the Oracle JVM. If
you search for IBM Java TLS 1.2 you find tons of reports of problems
with that. In most cases you can get around that using the system
property "com.ibm.jsse2.overrideDefaultTLS" as documented here:
https://ww
Hi Shawn ,
Thanks for your reply .
Here are the details abut java we are using :
java version "1.8.0_151"
IBM J9 VM (build 2.9, JRE 1.8.0 AIX ppc64-64 Compressed References
20171102_369060 (JIT enabled, AOT enabled)
I have already patched the policy jars .
And I tried to comment out the ciphers
On 11/21/2018 8:59 AM, Marc Schöchlin wrote:
Is it possible to modify the log4j appender to also log other query attributes
like response/request size in bytes and number of resulted documents?
Changing the log4j config might not do anything useful at all. In order
for such a change to be us
On 11/21/2018 7:32 AM, Tech Support wrote:
As per your suggestion, I had add the dataDir in the core.properties file.
It creates the data directory on the new location. But newly added data only
accessable.
If I move the existing index files into the new location, then only I can
able to
You really have to split your index. The good news is that you can use
aliases to search multiples cores at ones. That's probably what you
are looking for. So, you can start with one index and when it gets
close to capacity, add the second one and the third one, etc. But have
an alias that you keep
In SolrCloud there are a couple of places where it might be useful.
First pass each replica collects the top N ids for the aggregator to
sort. If the uniqueKey isn't DV, it needs to either decompress it off
disk or build an structure on heap if it's not DV. Last I knew anyway.
Best,
Erick
On Wed
In a word, "no". There's no provision in Solr for storing two
different parts of the same index in two different directories,
whether or not they're on the same drive.
Best,
Erick
On Wed, Nov 21, 2018 at 6:41 AM Tech Support wrote:
>
> @apa...@elyograg.org
>
> Dear Shawn,
>
> As per your sugg
On 11/21/2018 8:36 AM, Rajdeep Sahoo wrote:
The problem is that we are using master slave solr configuration and for
similar type of query sometime it is taking 512 ms and sometime it is 29
ms . we are observing this issue since the query modification. As part of
modification we have reduced a l
Just as a sanity check, is this getting replicated many times, or further
scaled up... it sounds like about $3.50/mo of disk space on AWS and it
should all fit in ram on any decent sized server.. (i.e. any server that
looks like half or quarter of a decent laptop)
As a question, it's interesting b
Is it a good idea to store the uniqueKey as docValues? A great idea? A maybe or
maybe not idea?
It looks like it will speed up export and streaming. Otherwise, I can’t find
anything the docs pro or con.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
Hello list,
i am using the pretty old solr 4.7 *sigh* release and i am currently in
investigation of performance problems.
The solr instance runs currently very expensive queries with huge results and i
want to find the most promising queries for optimization.
I am currently using the solr logf
Hi all,
The problem is that we are using master slave solr configuration and for
similar type of query sometime it is taking 512 ms and sometime it is 29
ms . we are observing this issue since the query modification. As part of
modification we have reduced a large no of facet.field param. In
solrc
@apa...@elyograg.org
Dear Shawn,
As per your suggestion, I had add the dataDir in the core.properties file.
It creates the data directory on the new location. But newly added data only
accessable.
If I move the existing index files into the new location, then only I can
able to read the da
I was used to take the backup of my core using the following API
curl
'http://localhost:8080/solr/report/replication?command=backup&location=/backup/solr-backup/&numberToKeep=1'
But recently, we started to see Exceptions like following
java.nio.file.NoSuchFileException:
/var/solr/data/re
On Tue, 2018-11-20 at 21:17 -0700, Shawn Heisey wrote:
> Maybe the error condition should be related to a new schema
> property, something like allowQueryOnDocValues. This would default
> to true with current schema versions and false in the next schema
> version, which I think is 1.7. Then a use
15 matches
Mail list logo
