Hi Peter,
Not sure, but increasing journal size might indeed help. Did you try? Cheers, Geert Van: [email protected] [mailto:[email protected]] Namens Peter Kester Verzonden: woensdag 11 juni 2014 10:01 Aan: MarkLogic Developer Discussion Onderwerp: Re: [MarkLogic Dev General] Retire a forrest gives CDMP-JNLTXNFULL Hi David, Yes, this is the rebalance that is built in into ML7, so I tend to stick with that. I would like to know how to resolve this error without using 3rd party libs. Can this be fixed by temporary up the journal size until rebalancing is done. Regards, Peter Peter Kester Senior Consultant [email protected] <mailto:[email protected]> +31 611188543 http://nl.linkedin.com/in/peetkes/ Graadt van Roggenweg, 328-334, 3531 AH Utrecht <http://www.marklogic.com/> http://www.marklogic.com/ New generation databases, you just need to think differently <http://t.co/YKkJ0Wxseo> www.nosqlfordummies.com <http://world.marklogic.com/> From: David Ennis <[email protected] <mailto:[email protected]> > Reply-To: MarkLogic Developer Discussion <[email protected] <mailto:[email protected]> > Date: dinsdag 10 juni 2014 23:10 To: MarkLogic Developer Discussion <[email protected] <mailto:[email protected]> > Subject: Re: [MarkLogic Dev General] Retire a forrest gives CDMP-JNLTXNFULL HI Peter. Is this the rebalance built into MarkLogic7? If you have the luxury of emptying the database and re-loading, consider that as it could be faster overall. Otherwise, perhaps you could re-purpose https://github.com/mblakele/task-rebalancer for the job. For this, you just need to force the forest ID in the assignment variable of rebalance.xqy. This is, of course the most elegant solution, but it leverages things like the spawning of tasks already in place. The heart of this is just to overwrite a document with itself (including properties, security/etc), so you could also make a stripped-down version for your purpose using Michael Blakeley's taskbot. Kind Regards, David On 10 June 2014 16:33, Peter Kester <[email protected] <mailto:[email protected]> > wrote: Hi all, I'v got a database with 3 forrests. We want to go back to 1 forrest so we retired two forests. The first forrest got rebalances OK and has 0 documents at the moment. The second forrest gives an error: There is currently an exception: XDMP-FORESTERR: Error in rebalance of forest STRLF3-content-localhost.localdomain-1: XDMP-JNLTXNFULL: The journal has exceeded its limit for in-process transaction records: txn_size=20.496MB, current_size=0MB, limit=8MB Information on this page may be missing. And the forrest won't rebalance. After a while the rebalanced kicks in again and will fail with the same error. How can I fix this? Should I increase the current journal size of 128 MB (I think that this is the default value) for the database? Locking = fast journaling = fast Journal-size = 128 Preallocate journals = false Total memory for the server is 8G. There are about 1.7 million docs in the db The failing forrest is 4.6 GB in size with about 600000 docs. The other forrest holds 1.1 million docs in the db and is about 8 GB in size. Thanks in advance, Peter Peter Kester Senior Consultant [email protected] <mailto:[email protected]> +31 611188543 <tel:%2B31%20611188543> http://nl.linkedin.com/in/peetkes/ Graadt van Roggenweg, 328-334, 3531 AH Utrecht <http://www.marklogic.com/> http://www.marklogic.com/ New generation databases, you just need to think differently <http://t.co/YKkJ0Wxseo> www.nosqlfordummies.com <http://world.marklogic.com/> _______________________________________________ General mailing list [email protected] <mailto:[email protected]> http://developer.marklogic.com/mailman/listinfo/general
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
