You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a lot of record updates coming in at the same time.
using config file '/var/www/shared/config/qa.sphinx.conf'...
indexing index 'schedule_delta'...
FATAL: failed to lock /var/www/shared/db/sphinx/schedule_delta.tmp.spl: Resource temporarily unavailable, will not index. Try --rotate option.
Hello @atomical 👋
I'm facing the same issue. I use Sidekiq as a worker for delta indexing, and my Sidekiq config includes usage of relatively new feature of Sidekiq capsules which I could configure to use only 1 thread at a time and make sure that the only one job is executed at a time. The problem though is that having a separate capsule for Delta indexing leads all the Delta indexing job to perform xxx times slower.
Here is the data to compare:
Capsule with other queues in it, concurrency is 3 -> 0.2s average job execution time
Separate capsule with only ts_delta queue, concurrency is 1 -> 42s each job execution time
And I run out of ideas how to handle it properly. I my case the job fails with:
tid=igxb class=ThinkingSphinx::Deltas::SidekiqDelta::DeltaJob jid=700414f64806a88d7d48fc0e WARN: Sphinx Guard file for index user_delta exists, not indexing: /bla/bla/blabla/shared/db/sphinx/production/ts-user_delta.tmp.
Hi Pat,
We have a lot of record updates coming in at the same time.
It's followed by the worker exiting.
We would like to avoid setting the number of threads to 1. Currently it is at 5. Have you seen this before?
The text was updated successfully, but these errors were encountered: