Too slow searches

Zurka

Hi,

I am having issues with my searches. It takes a lot of time to load the page, like 20-25 seconds each time I search something in Pawtucket2.

I am using the latest Providence and Pawtucket2 versions, ElasticSearch 5.6 and I have configured 10 shards. The index size is 6Gb (nearly 1M objects in the db)

My old version of CA has ElasticSearch 2.5 and 20 shards and works much faster.

Do I miss something?

seth

We'd need more information to tell you anything. Like what is the load on the server? Are there any other processes running? Are there queries running in MySQL at the same time (you can see these with SHOW PROCESSLIST in MySQL).

Zurka

Thank you for your fast reply seth.

When I search for something, there is just one query running in MySQL. This server is dedicated just for CA, there aren't any other webs or stuff.

These are our server's specifications:

4 CPU
8GB RAM
OS: Redhat8

I know that the database is pretty big but I have read that ElasticSearch should handle it easily with just 1 shard. We also are using one node.

I have updated the shard number, configuring to 2 shards, and I am going to launch the reindexation process again.

I havent' done any test with the PHP code, because I guess it's a configuration thing?

seth

No idea. Sorry. There's a bottleneck somewhere. One would have to have access to the running application and server to find it.

darrigan

Hi,
Not sure it will resolve the problem, but you can try to clean cache files, and launch a caUtils rebuild-search-index

Zurka

Thank you for you reply darrigan.

I fought in the past with the cache and that's the first thing that I do when something is going slow.

It won't resolve my problem but thank you anyways.

I am setting up the app in an Ubuntu 20.04 clean server, to figure out if it's a server configuration issue or an app issue.

I have also cloned the database to make a little one just to test if it's a database issue also.

If I keep struggling, do you know somebody there that can help with that? I can give access to the server, there is no problem.

seth

If you are stuck contact us at support@collectiveaccess.org and we'll figure something out.

Zurka

Thank you again for your reply seth.

The issue has nothing to see with CollectiveAccess. It seems that some auditd service rule is slowing the entire application.

We have disabled it and searches are fast again.

Thank you for your support.