Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

Bootstrap looses retire status of forest #322

Closed
grtjn opened this issue Dec 15, 2014 · 2 comments
Closed

Bootstrap looses retire status of forest #322

grtjn opened this issue Dec 15, 2014 · 2 comments
Labels
bug deployer

Comments

@grtjn
Copy link
Contributor

grtjn commented Dec 15, 2014

Run bootstrap with content-forests-per-hosts=3, then retire one of three, rerun bootstrap. Retire flag is effectively removed, where I think it should have been preserved..

This is only the case for forests automatically added by Roxy. Marking forest as Read-only is preserved..
@grtjn
Copy link
Contributor Author

grtjn commented Jan 20, 2015

@paxtonhare / @dmcassel what is your opinion. The code in setup.xqy is such that it detaches forests, then reattaches them. Was there a particular reason to do it like this?

I'll do a PR, we can discuss there..

grtjn added a commit to grtjn/roxy that referenced this issue Jan 20, 2015
@grtjn
Fixed marklogic-community#322: don't reattach forest, looses retire flag
86722c6
paxtonhare added a commit that referenced this issue Jan 20, 2015
@paxtonhare
Merge pull request #351 from grtjn/322-retired-forests
f41e8bf 
Fixed #322: preserving retired forest at bootstrap
@grtjn
Copy link
Contributor Author

grtjn commented Jan 21, 2015

Fixed in dev

@grtjn grtjn closed this as completed Jan 21, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug deployer
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@grtjn @dmcassel