Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
dutchsnowden Posted January 6, 2022 Posted January 6, 2022 Upgrading recently from 3.1.4 via 3.4, I have noticed that search is not working. Regardless of what is searched for nothing is found.
Solution Jim M Posted January 6, 2022 Solution Posted January 6, 2022 As mentioned in the blue bar, the search index is rebuilding. You can check this status by going to ACP -> System -> Dashboard -> Background Processes. SeNioR- and dutchsnowden 1 1
dutchsnowden Posted January 6, 2022 Author Posted January 6, 2022 (edited) Yes, I did. 15 minutes ago, Jim M said: As mentioned in the blue bar, the search index is rebuilding. You can check this status by going to ACP -> System -> Dashboard -> Background Processes. Thank you so much! 15 minutes ago, Jim M said: As mentioned in the blue bar, the search index is rebuilding. You can check this status by going to ACP -> System -> Dashboard -> Background Processes. Edited January 6, 2022 by dutchsnowden
Marc Posted January 7, 2022 Posted January 7, 2022 Sorry, Im not sure what the further question is on this. Please could you clarify? You asked there why you are not getting results and stated you have rest the back which tells you they are in progress.
dutchsnowden Posted January 7, 2022 Author Posted January 7, 2022 I started the manual rebuilding process, but this is so so slow it will never be done I hope when this is done, search will work.
Marc Posted January 7, 2022 Posted January 7, 2022 1 hour ago, dutchsnowden said: I started the manual rebuilding process, but this is so so slow it will never be done I hope when this is done, search will work. It will. Ensure you have a cron job set up to run your tasks also dutchsnowden 1
dutchsnowden Posted January 7, 2022 Author Posted January 7, 2022 I will but I hope to do it after this is done.
Randy Calvert Posted January 7, 2022 Posted January 7, 2022 (edited) Rebuilding the search index on my site took about 12 hours with the default database search. It was much faster (just under 2 hours) with Elasticsearch. The amount of time it takes depends on the available system resources and how busy your site is. Remember... this is a pretty database intense process and it's competing with your normal site users for resources. IPB tries to limit what it does at one time so as not to completely overwhelm your server and have your site down while it's being worked on. Edited January 7, 2022 by Randy Calvert
dutchsnowden Posted January 7, 2022 Author Posted January 7, 2022 I am talking about running it manually from ACP. I started it two full days ago. This one goes once a second, like so.
Randy Calvert Posted January 7, 2022 Posted January 7, 2022 That means you have not even STARTED the search index rebuild yet. It's rebuilding the posts themselves. (It's rewriting old BB code into new format, etc.)
dutchsnowden Posted January 7, 2022 Author Posted January 7, 2022 How do you start search index? 1 minute ago, Randy Calvert said: That means you have not even STARTED the search index rebuild yet. It's rebuilding the posts themselves. (It's rewriting old BB code into new format, etc.) I thought rewriting posts into new format was done by upgrade scripts.
Jim M Posted January 7, 2022 Posted January 7, 2022 9 minutes ago, dutchsnowden said: How do you start search index? Background tasks run in order they are added. After an upgrade posts are rebuilt then the search index. On the Dashboard in the ACP you can see the current order of tasks. 9 minutes ago, dutchsnowden said: I thought rewriting posts into new format was done by upgrade scripts. No. Upgrade procedures are done. Posts are not rebuilt though as it would mean the upgrade process for some sites would take days. It is handled post upgrade by the background tasks.
dutchsnowden Posted July 6, 2022 Author Posted July 6, 2022 indexing that takes days, strikes again after today's update. Running for 1h already. Is there a way to speed this up?
Marc Posted July 6, 2022 Posted July 6, 2022 Im not sure here how your indexing can take days after an update you have done only today. Ensuring you have your tasks running under cron would be the best way to ensure these are running as quickly as they can be. However generally it's a case of waiting for them to complete. These are intended to be a background task, and can happen with large upgrades
dutchsnowden Posted July 6, 2022 Author Posted July 6, 2022 I have no clue how long it will take, I was comparing with last time I have seen this which took more than 48h. Cron tasks seem to be running in very small chunks.
Marc Posted July 6, 2022 Posted July 6, 2022 Just now, dutchsnowden said: I have no clue how long it will take, I was comparing with last time I have seen this which took more than 48h. Cron tasks seem to be running in very small chunks. They will run based on what your mysql instance is capable of running generally. I understand it may have taken a while last time, but if I remember correctly (excuse me if Im wrong) that was an upgrade from quite an old version
dutchsnowden Posted July 6, 2022 Author Posted July 6, 2022 Correct, you are correct. It was after a nighmarish upgrade. Now I just upgraded to last version and this started again.
Marc Posted July 6, 2022 Posted July 6, 2022 5 minutes ago, dutchsnowden said: Correct, you are correct. It was after a nighmarish upgrade. Now I just upgraded to last version and this started again. It has, however there are many many other processes when you upgrade from 3.4 that are running alongside those. However it can take time on some servers
Marc Posted July 6, 2022 Posted July 6, 2022 That is the queue task running your background tasks, yes
dutchsnowden Posted July 6, 2022 Author Posted July 6, 2022 Thanks Marc, but I was asking WHICH in particular is the one responsible for the message above (reindexing)?
Marc Posted July 6, 2022 Posted July 6, 2022 15 minutes ago, dutchsnowden said: Thanks Marc, but I was asking WHICH in particular is the one responsible for the message above (reindexing)? Im not sure I understand your question there. Your reindexing is a background task as previously mentioned, and the queue task is responsible for running those background tasks
dutchsnowden Posted July 6, 2022 Author Posted July 6, 2022 I thought all in the list in there are task that are working on some background tasks. So the highlighted one is the one. thank you.
Recommended Posts