Awesome, thanks. On Jul 28, 2014 5:06 AM, "David Lee" <[email protected]> wrote:
> This is a Debug level log so that itself is an indication that this is > not an issue but or even generally 'informative' for normal use (or it > would be a warning or higher). > > Its due to the metering collection and its indicating that enough memory > was used to that the in memory > > Index was flushed to disk. > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Geert Josten > *Sent:* Monday, July 28, 2014 6:32 AM > *To:* 'MarkLogic Developer Discussion' > *Subject:* Re: [MarkLogic Dev General] XDMP-INMTRPLIDXFULL > > > > Hi Harry, > > > > MarkLogics built-in history logging (the Meters database) is using > triples. So, nothing to immediately worry about. It might affect monitoring > though. I'd have to check what could be behind this.. > > > > Cheers, > > Geert > > > > *Van:* [email protected] [ > mailto:[email protected] > <[email protected]>] *Namens *Harry Bakken > *Verzonden:* maandag 28 juli 2014 12:08 > *Aan:* General MarkLogic Developer Discussion > *Onderwerp:* [MarkLogic Dev General] XDMP-INMTRPLIDXFULL > > > > I noticed similar log entries to this on our 7.0-3 cluster and I am not sure > if it is anything to be concerned with- > > > > 2014-07-28 00:23:00.812 Debug: Forest::insert: Meters XDMP-INMTRPLIDXFULL: > In-memory triple-index storage full; list: table=2%, wordsused=2%, > wordsfree=97%, overhead=1%; tree: table=1%, wordsused=11%, wordsfree=89%, > overhead=0% > > > > We aren't using any triple indexes in any of the databases on the system. Any > info/advice is appreciated. > > > > Harry > > > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general > >
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
