-
Notifications
You must be signed in to change notification settings - Fork 91
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.
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
New catalog-solr instance is using wrong username/password #4622
Comments
@FuhuXia Is this for an old solr instance? It sounds like it's running any old version of the admin startup script. I would check the version of the broker used to create/update the solr instance. I would also check the the script on the The password doesn't get set if the |
Gave it a shot today, increased replica count before and after a |
When you check the logs (I would try to see if you can see the plan that the brokerpak ran and make sure that the
I'm now remembering that I may have manually edited the task definition in the AWS Console (if we never fixed the bug in the brokerpak that causes this). If you edit the task definition (with the correct number of solr instances) and then make sure to start a new container based on the new task definition, that will definitely be the "workaround". I assume that this isn't a common thing that we were going to support (changing the number of followers, but the long-term fix would be making sure the |
Here is what we know so far:
The # 3 workaround requires rebuilding solr index, which is time-consuming. Will look at @nickumia's idea on editing task definition for a better workaround. |
The issue arises because the |
New Solr instances created by scaling up catalog-solr are using the default solr username password. As a result, catalog-web gives solr error when it is connected to the new solr instances. Scale back down to the previous level to avoid the solr error. This issue means our solr followers are stuck with the current scale as the maximum instances we can have.
How to reproduce
Expected behavior
No solr error
Actual behavior
Solr error when the new instance is used.
Sketch
[Notes or a checklist reflecting our understanding of the selected approach]
The text was updated successfully, but these errors were encountered: