Query about solr configuration

[Ashim Kapoor]

Dear All,

Here is an excerpt from local.cfg

# Solr server/webapp.

# DSpace uses Solr for all search/browse capability (and for usage statistics by default).
# The included 'solr' webapp MUST be deployed to Tomcat for DSpace to function.
# Usually it will be available via port 8080 and the 'solr' context path. But,
# But, you may need to modify this if you are running DSpace on a custom port, etc.
solr.server = http://localhost:8080/solr

My IP address for the app is 192.100.30.xxx

Should I modify and make :-

solr.server = http://192.100.30.xxx:8080/solr

Please clarify.

Best,

Ashim

[Sean Carte]

As your tomcat is on the same server as solr, localhost is fine. Leave it as is.

--
All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CAGEJAoGBU%3D4GR-n6Oh426gkkWQa_y1u6xvQOxHmgPR0WrRf2Cw%40mail.gmail.com.

--

[Ashim Kapoor]

Hello,

Thank you for your email. What exactly is the difference between setting it as localhost vs 192.100.30.xxx ? Can you please elaborate?

Best,

Ashim

[Sean Carte]

Somebody, please correct me if I'm wrong, but I don't think there's any practical difference as far as Tomcat and solr are concerned. However, if you change your IP address at some stage, that's one other setting that you're going to have to remember to change.

--

[Mark H. Wood]

On Thu, Feb 27, 2020 at 01:26:12PM +0200, Sean Carte wrote:
> Somebody, please correct me if I'm wrong, but I don't think there's any
> practical difference as far as Tomcat and solr are concerned. However, if
> you change your IP address at some stage, that's one other setting that
> you're going to have to remember to change.

If you want to connect to Solr on any address other than localhost,
you'll have to disable the LocalHostRestrictionFilter that DSpace adds
to Solr. Otherwise Solr will refuse all contact except from
localhost.

<Parameter
name='LocalHostRestrictionFilter.localhost'
description="Disable Restriction Filter"
override='false'
value='false'
/>

You should then protect Solr using e.g. host firewall rules, since
Solr 4.x is completely unprotected from modification by anyone who can
connect to it. NEVER leave Solr open to the world.

I have run Solr both ways. If we ignore the filter, Solr does not
care how it was contacted.

> On Thu, 27 Feb 2020 at 13:20, Ashim Kapoor <ashim....@nipfp.org.in>
> wrote:
>
> > Hello,
> >
> > Thank you for your email. What exactly is the difference between setting
> > it as localhost vs 192.100.30.xxx ? Can you please elaborate?
> >
> > Best,
> > Ashim
> >
> > On Thu, 27 Feb 2020 at 16:46, Sean Carte <sean....@gmail.com> wrote:
> >
> >> As your tomcat is on the same server as solr, localhost is fine. Leave it
> >> as is.
> >>
> >> On Thu, 27 Feb 2020 at 12:01, Ashim Kapoor <ashim....@nipfp.org.in>
> >> wrote:
> >>
> >>> Dear All,
> >>>
> >>> Here is an excerpt from local.cfg
> >>>
> >>> # Solr server/webapp.
> >>> # DSpace uses Solr for all search/browse capability (and for usage
> >>> statistics by default).
> >>> # The included 'solr' webapp MUST be deployed to Tomcat for DSpace to
> >>> function.
> >>> # Usually it will be available via port 8080 and the 'solr' context
> >>> path. But,
> >>> # But, you may need to modify this if you are running DSpace on a custom
> >>> port, etc.
> >>>

> >>> *solr.server = http://localhost:8080/solr <http://localhost:8080/solr>*

> >>>
> >>> My IP address for the app is 192.100.30.xxx
> >>>
> >>> Should I modify and make :-

> >>> *solr.server = http://192.100.30.xxx:8080/solr
> >>> <http://192.100.30.xxx:8080/solr>*

> >>>
> >>> Please clarify.
> >>>
> >>> Best,
> >>> Ashim
> >>>
> >>>
> >>> --
> >>> All messages to this mailing list should adhere to the DuraSpace Code of
> >>> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> >>> ---
> >>> You received this message because you are subscribed to the Google
> >>> Groups "DSpace Technical Support" group.
> >>> To unsubscribe from this group and stop receiving emails from it, send
> >>> an email to dspace-tech...@googlegroups.com.
> >>> To view this discussion on the web visit
> >>> https://groups.google.com/d/msgid/dspace-tech/CAGEJAoGBU%3D4GR-n6Oh426gkkWQa_y1u6xvQOxHmgPR0WrRf2Cw%40mail.gmail.com

> >>> <https://groups.google.com/d/msgid/dspace-tech/CAGEJAoGBU%3D4GR-n6Oh426gkkWQa_y1u6xvQOxHmgPR0WrRf2Cw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> >>> .
> >>>
> >>
> >>
> >> --
> >>
> >>
>
> --

>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CA%2BxAuhPETTH8fziVcWv67aeuyezmgBO8w_s1e9yVqvvoMagUig%40mail.gmail.com.

--
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu