On Fri, 19 Dec 2014 06:11:27 -0800, Danny Sinang <[email protected]> wrote:
> We have 5 trigger databases (one for each Business Unit content database > with its own CPF domain and pipelines). > > The less than 30 triggers stored in each of them appear to have been > created solely by CPF. > > For manageability purposes, we'd like to combine them into just one > trigger database. > > My question is, would doing so cause any problems for CPF ? > > If yes, what workarounds would you suggest ? > > Regards, > Danny What it will mean is that every trigger will fire for every document modified/added/deleted in any database that shares that triggers database. In a CPF context this means that you will be creating race conditions on which trigger updates what state of the document. CPF has code in it to operate correctly in the face of race conditions similar to this, but the best that can be said about this is that you are adding unnecessary overhead. The other thing to think about is not just the triggers, but the other information CPF stores in the triggers database: domains, pipelines, and the configuration object (most important use: restart). CPF installation on a shared triggers database should be done once. The unit of sharing for CPF and triggers configuration is the triggers database, so don't expect to be able to have multiple distinct sets of triggers or CPF configurations to operate in a single triggers database. If all your databases can operate off the same CPF configuration you can have them all share the same triggers database and a single installation of CPF. If you want the same domain to have different behaviour in different databases, you cannot share the triggers database and you cannot have a shared CPF configuration. If each of the content databases has (or can be made to have) non-intersecting domains, then you could also share CPF configurations in a single shared triggers database. If you are worried about the overhead of the databases themselves, you can dial down some of the cache settings and turn off a lot of indexes. Look at the settings on the default Triggers database for guidance. //Mary _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
