incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron McCurry (JIRA)" <>
Subject [jira] [Commented] (BLUR-290) NRT Updates using RAMDirectory & Swap
Date Wed, 08 Jan 2014 12:51:51 GMT


Aaron McCurry commented on BLUR-290:

You make some good points.

1. In the TransactionRecorder there was a sync around the commit call and yes that plus the
sync around the WAL and for whatever reason the various syncs in the NRT code were playing
havoc with one another.

2.  Well the slow part of the commit is the internal sync that is has plus the sync call to
all the files on disk.  That sync to all the files on disk is what I have made to be almost

3. This is a great idea, if you extend the BlurIndex class and set the table property of "blur.shard.blurindex.class"
to equal your class you can try it out.  :-)

The basic reason I have done this is to make a rock solid implementation for the NRT piece
of Blur.  We can change and improve from here, we just needed a stable version to work from.


> 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