Varma:
What version of Solr is running? You said master slave so you are not
running a solrcloud? Some mistakenly hold onto the nomenclature as
describing the leadership state.
When you look at the log do you have a window on the replication logging?
Search Queries are routed to the master for
I'm using Solr 7.7.1, 12 shards,
router:{"field":"route", "name":"compositeId"}, and find the realtime get
only returns results if I specify the leader core-url. Most of the time I
see no results.
On Thu, 11 Oct 2018 at 23:41, Chris Ulicny wrote:
> We are relatively far behind with this one.
Is there something special about parent/child blocks you cannot do through
JSON? Or XML?
Both Solr XML and Solr JSON support it.
New style parent/child mapping is also supported in latest Solr but I think
it is done differently.
Regards,
Alex
On Wed, Jun 5, 2019, 6:29 PM Pratik Patel,
Hello Everyone,
I am trying to write some unit tests for solr queries which requires some
data in specific state. There is a way to load this data through json files
but the problem is that the required data needs to have parent-child blocks
to be present.
Because of this, I would prefer if there
++solr-user@lucene.apache.org
On Thu 6 Jun, 2019, 1:19 AM varma mahesh, wrote:
> Hi Team,
>
>
> What happens to Sitecore - Solr query handling when a core is corrupted in
> Solr slave in a Master - slave setup?
>
> Our Sitecore site's solr search engine is a master-slave setup. One of the
>
On 6/5/2019 2:40 PM, Gus Heck wrote:
Experiences that force the user to think about the browser cache are
sub-par :). Anything that changes the URL will interrupt caching so just
adding a query parameter &_v=8.1.1 (or whatever) to every request would
probably do the trick, there's no need to
Experiences that force the user to think about the browser cache are
sub-par :). Anything that changes the URL will interrupt caching so just
adding a query parameter &_v=8.1.1 (or whatever) to every request would
probably do the trick, there's no need to mess with file names or file
locations IF
On 6/5/2019 9:39 AM, Rahul Goswami wrote:
I have a solrcloud setup on Windows server with below config:
3 nodes,
24 shards with replication factor 2
Each node hosts 16 cores.
16 CPU cores, or 16 Solr cores? The info may not be all that useful
either way, but just in case, it should be
Could perhaps the UI have a version hard coded, and when the dashboard fetches
/admin/info/system it compares the version, and if newer than what is in the
JS, it will pop up a dialogue to ask user to reload and clear caches for the
site in browser?
Jan Høydahl
> 5. jun. 2019 kl. 20:47 skrev
Yes, set Xmx and Xms the same.
We run an 8 GB heap for all our clusters. Unless you are doing some really
memory-intensive stuff like faceting, 8 GB should be fine.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Jun 5, 2019, at 1:05 PM, Gus Heck
Probably not a solution, but so.ething I notice off the bat... generally
you want Xmx and Xms set to the same value so the jvm doesn't have to spend
time asking for more and more memory, and also reduce the chance that the
memory is not available by the time solr needs it.
On Wed, Jun 5, 2019,
On 6/5/2019 11:10 AM, Colvin Cowie wrote:
Upon opening the Admin UI I got some nasty behaviour, which appears to be a
result of some the Solr 6 Admin UI pages being cached.
In general I would consider this a bug, and a good reason to raise an
issue in Jira.
The admin UI should tell the
An alternative to backup and restore could be the data center replication in
Solr:
https://lucene.apache.org/solr/guide/7_3/cross-data-center-replication-cdcr.html
> Am 05.06.2019 um 19:18 schrieb Joe Lerner :
>
> Hi,
>
> Our application is migrating from on-premise to AWS. We are currently
On 6/5/2019 11:18 AM, Joe Lerner wrote:
Our application is migrating from on-premise to AWS. We are currently on
Solr Cloud 7.3.0.
We are interested in exploring ways to do this with minimal, down-time, as
in, maybe one hour.
One strategy would be to set up a new empty Solr Cloud instance in
Hi,
Our application is migrating from on-premise to AWS. We are currently on
Solr Cloud 7.3.0.
We are interested in exploring ways to do this with minimal, down-time, as
in, maybe one hour.
One strategy would be to set up a new empty Solr Cloud instance in AWS, and
reindex the world. But
Hello,
I have just hit this and wondered if anyone has seen similar before since
the login page was added to the Admin UI?
I'm using Solr 6.6.6 currently, but I'm in the process of moving to 8.1.x.
That means I've been accessing the UI from 6 and had it cached. I switched
off 6 and run the 8.1.x
Thanks for letting us know. Yeah, many thousands of fields is an anti-pattern.
At some point I’d like to put in a limit or log warning or something so people
would get warning when something like this happens.
And to make matters more “interesting”, the meta-data associated with the
fields
On 6/5/2019 8:41 AM, Danilo Tomasoni wrote:
Hello,
I have two solr instances with exactly the same configuration.
The only difference that i know is that the first (the working one, is solr
7.3.0,
while the one that's not working is solr 7.3.1)
If I execute the same query (with debugQuery=on)
Hello,
I have a solrcloud setup on Windows server with below config:
3 nodes,
24 shards with replication factor 2
Each node hosts 16 cores.
Index size is 1.4 TB per node
Xms 8 GB , Xmx 24 GB
Directory factory used is SimpleFSDirectoryFactory
The cloud is all nice and green for the most part.
Last I knew, you could define a userCache statically in solrconfig.xml, even if
you can’t use the config API to insert one….
> On Jun 5, 2019, at 2:22 AM, Mikhail Khludnev wrote:
>
> Hello, Abhishek.
>
> It seems config api lacks usercache functionaly, thus it deserves jira.
> Inserting user
This pretty frequently happens when you bounce solr instances around. I usually
use
ps aux | grep solr
to find the pid to kill.
I can’t help you at all about why lsof isn’t working, that has nothing to do
with Solr.
Best,
Erick
> On Jun 5, 2019, at 5:23 AM, Mary Eji wrote:
>
> Hi,
> I’ve
Hi,
I’ve been using Solr for a while now. I’m having trouble using the software
currently: I’m getting this error "Oops! Looks like port 8983 is already being
used by another process. Please choose a different port”.
I’m using Mac OS. When this happened sometimes ago in the Fall or so, I used
Hello,
I have two solr instances with exactly the same configuration.
The only difference that i know is that the first (the working one, is solr
7.3.0,
while the one that's not working is solr 7.3.1)
If I execute the same query (with debugQuery=on) it gets parsed in different
ways on the two
4 June 2019, Apache Solr™ 7.7.2 available
The Lucene PMC is pleased to announce the release of Apache Solr 7.7.2.
Solr is the popular, blazing fast, open source NoSQL search platform from the
Apache Lucene project. Its major features include powerful full-text search,
hit highlighting, faceted
On 6/5/2019 7:08 AM, vishal patel wrote:
I have attached RAR file but not attached properly. Again attached txt file.
For 2 shards and 2 replicas, we have 2 servers and each has 256 GB ram
and 1 TB storage. One shard and another shard replica in one server.
You got lucky. Even text files
Hi Shawn,
I see. Thank you so much for your reply! Best!
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
On 6/5/2019 5:35 AM, vishal patel wrote:
We have 2 shards and 2 replicas in Live also have multiple collections.
We are performing heavy search and update.
There is no information here about how many servers are serving those
four shard replicas.
-> I have*attached*some query which takes
We have 2 shards and 2 replicas in Live also have multiple collections. We are
performing heavy search and update.
-> I have attached some query which takes time for executing. why does it take
too much time? Due to the query length?
-> Some times replica goes in recovery mode and from the
Can you help me with the subquery way, i tried that long back but it was
giving me some exception (can't remember that).
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Hi Jason,
Yes. I am using the latest Solr 8.1.1.
The query which I'm using is the JSON Facet query which I faced the error
initially.
Regards,
Edwin
On Tue, 4 Jun 2019 at 20:15, Jason Gerlowski wrote:
> Hi Edwin,
>
> Thanks for the additional datapoint. It seemed to work for me, but we
>
Hello Christopher,
On 03.06.19 23:13, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ralph,
On 6/2/19 16:32, Ralph Soika wrote:
The whole system is highly transactional as it runs on Java EE with
JPA and Session EJBs.
And you write-through from your application
Hello, Jai.
It seems like sort functionality needs to be developed for
https://lucene.apache.org/solr/guide/7_4/transforming-result-documents.html#child-childdoctransformerfactory
However, it might be already reachable via more comprehensive
Hello, Abhishek.
It seems config api lacks usercache functionaly, thus it deserves jira.
Inserting user cache in runtime seems undoable, the closed option is to
modify solrCore.SolrConfg.userCacheConfigs and obtain new SolrIndexSearch
after that, but the latter is a tricky thing to achieve.
Hi Json,
Many thanks for this excellent explanation, it's all now clear to me, I've
fixed the problem!
I didn't anticipate that the aliases would be resolved before everything
else..
Thanks again!
Sotiri
On Tue, Jun 4, 2019 at 2:07 PM Jason Gerlowski
wrote:
> Hi Sotiris,
>
> First off, forget
34 matches
Mail list logo
