-
Notifications
You must be signed in to change notification settings - Fork 36
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
strange behaviour when using searchservices v2.0.0 #375
Comments
Are you using 2.0.0? Can you test that again using 2.0.0.1? |
yes, we tried 2.0.0 first, because it's default in your latest alfresco-docker-generator. right? could the differences you linked to between 1.4.3 and 2.0.0 really cause the problems i listed above? at the moment i can't test 2.0.0.1 unfortunately, because the system is in functional testing mode. i haven't tried to verify the problems with a different test-dataset though, so if i find time, i may be trying it again with 2.0.0.1. do you know any debug-settings for looking deeper at what is going on, when the indexer isn't finishing or deadlocking? |
@maxodoble Could you check in the Tomcat access logs if you see a lot of requests for On the Solr side, could you enable the following logger I think I'm facing the same issue as you, and it seems it's caused by the ACL trackers. As soon as I disable the tracker, the cpu usage drops to zero. |
@lmeunier Sorry, i don't have access to the test-dataset i used at the moment, so i can't check it unfortunately. |
hi,
we are getting a strange behaviour when trying to reindex a not so big repository with acs 6.2.0ga:
the reindex process is running through in about 3 hours. so far so good.
BUT: after a redeployment of the containers (docker-compose down, docker-compose up --build --force-recreate -d, data volumes are external and exposed to the containers with bind-mounts) we have the usual cpu spike during startup of the system, and then the alfresco and solr containers are showing permanent cpu usage of about combined 75% - 100%. postgresql cpu usage also permanently high, and this never stops.
searching old docs/new docs still working fine though.
the solr weboverview shows both indexes as current (green checkmark).
the ootb-admin-console shows in the view "solr tracking status", that indexing is "active" for both indexes???
because there are no users active, and indexing should be done, i can't explain what acs/search services is trying to do (and obviously failing to do here, it seems stuck somewhere)?
when changing searchservices back to v1.4.3 i don't get this behaviour by the way:
any idea how i could find out/debug the behaviour v2.0.0 is showing?
The text was updated successfully, but these errors were encountered: