pbxt-discuss team mailing list archive

[MARK CALLAGHAN <mdcallag@xxxxxxxxx>]

On Sat, Oct 30, 2010 at 9:19 AM, Paul McCullagh
<paul.mccullagh@xxxxxxxxx> wrote:
> Hi Mark,
>
> What has happened here is the index cache is full of dirty pages, and needs
> to be flushed.
>
> When a thread hits this situation it starts a background thread to flush the
> indexes. That is why we have xt_wait_for_async_tasks() in the top-most stack
> trace.
>
> The background tasks are all busy flushing the indexes. One of the problems
> here is that indexes are actually synced to disk before anything can
> continue (although this is unnecessary for an import - but there is no way
> to tell PBXT that this is the case).
>
> Also, writing an index is "all-or-nothing" so since about 20 GB of index
> data is dirty it probably all has to be written.

These stacks occur long before the database files are 20G on disk.

-- 
Mark Callaghan
mdcallag@xxxxxxxxx