-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add reindex trigger to repo settings #3796
Comments
Until this is resolved, can someone tell me how to manually force the reindexing? |
@mqudsi check the code gitea/modules/indexer/indexer.go Line 69 in 801843b
I think it will be reindex when you
|
@lunny are you talking about the bleve files in the various |
+1 I have an use case for having already existing repositories and being able to make gitea acknowledge them. Those repositories follow the same structure as the repositories that gitea owns but are created/updated by a separated replication service. |
I'm also in need of button for reindex trigger. Restarting gitea helps partially, some terms are not being found in code search after restart. |
I want this too. Deleting the https://github.com/go-gitea/gitea/blob/main/modules/indexer/code/indexer.go#L318 pageSize = 50 hardcoded 👀 I'm not sure but it looks like it only ever indexes the 1st 50 repos it finds ? This has to be an accidental bug right? Please note there is also a trace log which we can use to watch the re-index process in theory: I will post again if I ever figure out why its not indexing my repos. |
For now I was able to get it to re-index the repo I wanted simply by making a commit on that repo. But it would be nice if the re-index button was added to the admin panel, and also it would be nice if the re-index worked for all repos, not just some of them. |
This PR adds reindexing request buttons to the repository settings page. Fix go-gitea#3796 Signed-off-by: Andrew Thornton <art27@cantab.net>
Would be nice to be able to force a full re-index via gitea cli. currently struggling with this error:
|
ElasticSearch has an index alias feature which works sort of like an alias file on a computer (sometimes called a soft link). When an ElasticSearch client issues a search request to a cluster, it passes the name of the index it would like to search as a part of the request. That name must match either the name of an index or the name of an alias. You can't have two indexes with the same name, and you also can't have an alias with the same name as an index. Otherwise the ElasticSearch cluster wouldn't know which one you were trying to search; it's a unique ID. In this case it looks like your elasticsearch cluster was previously set up (perhaps by a previous version of gitea??) to use an index called
Maybe you should take a backup of whats in your elasticsearch right now and then completely reset it, delete all the indexes and aliases by hand. |
@ForestJohnson Yes, I've manually deleted the three gitea indexes and restarted gitea. Now it's working fine again. |
This PR adds reindexing request buttons to the repository settings page. Fix #3796 Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
This PR adds reindexing request buttons to the repository settings page. Fix go-gitea#3796 Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
In a perfect world it wouldn't be necessary, but there are bugs that cause the gitea db to become out of sync with the actual on-disk repo.
Please consider adding a "perform re-index operation" button to the repo settings, so that one can forcibly resync the UI with the repo. For example, I should be able to use it to correct the aftermath of #3795
The text was updated successfully, but these errors were encountered: