incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravikumar (JIRA)" <>
Subject [jira] [Commented] (BLUR-290) NRT Updates using RAMDirectory & Swap
Date Wed, 06 Nov 2013 04:20:18 GMT


Ravikumar commented on BLUR-290:

You have described the approach better. This is exactly what the patch aims to do.

I wrote some unit-tests and observed that when multiple threads are indexing, the "waitToBeVisible"
flag is increasing latency of writes.

One more issue is, NRTManager re-opens are really costly, as they involve 2 different IndexReaders
open at the same time. [Twice the memory, CPU etc...]. 

When we have N frequently changing IndexReaders [as in this case], re-opens are going to be
a real pain

> NRT Updates using RAMDirectory & Swap
> -------------------------------------
>                 Key: BLUR-290
>                 URL:
>             Project: Apache Blur
>          Issue Type: New Feature
>    Affects Versions: experimental-dev
>            Reporter: Ravikumar
>         Attachments:,,,,,,,,,,,,
> We have been discussing about handling humungous rows in Blur (BLUR-220). Explore the
idea of using RAMDirectory at the front, backed by persistent-index.

This message was sent by Atlassian JIRA

View raw message