lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] [Commented] (SOLR-2700) transaction logging
Date Thu, 25 Aug 2011 14:20:28 GMT


Yonik Seeley commented on SOLR-2700:

bq. it seems you are doing blocking writes which might not be ideal here at all.

Yeah, I had eventually planned on concurrent writes... we're already doing concurrent reads,
which seemed more important.

bq. What we need to store in main memory is the offset and the length to do the realtime get

Right, that's what we're currently storing (just the offset).

bq. If not I think we should use a faster hand written serialization instead of java serialization
which is proven to be freaking slow.

"javabin" is misleading - it does not use Java serialization (and is both much faster and
more compact).

bq. Another totally different idea for the RT get is to spend more time on a RAM Reader that
is capable of doing exactSeeks on the anyway used BytesRefHash.

Yeah, but it seems like we'd still need the transaction log stuff anyway (for durability and
to helping a peer recover.)

> transaction logging
> -------------------
>                 Key: SOLR-2700
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Yonik Seeley
>         Attachments: SOLR-2700.patch, SOLR-2700.patch, SOLR-2700.patch, SOLR-2700.patch,
> A transaction log is needed for durability of updates, for a more performant realtime-get,
and for replaying updates to recovering peers.

This message is automatically generated by JIRA.
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message