Hi,
we have some setups that use an encryption zone in HDFS. Once you have
the hdfs config setup the rest is transparent to the client and thus
Solr works just fine like that. Said that, we have some general issues
with Solr and HDFS. The main problem seems to be around the transaction
log
On 9/11/2019 5:27 PM, Ashwin Ramesh wrote:
I was wondering if there is a way we can tell solr (7.3+) to run none of
it's scoring logic. We would like to simply add a set of filter queries and
order on a specific docValue field.
e.g. "Give me all fq=color:red documents ORDER on popularityScore
Hi everybody,
I was wondering if there is a way we can tell solr (7.3+) to run none of
it's scoring logic. We would like to simply add a set of filter queries and
order on a specific docValue field.
e.g. "Give me all fq=color:red documents ORDER on popularityScore DESC"
Thanks in advance,
Ash
Hi,
I am interested in encrypting/protecting my solr indices. I am wondering
if Solr can work the an encrypted HDFS. I see that these instructions (
https://docs.cloudera.com/HDPDocuments/HDP3/HDP-3.1.0/configuring-hdfs-encryption/content/configuring_and_using_hdfs_data_at_rest_encryption.html)
We also see an accumulation of tlog files on the target solrs. One of our
production clouds crashed due to too many open files
2019-09-11 15:59:39.570 ERROR (qtp1355531311-81540)
[c:bioreliance-catalog-testarticle-20190713 s:shard2 r:core_node8
Hi,
It fails many times, sharing the iteration:
Passed:
Wed Sep 11 16:49:18 UTC 2019
Wed Sep 11 16:48:56 UTC 2019
Wed Sep 11 16:48:36 UTC 2019
Wed Sep 11 16:48:18 UTC 2019
Wed Sep 11 16:47:55 UTC 2019
Wed Sep 11 16:47:35 UTC 2019
Wed Sep 11 16:47:16 UTC 2019
Wed Sep 11 16:46:55 UTC 2019
Wed Sep
Is it every time it fails, or just sometimes?
What is the timestamps on the failed and passed iterations?
And how much disk space do you have available on the slave?
Venlig hilsen/Best regards
*Jon Kjær Amundsen*
Developer
Phone: +45 7023 9080
E-mail: j...@udbudsvagten.dk
Web:
I am seeing multiple entries for the exact same URLs and each time I re-index
the contents the crawler adds the same entry one more time.
I have id defined in the schema.xml file. It seems
Solr is not reading the schema file - I cannot think of any other
explanation how the unique key
Okay, after a bit of debugging and reading JIRA issues (SOLR-12074,
SOLR-12632), I think this does not work because there's no terms index for
point fields.
So it probably cannot work, and one would need to have a separate string
field with the same values (copyField) to use the termfreq function
My index size is 2.62 GB, and :
00:00:10
Thanks & Regards,
Akreeti Agarwal
-Original Message-
From: Paras Lehana
Sent: Wednesday, September 11, 2019 5:39 PM
To: solr-user@lucene.apache.org
Subject: Re: Replication Iteration
What is the size of your index? Is it too big? How fast is
What is the size of your index? Is it too big? How fast is your link
between master and slave?
I'm asking these because, for larger indexes, you may want to raise
commitReserveDuration defined in ReplicationHandler in solrconfig.xml.
00:00:10
>From SolrReplication
I am seeing the logs on both UI and file, but I only see this error:
ReplicationHandler
Index fetch failed :org.apache.solr.common.SolrException: Unable to download
segments_znow completely. Downloaded 0!=2217
Thanks & Regards,
Akreeti Agarwal
-Original Message-
From: Paras Lehana
Hi Akreeti,
Have you tried using the old UI to see errors? I had always experienced not
seeing status updates about replication in the newer UI. Check for the
option on top right of Solr UI.
And where are you seeing logs - on solr UI or from a file?
On Wed, 11 Sep 2019 at 16:12, Akreeti Agarwal
In the logs I don't see any errors, mostly after every 1-2 min replication
fails and I am not able to identify the root cause for it.
Thanks & Regards,
Akreeti Agarwal
-Original Message-
From: Jon Kjær Amundsen
Sent: Wednesday, September 11, 2019 12:15 PM
To:
Hello, James.
Right. Syntax is cumbersome
q=articledate:[2018-09-04T00:00:00Z TO 2019-09-10T23:59:59Z] {!join to=id
from=url v=$param}=articledate:[2018-09-04T12:00:00Z TO
2019-09-10T11:59:59Z])
On Wed, Sep 11, 2019 at 9:39 AM Smith2, James
wrote:
> Hi there,
>
> I was hoping that you may be
It depends on the timestamps.
The red iterations are failed replications and the green are passed
replications.
If the newest timestamp is green the latest replication went well, if it is
red, it failed.
You should check the solr log on the slave if a recent replication have
failed to see the
Hi there,
I was hoping that you may be able to assist us with a search issue we're facing.
Each one of these queries work on their own:
articledate:[2018-09-04T00:00:00Z TO 2019-09-10T23:59:59Z]
{!join to=id from=url}articledate:[2018-09-04T12:00:00Z TO
2019-09-10T11:59:59Z])
But if we try
17 matches
Mail list logo