Hey!
Working on getting Deadline Repository 10.0.0.35 installed on Windows however we have run into an issue with the command line option --dbsplit. I’ve set the option to --dbsplit true however it doesn’t look to have split it the same way as Deadline 8, possible bug that would need to be fixed?
Thanks
Hmmm, shouldn’t have changed, I’ll have a quick look.
We’ll see what the dev team says here, but if you upgrade your MongoDB for 10 there should be no performance issues like there were back in the Deadline 7.0 days. Mongo now supports per-collection write locking which it didn’t before. The lack of granular locking is why the option to split the database was necessary.
When I last talked to Laszlo about this, it was more about not needing to retool stuff to point to different locations. It really doesn’t harm anything to keep the split DBs around either, the only downside really is a bit of extra ‘wasted’ hard drive space because each DB will be using its own memory-mapped file.
In any case, as to the initial reported issue, I am seeing the same thing immediately after install (only Misc and Config are created initially), but these are created lazily (we might’ve created them explicitly in the installer in the past, I can’t remember for sure) – as soon as any of the client apps connect to the repo they should be ensuring that the needed Collections/DBs/indices are all present. Does this match what you’re observing? Does starting up a launcher/slave/monitor pointing to this repo create the DBs properly?
Hey Jon!
Thank you for looking into this, we are still working on getting our pipeline merged with D10 so we have not launched any of the applications just yet. I expect us to have this going this week so i’ll be able to provide an answer in a couple of days. I’ll let you know as soon as I can!
Hey Jon,
You were correct! Once we got repository running and the Monitor running on my machine the other DB’s were created. Thanks for looking into this!