Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Solr: reconfiguration needed in Heroku environment #693

Open
jnga opened this issue Jul 23, 2018 · 2 comments
Open

Solr: reconfiguration needed in Heroku environment #693

jnga opened this issue Jul 23, 2018 · 2 comments
Assignees
@jnga
Labels
bug enhancement

Comments

@jnga
Copy link
Contributor

jnga commented Jul 23, 2018

The upgrade done with #683 left off with Solr still working in Dev after deploying the project, but the new schema.xml and solrconfig.xml appear not to be reloaded correctly, resulting in a Provisioning Error in Heroku's WebSolr. Starting with Dev, fix this. Likely need extra Heroku permission to de-provision the WebSolr slice and try to re-create it. WebSolr support has been unresponsive to two inquiries, and they have not been active on Twitter since last fall, so it is unclear if this service is still being actively maintained.
@jnga jnga added the bug label Jul 23, 2018
@jnga jnga added this to the Release 3.1 milestone Jul 23, 2018
@jnga jnga self-assigned this Jul 23, 2018
@jnga jnga changed the title Solr: re-provision needed in Heroku environment Solr: reconfiguration needed in Heroku environment Jul 23, 2018
@jnga jnga mentioned this issue Jul 23, 2018
Closed
@jnga jnga mentioned this issue Jan 21, 2019
Closed
@jnga jnga modified the milestones: Release 3.2, Release 3.1 Jan 21, 2019
@jnga
Copy link
Contributor Author

jnga commented Jan 26, 2019 •
edited
Loading

This might be for Release 3.2, or later. It seems as if it will require re-provisioning the WebSolr Heroku add-on in order to get new schema.xml and solrconfig.xml versions to load correctly. The current version of the add-on is discontinued and appears to only be running as a "legacy" product. Discussion w/SK needed.

@jnga jnga modified the milestones: Release 3.3, Release 3.4 Sep 25, 2019
@jnga
Copy link
Contributor Author

jnga commented Sep 25, 2019

This Solr reconfiguration might best be postponed until the upcoming Heroku stack upgrade (due before May 1, 2020).

@jnga jnga modified the milestones: Release 3.4, Release 3.5 Sep 25, 2019
@jnga jnga removed this from the Release 3.5 milestone Nov 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jnga jnga

Labels
bug enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jnga