I have a need to make a bunch of changes to index
settings on a moderately sized database (under a million
documents), as well as change the fragmentation scheme.
What is the best way to apply all these changes so that
the least amount of work is done (this will ultimately
need to be done on the production system)?
The documents currently have a fragment parent that
results in up to seven fragments per document. I want
to change to a fragment root that will result in up to
three fragments. Index changes are a couple of new
range indexes and lots of word-query related things like
adding word positions and setting inclusions.
If I start making these changes on the various Admin
screens, the reindexer will kick off and everything will
eventually get done. But is there a way to combine the
work into a single pass (or fewer passes)?
For example, will this result in less work than just
banging in the changes and letting it go:
1) Disable auto-reindexer
2) Make changes to index settings and fragmentation scheme
3) Re-enable indexer
3a) Would a forced re-index be needed?
4) Wait
Will this result in ML doing less overall work by
combining multiple index updates in the same pass?
Also, would I be guaranteed that all existing fragments
will have been re-fragmented when all is said and done?
Can managing merge policy help here? Reducing the size
of merges during re-index? Stopping merges until reindexing
is finished?
Thanks.
---
Ron Hitchens {[email protected]} +44 7879 358212
_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general
