Hi Harv,

Did someone answer your question yet? I haven't seen any, so let me give it a 
shot.

I am not certain what you mean by 10,000 Mb. Do you mean 10 thousand megabyte 
as average size of documents? That sounds as awfull lot. You might mean 10 
thousand KILObyte, which sounds more reasonable, but is still quite a lot. 10 
thousand byte would be within the range MarkLogic Server should be working best.

Are you using document fragmentation? This can be highly relevant if you are 
dealing with large documents.

Anyhow, it all comes down to a kind of page size. When not using fragmentation, 
one document is one fragment. A fragment must fit in the working space of the 
MarkLogic Server to be able to handle it properly. I recall that Michael 
recently mentioned that it should be a few times larger than the largest 
document fragment in the database.

You can increase tree cache size using the MarkLogic Server Admin site. Look 
under the group options, there should be something called 'expanded tree cache 
size'..

Kind regards,
Geert

>


Drs. G.P.H. Josten
Consultant


http://www.daidalos.nl/
Daidalos BV
Source of Innovation
Hoekeindsehof 1-4
2665 JZ Bleiswijk
Tel.: +31 (0) 10 850 1200
Fax: +31 (0) 10 850 1199
http://www.daidalos.nl/
KvK 27164984
De informatie - verzonden in of met dit emailbericht - is afkomstig van 
Daidalos BV en is uitsluitend bestemd voor de geadresseerde. Indien u dit 
bericht onbedoeld hebt ontvangen, verzoeken wij u het te verwijderen. Aan dit 
bericht kunnen geen rechten worden ontleend.


> From: [email protected]
> [mailto:[email protected]] On Behalf Of
> Harv Galic
> Sent: vrijdag 15 mei 2009 20:41
> To: [email protected]
> Subject: [MarkLogic Dev General] XDMP-EXPNTREECACHEFULL
> during reindexing
>
> Hello! We needed to reindex a MarkLogic database and used the
> admin interface to launch reindexing, but after a short time
> got warning messages from all forests related to that database:
>
>  XDMP-FORESTERR: Error in reindex of forest .....:
>  XDMP-EXPNTREECACHEFULL: Expanded tree cache full on host ....
>
> etc.
>
> We still use 3.2-2 ML version (yeah, I know...) The database
> has four forests, each with about 1M documents, and each
> sized at about 10,000 MB, with 6 stands.
> The database has about 15 range element indexes, and about 15
> range element attribute indexes.
>
> What would be a recommended action? Temporary increase tree
> cache? Try again later without any changes? Else?
> Thanks, -Harv
>
> _______________________________________________
> General mailing list
> [email protected]
> http://xqzone.com/mailman/listinfo/general
>

_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general

Reply via email to