Hi all,
I'm trying the oak-upgrade tool to migrate a jackrabbit 2.x (2.20.13)
repository (RDB + file datastore) to the latest oak release in a mongodb
repository.
Apparently it worked, I mean no errors, but I must emphasise that for example
no Lucene index was created, but let me say this is not a big problem for me
because when the target application starts it creates its indexes and reindex
all, this compromise is acceptable to me except for large volumes of indexes.
So consider that after migration I start my application which create its Lucene
indexes, navigating through the tree I can correctly see indexes under
oak:index node, ok
I see something strange which would like to ask for an help:
*** oak-run index stats ***
I'm using regularly the index command of oak-run to get stats from my Lucene
index and see their definitions.
When I run it in the just migrated repository it doesn't work throwing the
following exception:
17:52:30 - Error occurred while performing index tasks
org.apache.jackrabbit.oak.plugins.document.DocumentStoreException: Unable to
initialize a read-only DocumentNodeStore. The DocumentStore nodes collection
does not have a root document.
at
org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.<init>(DocumentNodeStore.java:699)
at
org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreBuilder.build(DocumentNodeStoreBuilder.java:204)
at
org.apache.jackrabbit.oak.run.cli.DocumentFixtureProvider.configureDocumentMk(DocumentFixtureProvider.java:117)
at
org.apache.jackrabbit.oak.run.cli.NodeStoreFixtureProvider.create(NodeStoreFixtureProvider.java:73)
at
org.apache.jackrabbit.oak.run.cli.NodeStoreFixtureProvider.create(NodeStoreFixtureProvider.java:51)
at
org.apache.jackrabbit.oak.index.IndexCommand.execute(IndexCommand.java:136)
at org.apache.jackrabbit.oak.run.Main.main(Main.java:49)
org.apache.jackrabbit.oak.plugins.document.DocumentStoreException: Unable to
initialize a read-only DocumentNodeStore. The DocumentStore nodes collection
does not have a root document.
at
org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.<init>(DocumentNodeStore.java:699)
at
org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreBuilder.build(DocumentNodeStoreBuilder.java:204)
at
org.apache.jackrabbit.oak.run.cli.DocumentFixtureProvider.configureDocumentMk(DocumentFixtureProvider.java:117)
at
org.apache.jackrabbit.oak.run.cli.NodeStoreFixtureProvider.create(NodeStoreFixtureProvider.java:73)
at
org.apache.jackrabbit.oak.run.cli.NodeStoreFixtureProvider.create(NodeStoreFixtureProvider.java:51)
at
org.apache.jackrabbit.oak.index.IndexCommand.execute(IndexCommand.java:136)
at org.apache.jackrabbit.oak.run.Main.main(Main.java:49)
*** oak-run consistency-check ***
The consistency check too doesn't say VALID as I've always seen:
/oak:index/wm-car-index => VALID
Size : 97 B
Time taken : PT0.0703883S
/oak:index/wm-entity-index => INVALID
Size : 622 B
Missing blobs
- 6b80fde2fa743896a78f230efce33e65903cf8b359f434742299e67505f6ffff#528913
Time taken : PT0.0436371S
/oak:index/wm-index => INVALID
Size : 622 B
Missing blobs
- b2820694d9f205748b3cb7c4973070835865b8fc8f5bade85d5662b39e4b9613#9448
Time taken : PT0.0517582S
/oak:index/wm-motorvehicle-index => VALID
Size : 97 B
Time taken : PT0.0496223S
Valid indexes :
- /oak:index/wm-car-index
- /oak:index/wm-motorvehicle-index
Invalid indexes :
- /oak:index/wm-entity-index
- /oak:index/wm-index
Since the indexes were created from scratch and after migration, how is it
possible that there are blobs that cannot be found?
Until today, checking the consistency of the indexes had never given me an
‘invalid’ result. Today, I ‘simply’ experimented with migration.
Any help could be appreciated, thanks
Cordiali saluti / Best regards,
Raffaele Gambelli
Application Architect
E [email protected]<mailto:[email protected]>
M +39 3371641888
[cid:2066e875-aa57-40a2-8c47-cab275bab400]
[CEGEKA]
Via Ettore Cristoni, 84
IT-40033 Bologna (IT), Italy
T +39 02 2544271
WWW.CEGEKA.COM<https://www.cegeka.com>
Dichiarazione di
Riservatezza<https://campaigns.signature365.com/eu-B2uKnHEFS98nwDUb-xnoLLs9dLzfDepbj/gen_TaBH22N3obPLF7D6/go/uHO>
Le informazioni contenute nella mail sono riservate. Se si rende conto di non
essere il destinatario corretto della mail, la preghiamo di segnalare l'errore
al mittente e di cancellare immediatamente il messaggio. L’utilizzo improprio
di informazioni riservate può comportare
sanzioni.<https://campaigns.signature365.com/eu-B2uKnHEFS98nwDUb-xnoLLs9dLzfDepbj/gen_TaBH22N3obPLF7D6/go/uHO>
Protezione dei dati
personali<https://campaigns.signature365.com/eu-B2uKnHEFS98nwDUb-xnoLLs9dLzfDepbj/gen_TaBH22N3obPLF7D6/go/uHO>
La informiamo che i suoi dati saranno trattati da Cegeka nel rispetto delle
disposizioni di legge applicabili (D. Lgs 196/2003 e Regolamento UE 679/2016).
Per maggiori dettagli può consultare le nostre informative privacy al link
<https://campaigns.signature365.com/eu-B2uKnHEFS98nwDUb-xnoLLs9dLzfDepbj/gen_TaBH22N3obPLF7D6/go/uHO>
https://www.cegeka.com/it/informazioni-sulla-privacy<https://campaigns.signature365.com/eu-B2uKnHEFS98nwDUb-xnoLLs9dLzfDepbj/gen_TaBH22N3obPLF7D6/go/NsT>.<https://campaigns.signature365.com/eu-B2uKnHEFS98nwDUb-xnoLLs9dLzfDepbj/gen_TaBH22N3obPLF7D6/go/uHO>
