Closed MadMikeyB closed 5 years ago
Do you use multiple queue workers?
Nope, just the one.
@nticaric happy to share error logs with you - this happens constantly now.
@nticaric I really want to use and like your package, unfortunately the constant database locking is preventing me. Do you have time to assist, or is this package incapable of managing large datasets (6M+ rows) and persistent access?
Share your logs and your configuration please. Take into account that this could be an SQLite problem.
You're correct in that it's probably an SQLite issue. Are there any ways to move the index files into a separate MySQL database table?
Yes SQLite can support multiple users at once. It does however lock the whole database when writing, so if you have lots of concurrent writes it is not the database you want (usually the time the database is locked is a few milliseconds - so for most uses this does not matter).
Alternately, with multiple writes per second happening concurrently, it feels like this could also be solved by queueing the indexing operations rather than having them performed instantly, does this package support that?
@MadMikeyB please have a look this https://github.com/teamtnt/tntsearch#examples
I think you may give a try about changing the /config/scout.php config file, and passing the MySQL config to TNTSearch.
Thanks everyone, I did solve this issue by enabling the Scout Queue in my .env file. Dumb moment from me for sure!
SCOUT_QUEUE=true
SCOUT_QUEUE=true
Will make all MakeSearchable Jobs, you search results will be inaccurate unless you have queue worker running.
Hi there,
I'm getting the database being locked every day or so. I'm running quite a high traffic site with multiple indeces and they're seemingly auto-locking which is breaking functionality every day..
Any fix to this?