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

Do not name forests based on hostnames. #149

Closed
eedeebee opened this issue Oct 24, 2013 · 2 comments
Closed

Do not name forests based on hostnames. #149

eedeebee opened this issue Oct 24, 2013 · 2 comments
Labels
enhancement

Comments

@eedeebee
Copy link
Contributor

This is particularly an issue on AWS where hostnames can easily change

If DB is named, FOO, good names for forest are FOO-001, FOO-002 etc....

E
@eedeebee eedeebee reopened this Oct 24, 2013
@dmcassel
Copy link
Collaborator

I think this also makes sense in light of the ML7 talk about moving forests around to different storage tiers.

eedeebee added a commit to eedeebee/roxy that referenced this issue Oct 25, 2013
@eedeebee
Remove hostname from forest names to address issue marklogic-communit…
9919529 
…y#149
@dmcassel
Copy link
Collaborator

Merged changes into dev branch.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@eedeebee @dmcassel