Any update-heavy workload will tend to fill the in-memory stand, causing it to 
flush to disk. Likely your normal workload is light enough that the in-memory 
stand hits its idle timeout instead. I don't think there is a message 
associated with that timeout, so you would only see a "Saving..." message 
followed by a "Saved..." message for the new on-disk stand.

-- Mike

On 5 Aug 2013, at 07:41 , Gavin Haydon <[email protected]> 
wrote:

> Thanks for the swift response Mike,
> 
> So is this pool likely to fill quickly during a reindex?, as we do not 
> see this message usually. or is it more likely to be caused by a flush 
> of document inserts?
> 
> Cheers,
> Gavin
> 
> On 05/08/13 15:09, Michael Blakeley wrote:
>> That is normal, expected, and even desirable. The in-memory list is a fixed 
>> size, and is meant to fill up. The list is usually the largest pool in the 
>> in-memory stand, so it's good that it fills up first.
>> 
>> More generally, the key part of that log message is the log level: "Debug". 
>> No debug-level message is an error: it is just a debug-level message. If it 
>> were an operational problem it would have shown up at Notice, Warning, or 
>> higher. See http://docs.marklogic.com/guide/admin/logfiles for a complete 
>> list of log levels and instructions for setting the log level. If you have a 
>> support account, 
>> https://help.marklogic.com/Knowledgebase/Article/View/23/0/understanding-xdmp-inmmfull-messages
>>  might also be helpful.
>> 
>> -- Mike
>> 
>> On 5 Aug 2013, at 06:27 , Gavin Haydon <[email protected]> 
>> wrote:
>> 
>>> Hi,
>>> 
>>> Is it abnormal to see the following messages at the debug level in the
>>> error log:
>>> 
>>> 2013-07-30 01:16:53.963 Debug: Forest::doInsert: XDMP-INMMLISTFULL:
>>> In-memory list storage full; list: table=87%, wordsused=74%,
>>> wordsfree=0%, overhead=26%; tree: table=5%, wordsused=26%,
>>> wordsfree=74%, overhead=0%
>>> 
>>> and
>>> 
>>> 2013-07-30 00:58:35.176 Debug: Forest::insert:
>>> StoreRestApiContent-pathamkl03-08 XDMP-INMMLISTFULL: In-memory list
>>> storage full; list: table=87%, wordsused=74%, wordsfree=0%,
>>> overhead=26%; tree: table=5%, wordsused=25%, wordsfree=75%, overhead=0%
>>> 
>>> These were occurring frequently during a period of reindexing, for
>>> forests in the affected database. The reindex was taking place because
>>> of changes to the word query exclusions, where a number of elements had
>>> been added to the exclusion list (we don't what them included in text
>>> search).
>>> 
>>> The whole cluster was under high load during the index, with a
>>> detrimental effect on usage. I cannot find evidence of this message at
>>> any other time other than during the reindex. Also there is no evidence
>>> of any large fragment errors to go with these messages, which seem to be
>>> what most people experience when XDMP-INMMLISTFULL is seen.
>>> 
>>> Regards,
>>> Gavin Haydon
>>> Press Association
>>> 
>>> This email is from the Press Association.  For more information, see 
>>> www.pressassociation.com.
>>> This email may contain confidential information.
>>> Only the addressee is permitted to read, copy, distribute or otherwise use 
>>> this email or any attachments.
>>> If you have received it in error, please contact the sender immediately.
>>> Any opinion expressed in this email is personal to the sender and may not 
>>> reflect the opinion of the Press Association.
>>> Any email reply to this address may be subject to interception or 
>>> monitoring for operational reasons or for lawful business practices.
>>> 
>>> 
>>> _______________________________________________
>>> General mailing list
>>> [email protected]
>>> http://developer.marklogic.com/mailman/listinfo/general
>>> 
>> _______________________________________________
>> General mailing list
>> [email protected]
>> http://developer.marklogic.com/mailman/listinfo/general
>> 
> 
> 
> This email is from the Press Association.  For more information, see 
> www.pressassociation.com.
> This email may contain confidential information.  
> Only the addressee is permitted to read, copy, distribute or otherwise use 
> this email or any attachments.  
> If you have received it in error, please contact the sender immediately.  
> Any opinion expressed in this email is personal to the sender and may not 
> reflect the opinion of the Press Association.
> Any email reply to this address may be subject to interception or monitoring 
> for operational reasons or for lawful business practices.
> 
> 
> _______________________________________________
> General mailing list
> [email protected]
> http://developer.marklogic.com/mailman/listinfo/general
> 

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

Reply via email to