reloading all the cores

[Yirmiyahu Fischer]

Is there an http request that can make all the cores on a solr server
reload?
Many cores on the server use a shared file, and when this file is changed,
all the cores need to be reloaded.

Thanx.


*Yirmiyahu Fischer*

*Senior Developer |  **Tel**:* *03-9578900 *

*E**mail: **yfisc...@signature-it.com* * | **W*
*eb: **www.signature-it.com* 

Re: reloading all the cores

[Andy Lester]

> Is there an http request that can make all the cores on a solr server
> reload?

I don’t think there is, but you can use the STATUS API call 
(https://solr.apache.org/guide/8_11/coreadmin-api.html 
) to get a list of all 
the cores so that you can call the RELOAD command.

Andy

Re: Highlighting: echo matching query text?

[Stephen Lewis Bianamara]

Hi Alessandro,

Thanks for your reply, apologies for the slowness to get back to you.

It wouldn't be intended for the UI in the end, but rather for application
logic in post processing. In your example of *argues *matching *arguing*,
the desired result would actually be something like

 "comment_en": ["in debate club we treat arguing
like a sport" ]}}}


I'll try taking a look at the highlighters and see if this seems possible
to implement.

Thanks,
Stephen


On Fri, Dec 3, 2021 at 2:52 AM Alessandro Benedetti 
wrote:

> Hi Stephen,
> so you want to show in the UI the original token in the inverted index that
> caused the match?
> This relies on the text analysis configured Solr side and it would be far
> from being intuitive to your final user.
>
> With stemming you made the perfect example:
> The stem of the term potentially is not even a term at all in the language
> associated with the field.
> Not sure if showing the token from the index would help at all from the
> explainability side (in comparison to now showing it).
> Unless the user is informed about the entire text analysis chain(including
> the query time text analysis and he/she understands that), I guess showing
> the token will just complicate even more the situation:
> *e.g.*
> q: arguing
> D1 : argues (Match argu)
>
> Without knowing what index and query time means, what stemming means, and
> that stemming was applied at query time and at indexing time, I am not
> entirely sure it's going to add that much to the final user experience.
>
> Aside from my personal observations, I don't think there's anything in the
> super stratified highlighting module, so you should be able to pick some of
> the implementations and customize it.
>
> Cheers
> --
> Alessandro Benedetti
> Apache Lucene/Solr Committer
> Director, R&D Software Engineer, Search Consultant
>
> www.sease.io
>
>
> On Tue, 30 Nov 2021 at 19:00, Stephen Lewis Bianamara <
> stephen.bianam...@gmail.com> wrote:
>
> > Hi SOLR Community,
> >
> > I am investigating some different options with highlighting, and one
> > feature I wanted to build would require matching a highlighted match back
> > to the original matchin token. I couldn't find a way to do that in the
> > documentation, so I'm guessing that it doesn't exist yet. The application
> > for this would be to leverage solr to understand the query -> field
> > matching with many field types with varying matching rules.
> >
> > The simplest example of what I'd like would be something like this in
> > english: A document like
> >
> >{ "id": "test", "comment_en": "we like dogs" }
> >
> > ..and a query like "dog OR cat". I'd like highlighting to be able to
> return
> > something like this:
> >
> > {"highlighting": {
> >"text_en": {
> >"comment_en": ["we like *dogs*" ]}}}
> >
> > So the essence is that I don't need to know anything about english
> matching
> > rules (in this case plurals) outside of solr to know how it came to the
> > conclusion that this document was a match.
> >
> > Has anyone come up with a solution to this before? Does anyone know an
> > existing feature request for this if not?
> >
> > Thanks!
> > Stephen
> >
>

Solr 6 Replication - Trouble Shooting

[mtn search]

Hello,

While our team is building out a SolrCloud solution for our product we are
still needing to maintain the product in production which uses Solr 6
(master/slave configuration).

We regularly encounter Replication failures between the slaves and the
master.  I have used the following api call to investigate and it appears
that after the failure the Solr replication state gets into a bad state
where the next scheduled replication date is in the past.  So replication
fails and stops.

  server:8080/solr/collection1/replication?command=details&wt=json

I have tried calls to disable and re-nable replications without it being
able to successfully restart replication.

>From the Solr Admin UI (server:8080/solr/old.html#/collection1/replication)
I can select the Replicate Now button. This will successfully replicate
once, but not restart the periodic replication.

Any tips?

I think if there was an api to modify the next replication date, that would
do the trick.

Thanks,
Matt

Re: Solr 6 Replication - Trouble Shooting

[Shawn Heisey]

On 1/3/2022 2:21 PM, mtn search wrote:

From the Solr Admin UI (server:8080/solr/old.html#/collection1/replication)
I can select the Replicate Now button. This will successfully replicate
once, but not restart the periodic replication.

Any tips?

I think if there was an api to modify the next replication date, that would
do the trick.


Are you using the scripts to start Solr with the included jetty, or have 
you moved the webapp into a different container?  I only ask because 
port 8080 is the most commonly used port for standalone container 
installations, so I usually expect Solr on a different port number.


Can you show us the replication configs on the master and the slave? 
Was the "Replicate Now" button found on the admin UI for the slave or 
for the master?  What is the exact version of Solr 6 that you are using?


(In case you're wondering, I am aware that the terms in the previous 
paragraph are sensitive.  I am only using them because those are the 
terms used in the replication configuration for your Solr version.  If I 
had a reasonable way to avoid using those terms for this discussion, I 
would.)


It's been many years since I last used replication in my own setups, but 
the config is fairly straightforward, and hasn't changed a whole lot 
since Solr 1.4.1, which was the last time I used it.


Thanks,
Shawn