snaq
New Member
Posts: 20
inherit
268742
0
Jun 18, 2024 4:49:14 GMT -8
snaq
20
November 2023
snaq
|
Post by snaq on Jun 17, 2024 23:42:14 GMT -8
|
|
#eb7100
1480
0
1
Sept 7, 2024 10:42:26 GMT -8
Craig
209,066
September 2001
cmdynasty
|
Post by Craig on Jun 17, 2024 23:55:53 GMT -8
Hi ![:)](//storage.proboards.com/forum/images/smiley/smiley.png) The reindex should be done for you today. Regarding changing the thread name. It may take a little while for the searches to update after you change the name. How long after changing the name do you try and search for the thread name? Craig
|
|
snaq
New Member
Posts: 20
inherit
268742
0
Jun 18, 2024 4:49:14 GMT -8
snaq
20
November 2023
snaq
|
Post by snaq on Jun 18, 2024 0:23:47 GMT -8
Hi ![:)](//storage.proboards.com/forum/images/smiley/smiley.png) The reindex should be done for you today. Regarding changing the thread name. It may take a little while for the searches to update after you change the name. How long after changing the name do you try and search for the thread name? Craig We often search very quickly after changing the name (the name is changed often, like every 48 hours). I think this is something we can avoid doing, though.
|
|
#e61919
Support Staff
224482
0
1
Sept 6, 2024 16:16:22 GMT -8
Scott
23,916
August 2015
socalso
|
Post by Scott on Jun 18, 2024 8:09:30 GMT -8
snaq - this may contribute to or explain the issues you are having. Indexing for search is not immediate. When there is a change made that triggers the need for an index, that event is added to a queue. If a thread is constantly being posted to, edited, etc. (anything that would trigger the need for it to be indexed) it is continuously being bumped to the end of the queue and so the indexing is not occurring as quickly as you would like. The software is not designed for an immediate post/search cycle. Additionally there are 'rules' built into the indexing to keep things running smoothly. For instance, if a thread is constantly changing (in the manner that you've described in this and your other threads) it most likely is causing that particular thread to be skipped for index, but will eventually be completed later or when we manually trigger the reindex. Think of it like this, you and a bunch of friends are ordering food and one person cannot make up their mind. Rather than hold up the ordering process, the order-taker just moves on to the next person and then eventually comes back around to the indecisive person. (I did submit a reindex request for the forum.)
|
|