10000 Crux-lucene fails to index old stores · Issue #1399 · xtdb/xtdb · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Crux-lucene fails to index old stores #1399

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
Closed
deobald opened this issue Jan 25, 2021 · 2 comments
Closed

Crux-lucene fails to index old stores #1399

deobald opened this issue Jan 25, 2021 · 2 comments
Labels
1.x

Comments

@deobald
Copy link
Contributor
deobald commented Jan 25, 2021

https://opencrux.com/reference/21.01-1.14.0/lucene.html#_setup states that it is possible to "wipe the index directories for the Crux node and restart" to add crux-lucene to an existing database. This still seems to cause the Lucene store latest tx mismatch exception, however.

Steps to reproduce:

  1. Configure a Crux node without Lucene:
  (letfn [(kv-store [dir]
            {:kv-store {:crux/module 'crux.rocksdb/->kv-store
	                      :db-dir      (io/file "data/dev/" dir)
                        :sync?       true}})]
    (crux/start-node
     {:crux/tx-log              (kv-store "tx-log")
	    :crux/document-store      (kv-store "doc-store")
      :crux/index-store         (kv-store "index-store")
      :crux.http-server/server  {:port 9999}}))
  1. Add a record to the database with (put record)
  2. Shut down the server
  3. Add the crux-lucene dep: [juxt/crux-lucene "21.01-1.14.0-alpha"] ... update deps as appropriate (lein, etc.)
  4. Add the crux-lucene config: :crux.lucene/lucene-store {:db-dir "lucene-dir"}
  5. Wipe the index directory using rm -rf ./data/dev/index-store
  6. Restart the service.
    • This will still produce Lucene store latest tx mismatch
@deobald
Copy link
Contributor Author
deobald commented Jan 26, 2021

A quick note: This also seems to occur when switching to the multi-field indexer (:indexer 'crux.lucene.multi-field/->indexer) from the default indexer. Deleting both the index-store and lucene-store still results in a Lucene store latest tx mismatch error after the switch.

@Aleksion
Copy link
Aleksion commented Feb 1, 2021

Just hit this as well.
I tried wiping the store as well, and that worked, until it got out of sync for some reason, leaving me right back where I started.

jonpither added a commit to jonpither/crux that referenced this issue Feb 2, 2021
@jonpither
Fixes xtdb#1399 Lucene module starts before tx-ingester
1c85722
jonpither added a commit to jonpither/crux that referenced this issue Feb 2, 2021
@jonpither
Fixes xtdb#1399 Lucene module starts before tx-ingester
560b2a9
jonpither added a commit to jonpither/crux that referenced this issue Feb 2, 2021
@jonpither
Fixes xtdb#1399 Lucene module starts before tx-ingester
56d3daa
jarohen pushed a commit to jonpither/crux that referenced this issue Feb 2, 2021
@jonpither @jarohen
Fixes xtdb#1399 Lucene module starts before tx-ingester
8ad00bc
@jarohen jarohen closed this as completed in f764bce Feb 2, 2021
jonpither added a commit to jonpither/crux that referenced this issue Feb 3, 2021
@jonpither
Fixes xtdb#1399 Lucene module starts before tx-ingester
dca366d
@jacobobryant jacobobryant mentioned this issue Feb 10, 2021
Closed
@jarohen jarohen added the 1.x label Apr 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1.x
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@deobald @jarohen @Aleksion
0