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.

Sign up for GitHub

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

Jump to bottom

[QA] occ search:index:update is unreliable #288

Open

jnweiger opened this issue Jul 8, 2022 · 1 comment

Contributor

jnweiger commented Jul 8, 2022 •

edited

Loading

Seen with search_elastic 2.2.0 RC2 in 10.11.0 Alpha 1

occ search:index:reset reliably removes all entries from the search index.
- the web UI now shows '0 nodes marked as indexed, 0 documents in index using 226 bytes' OK
- no search results are shown from elastic. OK
occ search:index:update sometimes re-indexes the files. (It does so very reliably directly after setup).
- All subsequent attempts only print
```
Start Updating the Elastic Search index:
No pending jobs found.
```

Expected behaviour:

it should do its job. Maybe it shoud have a --force flag, to really do the job?
Resetting the last_run timestamp in the database usually allow jobs to run. But 'OCA\Search_Elastic\Jobs\UpdateContent' is not listed in oc_jobs.
The difference between rebuild, create, and update should be better documented.

The text was updated successfully, but these errors were encountered:

jnweiger mentioned this issue

search_elastic 2.2.0 #275

Closed

42 tasks

Contributor Author

jnweiger commented Jul 22, 2022

@GeraldLeikam fyi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment