Opened 18 years ago
Last modified 11 months ago
#385 new enhancement
Automatically launching a re-index or brute force search from browser requests needs to be configurable
Reported by: | Patrick Martin | Owned by: | Alex Smith |
---|---|---|---|
Priority: | normal | Component: | RepoSearchPlugin |
Severity: | major | Keywords: | |
Cc: | Trac Release: | 0.11 |
Description
In brief, being able to turnoff the auto-index behaviour for large and busy repositores would allow the post-commit script to handle the re-index, or a nightly task.
The update-index.py script is perfectly serviceable, and admins should have the option of only re-indexing using processes under their control, such as a cron job or Sheduled Task, to avoid a very large re-index from impacting apache's performance and stability.
A large re-index can blow the 2Gb address space, and thus never completes, which means once a repository has failed to index, it can never catch up. Being able to tune the re-index operations to ensure they succeed regularly would help mitigate this risk.
Tested against Trac and latest ReposSearchPlugin 0.10dev
Attachments (0)
Change History (10)
comment:1 Changed 18 years ago by
Status: | new → assigned |
---|
comment:2 Changed 18 years ago by
That's great.
I have some more suggestions in the configuration front, but I'll raise a separate ticket, as they might be a little too cheeky.
comment:3 Changed 18 years ago by
comment:5 Changed 15 years ago by
Owner: | changed from Alec Thomas to Ryan J Ollos |
---|---|
Status: | assigned → new |
comment:6 Changed 15 years ago by
Summary: | Automatically launching a re-index or brute force search from browser resquests needs to be configurable → Automatically launching a re-index or brute force search from browser requests needs to be configurable |
---|---|
Trac Release: | 0.10 → 0.11 |
Sounds reasonable, but would only be implemented on the 0.11 branch.
comment:7 Changed 13 years ago by
Hello,
I took over maintainership of this plugin from athomas some time ago. There is a significant amount of work to do on this plugin, and I don't foresee having the time to do it all.
helend has written the TracSuposePlugin, which seems like a much better solution. Rather than writing the repository search functionality from scratch, a Trac interface to an existing repository search tool has been created. Rather than throwing more effort at this plugin, I'd prefer to help helend with enhancements to the TracSuposePlugin, or spend my time on other Trac plugin projects altogether.
I'd like to get some feedback and hear if anyone knows of a compelling reason to continue this project rather than moving to the TracSuposePlugin. Is there functionality in this plugin that doesn't exist in the TracSuposePlugin? I'm open to hearing all opinions and suggestions.
I'll leave these tickets open for about a week, but in all likelihood will close all of them and deprecate the plugin.
Thanks for your time,
- Ryan
comment:8 Changed 10 years ago by
Owner: | changed from Ryan J Ollos to anonymous |
---|
comment:9 Changed 11 months ago by
Owner: | changed from anonymous to Alex Smith |
---|---|
Status: | new → assigned |
comment:10 Changed 11 months ago by
Status: | assigned → new |
---|
I agree. I'll add a configuration option for this soon.