You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Dave Brondsema <da...@brondsema.net> on 2015/06/29 17:25:06 UTC
[allura:tickets] #7907 Use standardized solr installation
---
** [tickets:#7907] Use standardized solr installation**
**Status:** open
**Milestone:** unreleased
**Created:** Mon Jun 29, 2015 03:25 PM UTC by Dave Brondsema
**Last Updated:** Mon Jun 29, 2015 03:25 PM UTC
**Owner:** nobody
We have a hacky setup for solr (both step-by-step and docker install):
* we wget solr, instead of using a system package
* we copy our schema into the solr example dir
* we run `start.jar` directly instead of a service
For docker, we should be able to use a solr image that somebody else has set up. For the step-by-step we should use system packages and perhaps borrow ideas from the solr container's Dockerfile.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #7907 Use standardized solr installation
Posted by Dave Brondsema <da...@brondsema.net>.
- **labels**: sf-4, sf-current, 42cc --> sf-4, 42cc
---
** [tickets:#7907] Use standardized solr installation**
**Status:** closed
**Milestone:** unreleased
**Labels:** sf-4 42cc
**Created:** Mon Jun 29, 2015 03:25 PM UTC by Dave Brondsema
**Last Updated:** Wed Dec 09, 2015 06:12 PM UTC
**Owner:** Igor Bondarenko
We have a hacky setup for solr (both step-by-step and docker install):
* we wget solr, instead of using a system package
* we copy our schema into the solr example dir
* we run `start.jar` directly instead of a service
For docker, we should be able to use a solr image that somebody else has set up. For the step-by-step we should use system packages and perhaps borrow ideas from the solr container's Dockerfile.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #7907 Use standardized solr installation
Posted by Igor Bondarenko <je...@gmail.com>.
- **status**: in-progress --> review
- **Comment**:
Closed #873. `ib/7907a`
---
** [tickets:#7907] Use standardized solr installation**
**Status:** review
**Milestone:** unreleased
**Labels:** sf-4 sf-current 42cc
**Created:** Mon Jun 29, 2015 03:25 PM UTC by Dave Brondsema
**Last Updated:** Wed Dec 09, 2015 01:55 PM UTC
**Owner:** Igor Bondarenko
We have a hacky setup for solr (both step-by-step and docker install):
* we wget solr, instead of using a system package
* we copy our schema into the solr example dir
* we run `start.jar` directly instead of a service
For docker, we should be able to use a solr image that somebody else has set up. For the step-by-step we should use system packages and perhaps borrow ideas from the solr container's Dockerfile.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #7907 Use standardized solr installation
Posted by Igor Bondarenko <je...@gmail.com>.
- **labels**: sf-4, sf-current --> sf-4, sf-current, 42cc
- **status**: open --> in-progress
- **assigned_to**: Igor Bondarenko
---
** [tickets:#7907] Use standardized solr installation**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** sf-4 sf-current 42cc
**Created:** Mon Jun 29, 2015 03:25 PM UTC by Dave Brondsema
**Last Updated:** Mon Oct 05, 2015 03:35 PM UTC
**Owner:** Igor Bondarenko
We have a hacky setup for solr (both step-by-step and docker install):
* we wget solr, instead of using a system package
* we copy our schema into the solr example dir
* we run `start.jar` directly instead of a service
For docker, we should be able to use a solr image that somebody else has set up. For the step-by-step we should use system packages and perhaps borrow ideas from the solr container's Dockerfile.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #7907 Use standardized solr installation
Posted by Dave Brondsema <da...@brondsema.net>.
- **status**: review --> closed
---
** [tickets:#7907] Use standardized solr installation**
**Status:** closed
**Milestone:** unreleased
**Labels:** sf-4 sf-current 42cc
**Created:** Mon Jun 29, 2015 03:25 PM UTC by Dave Brondsema
**Last Updated:** Wed Dec 09, 2015 05:04 PM UTC
**Owner:** Igor Bondarenko
We have a hacky setup for solr (both step-by-step and docker install):
* we wget solr, instead of using a system package
* we copy our schema into the solr example dir
* we run `start.jar` directly instead of a service
For docker, we should be able to use a solr image that somebody else has set up. For the step-by-step we should use system packages and perhaps borrow ideas from the solr container's Dockerfile.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] Re: #7907 Use standardized solr installation
Posted by Dave Brondsema <da...@brondsema.net>.
I think going to 5 would be fine for our recommended and documented installation process - it has been out for most of the year. As long as its still possible for people to run Allura on solr 4 (or older). Which I think it would, since as you say, we aren't doing anything fancy. And I absolutely agree using an official image would be best. Kind of the point of this ticket :)
FYI, you may run into an issue with the "cat" field. We were testing internally on Solr 4.10.2 with the allura core xml files and got an error mentioning `<str name="field">cat</str>` and it says there is no field cat. We removed several fields from the xml file to get it to work.
We also have config precendent (`solr.use_new_types`) for supporting multiple versions, if we do have code that needs to work differently on different versions.
---
** [tickets:#7907] Use standardized solr installation**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** sf-4 sf-current 42cc
**Created:** Mon Jun 29, 2015 03:25 PM UTC by Dave Brondsema
**Last Updated:** Wed Nov 11, 2015 03:48 PM UTC
**Owner:** Igor Bondarenko
We have a hacky setup for solr (both step-by-step and docker install):
* we wget solr, instead of using a system package
* we copy our schema into the solr example dir
* we run `start.jar` directly instead of a service
For docker, we should be able to use a solr image that somebody else has set up. For the step-by-step we should use system packages and perhaps borrow ideas from the solr container's Dockerfile.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #7907 Use standardized solr installation
Posted by Igor Bondarenko <je...@gmail.com>.
There are [official docker image](https://hub.docker.com/_/solr/) for solr now.
Unfortunately it only supports solr 5.3 (we use 4.2.1 currently).
There another [popular image](https://hub.docker.com/r/makuk66/docker-solr/) but it is deprecated in favor of official image and the earliest version it supports is 4.10.
Should we update to solr 5.3? AFAIK we're not using any fancy solr options, only `schema.xml` to describe solr schema, format of which did not changed between versions.
List of major changes can be found [here](https://cwiki.apache.org/confluence/display/solr/Major+Changes+from+Solr+4+to+Solr+5#MajorChangesfromSolr4toSolr5-solr.xmlFormat).
Of course we can create own solr image, but keeping up to date with versions would be better, I think.
And solr 5 introduces some "Ease Of Use/Operational Support" improvements which can be useful for this ticket specifically :)
Any concerns I'm missing?
---
** [tickets:#7907] Use standardized solr installation**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** sf-4 sf-current 42cc
**Created:** Mon Jun 29, 2015 03:25 PM UTC by Dave Brondsema
**Last Updated:** Thu Nov 05, 2015 11:35 AM UTC
**Owner:** Igor Bondarenko
We have a hacky setup for solr (both step-by-step and docker install):
* we wget solr, instead of using a system package
* we copy our schema into the solr example dir
* we run `start.jar` directly instead of a service
For docker, we should be able to use a solr image that somebody else has set up. For the step-by-step we should use system packages and perhaps borrow ideas from the solr container's Dockerfile.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #7907 Use standardized solr installation
Posted by Dave Brondsema <da...@brondsema.net>.
I've cherry-picked [3ea4c9] for the node installation, since that's a good fix to get out before our release. I haven't had a change to closely review all the rest of this ticket yet.
---
** [tickets:#7907] Use standardized solr installation**
**Status:** review
**Milestone:** unreleased
**Labels:** sf-4 sf-current 42cc
**Created:** Mon Jun 29, 2015 03:25 PM UTC by Dave Brondsema
**Last Updated:** Thu Nov 26, 2015 01:20 PM UTC
**Owner:** Igor Bondarenko
We have a hacky setup for solr (both step-by-step and docker install):
* we wget solr, instead of using a system package
* we copy our schema into the solr example dir
* we run `start.jar` directly instead of a service
For docker, we should be able to use a solr image that somebody else has set up. For the step-by-step we should use system packages and perhaps borrow ideas from the solr container's Dockerfile.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #7907 Use standardized solr installation
Posted by Dave Brondsema <da...@brondsema.net>.
- **status**: review --> in-progress
- **Reviewer**: Dave Brondsema
- **Comment**:
Do we need all the language stuff? I don't think we really use it, and it's a lot of files, 196K. Other unnecessary stuff like currency and fields like admin_subscribed etc might be nice to clean up if we wanted. But we don't need to worry about make it as minimal as possible either, just seemed like lang files were quite a lot to add.
docker-compose says:
> Warning: the mapping "solr_config/allura:/opt/solr/server/solr/allura" in the volumes config for service "solr" is ambiguous. In a future version of Docker, it will designate a "named" volume (see https://github.com/docker/docker/pull/14242). To prevent unexpected behaviour, change it to "./solr_config/allura:/opt/solr/server/solr/allura"
The "Mention chmod in the docs" commit can probably be changed to go into the fairly new `init-docker-dev.sh`
---
** [tickets:#7907] Use standardized solr installation**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** sf-4 sf-current 42cc
**Created:** Mon Jun 29, 2015 03:25 PM UTC by Dave Brondsema
**Last Updated:** Fri Dec 04, 2015 03:39 PM UTC
**Owner:** Igor Bondarenko
We have a hacky setup for solr (both step-by-step and docker install):
* we wget solr, instead of using a system package
* we copy our schema into the solr example dir
* we run `start.jar` directly instead of a service
For docker, we should be able to use a solr image that somebody else has set up. For the step-by-step we should use system packages and perhaps borrow ideas from the solr container's Dockerfile.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #7907 Use standardized solr installation
Posted by Igor Bondarenko <je...@gmail.com>.
- **status**: in-progress --> review
- **Comment**:
Closed #860. `ib/7907`
For docker setup need to manually created and `chmod 777` directory for solr data (see updated docs), I know it's a bit ugly, but didn't find a better way.
For local setup we still using manual download of solr image 'cause package for ubuntu is old (~3.6). But it is better than before, since solr now has script to install itself as a service.
---
** [tickets:#7907] Use standardized solr installation**
**Status:** review
**Milestone:** unreleased
**Labels:** sf-4 sf-current 42cc
**Created:** Mon Jun 29, 2015 03:25 PM UTC by Dave Brondsema
**Last Updated:** Wed Nov 11, 2015 03:48 PM UTC
**Owner:** Igor Bondarenko
We have a hacky setup for solr (both step-by-step and docker install):
* we wget solr, instead of using a system package
* we copy our schema into the solr example dir
* we run `start.jar` directly instead of a service
For docker, we should be able to use a solr image that somebody else has set up. For the step-by-step we should use system packages and perhaps borrow ideas from the solr container's Dockerfile.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #7907 Use standardized solr installation
Posted by Dave Brondsema <da...@brondsema.net>.
- **labels**: --> sf-4, sf-current
---
** [tickets:#7907] Use standardized solr installation**
**Status:** open
**Milestone:** unreleased
**Labels:** sf-4 sf-current
**Created:** Mon Jun 29, 2015 03:25 PM UTC by Dave Brondsema
**Last Updated:** Fri Jul 24, 2015 02:08 PM UTC
**Owner:** nobody
We have a hacky setup for solr (both step-by-step and docker install):
* we wget solr, instead of using a system package
* we copy our schema into the solr example dir
* we run `start.jar` directly instead of a service
For docker, we should be able to use a solr image that somebody else has set up. For the step-by-step we should use system packages and perhaps borrow ideas from the solr container's Dockerfile.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #7907 Use standardized solr installation
Posted by Igor Bondarenko <je...@gmail.com>.
I'm not sure about lang files. I added it because we have a lot of language-specific field types defined in our `schema.xml` and I tried to reuse old schema as much as posible.
For example:
~~~~~
<!-- Russian -->
<fieldType name="text_ru" class="solr.TextField" positionIncrementGap="100">
<analyzer>
<tokenizer class="solr.StandardTokenizerFactory"/>
<filter class="solr.LowerCaseFilterFactory"/>
<filter class="solr.StopFilterFactory" ignoreCase="true" words="lang/stopwords_ru.txt" format="snowball" />
<filter class="solr.SnowballPorterFilterFactory" language="Russian"/>
<!-- less aggressive: <filter class="solr.RussianLightStemFilterFactory"/> -->
</analyzer>
</fieldType>
~~~~~
I'm not sure if we're using them somewhere... Just checked now. In `schema.xml` we're using only `text_general` and `text_ws`, so I'll try to get rid of others and delete lang files.
I'll fix warning and chmod too. I used older docker back then, so didn't see that.
---
** [tickets:#7907] Use standardized solr installation**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** sf-4 sf-current 42cc
**Created:** Mon Jun 29, 2015 03:25 PM UTC by Dave Brondsema
**Last Updated:** Tue Dec 08, 2015 11:04 PM UTC
**Owner:** Igor Bondarenko
We have a hacky setup for solr (both step-by-step and docker install):
* we wget solr, instead of using a system package
* we copy our schema into the solr example dir
* we run `start.jar` directly instead of a service
For docker, we should be able to use a solr image that somebody else has set up. For the step-by-step we should use system packages and perhaps borrow ideas from the solr container's Dockerfile.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.