Point dev to newer hosted DB version #1567
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* This is very close to production version but since it is shared it's a crap shoot when creating a sandboxed *(free but limited btw)* DB. Interesting feature of mLabs. May try again to see if we can match it. First creation wasn't close enough; 2nd time it is close.
NOTES:
* Will leave old dev db up for a bit until full retesting occurs. Basic seems to be okay with new dev db.
* The FQDN name has changed for dev mLabs at some point in history. Probably offloaded onto a different server is an educated guess via DNS.
* pwd has to be at least 6 characters and include alphanumerics now... making as general as possible
* Can only import exported collections from here. Full DB import from export isn't happy which is okay as long as metadata `_since` is preserved. Probably has to do with db name conflict and mLabs.
* Metadata `_since` is preserved however it did complain about indexes on one collection:
``` console
2019-01-03T16:20:45.014-0700 Failed: openuserjs_devel.scripts: error creating indexes for openuserjs_devel.scripts: createIndex error: The field 'safe' is not valid for an index specification. Specification: { background: true, safe: null, name: "name_1", ns: "openuserjs_devel.scripts", key: { name: 1 } }
```
* 12 system indexes in new vs old which had 17. From v1 to v2. db name auto-adjusted.
* nodejitsu user index item not inclusive. Talk about a blast from the past.
* Some misc indexes that I'm not sure why they are there were not auto-imported.
* Btw we are Eastern served... so not quite sure why the traceroute tests were going West other than general internet misdirection at this time in the backbones.
* Btw if we take this info to the VPS we may lose the dev db and probably need to establish additional limited sub-accounts
Ref:
* https://docs.mlab.com/ops/#q-why-cant-i-change-the-mongodb-version-thats-running-on-my-sandbox-database
Applies to OpenUserJS#1548 OpenUserJS#262
Martii
added
DB
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NOTES:
_sinceis preserved. Probably has to do with db name conflict and mLabs._sinceis preserved however it did complain about indexes on one collection:2019-01-03T16:20:45.014-0700 Failed: openuserjs_devel.scripts: error creating indexes for openuserjs_devel.scripts: createIndex error: The field 'safe' is not valid for an index specification. Specification: { background: true, safe: null, name: "name_1", ns: "openuserjs_devel.scripts", key: { name: 1 } }Ref:
Applies to #1548 #262